Forcing Group Policy to Run at Startup
Group policy can be quirky in the way it runs at startup, often taking two or three reboots before it actually applies to a machine. Here we are going to look at the cause of this and how to fix it.
If you have ever done any work with group policy you may notice that it sometimes takes two or three reboots of a client computer before some policies take effect. This is pretty commonly seen with software installation and folder redirection policies more than any other. This delay is caused by a "feature" of Windows XP called "Fast Logon Optimization". This means that group policy is processed at the same time as when the processor is performing other tasks to get the computer booted up into a usable state.
The solution to this problem is disabling fast logon optimization with another GPO. You can find this setting under Computer Configuration\Administrative Templates\System\Logon. Here, you can enable "Always wait for the network at computer startup and logon". This could potentially increase the time it takes for your computers to log on, but it will also ensure that group policy gets its chance to be applied.
About this post
Posted: 2008-08-12
By: FortyPoundHead
Viewed: 1,843 times
Categories
Active Directory
Windows Server
Group Policy
Attachments
Loading Comments ...
Comments
No comments have been added for this post.
You must be logged in to make a comment.