We recommend that you leave the warning on the screen and that you do not click No in the Warning dialog box. Instead, manually check the SYSVOL replication.
After you verify that replication is working completely, click Yes in the Warning dialog box, and then let SBS Setup retry the operation.
After the Sysvol replication finishes, the Netlogon and Sysvol folders will be shared, and the new server will be considered to be a valid domain controller.
To manually check the SYSVOL replication, follow these steps:
- On the source server, restart the File Replication Service service. To do this, follow these steps.
Note The SYSVOL directory is being replicated from an existing domain controller to the new SBS. The domain controller is the source server.
- Click Start, type services, and then click Services under Programs.
- Right-click File Replication Service, and then click Restart.
- On the source server, open Event Viewer, and then view the File Replication Service event log. To open Event Viewer, click Start, type event viewer, and then click Event Viewer under Programs.
- In the File Replication Service event log, look for Event ID: 13568.
Note The most common cause of file replication failure is NTFRS Journal Wrap. If the source server experiences a Journal Wrap error, an event log entry that resembles the following will be logged:If the source server is in Journal Wrap, and the source server is the only functioning Domain Controller, follow these steps to set NTFRS on the source server as authoritative:
- On the source server, open Registry Editor. To do this, click Start, type regedit, and then click regedit under Programs.
- Expand the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
- In the right pane, double-click BurFlags.
- In the Value Data box, type D4, and then click OK.
- Exit Registry Editor.
- Open Services, and then restart the File Replication Service service.
- Check the File Replication Service event log for new errors.
If you have more than one working Domain Controller in the environment, follow the steps in the following Microsoft Knowledge Base article to resolve the NTFRS errors:
The second most common cause of NTFRS issues is connectivity or name resolution problems. In this case, the File Replication Service log will show an an Error event that resembles the following:To troubleshoot this issue, follow these steps:
- Click Start, click Run, type cmd in the Open box, and then click OK.
- Use the Ping command together with the internal fully qualified domain name (FQDN) of the source server to test the connection. To do this, run the following command:Ping<FQDN>Note In this command, <FQDN> represents the FQDN of your source server.
- Try to map a network drive to the sysvol share of the source server. To do this, run the following command:Net use * \\<Source_Server_Name>\sysvolNote In this command, <Source_Server_Name> represents the name of your source server.
- Check to make sure that no firewall programs on the source server are blocking RPC connectivity from the SBS 2011 Standard server.
- Open services.msc on the SBS 2011 server, and restart the File Replication Service service.
- Check the File Replication Service event log on the SBS 2011 server to see whether any errors occured.
Event ID: 13516
The File Replication Service is no longer preventing the computer CONTOSOSERVER 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.
For more information about the ping command, see the following Microsoft Technet topic:
Article ID: 2612832 - Last Review: Jul 12, 2013 - Revision: 1