Maintenance window configuration options

Maintenance window settings control which actions devices can perform, how reboots are handled, and when maintenance activities run. These settings help manage feature behavior, minimize user impact, and schedule maintenance to meet operational requirements.

Maintenance options

Define which features and actions can run during the maintenance window.

  • Name: Enter a descriptive name.
  • Features (Scheduled Maintenance (Features)): Select the features and actions allowed to run during the maintenance window. Features and actions that are not selected cannot run while the window is active. Each feature exposes a predefined set of actions, including Install, Upgrade, Update, and Reboot.

Reboot options

Control reboot behavior and notifications during the maintenance window.

Reboot method

Determines how reboots are enforced:

  • Allow user to postpone beyond the maintenance window: Allows the reboot to be delayed after the window ends.
  • Force user to reboot in the maintenance window: Allows the user to postpone until the end of the window. The device reboots automatically after the window closes.
  • Force reboot without user notification: Restarts the device immediately without notification.
  • Reboot only if accepted: Restarts the device only if a logged-in user accepts the request.

Prompt and countdown

Specifies how long the reboot warning is displayed. If not postponed, the device reboots when the countdown ends.

  • Message from: Sender name shown in the reboot notification

    • Default: Uses the system-defined sender name.
    • Custom: Uses a custom sender name.
  • Message: Specifies the text shown in the reboot notification.

    • Default: Uses the system-defined message.
    • Custom: Uses a custom message, which can include variables including {CustomerName}.

    The message should explain why the reboot is required and allow time to save work.

  • Place device in downtime during reboot: Suppresses monitoring notifications while the device is restarting.

  • Force device out of downtime after: Removes the device from downtime if it does not come back online within the specified time.

  • Save current system state: Preserves the desktop state so open windows and files are restored after reboot (supported operating systems only).

Schedule configuration

Define when maintenance actions run and how long the maintenance window remains active.

A reboot can be scheduled as:

  • recurring

  • one-time

The one-time maintenance window is removed after the reboot completes.

  • Maintenance window duration: Specify how long the window remains active.

  • Schedule Type: Select Recurring or Once.

  • Start Date and Start Time (Once): Set when the maintenance window runs.

  • Schedule (Recurring): Set when the maintenance window starts and how often it runs.

A one-time reboot cannot be scheduled for a date and time in the past.

Identifying One-Time and Recurring Reboots

In the Maintenance Windows list:

  • One-time schedules display as: Once at HH on

  • Recurring schedules display as: HH every

Common use cases for one time reboots

  • Schedule a one-time reboot after deploying operating system or application updates.

  • Restart devices after a software installation that requires a reboot to complete configuration.

  • Perform maintenance-related reboots outside business hours without creating a recurring schedule.

  • Schedule a single reboot as part of troubleshooting or corrective actions.

Related articles