A Maintenance Window defines a period during which system maintenance occurs on a device. Business Unit configurations include Maintenance Window settings so administrators can schedule maintenance activities. OneSite Patch installs patches only during the defined Maintenance Window.
Maintenance Windows can include one or more schedules that deploy based on urgency settings (Low, Normal, High, and Critical). Urgency settings are cumulative, so higher urgencies inherit any settings specified at lower urgencies.
Overlapping time settings do not have a restrictive effect, but Adaptiva recommends keeping your Maintenance Window time settings simple. When a patch encounters multiple time settings for Maintenance Windows, it reviews one after another until it finds a match.
OneSite Patch provides built-in Start Time objects, available from the following path:
Schedules\Patching Schedules\Window Start
-
Select Maintenance Windows in the left navigation menu of the OneSite Patch Dashboard, and then click Show All to display the available Maintenance Window settings.
Important
When choosing a Maintenance Window template, be sure to consider whether patch installation requires a restart. A narrow Maintenance Window can cause the restart to occur after the Maintenance Window ends.
-
Select the Name of an existing template to open it, and then save the template with a new Name:
A Dynamic Detection workflow sets the patching Maintenance Window based on the selected workflow rather than a set schedule. For more information, enter a support ticket and request help from Adaptiva Customer Support.
When enabled (default) all patches use the same Maintenance Window based on the highest level of urgency.
-
Select + Create Maintenance Window in the Maintenance Windows by Urgency section of the Maintenance Window template.
-
Select Apply to All Urgencies to enable or disable using the same Maintenance Window settings for all urgencies:
-
If you enable this setting (default) you do not need to create a Maintenance Window for all urgencies. Skip to Save and Deploy the Maintenance Window.
-
If you disable this setting, continue to Create a Maintenance Window.
-
To set a Maintenance Window to deploy patches that have Low and Normal urgency settings and ignore patches with High and Critical urgency settings, leave the High and Critical urgency settings in their respective default settings of NULL.
The configurations use the same template requirements to create a single maintenance window for all urgencies or to create individual windows for specific urgency levels. The difference between where you access the appropriate templates is whether you choose the enable Apply to All Urgencies to create a single maintenance window or disable it to create individual maintenance windows for each urgency level.
-
Select + Create Maintenance Window in the Maintenance Windows by Urgency section of the Maintenance Window template.
-
Select Browse next to Add Schedule, and then expand the Patching Schedules folder to see available schedules.
-
Select a schedule that sets the start time for the Maintenance Window, and then click Add Schedule to close the dialog.
-
Enter the number of Hours, Minutes, or Seconds until the Maintenance Window closes, and then click Create Maintenance Window.
An override duration for the All Urgencies Maintenance Window sets the amount of time to wait for the Maintenance Window to open for all urgency level updates. After this time, the system overrides the Maintenance Window setting.
Enter the number of Hours, Minutes, or Seconds to wait for the Maintenance Window to open before allowing an override.
You must deploy a Maintenance Window to make it available for use in a template. If you update a Maintenance Window template that was previously deployed, you must save and deploy it again for the changes to take effect.
-
Complete the Maintenance Window configuration (see Open and Save a Maintenance Window Template).
-
Select Save & Deploy to save and deploy your configuration:
-
If you want to deploy later, click Save.
-
Be sure to return and Deploy the Maintenance Window template to make it available for use.
-
Comments
0 comments
Article is closed for comments.