Comments on: SCOM Remote Maintenance Mode Scheduler 2.0

By: Tom

Tom — Wed, 24 Dec 2008 00:06:44 +0000

so when running the command, where it says -urlName can i substitute the group name that contains SNMP devices?

By: admin

admin — Tue, 23 Dec 2008 22:51:40 +0000

No it cannot be used for SNMP devices right now. If you look at http://www.scom2k7.com/schedule-a-into-url-maintenance-mode/ it should be pretty easy change the powershell script to Get-Monitoring class for SNMP devices.

So change

$URLWatcher = (Get-MonitoringClass -name whatever the correct SNMP class is) | Get-MonitoringObject | where {$_.DisplayName -eq $urlName}

By: Tom

Tom — Tue, 23 Dec 2008 22:23:03 +0000

Can this be used for SNMP devices, ie if i select a computer but enter the device name or is it ony specific to server objects?

By: MichaelW

MichaelW — Tue, 23 Dec 2008 05:03:47 +0000

Hi,

Setting maintenance mode for a group has given mixed results, it isn’t working for the domain controllers groups. To troubleshoot I’ve copied the cmd directly from scheduled tasks and run directly within powershell. The following is returned:

0 computers found in the ‘XXX-XXX-XXXXXX XXXXX XXXXX’ group

There are definitely group members, ie View Group Members works within the console; with dynamic group memberships.

Setting maintenance mode on computers and other groups appears to be working fine. The spaces in the group name hasn’t been a problem for other groups, only the Domain Controllers group. An option would be just to create separate tasks for each DC.

Any ideas? Thanks..

By: Walter Chomak's System Center Operations Manager 2007 Landing Zone : Remote Maintenance Mode Scheduler v1.7

Wed, 03 Dec 2008 16:48:13 +0000

[...] Courtesy of Everything System Center Operations Manager 2007 - http://www.scom2k7.com/scom-remote-maintenance-mode-scheduler-20/ [...]

By: Chuck

Chuck — Mon, 01 Dec 2008 18:51:35 +0000

This tool is a step in the right direction but it and scom itself have some serious limitations.
Why doesn’t scom have this built in? Why can’t I just put just one monitor into maintenance mode? I have servers that have services that go down for backup nightly. I am using windows watchers for the non-windows services for example. I would like the watcher group task to go into mm but the whole ‘watcher’ server has to go into mm. This is enterprise monitoring 101. Just because one service is down doesn’t mean I don’t care what else happens on the box. What if the backup service failed during the mm window? How would I know that if the whole server is in mm?
Sorry, this is a real sore point for me.

By: WebLog de Stéphane PAPP [MSFT] : Planifier la maintenance dans Operations Manager 2007

Wed, 26 Nov 2008 07:01:39 +0000

[...] pour planifier des plages de maintenance sur des groupes de serveurs de manière industrielle : http://www.scom2k7.com/scom-remote-maintenance-mode-scheduler-20/ Posted: Wednesday, November 26, 2008 8:01 AM by spapp Filed under: Information, Operations [...]

By: admin

admin — Mon, 24 Nov 2008 00:32:01 +0000

Yes just select the computer Tab at the top.

By: Ben

Ben — Mon, 24 Nov 2008 00:27:05 +0000

Hello
Is it possible to specify a single server to place into maintenance mode with the tool instead of a group?
Thanks
Ben

By: Manjun

Manjun — Fri, 21 Nov 2008 16:13:05 +0000

I am having the same issue as Samson, it did not put the target server in to maint. even I have admin right on task server and target server, I am running the scheduler from my PC that is in the same domain as the servers and the same ID,
Any one knows why and the solution?
Thank you in advance,

Manjun