Schedule Maintenance Mode Reskit Tool Info

Schedule Maintenance Mode Reskit Tool Info

  • Comments 6
  • Likes
 

I have a quick update on the Schedule Maintenance Mode RESKIT Tool, also some information \ best practices.

Best Practices:

  • Do not go beyond 20 Jobs scheduled.  Anything over this will start to place too much load on your Root Management Server
  • Do not schedule more then 20 items in one Job.  If you need to go over this please create a group and target this.  Note: The MP has a bug that only limits you to select up to six objects.  I have attached an updated MP that corrects this issue below.
  • When scheduling a group make sure to select system.group then select the group.  If you select the group itself the tool lists the individual group membership.

Known Issues:

  • A common issue with our international customers is a date time casting exceptions or the schedule is not landing on the correct day.  This tool was designed and tested on EN-US only.  I cannot make any promises but I will look into extending this to support other locals in the future.  The work around is to install the Windows EN-US language pack. 

Updated Schedule Maintenance Mode MP Download Zip file

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Good looking out, I had just downloaded this today, and was going to put it into use tonight for my Citrix farm, I downloaded and replaced the MP with your fixed one. Though I'm not sure what you mean by select system.group, then select the group. I do not see that option.

  • Hi parbogast, choose Group | System.Group.

  • Where is the AlertSuppression.mp I see in the documentation on 1.0.0.130 of Schedule Maintenance Mode.docx ?

    Thanks,

    DOm

  • It looks like the Maint Mode MP is causing a lot of config churn.  I ran the script that Kevin Holman provided on his blog site to check for top noisy rules in the last 24 hours and this is what I got:

    Managed Entity Type System Name   DiscoverySystemName Changes

    ScheduleMaintenanceMode.Library.JobComponent        NULL 3420

    ScheduleMaintenanceMode.Library.ScheduleComponent NULL 927

    I have also noticed that my SCOM console has been *very* slow since I installed the MP.  I'm going to uninstall the MP and see if that improves performance......

    blogs.technet.com/.../what-is-config-churn.aspx

  • The rules runs once a minute to check to see if something need to be placed into maintenance per job.  Config only gets changed if there is something for the rule to do.  Like placing something into mmode and updating the schedule.

    Unless you have created hundreds of Jobs this should have low per impact.

    Thanks

    Rob

  • thank you