Article ID: 316826 - View products that this article applies to.
This article was previously published under Q316826
When you use the File Replication Service (FRS) to replicate SYSVOL content throughout an enterprise, the replication of SYSVOL may not work.
This issue may occur if a new domain controller in the forest uses the original computer name of a renamed domain controller.
During promotion, the Active Directory installation wizard creates objects in Active Directory based on the domain controller's current NetBIOS computer name. The NTFRSmember object that the File Replication service (FRS) uses to replicate the contents of SYSVOL between domain controllers in the same domain is an example of such an object. Similarly, enabling the FRS replication of a Distributed File System (DFS) root or link in the DFS snap-in (Dfsgui.msc) creates NTFRSmember objects, but its NTFRSMember object uses a "rename-safe" alpha-numeric GUID.
In Windows Server 2003, administrators can change the computer name of a Windows Server 2003 domain controller by using My Computer or Netdom.exe, but neither method renames the domain controller's corresponding NTFRSmember object for SYSVOL from the old computer name to the new computer name.
The difference between a domain controller's NetBIOS name and the common name for its NTFRSmember object does not break any functionality until a new domain controller is promoted into the forest with the old NetBIOS name of the renamed domain controller. When this behavior occurs, the new domain controller deletes the existing (duplicate) NTFRSmember object and recreates a new NTFRSmember object for itself. The renamed domain controller that originally created the NTFRSMember object ends up without an NTFRSmember object.
When they rename the computer name of a Windows Server 2003 domain controller, administrators must also rename the NTFRSMember object for the SYSVOL replica set. There are two benefits to updating the NTFRSMember object to match the domain controller's new computer name:
(http://support.microsoft.com/kb/325379/EN-US/ )How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003
To resolve this issue, for each Windows Sever 2003 domain controller whose computer name (the first label of the computer's DNS name) is being renamed, update the computer name of the SYSVOL NTFRSmember object. To do so, follow these steps:
Article ID: 316826 - Last Review: December 3, 2007 - Revision: 5.3