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:
To use the Group Policy Object Editor to modify a GPO on a remote domain controller, follow these steps:
- Click Start, click Run, type dsa.msc, and then click OK.
- Click Active Directory Users and Computers DomainName, and then click Connect to Domain Controller on the Active menu.
- Type the target domain name in the Enter the name of another domain controller box, and then click OK.
- Click Start, click Run, type gpedit.msc, and then click OK.
- On the View menu, click DC Option.
- Click The one used by the Active Directory Snap-Ins, and then click OK.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.