Check the Status of the SYSVOL and Netlogon Shares
Updated: April 25, 2011
Applies To: Windows Server 2008, Windows Server 2008 R2
You can use this procedure to make sure that the Distributed File System (DFS) Replication service is started properly and then ensure that the sysvol shared folder and netlogon (scripts) shared folder are created and shared.
For information about checking SYSVOL status for File Replication Service (FRS), see the Windows Server 2003 topic Check the status of the shared SYSVOL (http://go.microsoft.com/fwlink/?LinkId=120774).
Membership in Domain Admins, or equivalent, is required to complete this procedure. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).
On the Start menu, point to Administrative Tools, and then click Services.
Verify that the DFS Replication service and the Netlogon service have a status of Started. If a service is stopped, click Restart.
Open a Command Prompt as an administrator: On the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, provide Domain Admins credentials, if required, and then click Continue.
To verify that the SYSVOL tree includes the sysvol and scripts shared folders, at the command prompt, type the following command, and then press ENTER:
Check the list to be sure that it includes
%systemroot%\SYSVOL\sysvol\(the SYSVOL share) and
%systemroot%\SYSVOL\sysvol\<Domain Name>\SCRIPTS(the NETLOGON share), where
<Domain Name>is the domain of the new domain controller.
Note If neither
%systemroot%\SYSVOL\sysvol\<Domain Name>\SCRIPTSare present, see Verify Active Directory Replication.
Verify that the proper permissions are set for SYSVOL replication. At the command prompt, type the following command, and then press ENTER:
Look for a message that states that
<ComputerName> passed test NetLogons, where
<ComputerName>is the name of the domain controller. If you do not see the “passed test” message, check the permissions that are set on the Scripts and Sysvol shared folders. For information about default SYSVOL permissions, see Reapply Default SYSVOL Security Settings.