Configure managed availability overrides
Applies to: Exchange Server 2013 SP1, Exchange Server 2013, Exchange Online
Topic Last Modified: 2013-11-15
Managed availability performs continuous probing to detect possible problems with Exchange components or their dependencies, and it performs recovery actions to make sure the end user experience is not impacted due to a problem with any of these components. However, there may be scenarios where the out-of-box settings may not be suitable for your environment. Managed availability probes, monitors and responders can be customized by creating an override.
There are two types of overrides: local and global. As their names imply, a local override is available only on the server on which it is created, and a global override is used to apply an override to multiple servers. Either type of override can be created for a specific duration or for a specific version of servers.
|When you create an override, it does not take effect immediately. The Microsoft Exchange Health Management service checks for configuration changes every 10 minutes and loads any detected configuration changes. Alternatively, you can restart the service to make the override changes effective immediately.|
For additional management tasks related to managed availability, see Manage health sets and server health.
Estimated time to complete each procedure: 1 minute
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
The following example shows how to create server-specific local overrides using the Shell.
Use the Add-ServerMonitoringOverride cmdlet to create a server-specific local override.
Add-ServerMonitoringOverride -Server ServerName -Identity <ItemtoOverride> -ItemType <ItemType> -PropertyName <PropertyName> -PropertyValue <Value> -Duration <DurationofOverride>
When using the ServerMonitoringOverride cmdlets, the Identity is in the form of HealthSetName\MonitoringItemName\TargetResource (for example, FrontEndTransport\OnPremisesInboundProxy or DataProtection\ServiceHealthMSExchangeReplEndpointEscalate\<ServerName>).
The following example shows how to remove a server-specific local override using the Shell.
The following example shows how to create a global override using the Shell.
Use the Add-GlobalMonitoringOverride cmdlet to create a global override.
Add-GlobalMonitoringOverride -Identity <ItemtoOverride> -ItemType <ItemType> -PropertyName <PropertytoOverride> -PropertyValue <NewPropertyValue>
You can also create a global override that applies to a specific version of Exchange and/or for a specific time duration.
Add-GlobalMonitoringOverride -Identity <ItemtoOverride> -ItemType <ItemType> -PropertyName <PropertytoOverride> -PropertyValue <NewPropertyValue> -ApplyVersion <ExchangeVersion> -Duration 45.00:00:00
The following example shows how to remove a global override using the Shell.