Patch Mgmt > Reboot Action
This function defines what happens at the end of each patch installation. After a patch installs, the machine needs to be rebooted before the patch takes effect. This function lets you define when that reboot occurs.
The patch installation script runs at the scheduled time and performs the following steps:
Downloads (or copies from a file share) all the patch files to a local drive (same drive as the agent is installed on).
Executes each patch file, one at a time.
Performs the selected reboot action described below.
Note: Service packs are always installed separately. If a service pack is also scheduled, it installs first, the machine reboots, then any additional patches are installed.
Note: Patches will not take effect until the machine next reboots.
Warning: It is strongly recommended that the Reboot Action for the Agent on the KServer be set to "Do not reboot after update"! Automatic rebooting of the KServer can have adverse effects on other KServer processes!
Reboot immediately after update.
Reboots the computer immediately after install completes.
Reboot <day of week> at <time of day> after install
After the patch install completes the computer is reboot at the selected time of day and day of week. Use this setting to install patches during the day when users are logged in (to get the UNC path) and then force a reboot in the middle of the night. Selecting every day reboots at the next specified time of day following the patch installation.
Warn user that machine will reboot in N minutes (without asking permission).
When the patch install completes, the message below pops open warning the user and giving them N minutes (you may pick any number of minutes you like) to finish up what they are doing and save their work. If no one is currently logged in, the system reboots immediately.
Skip reboot if user logged in.
Skips the reboot, after the patch install completes, if the user is logged in. Use this setting to not interrupt your users and rely on then rebooting later or shutting down their computer at the end of the day.
If user logged in ask to reboot every N minutes until the reboot occurs.
This setting displays the message below to ask the user if it is OK to reboot now. If no one is at the computer or they answer no, the same message appears in N minutes (you may pick any number of minutes you like) until the system has been rebooted. If no one is currently logged in, the system reboots immediately.
If user logged in ask permission. Reboot if no response in N minutes. Reboot if user not logged in.
This setting displays the message below to ask the user if it is OK to reboot now. If no one is at the computer, it reboots automatically after N minutes (you may pick any number of minutes you like) without saving any open documents. If no one is logged in, reboot immediately.
If user logged in ask permission. Do nothing if no response in N minutes. Reboot if user not logged in.
This setting displays the message below to ask the user if it is OK to reboot now. If no one is at the computer, the reboot is skipped. If no one is logged in, reboot immediately.
Do not reboot after update
Does not reboot. Use this if you users typically shut down their computer every night. You can rely on this behavior to reboot the machine for you. If the machine is a server that you do not want to reboot you can be notified via email when a new patch has been installed by checking Email when reboot required and filling in an email address.