OpsMgr 2007: Object still shows to be in Maintenance Mode after the window has expired

We get questions about this every so often so I figured I would send you all a heads up.  A Knowledge Base article is forthcoming but it happens enough that I wanted to go ahead and get this out now.

Although a maintenance mode window has expired, an object may still show to be in Maintenance Mode in the System Center Operations Manager 2007 console.

This is caused by placing the Root Management Server (RMS) into Maintenance Mode. When the RMS is in Maintenance Mode, the workflow's responsible for bringing instances out of Maintenance Mode are unloaded, therefore when Maintenance Mode windows expire the RMS will not automatically bring them out of maintenance mode.

Placing the Root Management Server, Secondary Management Servers and Gateway Servers into Maintenance Mode is not recommended or supported as it may product unpredictable results.

Do not place the Health Service and contained objects on an RMS, Secondary Management Server or Gateway Servers into Maintenance Mode.

J.C. Hornbeck

Comments (5)

  1. Anonymous says:

    Our servicedesk is using an adapted version of the GroupMaintenancemode -script from Boris Yanushpolski

  2. Anonymous says:

    how do you recommend performing patch tuesday on OpsMgr servers then?  just reboot with out putting into maintenance modes and deal with alert cleanup afterwards?

  3. Anonymous says:

    thank you

  4. Chris says:

    Thats not a resolution, that doesn't fix the problem it just prevents it

Skip to main content