The information in this article applies to:
SUMMARY
When a Group Policy Object (GPO) is changed by an administrator, the change takes place on a domain controller (typically the Windows 2000 domain controller holding the primary domain controller Flexible Single Master Operation [FSMO] role). The change is then replicated to other domain controllers through Active Directory and SYSVOL replication. At regular intervals, domain controllers and clients check for modifications to the GPOs. If any changes exist, they are applied. Q203607 How to Modify the Default Group Policy Refresh Interval MORE INFORMATIONTo trigger Group Policy application for the local computer, type the following line at a command prompt: secedit /refreshpolicy machine_policyTo trigger Group Policy application for the currently logged on user, type the following line at a command prompt: secedit /refreshpolicy user_policyNormally, if the GPOs that define the environment for the user have not changed from the last time Group Policy was applied, the GPO is skipped and not applied again. In either case, specifying "/ENFORCE" on the command line re-applies the policy even if the GPOs that apply to the computer or user have not changed. An example of the command line in this case is: secedit /refreshpolicy machine_policy /enforceAfter Windows 2000 has accepted the request, the following text should be displayed to the user: Group policy propagation from the domain has been initiated for this computer. It may take a few minutes for the propagation to complete and the new policy to take effect. Please check Application Log for errors, if any. Additional query words: kbfaqw2kds
Keywords : kbenv |
Last Reviewed: January 31, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |