Exchange Connection Problems

Fix Unhealthy Exchange Server 2016 Health Sets

Nimra MalikNimra Malik Nov 13, 2026 869 views

Question details

Identify and resolve the cause of unhealthy Managed Availability health sets in Exchange Server 2016.

Fix Unhealthy Exchange Server 2016 Health Sets
Product
Microsoft Exchange Server 2016
Device & OS
not provided
Scenario
An administrator is checking health sets for Outlook MAPI/HTTP, Outlook RPC, or archive connectivity on an on-premises Exchange server.
Observed behavior
One or more health sets report an Unhealthy status after a monitor or probe fails or triggers recovery.
Before you start

Identify the affected Exchange server and health-set name, and open the Exchange Management Shell with an account authorized to view server health. Record when the alert occurred so you can match it to event logs.

Solution 1Recommended

Investigate the affected Managed Availability health set

Use this approach to identify the failing monitor and check the services and connections it depends on.

1
Find the unhealthy monitor

In Exchange Management Shell, run Get-ServerHealth -Identity <ServerName> | Where-Object {$_.HealthSetName -eq '<HealthSetName>'} | Format-List *. Replace the placeholders with the affected server and health-set names, then note the unhealthy monitor and its details.

2
Review monitoring events

Open Event Viewer and look under Applications and Services Logs for Exchange ActiveMonitoring events around the alert time. Review the related probe, monitor, and responder results for errors and recovery actions.

3
Check component and service state

In Exchange Management Shell, run Get-ServerComponentState -Identity <ServerName>. In Services, check that the services relevant to the failing monitor are running; investigate any inactive component before changing its state.

4
Verify the affected connection

For MAPI/HTTP or Outlook RPC issues, inspect the relevant configuration with Get-MapiVirtualDirectory -Server <ServerName> or Get-OutlookAnywhere -Server <ServerName>. Check the reported endpoint, authentication, certificates, and network path. For archive alerts, check the connectivity path named in the probe error.

5
Recheck health

After addressing the specific error, run Get-ServerHealth -Identity <ServerName> again and allow time for monitoring to update. If the health set remains unhealthy, consult Microsoft's Managed Availability and health-set documentation or the Exchange Server support community with the monitor and event details.

Investigate the affected Managed Availability health set
Interpret the alert in context: An unhealthy status identifies a monitoring problem, not necessarily its root cause. Use the probe and event details before changing configuration or restarting services.
Free Microsoft Office alternative

Work with Office files using WPS Office

WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easier to move existing files. It does not diagnose or repair Exchange Server health sets.

Open and edit Word, Excel, and PowerPoint files, including DOCX, XLSX, and PPTX formatsUse a familiar interface to work with existing Office filesKeep server troubleshooting separate from everyday document workUse a free, lightweight office suite
QA img-9

Frequently Asked Questions

What does an unhealthy Exchange health set mean?

It means a Managed Availability monitor has reported an unhealthy condition, often because a probe failed. Inspect the monitor and associated events to determine the underlying cause.

How can I see the monitors in a health set?

In Exchange Management Shell, run Get-ServerHealth -Identity <ServerName> | Where-Object {$_.HealthSetName -eq '<HealthSetName>'} | Format-List *, replacing both placeholders with your values.

Where can I find details about a failed probe?

Open Event Viewer and check the Exchange ActiveMonitoring logs under Applications and Services Logs. Look for probe, monitor, and responder events near the time of the alert.

Does an unhealthy Outlook health set always mean the virtual directory is misconfigured?

No. The cause can also involve services, authentication, certificates, network connectivity, or another dependency. Check the failing probe's error before changing the virtual directory.