# User Interaction Settings

These settings use Toast notifications and can be configured to remain persistent. A User Interaction configuration may use the same settings for all urgencies or use them separately for individual urgency settings (Low, Normal, High, and Critical).

{% hint style="info" %}
Currently, user interaction notifications are not available for Linux devices.
{% endhint %}

![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-72c20a8f86700b8eee212dd346f0c3ff64242dd7%2Fgeneral-toast-notification.png?alt=media)

## Open and Save a User Interaction Template

1. Select **Advanced Settings > User Interaction Settings** in the side navigation menu and then select **Show All**.

   ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-cb4fead3674df9212cd35e02359cee1a93e156ed%2Fall-user-interaction-settings.png?alt=media)
2. Select the Name of an existing template to open it. This example uses the *Deployment & Reboot - 1 Hour Warning (Anytime)*\* template.
3. Save the template with a new name:

   a. In the upper-left of the dialog, select **More**, and then select **Save As**.

   b. Enter a new name for the template, and then select **Save as**. This returns you to a copy of the template with the new name.

   c. Enter a detailed **Description** of the process covered in this template, or leave the prepopulated description. Add a character to enable the **Save** button, and then select **Save**.

## Choose Urgency Settings

1. Scroll down to **User Interaction Settings** in an open User Interaction Settings template:
   * **Apply to All Urgencies**
     * When enabled, you have the option to create a single set of urgency settings that apply to all urgency levels (Low, Normal, High, and Critical).
   * **Apply to All Urgencies**

     * When disabled, you have options to create urgency settings for each level.

     ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-dabb4b87c6fe74a92a0fd0acde6589471455f2d0%2Fapply-to-all-urgencies-disabled.png?alt=media)
2. Select the **Apply to All Urgencies** toggle to enable or disable setting urgencies for all levels.

## Deployment Notification Settings

1. Select [**Edit Urgency Settings**](#choose-urgency-settings).
2. Select the toggle for **Notify User Before Installation** enable user notification when a deployment begins.
3. Click **+** next to **Starting Notification**.
4. Set the **Notification Suppression Duration** to the number of Days, Hours, Minutes, or Seconds before the user receives another notification.
   * For example, if the user sees and chooses 5 minutes, the client waits 5 minutes before allowing another deployment notification to pop up.
   * When set to zero (0), the user does not receive any delay options.
5. Enter **Notification Text** in the text box. The user sees this text when the notification arrives on their device.
6. Enable **Notify User On Completion** if you would like to send a completion notification upon success or failure.
7. Click **+** next to **Completion Notification**

   ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-29544988f1b4fe030b3765dddbd8345cb4bc73fc%2Fdeployment-notification-settings.png?alt=media)

## Reboot Notification Settings

The Reboot Notification Settings in a User Interaction Settings dialog provides choices to Suppress Reboots and to Notify User Before Reboot.

Enabling **Suppress Reboots** means that system automated reboots do not occur. Users must reboot their devices at their own discretion to complete patch deployments. Failure to reboot may prevent a deployment to that device. Use caution when suppressing reboots.

Enabling **Notify User Before Reboot** allows you to customize user notifications when a deployment requires a device reboot. Configuration options for administrators include the following:

* Prevent users from dismissing notifications.
* Schedule reboot only during maintenance windows.
* Customize reboot deadline and postponement options (Days, Hour, Minutes, Seconds).
* Prevent or allow snooze duration and customization.

  ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-df746637c1d165414a2d883c16b1640a43f52cd9%2Freboot-settings.png?alt=media)

### Configure Reboot Settings

