Dear Support

I would like to healthy check Exchange 2013 cu5 environment, show below unhealthy status. The health alert value of 'Compliance' is 'Unhealthy', that may cause some special unhealthy state of the server. an couple of Exchange server with roles CAS + MBX + DAG, only one issued server has this symptoms. no ForeFront in edge. How can I improve this status? 


RunspaceId              : a941d0bc-ce79-4918-94c6-5958b9e5d1e8
Server                  : meg1dcex01
State                   : NotApplicable
HealthSet               : Compliance
HealthGroup             : CustomerTouchPoints
AlertValue              : Unhealthy
LastTransitionTime      : 8/9/2014 11:32:45 AM
MonitorCount            : 9
HaImpactingMonitorCount : 0
Entries                 : {AuditLogSearchCompletedWithErrorsMonitor, AsyncSearchServiceletRunningMonitor, 
                          MailboxSearch.InconsistentItemReferenceErrorMonitor, MailboxSearch.RPCFailureEvents.Monitor, 
                          MaintenanceFailureMonitor.Compliance, MaintenanceTimeoutMonitor.Compliance, 
                          JournanlingMonitor, ComplianceOutlookLogonToArchiveRpcCtpMonitor, 
                          ComplianceOutlookLogonToArchiveMapiHttpCtpMonitor}
Identity                : Compliance\meg1dcex01
IsValid                 : True
ObjectState             : New

RunspaceId              : a941d0bc-ce79-4918-94c6-5958b9e5d1e8
Server                  : meg1dcex01
State                   : NotApplicable
HealthSet               : FEP
HealthGroup             : ServiceComponents
AlertValue              : Unhealthy
LastTransitionTime      : 8/9/2014 11:31:53 AM
MonitorCount            : 2
HaImpactingMonitorCount : 0
Entries                 : {MaintenanceFailureMonitor.FEP, MaintenanceTimeoutMonitor.FEP}
Identity                : FEP\meg1dcex01
IsValid                 : True
ObjectState             : New

RunspaceId              : a941d0bc-ce79-4918-94c6-5958b9e5d1e8
Server                  : meg1dcex01
State                   : NotApplicable
HealthSet               : OWA.Protocol.Dep
HealthGroup             : KeyDependencies
AlertValue              : Unhealthy
LastTransitionTime      : 8/11/2014 8:01:57 AM
MonitorCount            : 2
HaImpactingMonitorCount : 0
Entries                 : {OwaIMInitializationFailedMonitor, WacDiscoveryFailureEventMonitor}
Identity                : OWA.Protocol.Dep\meg1dcex01
IsValid                 : True
ObjectState             : New

RunspaceId              : a941d0bc-ce79-4918-94c6-5958b9e5d1e8
Server                  : meg1dcex01
State                   : NotApplicable
HealthSet               : MSExchangeCertificateDeployment
HealthGroup             : ServiceComponents
AlertValue              : Disabled
LastTransitionTime      : 1/1/0001 8:00:00 AM
MonitorCount            : 2
HaImpactingMonitorCount : 0
Entries                 : {TransportFedCertMonitor, TransportFedCertExpiredMonitor}
Identity                : MSExchangeCertificateDeployment\meg1dcex01
IsValid                 : True
ObjectState             : New

Hi,

About the FEP Health Set, since you don't have ForeFront installed, you can disable this Health Set. For more details about how to disable it, you can see the article below, please refer to the "Troubleshooting FEP HealthSet" part in this article.

Exchange 2013 Managed Availability HealthSet Troubleshooting
http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx

And for OWA.Protocol.Dep Health Set, please confirm if OWA is working well when the OWA.Protocol.Dep Health Set is Unhealthy. If OWA works well, you can override Monitor setting for this Health Set.

From the health report, MSExchangeCertificateDeployment Health Set is disabled, you can enable this Health Set to check result.

For Compliance Health Set, to investigate further to check what are the monitors that are causing the HealthSet to go into Unhealthy state, you can use the following command.

Get-ServerHealth Identity <ServerName> HealthSet Compliance

Here is a related article: http://blogs.technet.com/b/exchange/archive/2013/06/26/managed-availability-and-server-health.aspx

Best regards,
Belinda

We are seeing similar behavior with only

ComplianceOutlookLogonToArchiveMapiHttpCtpMonitor

it is in an unhealthy state.  I can find little to no information on how to begin troubleshooting this particular health set.  I read the link to above article, but was not directly applicable.  Any information would be greatly appreciated.