Kaseya Community

Schedule Monthly updates instead of weekly

This question is answered

I am planning on moving the 500ish client servers from manual patching to automatic patching through Kaseya.  However, we had a weekly rotation so that a server was rebooted once monthly.  I only see weekly reboot settings in Kaseya for servers.


Does anyone know how to change or modify patching schedules through Patch Management or agent procedures so that I can set servers to reboot once every month instead of once every week?

We are not using Policy Management much but this is an option.  We are also on 6.5.

Verified Answer
  • If you select the Reboot Action of "reboot every <specific day of the week> after install, that will reboot the machine on the selected day of the week but ONLY after a patch install runs.  Let's say you have Automatic Update scheduled to run on the third Saturday of a month and you configure the Reboot Action to reboot every Sunday at 10pm.  The first weekend of the month goes by.  No patches are installed that week because it's only the "first" Saturday.  When Sunday 10pm comes along, Reboot Action will not fire because no patches have been installed.  Another week passes, and on the second Saturday of the month, no patches are installed.  The  next day (Sunday), the reboot action would not fire because there have been no patches installed.  The third weekend of the month arrives and Automatic Update fires on Saturday.  The following day at 10pm, Reboot Action recognizes that a patch cycle took place and that there has been no reboot between the time the patch cycle completed and 10pm on Sunday.  Reboot Action will fire and reboot the machine.   The following week, no patches so no reboot.  

    There is a caveat to this.  In some instances, it is necessary for the Kaseya server to create more than one install script for patches.  For example, a cycle includes a patch that requires it be installed by itself (based on the coding of the patch from Microsoft).  The patch install scripts will be written such that the some patches will be included in one install script and other patch(es) will be included in a different install script.  These two scripts are all part of the same Automatic Update cycle, they just require separate processing.  In this case, the first install script will execute on the third Saturday of the month.  The first Sunday at 10pm after that first install script executes (which would likely be the day following the patches in that first install script), Reboot Action will fire and reboot the computer.  This patch cycle STILL has additional patches to install.  The additional patches will begin to fire after the reboot.  Let's say those patches complete by 1am on Monday morning.  The next Sunday, Reboot Action will recognize patches have been installed and Reboot Action will fire.  This would, theoretically, be on the fourth Sunday of the month.  This reboot would be valid since it's still working off of the install cycle that began the third Saturday of the month.   This is a less common occurrence, but it does happen when multiple install scripts are required for a single patch cycle, and something to keep in mind.  

All Replies
  • I may have figured out my issue.

    All under patch management tab:

    1) Set automatic update.

    2) Set Windows Auto update action to disable (let patch management control).

    3) Make sure Patch Policy is set up properly.

  • If you select the Reboot Action of "reboot every <specific day of the week> after install, that will reboot the machine on the selected day of the week but ONLY after a patch install runs.  Let's say you have Automatic Update scheduled to run on the third Saturday of a month and you configure the Reboot Action to reboot every Sunday at 10pm.  The first weekend of the month goes by.  No patches are installed that week because it's only the "first" Saturday.  When Sunday 10pm comes along, Reboot Action will not fire because no patches have been installed.  Another week passes, and on the second Saturday of the month, no patches are installed.  The  next day (Sunday), the reboot action would not fire because there have been no patches installed.  The third weekend of the month arrives and Automatic Update fires on Saturday.  The following day at 10pm, Reboot Action recognizes that a patch cycle took place and that there has been no reboot between the time the patch cycle completed and 10pm on Sunday.  Reboot Action will fire and reboot the machine.   The following week, no patches so no reboot.  

    There is a caveat to this.  In some instances, it is necessary for the Kaseya server to create more than one install script for patches.  For example, a cycle includes a patch that requires it be installed by itself (based on the coding of the patch from Microsoft).  The patch install scripts will be written such that the some patches will be included in one install script and other patch(es) will be included in a different install script.  These two scripts are all part of the same Automatic Update cycle, they just require separate processing.  In this case, the first install script will execute on the third Saturday of the month.  The first Sunday at 10pm after that first install script executes (which would likely be the day following the patches in that first install script), Reboot Action will fire and reboot the computer.  This patch cycle STILL has additional patches to install.  The additional patches will begin to fire after the reboot.  Let's say those patches complete by 1am on Monday morning.  The next Sunday, Reboot Action will recognize patches have been installed and Reboot Action will fire.  This would, theoretically, be on the fourth Sunday of the month.  This reboot would be valid since it's still working off of the install cycle that began the third Saturday of the month.   This is a less common occurrence, but it does happen when multiple install scripts are required for a single patch cycle, and something to keep in mind.  

  • Brande,

    Thank you for that caveat and explanation.  Very helpful.