Nichewares & Consulting, LLC

1.Shut down the File Replication Service on all domain controllers.

2.On PDC, go into the C:\WINNT\SYSVOL\sysvol\example.com directory and clean up the files that you want to have replicated across to the other domain controllers.

3.Set the BurFlags registry key to d2 Hex under the following registry location using regedt32 for each of the remote domain controllers and d4 hex for the authoritative replication server. This resets the server to reinitialize the File Replication process. Before changing this key, verify that the File Replication Service is stopped on all domain controllers.:

a.\\HKey_Local_Machine\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process

4.After setting the registry key, start the File Replication Service on authoritative server and wait for Event IDs 13553 and 13516 to be logged in the File Replication event logs. Once authoritative server registers these events, restart the File Replication services on all remote domain controllers.

5.Opened up the Event viewer and was looking for the following events to verify that the File Replication Service was working correctly. When you receive event log with Event ID: 13516, then the File Replication is working correctly:


a.first event log - Warning - Event ID: 13515 - "The File Replication Service may be preventing the computer AUTHORITATIVE_SERVER from becoming a domain controller while the system volume is being initialized and then shared as SYSVOL"

b.second event log - Information - Event ID: 13553 - "The File Replication Service successfully added this computer to the following replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"


c.third event log - Information - Event ID: 13554 - "The File Replication Service successfully added the connections shown below to the replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

d.fourth event log - Information - Event ID: 13516 - "The File Replication Service is no longer preventing the computer AUTHORITATIVE_SERVER from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL."


6.Verify that the replication of the files are consistent between the remote file servers and authoritative server.