You are currently offline, waiting for your internet to reconnect

Your browser is out-of-date

You need to update your browser to use the site.

Update to the latest version of Internet Explorer

Exchange Server 2013 restarts frequently after Cumulative Update 2 is installed

Assume that you have a server that is running Microsoft Exchange Server 2013 in a multiple domain or a parent/child Active Directory environment. After you install Exchange Server 2013 Cumulative Update 2, the server restarts frequently and displays an error message on a blue screen. These restarts are initiated by the ActiveDirectoryConnectivityConfigDCServerReboot Managed Availability responder.
This problem occurs because the ActiveDirectoryConnectivityConfigDCProbe probe incorrectly queries the domain controller (DC) of the child domain for the configuration DC of the root domain. Therefore, the probe fails and  ActiveDirectoryConnectivityConfigDCServerReboot starts the recovery activity.
To resolve this issue, install the following cumulative update: 
2892464 Description of Cumulative Update 3 for Exchange Server 2013
To work around this problem, follow these steps:
  1. Make sure that the server restarts are caused by the ActiveDirectoryConnectivityConfigDCServerReboot responder. To do this, run the following Windows PowerShell command on the affected Exchange server:
    (Get-WinEvent -LogName Microsoft-Exchange-ManagedAvailability/* | % {[XML]$_.toXml()}).event.userData.eventXml| ?{$_.ActionID -like "*ForceReboot*"} | ft RequesterName
    You can also search the crimson channel logs that are named “Recovery Action Logs” and “Remote Action Logs” for a “ForceReboot” entry to determine which responder is causing the restarts.
  2. After you verify that the ActiveDirectoryConnectivityConfigDCServerReboot responder is causing reboots, create either a time-bound or version-bound global override to disable the responder.

    To create a time-bound override, run the following command to disable the responder for 60 days starting on the date of creation:
    Add-GlobalMonitoringOverride -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
    To create a version-bound override, run the following command for servers that have Exchange Server 2013 with CU2 version 712.24 installed:
    Add-GlobalMonitoringOverride -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -ApplyVersion “15.0.712.24”
    • In the version-bound override command, the ApplyVersion parameter maintains the override until the installed version number of Exchange Server changes.
    • The global override is first created by Active Directory replication, and then it is read by the Microsoft Exchange Health Manager Service.
    • If you have multiple domain controllers, force or wait for Active Directory replication to begin. After the data is replicated, the Microsoft Exchange Health Manager Service should detect the changes that are created by the override and make the changes effective within 10 minutes.
  3. Make sure that the override that you have created is effective. To do this, run the following command to verify that the responder is disabled:
    (Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot"} | ft name,enabled

    If the responder is disabled, the Enabled property value will be 0 (zero). The following is an example of command output that shows a disabled responder.

    disabled responder
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 2883203 - Last Review: 11/25/2013 23:56:00 - Revision: 4.0

  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • kbqfe kbfix kbsurveynew kbexpertiseadvanced kbgraphxlink KB2883203