Using the BurFlags Registry key to rebuild the sysvol share
This week a customer’s domain controller had a stale sysvol share and ntfrs events in the registry were showing problems replicating.
After researching the issue we found this Microsoft KB article;
http://support.microsoft.com/kb/290762
We decided on doing a non-authoritative restore. After modifying the registry key and restarting the ntfrs service - voila! Problem Solved!
Let’s review the event log as this process re-builds the sysvol replica.
1. First, during the syncrhonization the server is prevented from being a domain control until is in sync.
2. Next, existing sysvol files on the stale domain controller are moved from the sysvol replica folder
3. the replica configuration is being reset
4. File replication service has added connections to the operations master to replicate the domain sysvol share
5. the process has completed and the server can again be an active domain controller
