SafetyNet-TC
asked on
Global Monitoring Override Of Managed Availability Messages Failing
Hello,
I have a client that would like the Exchange 2013 managed availability probes disabled. I followed this KB to do this, but the probe emails persist. My global monitoring overrides are shown below. The client has two CAS servers, one MBX server, and one Exchange 2010 server as of now. All three show version 15 build 913.22, also shown below:
This is the version I used with the -ApplyVersion parameter in the Add-GlobalMonitoringOverri de command. The commands I used are:
Add-GlobalMonitoringOverri de -Identity "FrontendTransport\OnPremi sesSmtpCli entSubmiss ion" -PropertyName Enabled -PropertyValue 0 -ApplyVersion "15.0.913.22" -ItemType Probe
Add-GlobalMonitoringOverri de -Identity "MailboxTransport\Mapi.Sub mit.Probe" -PropertyName Enabled -PropertyValue 0 -ApplyVersion "15.0.913.22" -ItemType Probe
Add-GlobalMonitoringOverri de -Identity "FrontendTransport\OnPremi sesInbound Proxy" -PropertyName Enabled -PropertyValue 0 -ApplyVersion "15.0.913.22" -ItemType Probe
This resulted in the following:
After applying these commands I initially restarted the MS Exchange Diagnostics and the MS Exchange Health Manager services, and when that didn't resolve I restarted all Exchange 2013 servers. The probe messages persist:
What can I try to resolve this?
Thank you!
I have a client that would like the Exchange 2013 managed availability probes disabled. I followed this KB to do this, but the probe emails persist. My global monitoring overrides are shown below. The client has two CAS servers, one MBX server, and one Exchange 2010 server as of now. All three show version 15 build 913.22, also shown below:
This is the version I used with the -ApplyVersion parameter in the Add-GlobalMonitoringOverri
Add-GlobalMonitoringOverri
Add-GlobalMonitoringOverri
Add-GlobalMonitoringOverri
This resulted in the following:
After applying these commands I initially restarted the MS Exchange Diagnostics and the MS Exchange Health Manager services, and when that didn't resolve I restarted all Exchange 2013 servers. The probe messages persist:
What can I try to resolve this?
Thank you!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.