When you use the Group Policy Object Editor on a computer that is running Windows Server 2003 or Windows XP to change GPOs on a remote domain controller, the changes do not take affect for a long time (896669)
The information in this article applies to:
- Microsoft Windows XP Professional
- Microsoft Windows XP Home Edition
- Microsoft Windows Server 2003, Datacenter Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
SYMPTOMSConsider the following scenario: - You are using a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP.
- You use the Group Policy Object Editor to change Group Policy objects (GPOs) on a remote domain controller.
In this scenario, the changes do not take affect for a long time. CAUSEThis behavior occurs when the specified domain controller is not included in the Partition Knowledge Table (PKT) cache. The PKT cache stores only 35 target domain controllers per domain in the Distributed File System (DFS) list. If the target remote controller is not in the DFS list, the GPOs do not change immediately. The GPOs change only after the File Replication service (FRS) replicates the changes to the SYSVOL shared folders of the specified domain controller. WORKAROUNDThis issue may occur when the dfsutil /pktinfo command does not show the target domain controller in the DFS list. To work around this issue, use one of the following methods: - Log on to the target domain controller, and then change the GPOs locally by using terminal server.
-
Use the ntfrsutl forcerepl command to force replication regardless of the predefined replication schedule. This method applies only to the SYSVOL shared folders of the domain controller replica.
To force the FRS service to start a replication cycle, type the following command at a command prompt:
ntfrsutl forcerepl ComputerName /r "SetName" /p DnsName The quotation marks in this example are required when you use the /r option. If the quotation marks are not present, the command does not work.
Note- ComputerName is the name of the computer that is running the FRS service.
- SetName is the name of the replica set.
- DnsName is the name of the domain from which you force replication.
For example, type:
ntfrsutl forcerepl ComputerName /r "Domain system volume (SYSVOL share)" /p Source domain controller.domain.com
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 10/26/2005 |
---|
Keywords: | kbBug kbtshoot KB896669 kbAudITPRO |
---|
|