66 Comments

1. SCOM Remote Maintenance Mode Scheduler v1.7 | Everything System Center Operations Manager 2007:

   [...]  http://www.scom2k7.com/scom-remote-maintenance-mode-scheduler-20/ [...]

   6 October 2008, 12:43 pm

2. Walter Chomak:

   Terrific! I was just doing some work which focuses on this functionlity. I am going to link to your post from my blog, hope you don’t mind!

   6 October 2008, 12:57 pm

3. Stefan Stranger's Weblog - Manage your IT Infrastructure : OpsMgr Remote Maintenance Mode Scheduler:

   [...] Source: Everything System Center Operations Manager 2007 [...]

   6 October 2008, 2:26 pm

4. Marc Cluke:

   It’s getting there, just not as quickly as we want. In our environment, it would be useful to be able to import a .txt, .csv, or .xls file with a list of servers.

   9 October 2008, 1:07 pm

5. admin:

   Marc, create a group with the list of your servers and put the group in Maintenance Mode.

   9 October 2008, 1:13 pm

6. Andrew:

   I am trying this for the first time. Not sure what this error means “The given path’s format is not supported”

   Great potential, though, to help in a big way….

   16 October 2008, 1:36 pm

7. David:

   Hi Tim:

   Thanks for the wonderful tool for the newbie SCOM 2007 admins like me.

   While running the scheduler, I ran into an issue. I tried to run the code directly from the command shell and I get the following error regarding the “null array”. Copy of your script is below the error message.

   Can you tell why I am getting null array?

   Thanks,

   David

   ===============================================================

   C:\>C:\WIN2k3\system32\WindowsPowerShell\v1.0\powershell.exe C:\MaintenanceModeV
   4\AgentMaintenanceModeV4.ps1 -rootMS: `atmspmom04′ -computerPrincipalName: ‘atms
   pasv01′ -minutes:30 -comment: ‘atmspasv01′ -reason: ‘PlannedOther’
   PathName :
   ManagementGroup : SCOM2007DC2
   ManagementServerName : atmspmom04
   Drives :
   You cannot call a method on a null-valued expression.
   At C:\MaintenanceModeV4\AgentMaintenanceModeV4.ps1:13 char:56
   + $healthServices = $computer.GetRelatedMonitoringObjects( <<<< $healthServiceC
   lass)
   Cannot index into a null array.
   At C:\MaintenanceModeV4\AgentMaintenanceModeV4.ps1:14 char:34
   + $healthService = $healthServices[0 <<<< ]
   Putting atmspasv01 into maintenance mode
   New-MaintenanceWindow : Cannot bind argument to parameter ‘MonitoringObject’ be
   cause it is null.
   At C:\MaintenanceModeV4\AgentMaintenanceModeV4.ps1:22 char:81
   + New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObje
   ct:$ <<<< computer -comment:$comment -Reason:$reason
   Putting the associated health service into maintenance mode
   New-MaintenanceWindow : Cannot bind argument to parameter ‘MonitoringObject’ be
   cause it is null.
   At C:\MaintenanceModeV4\AgentMaintenanceModeV4.ps1:26 char:81
   + New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObje
   ct:$ <<<< healthService -comment:$comment -Reason:$reason
   Putting the associated health service watcher into maintenance mode
   New-MaintenanceWindow : Cannot bind argument to parameter ‘MonitoringObject’ be
   cause it is null.
   At C:\MaintenanceModeV4\AgentMaintenanceModeV4.ps1:30 char:81
   + New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObje
   ct:$ <<<< healthServiceWatcher -comment:$comment -Reason:$reason

   =============================================================

   param($rootMS,$computerPrincipalName,$minutes,$comment,$reason)
   Add-PSSnapin “Microsoft.EnterpriseManagement.OperationsManager.Client” -ErrorVariable errSnapin;
   Set-Location “OperationsManagerMonitoring::” -ErrorVariable errSnapin;
   new-managementGroupConnection -ConnectionString:$rootMS -ErrorVariable errSnapin;
   set-location $rootMS -ErrorVariable errSnapin;
   $computerClass = get-monitoringclass -name:Microsoft.Windows.Computer
   $healthServiceClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthService
   $healthServiceWatcherClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthServiceWatcher
   $computerCriteria = “PrincipalName=’” + $computerPrincipalName + “‘”
   $computer = get-monitoringobject -monitoringclass:$computerClass -criteria:$computerCriteria
   $healthServices = $computer.GetRelatedMonitoringObjects($healthServiceClass)
   $healthService = $healthServices[0]
   $healthServiceCriteria = “HealthServiceName=’” + $computerPrincipalName + “‘”
   $healthServiceWatcher = get-monitoringobject -monitoringclass:$healthServiceWatcherClass -criteria:$healthServiceCriteria
   $startTime = [System.DateTime]::Now
   $endTime = $startTime.AddMinutes($minutes)

   “Putting ” + $computerPrincipalName + ” into maintenance mode”
   New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$computer -comment:$comment -Reason:$reason

   “Putting the associated health service into maintenance mode”
   New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$healthService -comment:$comment -Reason:$reason

   “Putting the associated health service watcher into maintenance mode”
   New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$healthServiceWatcher -comment:$comment -Reason:$reason

   21 October 2008, 7:33 pm

8. David:

   Hi Tim:

   I figured out that if I am using the FQDN instead of netbios name, it works.

   However, I have one question. Your program is setting the default location of the powershell program to c:\windows and I need to change that to c:\win2k. What do I change to give correct location of the powershell program?

   Thanks,

   David

   22 October 2008, 7:52 pm

9. FastBitz:

   Terrific Solution!!! Thanks very much.

   23 October 2008, 6:53 am

10. Roger:

    Does this tool also put the health service and health service watcher into maintenance mode for the specified server?

    24 October 2008, 11:46 am

11. Alex:

    It doesn’t look like this tool puts the health service and health service watcher into maintenance mode for the specified server. I still receive heartbeat failure notifications when I shedule a server for maintenance mode. Can the health service and health service watcher be added into this utility?

    24 October 2008, 1:03 pm

12. admin:

    Yes it does puts the health service and health service watcher into maintenance mode for the specified server. Are the scripts firing correctly? Did you try to fire the scripts outside of a scheduled task?

    24 October 2008, 1:10 pm

13. Alex:

    Sorry… I took a look at script now. I see that it does include the health service and health service watcher. The reason it wasn’t working is because I was receiving the “Security Warning”, I unblocked the file and all is well. Thanks.

    24 October 2008, 4:20 pm

14. Ross:

    Nice tool but 1 draw back i’ve noticed.
    It creates the scheduled task on the task server to run using the specified credentials but it uses the account you are logged on as to connect to the task server in order to create it – hence doesn’t work.
    In our environment our normal logon accounts don’t have access to servers. We have admin accounts for this.
    We could run the scheduled tasks on our local PCs but for centralisation and managment this is not good. What happens if a patch goes out overnight and my pc gets rebooted? The task might not run.
    Runas doesn’t work easily for this tool either. I have to runas my cmd line as my admin account and then cd to the shortcut and run that – pain in the neck.
    The only alternative i can see is have everyone login to the task server and use the tool from there but again only 2 (or 3) users connecting at once via RDP.

    I’m sure in most environments this works a treat.
    Has anyone else come across this issue? Thanks

    27 October 2008, 11:32 am

15. Samson:

    The scheduler is a fantastic tool. But in our case it doesn’t work properly.
    It seems that the script started successfully but the target server is not
    set in a maintenance mode. I have tried several times with different accounts
    on different group and on single server the result is the same. I installed
    the scheduler according to your instruction. What is goes wrong. Is there any
    log file to look?

    Thanks,
    Samson

    17 November 2008, 5:42 am

16. HanZi:

    Hi
    Was attempting to install onto our new test bench to see if it fulfills our Maintainance Mode problem.. However it fails at the first hurdle 1) Tries to load .net 3.5 (even thought we hve it installed) then the scheduler setup failes with “application requires that assembly system.core version 3.5.0.0 be installed in the GAC first.”
    All the best
    Hans

    18 November 2008, 11:10 am

17. Chris:

    I agree with Ross, any chance the next release will have the run-as option? We have people in our datacenter that do the monthly server patching and I would like to let them use this tool. They have an admin account and a regular account. There admin account as admin access to the RMS but there regular account does not. So for this scheduler tool to work they would have to be logged into their machine with there admin account. Right now i have their regular account as admins on the RMS but this is not ideal for many reasons. A run as option would make this tool PERFECT. otherwise for the rest of us admins it has worked flawless. Thanks

    20 November 2008, 1:23 pm

18. Chris:

    Nevermind about my last post, i got it working. The run-as option does not work with the shortcut that is created during install. If you go to the following directory C:\Documents and Settings\Yourname\Local Settings\Apps\2.0\5EK5NR3C.LTB\LH93A6KO.OGA\scom..tion_bfe6b84180b2a09d_0002.0000_1929c92e134b4a91
    and copy the scom scheduler exe to your desktop and shift\right click the run as option is there and it works. So it is now completely flawless.

    20 November 2008, 1:36 pm

19. admin:

    Chris and Ross you can do a run as if you search for the actual executable or run process explorer to find it. It is stored in your profile. Once you find it you can even create a new shortcut that has the ability to use run as.

    Mine is under

    C:\Users\tmcfadden\AppData\Local\Apps\2.0\71VQGZ58.OLE\K26N56H6.6VB\scom..tion_bfe6b84180b2a09d_0002.0000_7a7212912dc1142f\Scom Scheduler.exe

    XP might be something like

    C:\Documents and Settings\tmcfadden\AppData\Local\Apps\2.0\71VQGZ58.OLE\K26N56H6.6VB\scom..tion_bfe6b84180b2a09d_0002.0000_7a7212912dc1142f\Scom Scheduler.exe

    20 November 2008, 1:40 pm

20. Manjun:

    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

    21 November 2008, 12:13 pm

21. Ben:

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

    23 November 2008, 8:27 pm

22. admin:

    Yes just select the computer Tab at the top.

    23 November 2008, 8:32 pm

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

    [...] 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 [...]

    26 November 2008, 3:01 am

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

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

    3 December 2008, 12:48 pm

25. MichaelW:

    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..

    23 December 2008, 1:03 am

26. Tom:

    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?

    23 December 2008, 6:23 pm

27. admin:

    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}

    23 December 2008, 6:51 pm

28. Tom:

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

    23 December 2008, 8:06 pm

29. Marcus:

    Have been running this tool on SCOM 2007 environment and found it extremely usefull. Last week we upgraded to SCOM 2007 R2 and now this tool does not seem to work any more. Have commands changed in R2? Are there modifications that can/need to be made for this tool to function correctly with R2?

    Thanks

    9 August 2009, 8:14 pm

30. Tim:

    I am working on a new version that supports R2. The new version has a bunch of new features and should be out soon.

    - Tim

    9 August 2009, 9:51 pm

31. SCOM: Automatically Starting Maintenance Mode When Servers are Rebooted for Patching « Operating-Quadrant:

    [...] more efficient.   These include:  Tim McFadden’s remote maintenance mode scheduling utility:  http://www.scom2k7.com/scom-remote-maintenance-mode-scheduler-20/ and Clive Eastwood’s AgentMM utility: [...]

    15 August 2009, 3:49 pm

32. Operations Manager 2007 R2: Extensions « System Center Spartan:

    [...] that we use multiple ones… From running a PowerShell script from the Agent to creating a Schedule Task for MM to the Scheduled Maintenance [...]

    31 August 2009, 10:02 am

33. Trond Hindenes:

    Hi,
    THis is such a great little tool!

    2 requests though:
    1. Make the window wider, or at least possible to widen it. Our group names are loooong…
    2. Make it possible to set the taskserver/RMS server on a per-computer basis so that all operators are sure to use the same computers for tasks and RMS connection…

    Any chance you’ll release the source code for this so others can contribute?

    Good woork!

    Regards,
    Trond Hindenes / Norway

    2 September 2009, 12:46 pm

34. Dominique:

    Hello,

    It is the tool I was looking for, so I did the first steps but now I am blocked with an error:
    The files name, directory name, or volume label syntax is incorrect (EXCEPTION FROM HRESULTS 0x8007007B

    Let me know,
    Thanks,
    Dom

    16 September 2009, 8:20 pm

35. Dominique:

    Hello,

    I tried per computer and I did not get the error. So it was per group I got the issue.
    Should I see the wrench also within the SCOM Console? so far after 4 minutes I do not have it…

    Thanks,
    Dom

    16 September 2009, 8:24 pm

36. Kees::

    There seems to be a problem with the display/definition of the Start-time in case one has defined a 24-hour clock. I don’t see AM or PM displayed after the time, but the time is not given in 24-hour format either. So it’s rather confusing, and not clear whether the time AM or PM is used.

    Regards,
    Kees

    6 October 2009, 8:33 am

37. Bryan:

    Any word on that r2 version? I am really in need of some kind of schedule. I have reboots occuring automatically for groups of computers almost every night, and my admins are getting very annoied wiht the heartbeat alerts for know reboots.

    Thanks!

    13 October 2009, 8:15 am

38. Jon:

    Great work Tim,
    I look forward to the new version of this tool as the environment I am working in is R2.

    26 October 2009, 4:01 pm

39. Johan:

    Great tool!

    Thank you

    29 October 2009, 3:06 am

40. Joel:

    Any news on that new version for R2. I’m really keen to implement it into my environment!

    5 November 2009, 7:36 pm

41. Jeramey:

    Do you think that you will ever enable an import csv file function? That would be nice on the computer tab.

    11 November 2009, 3:41 pm

42. Lars:

    We also love this app, but i have one lite question. If i use the app and put all servers into maintence mode for 4 hours, but after 2 hours all my work is done and now i want to remove the maintence mode on all servers. Is there a simple way of doing that?

    12 November 2009, 4:34 am

43. Michael:

    Hi-

    Any word on when the next version will be released with R2 support? Love this tool!

    24 November 2009, 4:46 pm

44. Shay:

    Also anxiously awaiting R2 version….

    Thanks for the great app.

    11 December 2009, 5:43 pm

45. Mark:

    Hello all,

    I am trying to modify the powershell script to act on a monitor created by the Management Pack Template “Web Application”. First I run

    $monitoringclass = get-monitoringclass -name:Microsoft.SystemCenter.WebApplication.Perspective

    Followed by

    $monitoringobject = get-monitoringobject -monitoringclass:$monitoringclass -criteria:”SCS Web Other – iExpense”

    The second statement fails. When I run it interactively, I get this message:

    Get-MonitoringObject : The specified MonitoringClass ‘Microsoft.SystemCenter.Web
    lication.Perspective’ is not supported because it is abstract.”

    I’m not sure I understand what this means. Can anyone explain the issue or offer any workarounds? Any info would be greatly appreciated.

    16 December 2009, 10:46 am

46. Chad:

    Any word on the version of the scheduler for R2?

    18 December 2009, 10:08 am

47. Andreas:

    Can you say when the new version will be available?

    21 January 2010, 1:53 pm

48. Michael:

    Awesome tool! I have installed on my computer (running R2). It says “success” when i create it, but it doesnt seem to get into maint. mode.

    Also, the time is a little confusing. How do i set it in mm from 13.30 – 14.00 for instance?

    Thanks a lot!

    4 February 2010, 8:48 am

49. Michael:

    Also, is it possible to have the program write an entry in the eventviewer? That would be nice.

    Sorry for double post before

    4 February 2010, 9:51 am

50. Scott:

    Hello, Has anyone installed and attempted to use the SCOM scheduler with and get the following error upon creating a new task.

    “Access is Denied: (Exception from HRRESULT: 0×80070005 (E_ACESSDENIED))

    5 February 2010, 1:47 pm

51. Scott:

    Hello, after installing the scheduler, I ge the following error when creating a task,

    Access is Denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))

    Any ideas??

    Thx

    5 February 2010, 1:49 pm

52. OngBak:

    Bump for R2 support!

    8 February 2010, 10:02 pm

53. Marty:

    I’m on R2. Do I need to wait for the anxiously awaited “R2 version?”

    16 March 2010, 10:37 am

54. Rick Shover:

    Looks likeit would be a great tool, but when I try to run it from the Computer tab I am getting “Network address invalid.” Not sure what to do about that. I tried using teh FQDN for the RMS server – didn’t make a difference. Thanks for any help that you might be able to give.

    17 March 2010, 4:20 pm

55. Dominique:

    Hello,

    I tried per computers and everything works well.
    When I try to use a group after browsing the list of group I am getting an error:
    “Object reference not set to an instance of an object.”

    What am I missing?
    Thanks,
    Dom

    23 April 2010, 2:43 pm

56. Dominique:

    I reinstalled it and it works for groups except for nested Groups, is it normal?
    Thanks,Dom

    23 April 2010, 3:08 pm

57. Dominique:

    Okay Tim I found your comments “Only groups in unsealed management packs will show up” the nested group is a sealed MP so it might be why the machines did not get the MM scheduled, isn’t it?
    Anyway your tool is fantastic… ane very helpful all times…

    Thanks,
    Dom

    23 April 2010, 3:13 pm

58. Doug:

    It doesnt seem to like any groups with spaces in them which is nearly all of them. I get a Group ‘testing 123′ not found. Works fine for groups which dont have spaces.

    27 April 2010, 1:17 pm

59. Tim:

    I have tested it many times. Groups with a space work fine.

    27 April 2010, 6:56 pm

60. Everything System Center Operations Manager 2007 » Blog Archive » SCOM Remote Maintenance Mode Scheduler 2.0 R2 Scripts:

    [...] Maintenance Mode Scheduler 2.0 [...]

    28 April 2010, 4:17 pm

61. Jason:

    How about putting domain groups into maintenance in addition to the current SCOM groups?

    28 April 2010, 5:42 pm

62. Tim:

    Not sure what you mean. Can you explain more?

    28 April 2010, 5:57 pm

63. John Bradshaw:

    Beauty! Works a treat on R2.
    thx Tim,
    John Bradshaw

    28 April 2010, 9:00 pm

64. Krazy:

    works like a charm in R2 … U THA MAN !!!
    Thanks

    3 May 2010, 8:33 am

65. Mats Augustsson:

    Hi! Have solved my problem now. I needed to put some text in “Comment”.

    One other thing: Do you think that you will update this script/program to also have the possibility to just put one application into Maintenance Mode for one server.

    18 May 2010, 9:07 am

66. Frankg:

    Great tool ! Could you please add linux machine in the “get-computer” query of your next version ?

    Thanks

    Frank

    21 May 2010, 3:15 pm

Leave a comment