Patching Strategies are the central management objects in Adaptiva because they group the details that define how, when, and where to update patches. Adaptiva includes prepopulated templates that address most patching scenarios. You can save these templates using your own titles and descriptions, and then customize them to your environment.
Each Patching Strategy uses building blocks that can include Schedules, Notifications (Chains), Deployment Channels, and Bots to define a given patching scenario. At minimum, a Patching Strategy must include a Patching Process and a Deployment Bot.
Functionally, a Patch Strategy performs the following:
Automated handling of new patches
Automatically discovers new patches and uses the Deployment Bot to match new patches to the Patching Strategy. The Patching Process queues patches for processing and, according to the set schedule, activates patch deployment in groups to minimize the impact on endpoints and end users.
Customized targeting of patches
Administrators can target specific products and high-profile patches that trigger a Deployment Bot based on individual products. Targeting is particularly useful when you first install Adaptiva, you have a considerable number of products that require patching, and you prefer to review the progress of patching before fully automating the process.
Reuse Intent Schema Objects
All objects in Adaptiva are interoperable and designed for use in any Patching Strategy. Create a patching process, schedule, notification or approval chain, or deployment process once, and then use them in various Patching Strategies depending on your needs.
These built-in strategies are often enough to get an organization started with a patch deployment scenario.
Effective management and deployment of software patches is crucial for maintaining the security and stability of an IT infrastructure. The Patching Strategies included in address various deployment scenarios and considerations.
Recommended Use
You can choose a Patching Strategy template, save it under a descriptive local naming convention, and then customize it as needed. Patching Strategy templates reference objects that include the minimum requirements for a successful patching strategy: Deployment Wave, Deployment Bot, and Patching Process.
recommends creating a folder to hold all new or customized strategies. This separates them from the strategies provided with the product.
Patching Strategy templates cater to four specific use cases: Approval Types, Rollout Scheduling, User Interaction Settings, and Rollout Phasing. When deciding which Patching Strategy to choose, consider the following example to understand naming:
By offering various combinations of these parameters, the templates are a versatile framework that can accommodate a wide range of patching scenarios.
Minimal customization includes adding the products to patch and a schedule. This flexibility allows for efficient patch management without the need for extensive customization or the creation of new strategies.
-
Approval Type: Level of approval needed prior to deployment:
-
No Approval: Deploys at once.
-
Initial Approval: Requires approval prior to deploying.
-
Phased Approval: Requires approval between each wave in the Deployment Waves object.
-
-
Rollout Scheduling: Defines the schedule and impact of a deployment.
-
Immediate: All product patches deploy at once.
-
RiskBased: Targeted and controlled deployment based on specific risk levels (low, medium, high, critical). Schedule and run patch deployments based on risk levels. Uses Deployment Channels.
-
-
User Interaction: Defines permitted user actions related to the patch installation.
-
Mandatory: Alerts the end user who can postpone depending on User Interaction Settings but cannot decline. All product patches deploy at once.
-
Options: Alerts the end user. Otherwise, functionality not available in this release.
-
-
Rollout Phasing: Deploys in separate phases to allow a review before continuing.
-
Minimal customization includes adding the products to patch and a schedule.
-
This flexibility allows for efficient patch management without the need for extensive customization or the creation of new strategies.
-
Each of these strategies requires an approval step before deploying updates. Except for Risk Based Mandatory Deployment, the Patching Process within these strategies manages the deployment process exclusively and does not use Deployment Channels.
Similarly, the Deployment Bot does not apply any filtering mechanism, so the Patching Process manages all updates related to the products included in the non-risk strategies.
-
Initial Approval - Immediate Mandatory Deployment
Approval required prior to deployment, then deploys at once with no user interaction.
-
Initial Approval - Immediate Mandatory Phased Deployment
Approval required prior to deployment, then deploys at once in a phased manner, rolling out to each wave of business units sequentially with no user interaction control.
-
Initial Approval - Immediate Optional Deployment
Approval required prior to deployment, then deploys at once in a phased manner, rolling out to each wave of business units sequentially. User interaction allowed.
-
Initial Approval - Risk-Based Mandatory Deployment
Approval required prior to deployment, and then deploys at once to all devices in the targeted business units based on the patch risk levels.
Uses both Deployment Waves and Deployment Channels. Higher-risk updates have priority in high-frequency Deployment Channels. Lower-risk updates belong to lower-frequency Channels.
Also uses Deployment Bot to filter patches based on risk level, and then sends the final wave to the proper Deployment Channels.
Ensures processing and deployment of the final wave through the most suitable Deployment Channel and adds a layer of control and customization to the deployment process.
Each of these strategies requires no approval before deploying updates. Except for Risk Based Mandatory Deployment, the Patching Process within these strategies manages the deployment process exclusively and they do not use Deployment Channels.
Additionally, the Deployment Bot does not apply any filtering mechanism, so the Patching Process manages all updates related to the products included in the non-risk strategies.
-
No Approval - Immediate Mandatory Deployment
No approval needed prior to deployment. Deploys at once with no user interaction.
-
No Approval - Immediate Mandatory Phased Deployment
No approval needed prior to deployment. Deploys at once in a phased manner, rolling out to each wave of Business Units sequentially. No user interaction.
-
No Approval - Immediate Optional Deployment
No approval needed prior to deployment. Deploys at once to all devices in the targeted business unit. User interaction allowed.
-
No Approval - Risk-Based Mandatory Deployment
No approval needed prior to deployment. Deploys at once to all devices in the targeted business units based on the patch risk levels. No user interaction.
Uses both Deployment Waves and Deployment Channels. Higher-risk updates have priority in high-frequency Deployment Channels. Lower-risk updates belong to lower-frequency Channels.
Also uses Deployment Bot to filter patches based on risk level, and then sends the final wave to the proper Deployment Channels.
Ensures processing and deployment of the final wave through the most suitable Deployment Channel and adds a layer of control and customization to the deployment process.
Each of these strategies requires phased approvals before deploying updates. Except for Risk Based Mandatory Deployment, the Patching Process within these strategies manages the deployment process exclusively without using Deployment Channels.
Similarly, the Deployment Bot does not apply any filtering mechanism, so the Patching Process manages all updates related to the products included in the non-risk strategies.
-
Phase Approval - Immediate Mandatory Phased Deployment
Approval required between each wave of the deployment, and then deploys the updates in a phased manner, rolling out to each wave of business units sequentially. No user interaction.
-
Phase Approval - Risk-Based Mandatory Deployment
Approval step required between each wave of the deployment, and then deploys the updates at once to all devices in the targeted business units based on risk levels. No user interaction.
A Patching Strategy template contains specific fields that you can configure to make a unique Patching Strategy for your environment. Adaptiva recommends opening an existing strategy that contains most of the configuration items you want, and then saving it with a new name and description. The configuration options are the same whether you create a new strategy or modify an existing strategy.
-
Follow the instructions in Create a New Folder for Objects.
-
Hover over or click Strategy in the left navigation menu of the Dashboard, and then select Patching Strategies.
-
Select
Patching Strategies, and then select Show All to see all available Patching Strategies.
For descriptions of each template type, see Patching Strategy Templates.
-
Select the Name of a strategy to open it.
-
Select More in the upper left corner of the template, and then select Save As:
-
Enter a unique name that reflects what the strategy does conceptually. For example,
ITS Immediate Daily Product Patching. -
Select Save as on the bottom left corner of the dialog. This opens your strategy template with all the default entries for the built-in strategy, including a detailed description.
-
Enter a detailed Description of your new template or keep the existing detail, and then click Save on the upper-left corner of the dialog.
-
Tip
Remember to click Save on the upper left corner to save your progress as you make changes. After completing the Patching Strategy configuration, you must save and enable the completed strategy to make it available for use.
In , configuration options provide several opportunities to select or exclude software products for a patching strategy. Options include include making product sections when creating a strategy, exempting products from business units, and more.
For more information about the products available with , see Software Products.
-
Scroll to the Products workspace in an open Patching Strategy template. The image below shows the default settings.
-
Select the Include All Products toggle to enable it.
The following image shows the default settings and options when you select Include All Products.
-
Select Save on the upper left corner of the strategy:
-
Choose one of the following options to continue managing products:
-
To exclude specific products for this strategy, see Exclude Products from a Patching Strategy
-
To include specific platforms, see Include or Exclude Platforms in a Patching Strategy
-
-
Scroll to the Products workspace in an open Patching Strategy template. The image below shows the default settings.
-
Select + Browse to open the Select Software Product table:
-
Select Save on the upper right corner of the Patching Strategy:
After enabling Include All Products from the Products workspace in an open Patching Strategy, you have the option to exclude individual products for the same Patching Strategy.
Important
When you add Business Units to a Strategy, the Patching Exceptions set for the Business Unit take precedence over the Product settings in the Patching Strategy.
When you enable Include All Products from the Products workspace in an open Patching Strategy, you also include all platforms by default.
-
Select + Browse to open the Select Software Product table:
-
Select the Include All Platforms toggle to disable it and view the available Platforms.
-
Decide which platforms to include:
-
To include all Platforms, either Select All or select the Include All Platforms toggle to enable it.
-
To include specific Platforms, select those you want to include.
-
-
Select Save on the upper left corner to keep your changes:
Adaptiva provides several Trigger Metadata Properties..
If a trigger metadata property changes in a given patch, and the patch meets each of the requirements below, the Patching process re-presents the patch to the Patching Strategy.
The changed patch must:
-
Belong to a product in the strategy
-
Be applicable on at least one device.
-
Have been presented previously.
The first table you see shows all available trigger properties.
-
In the Select Trigger Properties table of the Trigger Metadata Properties dialog, select one or more properties to use as triggers:
-
To find a specific trigger, enter a trigger name on the Search line, and then select Search.
-
To sort the list of Trigger Properties, click Property to reverse the alphabetical support order.
-
To page through the available trigger properties, use the navigation tools on the bottom-right of the dialog.
-
-
Select OK on the bottom-left corner of the dialog to save your selections and return to the Patching Strategy template.
-
Scroll down to Trigger Metadata Properties in an open Patching Strategy template. If the Patching Strategy includes Trigger Metadata Properties, the table under +Select lists those properties.
-
Select the ellipsis (…) under Actions for the trigger you want to remove, and then select Remove.
-
Select Save on the upper-left corner of the Patching Strategy to save your changes.
Deployment settings in a Patching Strategy include choosing a Deployment Wave, Creating a Deployment Bot Runtime configuration, and choosing whether to present each patch to the first matching Deployment bot only (defaults to disabled). When customizing an existing Patching Strategy (recommended), settings may include tables with configuration selections other than the default.
Begin by adding a Deployment Wave.
-
Select Browse next to Deployment Wave in the Deployment Settings workspace of an open Patching Strategy template.
This opens the All Deployment Wave dialog.
-
Select a Deployment Wave from the list.
-
Adaptiva provides a Single Wave-All Clients Deployment Wave, which includes a Business Unit called All Clients Business Unit.
-
If you are following the tasks in Introduction to Patching Strategies, choose Single Wave-All Clients.
-
-
Select OK on the bottom left of the dialog to return to the Patching Strategy.
Important
When updating an existing Patching Strategy with a new Deployment Wave, the system prompts you with a recommendation to specify Business Unit Addition Settings.
-
Select OK to close the recommendation. The system returns you to the Patching Strategy at the Business Unit Addition Settings workspace:
-
If you are following the tasks in Introduction to Patching Strategies, skip to Add Software Products. There is no need to modify the Deployment Bot Runtime settings for purposes of this exercise.
-
If you are creating or modifying a Patching Strategy for ongoing use, continue with the next step.
-
-
Choose whether to specify Business Unit Addition Settings (recommended), if prompted by the system.
-
To continue with Deployment Settings, see Deployment Bot Runtime Settings. You may configure Business Unit Addition Settings later in the template.
-
To complete Business Unit Addition Settings now, see Business Unit Addition Settings.
-
In Patching Strategy templates, the Create Deployment Bot Runtime dialog provides a single location to add processes to your Patching Strategy. Use these settings for more advanced operations. For example, when you have multiple Business Units that require the same Patch Deployment Bot but use a different Patching Process and schedule, you can create multiple Deployment Bot Runtime combinations to patch according to different requirements.
After adding a Deployment Wave to the Patching Strategy Deployment Settings, you can configure Deployment Bot Runtime scenarios. Follow these procedures for each Deployment Bot Runtime you need to create. If you need to create a Deployment Bot, see Creating Deployment Bots.
See also:
Bots – Patch Deployment and Notification Bots
Deployment Channels and Deployment Channel Processes
Business Units and Rollout Processes
Before creating a Deployment Bot Runtime, select a Deployment Wave to enable the Create Deployment Bot Runtime selection.
-
Select + Create Deployment Bot Runtime from the Deployment Settings workspace of an open Patching Strategy template.
This opens the Create Deployment Bot Runtime dialog:
-
Begin by adding a Patch Deployment Bot.
-
Select Browse next to Patch Deployment Bot to open the Select Patch Deployment Bot dialog.
-
Choose a method for viewing Patch Deployment Bots:
-
Select
-
Select a Filtered by: setting beneath
-
-
Select the template you want to use. For example, in Filtered by: Known Exploit, select Mandatory Install (Known Exploit Exists).
-
Select OK on the bottom left of the dialog to return to the Create Deployment Bot Runtime template.
-
Select Browse next to Add Patching Process in the Create Deployment Runtime dialog.
-
Select
-
Select the process you want to use. For example, select Immediate Phased Deployment – Initial Patch Manager Approval).
-
Select OK on the bottom left of the dialog.
Important
The Business Units you add here must be the same Business Units included in the Patching Strategy Deployment Wave. If you select other Business Units here or select All Business Units, the Patching Strategy will take no action on those that do not match the Deployment Wave settings.
-
Decide whether to include all Business Units in this Deployment Bot Runtime, or to add specific Business Units:
-
To include all Business Units, click the Include All Business Units toggle to enable running this configuration on all Business Units (defaults to disabled), and then skip to step 3.
-
To choose specific Business Units for this Runtime, click + Browse, and then continue with the next step.
-
-
Select one or more Business Units to add to this Runtime. For example, to use this Runtime on all Windows 11 systems using a Wi-Fi connection, select Operating System – Windows 11 and Office Type – WiFi.
-
Select OK on the bottom left of the dialog to view the completed Runtime Bot.
-
Select Create Deployment Bot Runtime on the bottom-left corner of the dialog to return to the Patching Strategy.
-
Return to Create Deployment Bot Runtime Scenarios to add more Deployment Bot/Patching Process pairs to this Patching Strategy.
After creating a Deployment Bot Runtime, set the runtime schedule for each Patching Process.
-
Select the ellipsis (…) under Actions in the Patching Process Settings table of an open Patching Strategy template, and then select Edit Process Setting.
-
Add one or more schedules for the process:
-
Select + Browse next to Execution Schedules.
-
Select
-
Select one or more schedules to use for the Process Setting runtime, and then select OK on the bottom left corner of the dialog.
All Deployment Bot Runtime pairs that use the same Patching Process in this Patching Strategy run on the schedules you choose.
-
Enter the number of Hours, Minutes, and Seconds that the patching process may run before timing out. Zero indicates no time limit.
-
-
Select OK, to return to the Patching Strategy workspace.
This toggle switch enables or disables whether the Patching Strategy stops presenting patches to Deployment Bots as soon as it discovers the first matching Deployment Bot. If you choose to enable this behavior, be sure to order the Bots in your Deployment Bot Runtime from most important to least.
-
Scroll down to the bottom of the Deployment Settings workspace of an open Patching Strategy.
-
Select the Present each Patch only... toggle to enable or disable (default) whether the Patching Strategy stops presenting patches to later Bots after discovery of a matching Bot.
-
Select Approval Chains to open the Approval Chains workspace.
-
Select Browse next to the type of Approval chain you want to add (Product Owner, Patch Management, Security, and so on).
-
Select an Approval Chain from the Approval Chains table.
-
Select OK to return to the object template.
-
Repeat Steps 2 through 4 for each of the groups listed in the Approval Chains workspace:
-
Skip any groups that do not apply to your situation.
-
When each group from which you need an approval contains an approval chain, continue with the next step.
-
-
Select Save at the upper left to save your progress:
Patching Strategy, Deployment Channel, and Business Unit objects include a Notifications dialog where you can configure notification details. The configuration choices differ slightly for each object.
Important
This configuration requires selecting a specific type of Notification Cycle template. Contact Adaptiva Customer Support for assistance with this configuration and for information about choosing the correct template.
Notification Chain settings exist in the object templates for Patching Strategies, Deployment Channels, and Business Units.
-
Expand the Notifications box in an open object template to show the available configuration options.
-
Select Browse next to Notification Chain. This opens the Notifications Chain dialog.
-
Select
-
Select a Notification Chain from the table. To edit or create Notification Chains, see .
-
Continue editing the Notification settings or click on the bottom left corner to return to the template.
Both Patching Strategies and Deployment Channel templates have an option to Add Patch Notification Bots.
-
Select + Browse next to Patch Notification Bots in the Notifications workspace of the object template.
This opens the Select Patch Notification Bots dialog.
-
Select
-
Choose one or more Notification Bots to set requirements for this template. To create more Notification Bots, see Creating Notification Bots.
-
Select OK on the bottom left of the dialog to return to the starting template.
These values must match the corresponding values defined in the Notification Bots. Otherwise, the Notification Cycle does not send a notification.
Execution Schedules control when and how often a Notification Cycle sends notifications. Choose schedules based on when and how often receiving parties require notification.
-
Select + Create Notification Setting from the Notifications workspace of a object template.
-
Select +Browse next to Execution Schedules to display the available schedules.
-
Select one or more schedules from the All Schedules table, and then select OK on the lower-left corner of the dialog.
-
Continue editing the notification settings or click to return to the template.
When enabled, sends notifications to the Roles shown in the Notification Chain associated with the Patching Strategy or Deployment Channel template. Defaults to disabled.
-
In the + Create Notification Setting dialog in the Patching Strategy or Deployment Channel template, decide whether to enable notifications:
-
Select the Notify Patching Strategy Chains toggle to enable or disable (default) whether the notification cycle sends notifications to the chains included in the strategy.
-
Select the Notify Business Unit Chains toggle to enable or disable (default) whether the notification cycle sends notifications to Business Unit chains included in the strategy.
-
-
Continue editing the Notifications settings or click to return to the template.
This setting names the Notification Cycle that processes the Notifications for the Patching Strategy or Deployment Channel. Notification Cycle workflows are customized for specific uses. Adaptiva does not provide sample Notification Cycle templates. These templates exist only if you create them for your environment.
Important
Contact Adaptiva Customer Support for assistance with Notification Cycle templates.
-
Select + Create Notification Setting from the Notifications box in the object template.
This opens the Create Notification Setting dialog.
-
Select Browse on the Add Workflow line. This opens the list of available workflows.
-
Select your custom workflow from the list, and then click Add Workflow on the lower-left corner of the dialog.
-
Continue editing the Notification settings or click to return to the template.
Specifies the maximum length of time that the Notification Cycle Workflow runs before timing out. If set to all zeros (default) the workflow may run indefinitely. Choose this setting with care. If the notification times out before sending all notifications, the next cycle triggers the notifications again.
-
Select + Create Notification Setting the Notification box of the object template.
-
Next to Time Limit, set the Hours, Minutes, or Seconds that the Notification Cycle will run, or leave the setting default at 0 for each item to allow the workflow to run indefinitely.
-
Continue editing the Notification settings or click to return to the template.
Customer Extension Data is an advanced feature of Adaptiva. The Customer Extension Data fields allow advanced users to specify different key/value pairs for use in customized Patching Strategies, Deployment Chains, or Business Units when necessary to achieve different results.
Customer Extension Data fields relate directly to fields in a customized template. If you do not have customized templates with key/value pairs you can modify, you do not need to configure or use this feature.
If you want to create customized templates that use key/value pairs for some settings, contact Adaptiva Customer Support.
The Content Prestaging feature deploys content to devices ahead of the scheduled deployment, either pushing content to a location or allowing a client to pull content. Prestaging content makes the content available on the device locally when the deployment time arrives. This reduces the deployment time and minimizes the chances of missing service windows or having devices going offline before a content download finishes.
You can create Content Prestaging Settings within the Patching Strategy, Business Unit, or Deployment Channel templates.
The templates for Patching Strategies, Deployment Channels, and Business Units include the choice to set Content Prestaging settings. Settings default to Not Enabled.
Content Prestaging settings include two options:
-
Server Content Push (Recommended) – The Adaptiva pushes the content to the best-suited sources in all locations that require the content.Adaptiva recommends this type of prestaging when the Deployment Strategy targets only a subset of devices. High-availability machines receive the content and function as local sources during discovery and deployment.
-
Client Content Pull – This option enables any client that requires the content to download and cache it before deployment. Suitable when a Deployment Strategy targets all clients that need the updated content.
Push Content
-
Not Enabled -- Disables any prestaging as part of the Patching Process workflow or Patching Strategy.
-
Handled by System – The Adaptiva system handles the prestaging automatically and pushes content to three automatically chosen devices within the office that require the content.
This push occurs at once when the metadata updates include the latest content that meets patching requirements.
-
Handled by Workflow – When enabled as part of a Patching Process, Deployment Channel, or Business Unit template, pushes the content upon deployment of the Patching Process.
Pull Content
-
Not Enabled -- Disables any prestaging as part of the Patching Process workflow or Patching Strategy.
-
Handled by System – The Adaptiva system handles the prestaging automatically. The Client pulls content from the Server and instructs all Clients that require the content to download and cache it ahead of any deployment.
-
Handled by Workflow – When enabled as part of a Patching Process, Deployment Channel, or Business Unit template, the Client pulls the content upon deployment.
Use this procedure to add or change Content Prestaging Settings in Patching Strategy, Business Unit, or Deployment Channel templates.
-
Expand the Notifications box in an open object template, and then scroll down to the Content Prestaging Settings.
-
Expand the Content Prestaging Settings box to view the available settings.
Client Content Pull defaults to Not Enabled. To enable pull settings, complete the following steps in the Content Prestaging Settings of a Patching Strategy, Business Unit, or Deployment Channel template:
-
Select the arrow to the right of Client Content Pull to expand the menu of available options.
-
Select the option you need for the object template you are using. For definitions of push options, see Defining Content Prestaging Settings.
-
Select Save on the upper left to save your changes:
Server Content Push defaults to Not Enabled. To enable push settings, complete the following steps in the Content Prestaging Settings of a Patching Strategy, Business Unit, or Deployment Channel template, complete the following steps:
-
Select the arrow to the right of Server Content Push to expand the menu of available options.
-
Select the option you need for the object template you are using. For definitions of push options, see Defining Content Prestaging Settings.
-
Select Save on the upper left to save your changes:
Business Unit Addition Settings do not have a separate menu item. Configure these settings from the Business Unit Addition Settings dialog in a Patching Strategies template.
When you have added a new Business Unit to an enabled Patching Strategy that has already completed the current patching cycle, you must use the Business Unit Addition Settings to add the parent Business Unit that contains the details, such as Patches and Patch Approval Settings, any Business Unit added to the Strategy will inherit.
The Business Unit you specify here includes the patch approvals the Patching Strategy will use for any Business Units you add to the Strategy after the Strategy has run.
The Patching Process you select here is the same process you identified in the Deployment Bot Runtime configuration of the Patching Strategy.
-
Select Strategy > Patching Strategies from the left navigation menu of the Patch Dashboard.
-
Scroll down to Business Unit Addition Settings and then click the right arrow to expand the box.
Specify the parent Business Unit for this strategy so that when new Business Units become part of the strategy after it has already run, the new Business Units inherit settings from the same parent.
-
Select Browse next to Template Business Unit in the Business Unit Addition Settings dialog of an open Patching Strategy template.
-
Select the Business Unit that has the parent settings for any future Business Units added to the Strategy.
-
Click OK to return to the template.
-
Select Save on the upper left to save your changes:
Important
If you came to this procedure while you were configuring Deployment Settings in a Patching Strategy, return to Deployment Settings to continue the Strategy configuration.
Identify the Patching Process that controls the approval and deployment logic for the existing Business Units in this strategy. This is the same Patching Process identified in the Deployment Bot Runtime, which is the only Patching Process you can choose here. This ensures that any Business Units added after initial creation of this strategy use the same Patching Process as the existing Business Units.
-
Verify that the Deployment Bot Runtime details are accurate. The Patching Process settings needed for Business Unit Addition settings are the same as those used in the Deployment Bot Runtime.
-
Select Browse next to Patching Process in the Business Unit Additions dialog of an open Patching Strategy. If Browse is disabled, check the Deployment Bot Runtime Settings.
-
Select the available Patching Process, and then click OK.
-
Select Save on the upper left cornerto save your changes:
After completing the Patching Strategy configuration, including Add Software Products, you must enable the Patching Strategy. When enabled, the strategy runs according to the configured schedules.
After you Enable the Patching Strategy, you can view the pending approval request.
-
Select the Approval Requests in the left navigation menu of the Dashboard.
-
The view defaults to All requests, which includes pending and completed.
-
The Patching Strategy you just enabled appears in the Approval Summary table with a Request Status of In Progress and Awaiting Response.
-
-
Select Flex Controls > Cycle Operations > Patching Cycles from the left navigation menu of the Dashboard.
-
Check the Running Patch Processes table, which lists the status of the Patching Strategy as Waiting.
-
Select Approval Requests in the left navigation menu, and then click the Patching Strategy in the table.
-
Select Approve, and then click Back to Approval Requests. You can wait until the patch time passes, or you can start the deployment manually.
After the Patching Strategy approval process status shows Completed, you can wait until the time setting for patch deployment, or you can start the deployment immediately.
-
Select Flex Controls > Patching Cycles, and then click the name of the Patching Strategy to open the Cycle Information.
-
Select Play
under Cycle Information, and then click Close. This returns you to the Patching Cycles workspace where you can view Running Patch Processes.
-
Select the Patching Strategy name to view details about the patching process.
OneSite Patch provides simplified processes to manage and modify Patching Strategies that you have already enabled. From an open, enabled Patching Strategies, the More menu contains the following options:
-
Select Strategy > Patching Strategies, and then navigate to the enabled strategy you want to submit.
-
Select the strategy Name to open it.
-
Select More, and then select Submit Patches. This opens the dialog for the selected strategy.
-
Choose one of the following options:
-
To create approvals, select the Create Approvals toggle to enable Patch Approvals, and then select + Create Patch Approval. See Approvals for Adding Patches.
-
To choose patches, select + Browse, and then see Select Installable Software.
-
to Enabled Patching Strategies
When you submit patches to an enabled strategy, you may also create approvals specific to the individual patch. Otherwise, the patching process and bots create the approvals automatically based on the process or bot settings.
The Create Approvals functionality requires at least one approval scenario. You must create separate approvals for each patch you choose to add to an enabled patch.
Approvals in this instance consist of the following, required settings:
-
Identify the patches or software that require approval.
-
Set the state and urgency for the approval.
-
Add a Patching Process
-
Add Business Units
You may also add a Deployment Channel (optional).
Complete the required fields in the Create Patch Approval dialog. The dialog already includes the name of the Patching Strategy you chose to modify.
-
Select + Browse for Patch to select the patch to add. This opens a software selection table.
-
Select the Desired State for the patch approval, and then select the Urgency (Low, Normal, High, Critical):
-
Add a Patching Process (required) and a Deployment Channel (optional):
Tip
Add a Deployment Channel only when you have included it in the Deployment Bot Runtimes section of the Patching Strategy Deployment Settings.
-
(Required) Select Browse next to Patching Process, and then select a process from the table.
-
Select OK to return to the patch approval dialog.
-
(Optional) Select Browse next to Add Deployment Channel, and then select a channel from the table (see Tip above).
-
Select OK to continue creating the approval.
-
-
Select + Browse next to Business Units to open the dialog.
-
Complete the approval for the selected patch:
-
Select Create Patch Approval. The patch submission now includes a table that lists the patch you selected.
-
(Optional) Return to Step 1 to create a patch approval for another patch.
-
Select OK to return to the dialog.
-
-
Select Strategy > Patching Strategies, and then navigate to the enabled strategy you want to resubmit.
-
Select the strategy name to open it.
-
Select More, and then select Re-submit Patches. This opens a table of applicable patches for the selected strategy.
-
Select the patches you want to resubmit with this strategy, and then click OK.
-
To verify the status of your Approval Request, see Approval Requests.
In , configuration options provide several opportunities to select or exclude software products for a patching strategy. Options include include making product sections when creating a strategy, exempting products from business units, and more.
For more information about the products available with , see Software Products.
-
Scroll to the Products workspace in an open Patching Strategy template. The image below shows the default settings.
-
Select the Include All Products toggle to enable it.
The following image shows the default settings and options when you select Include All Products.
-
Select Save on the upper left corner of the strategy:
-
Choose one of the following options to continue managing products:
-
To exclude specific products for this strategy, see Exclude Products from a Patching Strategy
-
To include specific platforms, see Include or Exclude Platforms in a Patching Strategy
-
-
Scroll to the Products workspace in an open Patching Strategy template. The image below shows the default settings.
-
Select + Browse to open the Select Software Product table:
-
Select Save on the upper right corner of the Patching Strategy:
After enabling Include All Products from the Products workspace in an open Patching Strategy, you have the option to exclude individual products for the same Patching Strategy.
Important
When you add Business Units to a Strategy, the Patching Exceptions set for the Business Unit take precedence over the Product settings in the Patching Strategy.
When you enable Include All Products from the Products workspace in an open Patching Strategy, you also include all platforms by default.
-
Select + Browse to open the Select Software Product table:
-
Select the Include All Platforms toggle to disable it and view the available Platforms.
-
Decide which platforms to include:
-
To include all Platforms, either Select All or select the Include All Platforms toggle to enable it.
-
To include specific Platforms, select those you want to include.
-
-
Select Save on the upper left corner to keep your changes:
Comments
0 comments
Article is closed for comments.