Monday, April 6, AM. Define it as a domain policy. It sounds like it is something you want for domain users. For things I want to apply to every machine in the domain, I put them into the default domain policy. Monday, April 6, PM. Hi, In addition to others. Wednesday, April 8, AM. For sure define it as a domain policy, but as a rule I don't screw with the default domain policy if, for no other reason, I don't apply the same policies to mobile devices, servers and workstations.
Do it at the OU level where you have placed all your workstations. 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:. The CSE that requires synchronous policy application can still be called during asynchronous policy application.
Instead of applying policy settings, the CSE signals for synchronous processing to be applied at the next startup or sign-in. When synchronous policy application is required and Fast Logon Optimization is enabled, it can take up to two reboots or two sign-ins for the policy settings to apply. This is demonstrated in the following examples.
In example 1, a user is not signed in to the client computer when a change is made to user policy settings, and synchronous processing is not requested.
In this case, the policy settings are applied after two sign-ins. In example 2 a user is signed in to the client computer when a change is made to user policy settings, and the user stays signed in to the computer so that background processing takes place prior to sign-out.
In this case, the policy settings are applied after one sign-in. These examples assume that only policy settings for a single CSE that requires synchronous processing have changed. You may find that the expected behavior for a single CSE varies when combined with the processing requirements of other CSEs. Example 1: Fast Logon Optimization with synchronous processing when the user is not signed in. In this example, the user is not signed in to the computer when there is a change to the user policy setting for a CSE that requires synchronous processing.
Synchronous processing was not requested when the user policy setting was last processed. In this example, it takes two sign-ins for the CSE to apply the policy settings. When the user signs in, Fast Logon Optimization is in effect and Group Policy processes asynchronously. This application of policy is similar to a background refresh and can reduce the time it takes for the logon dialog box to display and the length of time it takes for the shell to be available to the user.
Administrators can change the default by using the Group Policy Object Editor. Be aware that, under the listed conditions, a computer can start asynchronously. However, because logon is synchronous under these conditions, logon does not exhibit optimization.
Folder redirection and software installation policies. Be aware that when logon optimization is on , a user may need to log on to a computer twice before folder redirection policy and software installation policy are applied.
0コメント