With multiple disks on an Exchange server for DAG all the database health for low log space all rollup to the server. So if a another disks breaches the threshold an alert is not sent as the existing one is still there and has already sent an alert.1 vote
Create an updated version of the MP for Exchange 2016 and do the same for 2019. Let's not be lazy. Even if the monitoring did not change much, a new MP is required so that we have proper views, groups, descriptions in alerts, etc.
This isn't the way things should be done: https://blogs.technet.microsoft.com/exchange/2016/06/13/monitoring-exchange-server-2016-with-system-center-operations-manager/
Especially for a mission critical application like Exchange.64 votesunder review · AdminAakash Basavaraj[MSFT] (Program Manager, Microsoft System Center Operations Manager) responded
All – I agree we are arriving late to this party but we plan to take this up soon. In the meantime, can you share few inputs on the current Exchange MP (which seems to work with Exchange 2016 & 2019) such as additional monitor/rules that need to be added etc.
Please feel free to write to us at firstname.lastname@example.org.
Just Change it do be done by anything else,
Rather then using a Powershell script that run every 4 Hours on every Server in the Organization5 votes
- Don't see your idea?