SCOM 2012 Maintenance Mode Scheduler

We believe that core to any monitoring system is the ability to send out accurate alerts. SCOM sends out many valuable alerts but will flood e-mail boxes and paging systems during maintenance windows.  We set out to build a maintenance mode scheduler that anyone can quickly and easily use to prevent these floods of useless information.


  • Easily access the new web based maintenance mode scheduler from any browser.
  • End users will thank you at how easy it is to pick a computer, group, object, and even a subscription with a start time and end time. The app calculates the minutes for them and schedules a future maintenance window.
  • The manage tab will make it easy to see and manage any upcoming maintenance windows and identify any gaps.
  • The new integrated dashboards make it feel like the scheduling maintenance mode was always there.
Download Free Trial



Schedule a group of Computers, Databases, or any objects in the group into maintenance Mode.

One Click Maintenance Mode

Another great feature is the ability to do one click maintenance mode from any server.  This means is you can place the same shortcut on the desktop of your all your servers.  With one click, the IT administrator can put the server into maintenance mode.


After the shortcut is clicked, the web page automatically detects what server you are on and puts the server into Maintenance Mode with no interaction.


Dashboards Integrated Into The SCOM Console




Most organizations only use the alerts from SCOM.  Now you can schedule your complex subscriptions into maintenance mode.  You can choose to send the alerts that where queued up or discard them.


Manage any upcoming maintenance windows and identify any gaps



Windows 8 App

The Windows 8 app can be download from the Windows App Store.  It uses the existing the same infrastructure and web service as the Web based version.

Download Now from the App Store





Click Here to Purchase

Any problems, bugs, or issues please e-mail:


Related Posts

SCOM 2012 Maintenance Mode Scheduler Installation Guide –

SCOM 2012 Maintenance Mode Scheduler User Guide

Securing SCOM 2012 Maintenance Mode Scheduler –


Continue Reading

Crazy DB Performance Collection rules in the SQL MPs

One of my customers was experiencing lots of growth in their OperationsManager DB.

They monitor hundreds of SQL servers. I had a look into their Top Tables using Kevin Holman’s Large table query.

Things looked pretty normal where Performance tables are the top tables



I drilled down a little further in the performance data and see this.



Focusing on the two top counters that are 4x larger then the next few.

I took a look at the counters for one of my SQL servers and realize that we are collecting the same counter over and over for each database instance on a SQL server.



This is crazy.  It might make some sense if a customer ran every database on a individual drive, but that is not the norm.  Most SQL servers have one or a few drives for their DB files and Logs.

To double check I looked at the OperationsManager database performance tables.


Sure enough we are collecting the same data 13 times in my case.

So how do we fix this?  Disable the rule that collects this data using an override for SQL 2005, 2008, 2012, and 2014.

Rule for SQL 2012 is called

  • MSSQL 2012: Collect DB Disk Write Latency (ms)
  • MSSQL 2012: Collect DB Disk Read Latency (ms)







I then recommend collecting this data if you need it once per disk.

To enable it, create an override for Windows Server 2008 and 2012 Logical Disk

  • Collection Rule for Average Disk Seconds Per Write Windows Server 2012
  • Collection Rule for Average Disk Seconds Per Read Windows Server 2012




Override True



Continue Reading

SCOM 2012 Maintenance Mode Scheduler Version 7

New Features in Version 7

  • CSV Server Import – Now you can schedule a list of Windows or Unix computers for Maintenance Mode using a CSV (Comma Separated Values) file.
  • Intelligent Maintenance Mode – Before a computer or object is put into maintenance mode it is checked to see if it’s already in maintenance mode. If the existing maintenance window is longer then the new maintenance window, the existing window is kept.
  • Unix/Linux Support for Immediate Maintenance Mode – Unix Admins can now use the MMNow page to immediately put servers into Maintenance Mode using a web browser or wget from a shell script.
  • Management Servers in a Group are prevented from going into Maintenance Mode – If a group is scheduled for maintenance mode that contains Management Servers. The Management Servers are now skipped from going into Maintenance Mode.
  • New Jobs Report Fixed – Some users were experiencing an issue where the MMScheduler box was grayed out. This has now been resolved.
  • Improved permissions tool – It is now easier to grant new permissions as existing users and groups show up when the tool is opened.
  • Improved Logging – Events are created when a Schedule Maintenance Job is run or when a user puts a server into maintenance mode immediately using MM Now


Download Now

CSV Server Import

CSV File



Unix/Linux Support for MMNow Page


Calling One Click MM using wget from a Unix/Linux Shell Script


Calling One Click MM using Invoke-WebRequest from PowerShell script on a Windows Computer


New Jobs Report Fixed


Improved permissions tool


Improved Logging


Continue Reading

Alert on SQL Job Failure when SQL Agent Job Discovery is Enabled

Customer was asking why they were not getting alerts for SQL Agent Job failures.  They had enabled individual SQL Agent Job Discoveries that is talked about in Kevin’s post.

By default the Last Run Status monitor does not alert.  So they created an override to enable Generates Alert.



Problem was no alerts came through.  Looking at Alert severity it says “Critical” and Alert on State it says “The monitor is in a critical health state”.  Looks good to me.

But still no alerts.

Lets take a look at the monitor.  The monitor is in a warning state.  That is weird I thought Alert severity is “Critical” from the above screenshot.



Lets take a look at the monitor.  I right click and go to monitor properties.  There is no Critical Health State, only Warning and Healthy for this monitor.  Looks like a bug to me or bad MP practices.


If I look back at my Overrides I can see that this monitor will only Alert On State if “Alert if it is in a Critical Health State”



Well it will never go into a “Critical Health state” because it doesn’t exist.   There is no way to override the monitors health.  This is not usually an issue because most monitors are either two state Health and Critical, or three state, Healthy, Warning, and Critical.

So what to do?

The only way to get the monitor to alert is to create an override so that Alert on State is changed to Warning.


Now when the monitor changes to a “Warning state” I get an Alert.



But why is it a “Warning”?  Not really sure.  The default behavior is Alert severity is “Critical”

If I create another override for “Alert severity” Critical



Now I get a critical alert.




But the monitor is still in a warning state and could be confusing to the end user.



I will file a bug to get this changed.







Continue Reading

Microsoft acquires BlueStripe

Today it was officially announced that Microsoft has acquired BlueStripe software, which has been a key partner for Operations Manager and Azure for monitoring application performance and availability of distributed business applications seamlessly and comprehensively.


You can read more of the announcement here

Continue Reading