1 Reply Latest reply on Nov 17, 2017 6:07 AM by cwinning

    Schedule reboot during maintenance window - best practice


      Hello -


      We recently picked up Shavlik Protect to patch our Windows Servers, and I had a question that I don't seem to be able to find a quick answer for:


      Schedule reboot

      If you elect to reboot the machines, you can specify when the reboot should occur. You can:

      • Reboot the machines immediately after installation
      • Reboot at a specific time
      • Reboot at a specific date and time


      If I schedule updates to begin at 11PM, and I have a “must be available” timeline of 3AM (server must be available again in terms of maintenance window).  If I schedule a reboot at specific time of 2:30 AM and the patching is still occurring will this interrupt/halt the patching (and notify me?), or will it continue patching AFTER the reboot and then reboot again down the road?  I really want to ensure that if patching takes longer than expected I wont be an situation of a reboot occurring post 3AM (if I pick reboot immediately after install), but I also don’t want to cause issues with the patching because we rebooted in the middle of patching?


      Also how does it handle several patches that trip the reboot flag?  Does it apply all the patches in the group and then reboot, or is intelligent enough to apply patch, reboot and then continue patching?



        • 1. Re: Schedule reboot during maintenance window - best practice
          cwinning CommunityTeam



          I initiated a deployment and set the restart to occur 5 minutes into the future.  The restart didn't occur until all of the patches were processed, therefore this isn't a good method to ensure the deployment windows doesn't exceed your change window.  Providing enough time for the scan and deployment to allow completion before 3AM is your only solution.  Barring slow scan times (WAN links) or a large amount of patches, most scan/deployments are completed well before 3 hours.  I would suggest testing.


          We use the /norestart (or equivalent) switch for all patch installs. This means all patches are installed with no restart, the restart is controlled by the Deployment Template.