You must designate one domain controller as being authoritative for the Sysvol replica set. If all of the domain controllers in the domain have been restored, select the primary domain controller emulator flexible single master operations (FSMO) role holder:
- Stop the File Replication service on the domain controller.
- Start Registry Editor (Regedt32.exe).
- Locate and then click the BurFlags value under the following key in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
- On the Edit menu, click DWORD, click Hex, type D4, and then click OK.
- Quit Registry Editor.
- Move data out of the PreExisting folder.
- Restart the File Replication Service.
When you set the D4 registry setting on one domain controller, you must set the D2 registry setting on every other domain controller. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
If you restore all of the domain controllers in the domain backup, all the domain controllers enter the seeding state for FRS and try to synchronize with an online replica. This replication does not occur because all of the domain controllers are in the same seeding state. Setting the primary domain controller FSMO role holder to be authoritative forces the domain controller to rebuild its database based on the current contents of the system volume. When that task is completed, the Sysvol and Netlogon shares are shared. All the other domain controllers can then start synchronizing from the online replica.
Article ID: 316790 - Last Review: Dec 16, 2009 - Revision: 1