locked
SCCM Patching and SCOM alerts RRS feed

  • Question

  • Howdy,

    In our Automatic Deployment Rules we have the box checked that says:
    Disable Operations Manager alerts while software updates run

    However, when our latest patching group ran on Saturday we got tons of Heartbeat failure alerts by all the servers that were getting patched.

    Can anyone tell me how that checkbox is supposed to work and what it does to make SCOM not send alerts?

    Do we need to configure something to tell SCCM where SCOM is located?  Do we need to configure any connector of any sort?  Does this checkbox not really do what it seems like it should do based on the description?

    I found a snippet that someone posted on their own blog that says:

    Most of seasoned System Center specialists must already know that these tick boxes do not make the computers enter maintenance mode in OpsMgr. It’s suppressing alerts by pausing the OpsMgr healthservice. As far as I know, there is no way to initiate maintenance mode from an agent. Maintenance mode can only be started from the management server (via Consoles or any scripts / runbooks / applications via SDK).

    I don't know if that's true or not but seems like it wouldn't prevent Heartbeat alerts when a machine reboots after patching anyway.

    Thanks!

    Wednesday, November 4, 2015 10:18 PM

Answers

  • It's almost true. In ConfigMgr 2012, it pauses the OpsMgr service *and* dumps the workflows. This is roughly equivalent to maintenance mode. I honestly don't remember enough about heartbeat in OpsMgr and what initiates it or its failure. Thus, asking this on an OpsMgr forum would yield better info.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, November 4, 2015 10:48 PM

All replies