On servers running Windows Server 2008 or later, this policy setting is ignored during Group Policy processing at computer startup and Group Policy processing will be synchronous (these servers wait for the network to be initialized during computer startup). Group Policy is applied in the foreground, synchronously. If you enable this policy setting, computers wait for the network to be fully initialized before users are logged on. If a user has never logged on to this computer before, computers always wait for the network to be initialized. If a user with a roaming profile, home directory, or user object logon script logs on to a computer, computers always wait for the network to be initialized before logging the user on. In addition, changes that are made to the user object, such as adding a roaming profile path, home directory, or user object logon script, may take up to two logons to be detected.
Therefore, they must be processed in the foreground before users are actively using the computer. To be able to operate safely, these extensions require that no users be logged on. Note that because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logons to apply changes. Group Policy is applied in the background after the network becomes available. Existing users are logged on using cached credentials, which results in shorter logon times. By default, on client computers, Group Policy processing is not synchronous client computers typically do not wait for the network to be fully initialized at startup and logon. This policy setting determines whether Group Policy processing is synchronous (that is, whether computers wait for the network to be fully initialized during computer startup and user logon). ADMX_Logon policies ADMX_Logon/BlockUserFromShowingAccountDetailsOnSignin ADMX_Logon/DisableAcrylicBackgroundOnLogon ADMX_Logon/DisableExplorerRunLegacy_1 ADMX_Logon/DisableExplorerRunLegacy_2 ADMX_Logon/DisableExplorerRunOnceLegacy_1 ADMX_Logon/DisableExplorerRunOnceLegacy_2 ADMX_Logon/DisableStatusMessages ADMX_Logon/DontEnumerateConnectedUsers ADMX_Logon/NoWelcomeTips_1 ADMX_Logon/NoWelcomeTips_2 ADMX_Logon/Run_1 ADMX_Logon/Run_2 ADMX_Logon/SyncForegroundPolicy ADMX_Logon/UseOEMBackground ADMX_Logon/VerboseStatusĪDMX_Logon/BlockUserFromShowingAccountDetailsOnSignin Edition For more information, see CDATA Sections. To avoid encoding the payload, you can use CDATA if your MDM supports it. The payload of the SyncML must be XML-encoded for this XML encoding, there are a variety of online encoders that you can use.
For an example SyncML, refer to Enabling a policy. You must specify the data type in the SyncML as chr. For details, see Understanding ADMX-backed policies. These are ADMX-backed policies and require a special SyncML format to enable or disable.
0 kommentar(er)
