Troubleshooting Group Policy in Windows Server2003
Guy Recommends
A solution to monitor, manage and archive thousands of
events that are generated by devices across the entire network. Download FREE
trial
Troubleshooting Group Policy Tips
I have distilled my troubleshooting tips for solving problems with Group
Policy on Windows Server 2003. My advice ranges from the obvious, gpupdate, to the obscure, spaces in policy names.
As an MCT trainer, I can thoroughly recommend TrainSignal because they
provide practical hands on training. In particular, I like the way TrainSignal cover all learning methods, instructor lead, video and of course text material. You can either take one module, for example Group Policy or go for
a combination of modules.
See more about Group Policy training here
Get into the troubleshooting state of mind
My first tip for troubleshooting Microsoft's Group Policy is this: Put yourself in the right frame of mind. Get into
'State' as Anthony Robbins would say. Believe that you are going to solve
this problem.
80% of all computer problems are caused by a simple fault. In the case of Group Policies, check that the user or computer is in the OU that you are testing. By default, all computers are in the
Computer folder. That means that if you set a policy at an OU, the computer settings will have no effect on any computers still in the original computers folder.
A variation of this problem is, that people do not realize that Windows Server 2003 Domain Controllers have their own special policy, again find the Domain Controller container and configure that default policy. I
would advise against moving the Domain Controllers into an OU.
So, if you logon as a user and none of your policy settings apply - check to
see that the user account is in the same OU as the policy you are testing.
Incidentally, when troubleshooting, this is why I always include one or two trivial computer settings along with
main user setting that
I am testing. If the trivial computer settings work, but the one I am testing
fails, then that pin points where the fault lies.
There are two factors in Group Policy synchronization. Active directory replication from the FSMO master to the other DCs. Also FRS (file replication services) replicating the very
group policies under the sysvol\sysvol folder.
Be ruthless, logon an as an administrator at the Windows 2003 server, which holds the FSMO PDC Emulator master and see if that cures the problem.
That depends! Most do. Gpupdate
/force refreshes the
policy instantly, however some policies require a reboot or a user to
logon again. For example, Software policies.
Hopefully, its just a DC replication delay.
Try and force domain replication in Active Directory Sites and Services,
drill down trough Server to NTDS and synchronise.
The script runs perfectly as a console user, but not as a logon script on a Workstation. Solution make sure that on the Workstation, the primary DNS server = Domain controller.
If necessary
set the DNS server manually rather than relying on DHCP
Run DcGpoFix to return the default Group Policies to their original state.
°
Troubleshooting
Group Policies is tricky
As an MCT trainer, I can thoroughly recommend TrainSignal because they
provide practical hands on training. In particular, I like the way TrainSignal cover all learning methods, instructor lead, video and of course text material. You can either take one module, for example Group Policy or go for
a combination of modules.
See more about Group Policy training here