Group policy logon optimization is in effect windows 7

->>>> Click Here to Download <<<<<<<-

Get new features first. A subscription to make the most of your time. Try 1 month free. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon.

Pictures helped. Didn't match my screen. At sign-in A user does not have to wait for Group Policy to finish processing before signing in. To keep this from happening, the CSE is designed to require synchronous processing to apply the new settings.

During asynchronous processing, the CSE signals the system to indicate that a synchronous application of Group Policy is required. Group Policy foreground processing applies when the computer starts or shuts down and when the user signs in or signs out. During foreground processing, policy settings can be applied asynchronously or synchronously. Group Policy background processing applies during periodic refreshes after the computer has started or a user has signed in.

During background processing, policy settings are only applied asynchronously. When Group Policy processes on a Windows-based computer, client-side extensions interpret the stored policy settings and make the appropriate changes to the environment.

These parameters are in the form of registry values. This section provides an overview about the information that is stored in the registry. This is for informational purposes, and it is not recommended that you adjust the CSE processing properties by using the registry.

Serious problems might occur if you modify the registry incorrectly. If you do make any changes to the registry, it is recommended that you back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see article in the Microsoft Knowledge Base. For more information about identifying registered Group Policy client-side extensions, see article in the Microsoft Knowledge Base.

If this value is set to 1, the CSE will not be called during background processing. A CSE that requires synchronous processing can still be called during background processing. However, because background processing is always performed in asynchronous mode, a CSE that requires synchronous processing exits after signaling a request for the next sign-in to be run in synchronous mode.

Each CSE determines if it requires synchronous processing to apply changes to the policy settings. The following table provides information about the synchronous processing requirements and the default background processing behavior of CSEs in Group Policy.

In Windows 7 and later versions, as well as Windows Server R2 and later versions, startup scripts run asynchronously by default. In earlier versions of Windows, startup scripts run synchronously by default. Although the requirement to run a client-side extension in synchronous mode is not configurable, other default behavior for each CSE can be configured through policy settings.

To configure the properties that are associated with a CSE, apply the Administrative Templates computer configuration policy settings that are created for this purpose. The following table provides the names of the policy settings and the CSE properties that can be modified. By default in Windows 8.

Policy settings apply asynchronously when the computer starts and when the user signs in. As a result, these operating systems do not wait for the network to be fully initialized at startup and sign-in. Existing users are signed in by using cached credentials. This results in shorter sign-in times. Group Policy is applied after the network becomes available. Under the preceding conditions, computer startup can still be asynchronous.

However, because sign-in is synchronous under these conditions, sign-in does not exhibit optimization. When a CSE requires synchronous processing:. I have a Windows TS server that uses folder redirection group policy to redirect all user's folders to a file server. I have been seeing the warning event appearing on the application log on TS server and here is what it says: "Folder redirection policy application has been delayed until the next logon because the group policy logon optimization is in effect.

The problem I have is that I keep seeing that event appearing. In the mean time I can confirm all user's folders were redirected properly to the server shares, users have been accessing the redirection locations fine without problem. Turned on the folder redirection debug logging by using the registry suggested by Microsoft does give me a lot more details about the application but nothing indicates problem somewhere, all I can see from the details logs are informative.

Join our community to see this answer! Unlock 1 Answer and 8 Comments. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial.

What do I get with a subscription?