change automatic agent upgrade behaviour
currently using the automatic client upgrade process on servers causes the SCOM agent to be stopped ahead of the upgrade causing hundreds of SCOM alerts that then need closing or investigating. The option of "don't upgrade servers" still causes the SCOM agent to be stopped.
Either provide the option not to stop the SCOM agent during client upgrade or honour the "don't upgrade servers" check before you stop the SCOM agent.
here is the error one gets with the client upgrade feature. Since you can modify the program like other one can not uncheck the OpsMgr Mainenance Mode.
Carl Polk commented
Yes this really bothersome as the alerts freak out my Operations guys. The client doesn’t install on the server as designed, but still generates alerts. Surely SCCM can get the OS first before stopping SCOM checking the OS then realizing it’s a server OS.
Yes this needs to be addressed. Pretty old request but its needed. regular programs have the option of NOT triggering MOM alerts however the automatic client clinet upgrade does not. Like the post mention even if you set to not upgrade servers and add an exlusion collection for servers, the MOM / SCOM alerts still get triggered on servers