Restoring and Rebuilding SYSVOL
Applies To: Windows Server 2008, Windows Server 2008 R2
A domain controller cannot function without a properly shared and replicating SYSVOL. If your efforts to move SYSVOL or perform certain maintenance tasks fail and SYSVOL is not replicating, you must recreate (rebuild) SYSVOL on the domain controller. Attempt to rebuild SYSVOL on a domain controller only when all other domain controllers in the domain have a healthy and functioning SYSVOL. Do not attempt to rebuild SYSVOL until you correct any problems that may be occurring with Distributed File System (DFS) Replication in a domain.
Use the procedures in this section only on a domain controller that does not have a functioning SYSVOL.
The following tools are required to perform the procedures for this task:
Active Directory Sites and Services
To complete this task, perform the following procedures in order:
You will import the SYSVOL from a replication partner.
Perform this procedure on the replication partner from which you are copying SYSVOL to make sure that the SYSVOL tree that you copy from the partner is shared and replicating properly.
Verify that replication is working on both replication partners.
Restart the domain controller in Directory Services Restore Mode (DSRM) by using one of the following methods:
If you are sitting at the console of the domain controller, restart the domain controller locally in DSRM.
If you are accessing the domain controller remotely using Remote Desktop Connection, restart the domain controller remotely in DSRM.
In DSRM, the DFS Replication service is stopped automatically. You have to stop only the Netlogon service. Both services restart automatically when you restart the domain controller normally after you complete the procedure to import the SYSVOL folder structure.