Article ID: 2742959 - View products that this article applies to.
You use the Virtualized Domain Controller (VDC) cloning feature that is introduced in Windows Server 2012. After you clone a new domain controller, you find that the server starts in Directory Services Repair Mode (DSRM). Additionally, when you examine the Directory Services event log on the cloned domain controller, you find an event that resembles the following:
Log Name: Directory Service
You verify that the clone computer belongs to the Cloneable Domain Controllers group.
One of the following issues occurred:
To resolve this issue, set the correct computer name in DcCloneConfig.xml. When you do this, follow these guidelines:
After you set the correct computer name in DcCloneConfig.xml, follow these steps:
This behavior is by design.
You can also use clone domain controller names that are auto-generated. Such names are created when you do not specify a <ComputerName> element in the DcCloneConfig.xml. This automated process assigns a new computer name that is created by using first seven characters of the source computer, a hyphen, the letters "CL," and an incrementing number from 0001 to 9999.
For example, a source server that is named DCcohovineyard can have the following clone domain controller name that is auto-generated:
DCcohov-CL0001Note Directory Services Repair Mode was called Directory Services Restore Mode in previous Windows operating systems.
For more information about how to configure and troubleshoot VDC together with details and step-by-step guidance, see the following articles:
http://technet.microsoft.com/en-us/library/hh831734.aspxFor more information about rules for valid NetBIOS computer names, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/909264/ )Naming conventions in Active Directory for computers, domains, sites, and OUs
Article ID: 2742959 - Last Review: September 18, 2012 - Revision: 12.0