Archive for the ‘Maintenance Mode’ Category

Scheduled Maintenance Mode – scalability considerations

June 16, 2011 Leave a comment

Suggested Support numbers are as follows:

  • Up to 20 jobs per management group
  • Up to 10 items (computer, group, other class) in a job. If you would like to schedule 1000 agents you should place them in a group.

There does seem to be an issue with trying to modify jobs that have more than 6 objects – I have found (and others have been able to replicate) that when you try and modify the job details, an error is thrown and the schedule is blank (and can’t be re-added). A fix is in the pipeline so stay tuned if you are affected by this.


Scheduled Maintenance – Process Monitors

April 3, 2010 Leave a comment

$processname = “Process Monitor Name”
$comment=”Mostly Harmless”

Add-PSSnapin “Microsoft.EnterpriseManagement.OperationsManager.Client” -ErrorVariable errSnapin;

Set-Location “OperationsManagerMonitoring::” -ErrorVariable errSnapin;
new-managementGroupConnection -ConnectionString:$rootMS -ErrorVariable errSnapin;
set-location $rootMS -ErrorVariable errSnapin;

$ProcessWatcher = (Get-MonitoringClass -name Microsoft.SystemCenter.Process.BaseMonitoredProcess) | Get-MonitoringObject | where {$_.DisplayName -eq $processname}

$startTime = [System.DateTime]::Now
$endTime = $startTime.AddMinutes($minutes)

“Putting Process into maintenance mode”

foreach ($name in $processwatcher) {
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$name -comment:$comment -Reason:$reason


Categories: Maintenance Mode

Scheduled Maintenance Mode for Web Monitors

April 3, 2010 Leave a comment

If you want to use scheduled maintenance against web watchers then this article is for you.

Categories: Maintenance Mode

Maintenance Mode Process Flow

March 29, 2010 Leave a comment

Another one pulled from a post by Kevin Holman on the technet forums which explains the process of setting maintenance mode/

Kevin Holman:

You put an agent in MM which is a call to the SDK to trigger MM for an agent.

A config update is recalculated and sent to that agent.

The agent gets the config update, which has instructions to unload its workflows targeting classes that were placed into MM.

The RMS checks on a schedule for all agents that have MM expiring – and then sends a config update to the agent to stop MM at the appropriate time.

The agent loads up workflows again when MM ends.

Categories: Maintenance Mode

Maintenance Mode – database settings

July 9, 2009 Leave a comment

Ever wondered what all those values are in the vMaintenanceModeHistory table? Kevin Holman tells all:

Also, Kevin has provided a great outages and maintenance mode report –

Categories: Maintenance Mode