Article ID: 958804 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Symptom 1When you try to join a Windows Server 2003-based computer to a domain, the operation may not be successful. Additionally, you receive the following error message:
Domain Controller for this domain could not be contacted.
Symptom 2When you try to remove Active Directory from a domain controller in a Windows Server 2003-based computer in the same domain by using another domain controller, you may receive the following error message:
The check box that indicates that this domain controller is the last controller for the domain domain name is not selected. However no other Active Directory Controller for this domain can be contacted.
Symptom 3When you run the dcdiag.exe command prompt utility on a Windows Server 2003-based computer, the operation is unsuccessful. The following errors are logged:
This problem occurs because the domain controller that is present in the domain is not identifying itself as the domain controller. This indicates that the Sysvol and the Netlogon folders are not shared. This problem may occur when the policies and scripts that are stored in the %Windows%Sysvol\Sysvol\DomainName folder are not available.
The policies and scripts may not be available in the following scenarios.
Scenario 1The Policies and Scripts folders may be missing completely.
Scenario 2The Policies and Scripts folders may be present in the Ntfrs_Preexisting folder.
Scenario 3The Policies and Scripts folders are present. However, they are empty.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this problem, verify the following path for the Policies and Scripts folder:
%Windows%Sysvol\Sysvol\Domain NameFollow the steps, depending on the cause.
Resolution 3For both single domain controller setup and multiple domain controller environments, restore the Policies and Scripts folders from a valid backup.
For more information about how to rebuild Sysvol tree, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/315457/ )How to rebuild the SYSVOL tree and its content in a domain
You must be careful when you reinitialize the File Replication Service (FRS) database by setting the value to D4 or D2. If Distributed File System (DFS) is configured in the network, the reinitializing of the database will differ, depending on the replica sets.
For more information about BurFlag registry key, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/290762/ )Using the BurFlags registry key to reinitialize File Replication Service replica sets
Article ID: 958804 - Last Review: November 11, 2008 - Revision: 1.0