On a Windows 2000 or Windows 2003 domain, I am testing out various group policies. As I understand it, domain controllers should only take 15 minutes to sync if they are all local to each other (and you can force them to sync through the snapin for Sites and Services). However, it always takes much longer than this (2 hours?) before my new group policies ever seem to be applied.
How can I speed this up so I can test in a timely manner?!
For some reason the gpupdate /force doesn't seem to help. Part of what I am testing is a logon script in the GPO. I can run the gpupdate /force, and it says it does something, then log off/on, but the script still won't run. Any ideas?
What you are doing through Sites and Services is forcing a replication of Active Directory data between the Domain Controllers. This means all DCs are updated with the new Group Policy settings in their Active Directory databases, but the policies won't actually have applied to the DCs at this stage.
To apply the policies, you then need to issue the command gpupdate (with an optional /force switch) which will resync the policies on the DCs from Active Directory.
According to gpresult and rsop.msc the policy is being applied, but the script still hasn't run (I have a pause in it so I see it even if it were to fail for some reason). I've done this before, and after several hours it always works. I have the script under the logon section under the User Config part of the Policy like I usually do.
I tried a reboot twice but didn't seem to help. I'm about to try it again now that it's been a while. After that I'll start testing on another user... still a mystery to me.
Reality check... if I have the script under the User Config... is there any reason to have the actual computer in that OU? Because I only have the user in the OU, not the computer. Please don't tell me that is the problem. :(
No - the script is in User Config, so applies to User objects. Having the computer in the OU will only have an effect if you have set policies in Computer Configuration.
Check it out... I found this error. I first map a drive (it's not appearing) and then run a very slow install. The install may be over 10 minutes, so that may be triggering it.
error in eventvwr:
Execution of GPO scripts has timed out and have been terminated.
That definitely looks like it is the issue. The drive would only get mapped if it was done before the software installation begin. If GPO processing timed out before any of your scripts or drive mappings were processed, it won't get mapped.
Try running the login script alone on a seperate GPO above the one that creates issues. That will figure out whether your login scripts are working, which was the initial question.
I have 10 GPOs applied to this particular user, and I'm wondering if I need to trim that down. I'll keep playing with it.
I'm going to go ahead and give y'all your points before this goes off on another tangent. Thanks a ton. If I have a new question I'll post it separately.
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.