This article helped me out today while fixing a broken Active Directory on a SBS 2003 system I was recoverying from backup.

You will find that your SYSVOL and NETLOGON shares are missing. To reconfigure these manually can be a task in itself. The below article shows a much easier way for creating these shares.

Short Link:

If you have a domain controller and the SYSVOL is missing you will be getting the following error in your logs:Event Type: ErrorEvent Source: UserenvEvent Category: NoneEvent ID: 1006Date: 22/02/2010 Time: 6:01:40 PMUser: NT AUTHORITY\SYSTEMComputer: ORION2\Description:Windows cannot bind to domain. (Local Error). Group Policy processing aborted. 
To get this fixed copy the SYSVOL folder of a healthy domain controller manually. To get the domain controller to re-establish the shares properally and publish it under the domain namespace theres a trick to this which I will show you. 
Navigate to the following registry key on the domain controller you just copied the SYSVOL to:HKLM\SYSTEM\CurrentControlSet\Services\Ntfrs\Parameters\Backup/Restore\Process at StartupSet the value of the BurFlags registry entry to D4(Hex).Restart the File Replication Service (Ntfrs) serviceThe DC will now automatically share the SYSVOL and republish it under the domain namespace. Very handy!


  1. Thanks a lot! It saved me a lot of hours of work recovering a broken AD forest.


Post a Comment

Popular posts from this blog

Office 365 ScanPST to fix corrupted Outlook files

Deleting Office 365 Tenant

PowerShell: Download and Install Java 8 JRE