The "Interactive Reboot" built-in service will initiate an interactive flow notification based to involve the logged in endpoint user with the needed reboot operation.

Operating Systems

The Interactive Reboot built-in service supports all Windows Servers (via pop-up) and Windows Desktops (via toast notification)

Note - To generate notifications, JetPatch needs to register an application (jetpatch_enduser_app.exe) to the Windows start menu.

Interactive Reboot Settings

The JetPatch Administrator can control the following Interactive Reboot task settings by clicking the "Edit" action on the Interactive Reboot task:

1. Notification Count - the number of times a user can snooze/ignore the reboot notification (5 by default)
2. Notification Timeout (Mins) - the number of minutes for a notification to be shown (60 by default). If there is no response from the endpoint user after the specified timeout, a new notification will be shown.
3. Allow the user to cancel the reboot - A flag to allow the user to cancel the reboot, or not.
4. Start reboot procedure only if reboot is needed - Before raising any notifications for the Interactive Reboot, the JetPatch Agent (Connector) will check if a reboot is needed. If a reboot is not needed it will not continue to the interactive flow.

Interactive Reboot Flow

Interactive Reboot can be executed as part of Workflows or as an independent task.

If a reboot is required, the endpoint user will encounter a JetPatch notification asking him to perform a reboot to his computer.  In JetPatch, a pending reboot suspension will be applied. 

The endpoint user will have several options on the notification itself - 

1. Reboot Now - The Connector will initiate a reboot to apply the changes in 2 minutes after the user confirmation.
2. Snooze - Notification is dismissed and will be shown again after 4 hours.
3. Cancel - The user will be able to cancel the reboot by clicking on the "Cancel" button.
   Note - This option will be available only if the "Allow the user to cancel the reboot" flag is marked

If the endpoint user will reach the limit of notifications that are allowed to be snooze, the next notification will be prompt the user that a reboot was initiated and will perform in 15 minutes. The only options that available for the user in this notification is Reboot Now and Cancel (if it was configured to allow the endpoint user to cancel the reboot)

For example - Notification Count is set for 2 -

1. At 01:00 PM notification (#1) is raised and the user clicking on "Snooze" option
2. 4 hours later, at 05:00 PM, another notification (#2) is raised with the same format as the first one. The user clicks on Snooze again.
3. 4 hours later, at 09:00 PM, another notification is raised but this time it's warning the user for an upcoming reboot, in the next 15 minutes.

Examples

Minimum Employee Interruption

The environment administrator wants to reboot the workstations in 24 hours, but reduce the notification interruption for the current working employee.

• Settings:
  • Notification Count = 6
  • Notification Timeout = 240 (minutes)
  • Allow the user to cancel the reboot = unmarked
• Explanation:
  • In any case of notification ignored or a user chooses to snooze the reboot, four hours later another notification will be shown, up to 6 times. After 24 hours all workstations will perform a reboot (unless the user didn't chosen to do the reboot by himself)

Reboot in one hour if no user is using the endpoint

The environment administrator wants to reboot the unused workstations in one hour, while the workstations that are used can be rebooted later.

• Settings:
  • Notification Count = 3
  • Notification Timeout = 20 (minutes)
  • Allow the user to cancel the reboot = unmarked
• Explanation:
  • If a user is not working on the endpoint - 3 notifications will be shown at 20 minutes intervals, and after an hour a reboot will happen.
  • If a user is working - the user will be able to snooze the notification 3 times to 12 hours in total.

Notes

• Interactive Reboot task can be selected in a Workflow only as the last task for Post-Patching task.
• JetPatch will write logs to the "Logs & Alerts" in "Platform Configuration", describing the endpoint user actions/decisions and interactive reboot flow.
• Activities table - the "Interactive Reboot" activity can be seen in the Activities table as any other activity in JetPatch. A successful status for the "interactive Reboot" means that
  • Connector didn't raise any notification to the endpoint user because a reboot is not needed (only applicable if the "Start reboot procedure only if a reboot is needed" setting is selected)
  • Connector raised the first notification successfully and is now waiting for the user's decision.
• Snooze times will be available in the future.
• Endpoints without an active or idle user will be automatically rebooted.