Reboot Action

Patch Management > Reboot Action

• This page applies to the following products: On Premises, Kaseya Advanced, Kaseya Essentials, IT Center

The Reboot Action page defines how reboots are performed after a patch install. Patch installs do not take effect until after a machine is rebooted. The Reboot Action policy applies to Machine Update, Patch Update and Automatic Update. It does not apply to Initial Update. See Methods of Updating Patches, Configuring Patch Management, Patch Processing, Superseded Patches, Update Classification and Patch Failure for a general description of patch management.

Warning: It is strongly recommended that the Reboot Action for agents installed on the KServer and the database server used by the KServer be set to Do not reboot after update. Automatic rebooting of the KServer or database server can have adverse effects on other KServer processes!

Patch Process

The patch installation procedure 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, typically the same drive the agent is installed on.
• Executes each patch file, one at a time.
• Performs a reboot of the machine, as specified by this page.

  Note: If you schedule multiple patches for installation on the same machine, all the patches are installed at the same time. After all the patches have been installed the machine reboots once. This technique saves time and reboots.

  Note: Service packs are always installed separately. If you are installing a service pack with other patches you will see a reboot after the service pack install and then another single reboot after all the other patches are installed.

View Definitions

You can filter the display of machine IDs on any agent page using the following options in View Definitions.

• Show machines that have/have not rebooted in the last N periods
• Machines with Reboot Pending for patch installations

Apply

Click Apply to apply parameters to selected machine IDs.

Reboot immediately after update.

Reboots the computer immediately after the install completes.

Reboot <day of week> at <time of day> after install.

After the patch install completes, the computer is rebooted at the selected day of week and time of day. Use these settings to install patches during the day when users are logged in, then force a reboot in the middle of the night. Selecting every day reboots the machine 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 a specified number of minutes 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.

If the user is logged in, the reboot is skipped after the patch install completes. Use this setting to avoid interrupting your users. This is the default setting.

If user logged in ask to reboot every <N> minutes until the reboot occurs.

This setting displays the message below, asking the user if it is OK to reboot now. If no one is at the computer or they answer no, the same message appears every N minutes repeatedly, 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, asking the user if it is OK to reboot now. If no one is at the computer, it reboots automatically after N minutes without saving any open documents. If no one is currently logged in, the system reboots 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, asking 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. Typically used if the machine is a server and you need to control the 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. You can also format the email message by clicking the Format Email button. This option only displays for master role users.

The following types of patch reboot emails can formatted:

• Patch Reboot

  Note: Changing the email alarm format changes the format for all Patch Reboot emails.

The following variables can be included in your formatted email alerts and in procedures.

Run select agent procedure before machine is rebooted

If checked, the selected agent procedure is run just before the machine is rebooted.

Run select agent procedure after machine is rebooted

If checked, the selected agent procedure is run just after the machine is rebooted.

Select All/Unselect All

Click the Select All link to check all rows on the page. Click the Unselect All link to uncheck all rows on the page.

Check-in status

These icons indicate the agent check-in status of each managed machine. Hovering the cursor over a check-in icon displays the agent quick view window.

Online but waiting for first audit to complete

Agent online

Agent online and user currently logged on.

Agent online and user currently logged on, but user not active for 10 minutes

Agent is currently offline

Agent has never checked in

Agent is online but remote control has been disabled

The agent has been suspended

Edit icon

Click the edit icon next to a machine ID to automatically set header parameters to those matching the selected machine ID.

Machine.Group ID

The list of Machine.Group IDs displayed is based on the Machine ID / Group ID filter and the machine groups the user is authorized to see using System > User Security > Scopes.

Reboot Action

The type of reboot action assigned to each machine ID.

Topic 358: Send Feedback. Download a PDF of this online book from the first topic in the table of contents. Print this topic.