Export (0) Print
Expand All
Expand Minimize

This Exchange cluster node is also a domain controller

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the Microsoft Windows® Management Instrumentation (WMI) object (Win32_ComputerSystem class) to determine the DomainRole value for the server. The DomainRole value represents the role of a computer in a domain. The table that follows lists the valid values for DomainRole.

 

Value Meaning

0

Stand-alone workstation

1

Member workstation

2

Stand-alone server

3

Member server

4

Backup domain controller

5

Primary domain controller

In addition, the Exchange Server Analyzer queries the ClusSvc WMI object (Windows Cluster Service object, Win32_Service class) to determine its Started value. A value of True indicates the Cluster service is started and a value of False indicates the service is not started.

If the Exchange Server Analyzer determines that the value for the DomainRole value is greater that 3 on an Exchange Server computer where the Cluster service is started, an error is displayed. This error indicates that an Exchange server is running in a Windows server cluster whose nodes are domain controllers.

Running an Exchange Server cluster node as a domain controller is not a supported configuration.

  1. Choose a non-cluster server to act as the domain controller, and run the Active Directory Installation Wizard (dcpromo) to promote that server.

  2. After the Active Directory® directory service has been configured on the new domain controller, wait for the existing Active Directory content to replicate to the new server.

    Depending on the size of Active Directory, this operation could take several hours.

  3. Run the Active Directory Installation Wizard (dcpromo) on the cluster server to demote the server and remove Active Directory.

For more information about promoting and demoting domain controllers, see the Microsoft Knowledge Base article 238369, "How To Promote and Demote Domain Controllers in Windows 2000" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=238369).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft