17 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. FastBitz:

   Terrific Solution!!! Thanks very much.

   23 October 2008, 6:53 am

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

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

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

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

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

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

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

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

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

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

Leave a comment