Windows 7 enable asynchronous group policy processing

It will start, perform its actions, and then stop. Group Policy processing overview Group Policy processing happens in two phases:. Note: The Group Policy architecture includes both server and client-side components. The server component includes the user interface GPEdit. When Group Policy is applied to a user or computer, the client component interprets the policy and makes the appropriate changes to the environment. These are known as Group Policy client-side extensions.

In troubleshooting a given extension's application of policy, the administrator can view the configuration parameters for that extension.

These parameters are in the form of registry values. There are two things to keep in mind:. This will require admin privileges for the computer side policies. If you do not have admin rights an old fashioned reboot should force policy to apply. Click Start , click Run , type regedit, and then click OK. On the Edit menu, point to New , and then click Key. In the Value data box, type Hexadecimal , and then click OK.

Exit Registry Editor. View the Gpsvc. In heavy logging scenarios, one of the writes attempts may fail and we may possibly lose debug log information.

To reduce the chance of lost logging while troubleshooting, initiate machine and user policy processing separately:. Here is an example:. GPSVC 31c. What are those? The second number is , which relates to the TID. One thing to consider: we will have two different threads for Machine and User GPO processing, so make sure you follow the correct one.

Synchronous vs Asynchronous Processing I will not spend a lot of time explaining this because there is a great post from the GP Team out there which explains this very well.

This is important to understand because it has a big impact on how settings are applied and when. Synchronous vs. The default foreground processing mode for Windows clients since Windows XP has been asynchronous. Asynchronous GP processing does not prevent the user from using their desktop while GP processing completes. For example, when the computer is starting up GP asynchronous processing starts to occur for the computer.

In the meantime, the user is presented the Windows logon prompt. Likewise, for asynchronous user processing, the user logs on and is presented with their desktop while GP finishes processing. There is no delay in getting either their logon prompt or their desktop during asynchronous GP processing. When foreground processing is synchronous, the user is not presented with the logon prompt until computer GP processing has completed after a system boot.

Likewise the user will not see their desktop at logon until user GP processing completes. This can have the effect of making the user feel like the system is running slow. To summarize, synchronous processing can impact startup time while asynchronous does not.

For computers, Group Policy is applied when the computer starts. For users, Group Policy is applied at log on. This initial processing of policy can also be referred to as a foreground policy application. The foreground application of Group Policy can be synchronous or asynchronous. In synchronous mode, the computer does not complete the system start until computer policy is applied successfully, and the user logon process does not complete until user policy is applied successfully.

If you disable or do not configure this policy setting detecting a slow network connection will not affect whether Group Policy processing will be synchronous or asynchronous. Skip to main content. Navigation Microsoft security bulletins. Windows event ID encyclopedia.