ICTCity

Sorry, I can't understand.

I think you must do something with rundll32 but actually I don't know how. Are you doing a contest? :D

Hi, First of all do the following: Open GP management and run a RESULTANT GROUP POLICY, specify the policy and a computer. When done, check the results, there's a section called "Applied GP" and "Deny GP", chech if that policy has been applied correctly or not.

IF I can understand your question... the answer is yes. You can RDP (remote desktop) into your DC and make any test you want.

If you want to continue / share your ideas, feel free to do it. I'm really interested in this topic. I can't find people which are really interested in discovery how things work, just "use and wait until disaster". If you want... I'm here :)

you could try to rewrite you MBR with a linux live cd or with bart pe... But I'm quite sure it will not work...

I had a similar problem and was caused by a restore from an image of another system. It's like Windows cannot read the bootloader anymore... you could try to reach the page where you can run bcdedit and so on, and let windows try to fix for you (there's an option, but I can't remember how it's called).

You MUST use DOMAIN ADMIN: my.local.domain\Administrator password Saad now is a LOCAL admin.

you're welcome :)

Saad is a member of DOMAIN ADMIN? What does: "In Server Manager the DNS server has turned to an i but the Domain Services is a triangle with a ! in it." mean? Can you post a screen shot?

Raid 1 is useful but not the best solution. The point is everytime the same... people confuse HA with DR. Raid 1 provide a COPY of disk, so you can access your disk (even if one is failed), but this doesn't mean you can keep working without problems. One your system is up and running, I usually take a full backup for the entire system. Then, day per day, a normal backup. In case of a disaster, you can rebuild your array (as described in previous post) from the image. I know this is disappointing, That's because I rely on RAID5 instead of RAID1 (which actually is the same process of raid one in some way, but it can rebuild everything from just 2 disks, there's no principal disk).

Usually I do the following: Share permissions: domain users: full control (root folder, and sub folders). Then, NTFS permissions to prevent access to some users, but basically share permissions are full control to "everyone".

Are there any apps which are related to DCOM? (Fax service...) If so, contact the vendor.

So that's correct! If you have READ ONLY in share permissions, you can only READ. Set full control to share permissions and then change the NTFS permissions according to your needs.

This looks like the share, not the path itself. Try to map the full path, just to test it. \\IP\Full\Path\ShareA

Is your user member of another group? If you run "net use" on cmd when logged in as user, what's the output?

On the advanced screen, select EFFECTIVE PERMISSION tab and add your user, then check if there he has full control or not.

Here's the point. Right click the "one" folder > properties > security > advanced > Change permissions and UNTICK "Include inheritable permissions...". Let me know!

Hi, I think your problem has been caused by different hardware, so my solution is just a reinstallation...

It's hard to say... Join the pc to domain, then try to ping the pop name and see if you have the correct IP. If not, insert a static entry into DNS. You can also do the following: Join domain On one client open the CMD and type: ipconfig /flushdns Open outlook and wait until the error. Open CMD and type: ipconfig /displaydns >Result.txt Post the Result.txt file.

reinstall windows server 2008, this is a critical error.

To join a domain, you must have the permissions to do that. By default Admins have this right.

when you type the username (must have the permission to join domain), write something like this: username = Admin_user@my.domain.local it should resolve your issue.

Basically a NON shared drive is not writeable to domain users unless you express something else. I think that local admin and local users (and domain admin) can write on that disk, but the others no. You can always specify something else :)

The only way is to use a script (power shell or VBS). Check the extension, then set permissions.