Does anyone have any examples to share for how to run a baseline on reboot one time thru a schedule?
The challenge i am trying to overcome:
Windows Servers 2012-2022
- Some application updates like MS SQL Server don’t always install without a reboot first
- there may be pending actions requiring a reboot, which the SQL MSI see’s and just exits
- other applications require pre-reqs which require a reboot before cleanly updating.
-
I have several servers that their support teams do not allow automated reboots. Aka they want to be logged in and shutdown the app and initiate the reboot
a. current patching process runs as much of the patch cycle as possible without reboot and exits.
typically failing to install a few updates due to the queue of actions pending a reboot to complete -
The app teams don’t necessarily want to look for, or accept ‘offers’ when presented.
It would be nice to target a baseline to only start on system startup, which it then could install updates, and reboot again as needed with a final reboot to let all services be normal. I also understand that typically the BES Client is run as “delayed start” which may or may not need to be changed to avoid delays in running updates on boot?
I know there are ‘windows startup’ and ‘windows shutdown’ options in local policy and potentially a few other things. Before i make a mountain out of this, anything people can share for the cleanest and safest way to handle this flow, being that these are Servers and accidental boot loops, or other issues related to this configuration may be very public would be appreciated.
Thank you