Home
%3CLINGO-SUB%20id%3D%22lingo-sub-697122%22%20slang%3D%22en-US%22%3EMonitoring%20Exchange%20using%20Multiple%20OWA%2FECP%20Virtual%20Directories%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-697122%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20an%20Exchange%20Administrator%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FConfiguring-Multiple-OWA-ECP-Virtual-Directories-on-the-Exchange%2Fba-p%2F611217%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ecreates%20additional%20Virtual%20Directories%20for%20Outlook%20on%20the%20Web%20or%20Exchange%20Control%20Panel%3C%2FA%3E%2C%20we%20have%20found%20that%20a%20few%20Managed%20Availability%20probes%20fail%20on%20Exchange%20Server%202013%20or%20above.%26nbsp%3B%20This%20occurs%20because%20the%20monitoring%20probes%20use%20the%20Server's%20FQDN%20to%20access%20the%20RPC%20or%20MAPI%2FHTTP%20frontend%20virtual%20directory%20(e.g.%20%3CA%20href%3D%22https%3A%2F%2Fex01.contoso.local%2Frpc%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fex01.contoso.local%2Frpc%2F%3C%2FA%3E...%2C%20%3CA%20href%3D%22https%3A%2F%2Fex01.contoso.local%2Fmapi%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fex01.contoso.local%2Fmapi%2F%3C%2FA%3E...).%26nbsp%3B%20Unfortunately%20when%20the%20probes%20resolve%20the%20local%20machine's%20FQDN%2C%20there%20is%20a%20chance%20of%20getting%20an%20IP%20address%20bound%20to%20the%20manually%20created%20secondary%20website.%26nbsp%3B%20When%20this%20happens%2C%20the%20probe%20request%20fails%20with%20HTTP%20Status%20code%20404%20(Not%20Found)%20because%20there's%20no%20such%20virtual%20directory%20defined%20in%20the%20web%20site.%26nbsp%3B%20If%20the%20probes%20keep%20failing%2C%20their%20corresponding%20responders%20are%20alerted%2C%20resulting%20in%20execution%20of%20a%20recovery%20action.%20%26nbsp%3BIn%20certain%20instances%2C%20the%20probes%20will%20recycle%20the%20frontend%20MAPI%2FHTTP%20application%20pool.%20%26nbsp%3BObviously%2C%20this%20is%20unnecessary.%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20avoid%20this%20issue%2C%20we%20recommend%20you%20use%20Add-GlobalMonitoringOverride%20or%20Add-ServerMonitoringOverride%20to%20disable%20impacted%20probes.%3C%2FP%3E%0A%3CPRE%3EAdd-GlobalMonitoringOverride%20'Compliance%5CComplianceOutlookLogonToArchiveRpcCtpProbe'%20-PropertyName%20Enabled%20-PropertyValue%200%20-ItemType%20Probe%0AAdd-GlobalMonitoringOverride%20'Compliance%5CComplianceOutlookLogonToArchiveMapiHttpCtpProbe'%20-PropertyName%20Enabled%20-PropertyValue%200%20-ItemType%20Probe%0AAdd-GlobalMonitoringOverride%20Outlook%5COutlookRpcCtpProbe%20-PropertyName%20Enabled%20-PropertyValue%200%20-ItemType%20Probe%0AAdd-GlobalMonitoringOverride%20OutlookMapiHttp%5COutlookMapiHttpCtpProbe%20-PropertyName%20Enabled%20-PropertyValue%200%20-ItemType%20Probe%0A%3C%2FPRE%3E%0A%3CP%3EMore%20information%20on%20the%20use%20of%20these%20settings%20is%20available%20at%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fhigh-availability%2Fmanaged-availability%2Fmanaged-availability%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EManaged%20Availabilty%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EThanks%20to%20Ryusuke%20Fujita%20for%20figuring%20out%20this%20post.%3C%2FP%3E%0A%3CP%3EThe%20Exchange%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-697122%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20might%20have%20some%20issues%20with%20monitoring%20if%20you%20have%20multiple%20OWA%20and%20ECP%20Virtual%20Directories%20-%20Read%20this%20to%20find%20out%20more%20and%20what%20to%20do%20about%20it.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-697122%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

When an Exchange Administrator creates additional Virtual Directories for Outlook on the Web or Exchange Control Panel, we have found that a few Managed Availability probes fail on Exchange Server 2013 or above.  This occurs because the monitoring probes use the Server's FQDN to access the RPC or MAPI/HTTP frontend virtual directory (e.g. https://ex01.contoso.local/rpc/..., https://ex01.contoso.local/mapi/...).  Unfortunately when the probes resolve the local machine's FQDN, there is a chance of getting an IP address bound to the manually created secondary website.  When this happens, the probe request fails with HTTP Status code 404 (Not Found) because there's no such virtual directory defined in the web site.  If the probes keep failing, their corresponding responders are alerted, resulting in execution of a recovery action.  In certain instances, the probes will recycle the frontend MAPI/HTTP application pool.  Obviously, this is unnecessary. 

To avoid this issue, we recommend you use Add-GlobalMonitoringOverride or Add-ServerMonitoringOverride to disable impacted probes.

Add-GlobalMonitoringOverride 'Compliance\ComplianceOutlookLogonToArchiveRpcCtpProbe' -PropertyName Enabled -PropertyValue 0 -ItemType Probe
Add-GlobalMonitoringOverride 'Compliance\ComplianceOutlookLogonToArchiveMapiHttpCtpProbe' -PropertyName Enabled -PropertyValue 0 -ItemType Probe
Add-GlobalMonitoringOverride Outlook\OutlookRpcCtpProbe -PropertyName Enabled -PropertyValue 0 -ItemType Probe
Add-GlobalMonitoringOverride OutlookMapiHttp\OutlookMapiHttpCtpProbe -PropertyName Enabled -PropertyValue 0 -ItemType Probe

More information on the use of these settings is available at Managed Availabilty.

Thanks to Ryusuke Fujita for figuring out this post.

The Exchange Team