This article has been archived. It is offered "as is" and will no longer be updated.
Consider 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 are not applied for a long time.
This 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.
This 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:
Microsoft Windows XP Professional, Microsoft Windows XP Home Edition, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86)