Updated MP – Sample Agent Maintenance Mode MP Version

A new version of my Sample Agent Maintenance Mode MP is available for download!


What is new?

  • Added “Sample Agent Maintenance Mode Class” to be able to also stop maintenance from the agent
  • Updated Maintenance Mode Splash screen to confirm shutdown/reboot and check for maintenance mode before initializing shutdown/reboot. Also added stop maintenance mode button.
  • Updated TriggerOM12MM.Instance.Event.vbs to also trigger stop maintenance mode

You can download it from here:


Special thanks to Thomas Peter from VAS Value Added Services GmbH who worked on this version of the package!

Here is the link to my old blog entry: https://systemcentertipps.wordpress.com/2012/08/02/sample-agent-maintenance-mode-2012-mp-8/

The files are provided “As Is” without any guarantee. Please implement in your test environment first and check functionality.

Published by


* 1974, female, working as a Consultant. Main topics: MS System Center, ServiceNow. Twitter: @SN_Tipps

5 thoughts on “Updated MP – Sample Agent Maintenance Mode MP Version”

  1. I created a very similar Maintenance Mode application. Actually there are 2 of them. Each server has an icon on the desktop allowing an user that has login rights to place that server in Maintenance mode. The second is a console on a Terminal Server. It allows a user to place any server into Maintenance Mode from that console. Even better it uses drag and drop for server lists in CSV or TXT format. Both apps also allow for removing servers from Maintenance Mode. The splash screen isn’t as pretty, though!

  2. Hi,

    We experienced that this functionality did not work on agents managed by Gateways. By accident we stumbled upon the following blog http://blogs.technet.com/b/kevinholman/archive/2015/10/28/monitor-an-agent-but-run-response-on-a-management-server.aspx which states that Microsoft.SystemCenter.ManagementServer (which is being used as target for the write action in this MP) also includes GW’s (without SDK capabilities). By changing the target to Microsoft.SystemCenter.CollectionManagementServer we ensured the Management Server is being used instead of the GW. Right after our agents managed by Gateways work as well!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s