Domain Controller Override is set in the Registry_ConfigDCHostNameMismatch
Applies to: Exchange Server 2013
Topic Last Modified: 2012-06-05
The content in this topic hasn't been updated for Microsoft Exchange Server 2013. While it hasn't been updated yet, it may still be applicable to Exchange 2013. If you still need help, check out the community resources below.
Microsoft Exchange Server 2007 setup cannot continue because its attempt to use the specified domain controller failed. A domain controller has been statically mapped in the registry.
Exchange 2007 setup requires that the domain controller specified in the setup command match the domain controller that has been statically mapped using a registry override.
To resolve this issue, run setup again, specifying the statically mapped domain controller for the /DomainController: <FQDN of the statically mapped domain controller> parameter.
For more information about DSAccess and directory services detection, see Microsoft Knowledge Base article 250570, "Directory Service Server Detection and DSAccess Usage" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=250570).