We are having many problems with the health monitoring of exchange in our SCOM 2012 environment. We have 9 exchange servers, with 3 DAGS across the 9 servers. WE are constantly getting health events in SCOM, even for monitors i've explicitly disabled. For example, the FIPS monitor. Following this guide (http://blogs.technet.com/b/exchange/archive/2013/08/13/customizing-managed-availability.aspx) i disabled the FIPS probes/monitors all together across our entire Exchange environment, and yet in SCOM, all 9 servers show this monitor as being unhealthy. Is my understanding on this functionality incorrect, or is it just not functioning properly?

Similarly, even when an Exchange monitor is completely healthy, it shows as unhealthy in SCOM. Right now, HubTransport shows as unhealthy in SCOM For all our Exchange servers, but when i run this command everything shows as healthy, across all servers.

Get-ServerHealth <server name> | ?{$_.HealthSetName -eq "HubTransport"}

I understand that these monitors can be unhealthy for a while and correct themselves, but shouldn't that correct them in SCOM as well? And for disabled monitors, like FIPS, they should never be unhealthy at all. So why are they showing as unhealthy in SCOM? Am i expected to reset health in SCOM every time an unhealthy flag is thrown in Exchange?

From what i've seen there is a huge discrepancy between how SCOM works and how Exchange monitors work. They don't seem to integrate well, at all. Does anyone have any suggestions on getting Exchange 2013 monitors to work properly in SCOM? Is this my error as a user, or is it just bad software

Hi,

I recommend you use the Get-HealthReport cmdlet to check Exchange Server health again.

What's more, please verify if the account you use has the Organization Management permission and Server Management permission. Also, you can change an account and see the result.

Moreover, please take your time to post the unhealthy information from SCOM monitor about Exchange server for my further research.

Hope my clarification is helpful.

If there is any update, please feel free to let me know.

Best regards,
Amy

I have used the Get-HealthReport and all Monitors show as Healthy or Disabled. Right now i have 5 servers in SCOM that are red with the failure being HubTransport. All HubTransport monitors show healthy.

I'm certain my account has permissions, but the results are the same regardless of account.

Here is the output from SCOM.

http://pastebin.com/pYJGpWSn

We do have pretty much the same problem here.

One server for example shows completely healthy via "Get-ServerHealth" while it beeing listed as Critical in SCOM ("FrontendTransport"). But even worse Unhealthy components are listed as Healthy in SCOM - as it is just the state for the ActiveSyncCTPMonitor on one server right now.

This makes SCOM pretty much useless if I can't rely on the information shown there.