Topic Last Modified: 2010-02-15

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source

MSExchange ADAccess

Alert Type


Rule Path

Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access

Rule Name

The Configuration Domain Controller specified in the registry is not available.


This Warning event indicates that the computer specified in the Windows registry that must be used as a Configuration Domain Controller (CDC) cannot be reached. This situation can occur if one or more of the following conditions are true:

  • A registry key or server name is configured incorrectly. For example, you may have incorrectly spelled the name of the domain controller in the registry.

  • The computer specified in the event description has a network connectivity issue.

  • The domain controller specified in the event description is not running.

If the correct server name was specified, the specified server may be down or the network path may be down. Usually, if a configured domain controller is not reachable for any reason, Microsoft Exchange will select an appropriate CDC from the list of available domain controllers. Therefore, in most cases, this event can be ignored. However, if there is an accompanying MSExchangeDSAccess Event ID 2102, the Exchange services might not start. In this case, you must determine the basis of the problem and make sure that the domain controllers are reachable.

User Action

If the Exchange services start without any problems, you can safely ignore this warning. However, if the Exchange services do not start, do one or more of the following:

  • Make sure that the registry key and the server name are configured to use the correct values.

  • Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

  • Run the Dcdiag command-line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.