SCOM supports putting discreet objects/classes/targets into maintenance mode. This gives a very fine control over what objects/classes/targets have alerts forwarded or not.
Unfortunately, behaviorally, our operations team doesn't want that level of control.
Behaviorally they want to put the entire server, or groups of servers, into maintenance mode. Where "maintenance mode" means no alerting of any kind. Period. Fin.
Today, we come close, by putting
HealthService (which also seems to cover Agent). Putting those objects into maintenance mode allows us to do application deployments (service stops, etc) and anything requiring a reboot.
However, we still get occasional alerts from objects in either like the Dell MP or BizTalk MP. Alerts that don't tend to target
WindowsComputer, or anything in its inheritance chain(?).
We tried putting
Entity object/class/target into maintenance mode but this seemed to send the RMS server into a tizzy. e.g. If we made 50 requests, for 50 different servers, maybe 1 in 5 would actually be placed into maintenance mode. The remainder would be ignored.
We are using the SCOM API via Power Shell, or the SCOM SDK object model, to put things into maintenance mode.
Is there a recommended way to put a server, and all its contained objects, into maintenance mode, reliably?
Is there something our team should be considering on why we don't want to put everything into maintenance mode?