While this document is mostly about user interaction settings, you should also read [Maintenance Windows in Business Units](https://docs.adaptiva.com/patch/patching-fundamentals/business-units#maintenance-windows-in-business-units). It is possible to set rules that counteract each other. Review the table below:

| **Notify User Before Reboot** enabled? | **Perform Reboot Only During a Maintenance Window** enabled? | Deployment window defined? | Reboot window defined? | Resulting device reboot behavior                  |
| -------------------------------------- | ------------------------------------------------------------ | -------------------------- | ---------------------- | ------------------------------------------------- |
| No                                     | N/A                                                          | N/A                        | N/A                    | Device can reboot anytime                         |
| Yes                                    | No                                                           | N/A                        | N/A                    | Device can reboot anytime                         |
| Yes                                    | Yes                                                          | No                         | N/A                    | Device will never reboot                          |
| Yes                                    | Yes                                                          | Yes                        | No                     | Device reboots only during the maintenance window |
| Yes                                    | Yes                                                          | Yes                        | Yes                    | Device reboots only during the reboot window      |

With **Notify User Before Reboot** enabled, you may set other conditions related to the reboot. These include notification dismissal, rebooting during maintenance window, and reboot deadline.

1. Select the **Perform Reboot Only During Maintenance Window** toggle to enable or disable reboot during the maintenance window established in the Business Unit that includes the device:
   * Enable to reboot only during the maintenance window.
   * Disable to allow reboot at any time.
2. Select the **Prevent Notification Dismissal** toggle to enable or disable whether the client device user may dismiss the notification:
   * Enable to prevent the user from dismissing the notification.
   * Disable to allow the user to dismiss the notification.
3. Enter the number of **Days, Hours, Minutes, or Seconds** to set the Reboot Deadline.

* These entries define the amount of time that may pass before the system forces the reboot to occur.
* If zero, OneSite Patch provides no warning to the user.

The image below is the reboot notification a user will see from their perspective:

![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-ddf1cdb66398094e760b034f1de17b3182a5906e%2Freboot-notification.png?alt=media)

#### Warning

{% hint style="warning" %}
If you change the Business Unit associated with an endpoint, the endpoint will inherit the rules from its new Business Unit. The change may trigger immediate patching or reboot.
{% endhint %}

See also [Maintenance Windows in Business Units](https://docs.adaptiva.com/patch/patching-fundamentals/business-units#maintenance-windows-in-business-units).

## Managing Snooze Settings

When defining User Interaction Settings, OneSite Patch provides several configuration choices that define how a user interacts with reboot notifications and snooze settings. With Allow Snooze enabled, the user receives notification of a required reboot and may snooze the notification. This does not change the reboot deadline. Rather, it allows the user to snooze the notification for a set period of time that does not exceed the Reboot Deadline.

Administrators set the parameters of the user interaction by setting maximum snooze duration times, snooze reminders, and snooze durations. You may customize all snooze option settings to timing that meet your requirements.

The Snooze Duration's default settings are shown below. If you do not specify a snooze duration (all settings 0), the default settings apply. The combination of default settings for Snooze Duration will not exceed the Maximum Snooze Duration setting. For example, setting the maximum duration to 30 minutes, limits the end user choices for snooze options to 5 minutes or 15 minutes.

## Configure Snooze Settings

Customize user interactions with reboot notifications by allowing snooze, and then setting snooze durations and snooze reminders. For details about default settings and limitations, see Managing Snooze Settings.

1. Select the toggle for **Allow Snooze** to enable or disable snooze options.

   ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-aefd39729839cb076cace77e2320010217a9f2c0%2Fsnooze-settings.png?alt=media)

* When enabled, you may define the timing of user interactions reboot notifications.
* When disabled, the user receives no notification.

1. Define the Snooze settings:

   a. **Maximum Snooze Duration**: This is the maximum amount of time the user may snooze the reboot.

   * Enter the **Days**, **Hours**, **Minutes** or **Seconds** that define the **Maximum Snooze Duration** (defaults to 8 hours).

   b. **Snooze Reminder** settings: Sets the amount of time between the notifications the user receives after the first snooze.

   * Enter the **Days**, **Hours**, **Minutes** or **Seconds** that define the **Snooze Reminder** gap (defaults to 6 hours).

   c. **Snooze Duration**. Leave settings at zero (0) to use the default settings.

   * Enter the **Days**, **Hours**, **Minutes** or **Seconds** that define the **Snooze Duration** (defaults to 4 hours, 2 hours, 1 hour, 15 minutes).
2. Select **+Add** to create additional **Snooze Duration** settings. You may add up to 5 additional lines.
3. Select **OK** on the bottom left corner to return to the User Interaction Settings workspace.

## Interfering process notification settings

![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-da61430aa80b8915f9e39075c098399a56e5e234%2Finterfering-process-notification-settings.png?alt=media)

When **enabled**, this will not show users any notifications asking them to choose applications that interfere with patch deployment. If **disabled** you can configure the following:

* **Time Until Force Termination** - Set time (days, hour, minutes, seconds) before the application is forcibly terminated.
* **Allow Snooze** - Allow the notification to be snoozed for a period of time.
* **Show Persistent Notification** - Shows a notification that cannot be closed by the user.
* **Notification Title** - Notification window title.
* **Notification Text** - Notification message with dynamic macros.
  * Dynamic macros allow you to enter a variable placeholder that will populate with the appropriate data when the notification is received. These macros can be copied from the **Notification Text** tooltip. There are four dynamic macros available that include:
    * **{patchName}** - Name of the patch that requires interfering process to terminate.
    * **{productName}** - Name of the product that requires interfering process to terminate.
    * **{version}** - Version of the patch.
    * **{interferingApps}** - Applications that will be required to close before patching.

      ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-a88ba36e66e9dc1d31ae5f44f92bed50453e8ce1%2Fdynamic-macros.png?alt=media)
* **Terminate Button Text** - Text displayed for termination button.

  ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-eb6999930a08e6049a027c1367688753382d3889%2Finterfering-termination.png?alt=media)

Once this is set up, you should receive a Toast notification that looks similar to:

![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-51c052db3fb3993c1af98f63b0f50555e85da8bf%2Fterminate-toast-notification.png?alt=media)

## Save and Deploy User Interaction Settings

After creating and configuring or editing User Interaction Settings, you must deploy them. Otherwise, the User Interaction Settings are not available in the list of templates when you add **User Interaction Settings** to a Business Unit.

* Save your changes:
  * Select **Save & Deploy** to save and deploy your configuration:
  * Select **Save & Deploy** to save and deploy your changes.
  * Select **Save** to save your changes without deploying. Be sure to return and **Deploy** the changes to make them available for use.

    ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-5e7190f4a47d87a9d3f4a3d51d63f7a000e9ba75%2Fimage15.png?alt=media)