Operations Manager 2012 still doesn’t block placing management servers into maintenance mode. However, the way Management Servers behave when placed into maintenance mode has changed:
- If a Management Server is placed into Maintenance Mode then the System Center Management Configuration Service will change the agent assignment to force the agents to failover to another management server so data loss will not occur.
- In Operations Manager 2007 a Management Server couldn’t take itself out of Maintenance Mode as Maintenance Mode unloads all workflows (including the “End Maintenance Mode” workflow). This has changed in Operations Manager 2012 by assigning the “End Maintenance Mode” workflow to the “All Management Servers” resource pool. This way the workflow will failover to another Management Werver and reload to be able to exit maintenance on the Management Server that was placed into Maintenance Mode.Note: If you only have one Management Server and you place it into Maintenance Mode it will never come out because there is no other Management Server for workflow failover.
[...] 5) Maintenance Mode changes – More info [...]
Thanks Graham! Any changes with maintenance mode in a virtualized environment? For example, we run a VMM with HyperV environment with all our SCOM servers virtualizaed. The problem we always run into is when we have to place the Host server into MM, or placing the VMM server into MM. This always had a chain reaction placing all virtual servers sitting on that Host into MM. We always ran into this during Patch Tuesday each month.
Thanks,
Tom
Hi Tom
I don’t know if this has changed but I also haven’t tested this yet. I’ll see if I can find some time and get back to you.
Cheers
Graham
What about a true built in MM scheduler instead of a half baked release with the admin resource kit?
I agree Jon though this isn’t on the road map for SCOM 2012 as far as I know.
Las Vegas Maids…
[...]Maintenance Mode changes in SCOM 2012 // Designing Integrated Solutions[...]…