Exchange Health Manager has restarted a server even though a Global Monitor Override was in place.

Scenario:  You have a GlobalMonitoringOverride configured to prevent the reboot of an Exchange Server for a specific Exchange Health Monitor responder, but MSExchangeHMWo still rebooted the server anyways.   In our example below, we have an existing global monitor override that should prevent reboots for the responder "ActiveDirectoryConnectivityConfigDCServerReboot". 

Cause:   The globalmonitoringoverride had an expiration date for 60 days after it was set.

Resolution: Remove the existing GlobalMonitoringOverride and replace it.

step 1 - View the current globalmonitoringoverride

get-globalmonitoringoverride

  
step 2 - View the log file associated with the reboot for the Repsonder

(Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot"} | ft name,enabled

 step 3 (only if you have override setup already)


remove-GlobalMonitoringOverride -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled  

   
Step 4  - Apply Either of the options below.

Apply based on duration of 60 days

Add-GlobalMonitoringOverride -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00

Apply based on Exchange version


Add-GlobalMonitoringOverride -Identity AD\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 –ApplyVersion "15.00.0847.32"
  
Step 5 - Restart the "Microsoft Exchange Health Manager" service