Flex Control settings include the functions listed in the table below. These options provide added flexibility when creating and managing Patching Strategies.
Blacklisting |
Provides an extra level of protection for customer devices and patching processes. Prevents the download and installation of potentially damaging content to customer devices. See Blacklisting. |
Cycle Operations |
Includes access to Patching, Deployment, and Rollout Cycle details. Details include a graphical representation of any cycles in progress and a table that lists details for each cycle in progress. Also includes a graphical representation of previously completed cycles and a table that lists a each completed cycle. Select each completed cycle to review details. See Cycle Operations. |
Exceptions |
Allows administrators to exclude Business Units from specific updates on certain products or to use settings to maintain all endpoints at a specific version of a product. See Patching Exceptions. |
Global Pause |
Use Global Pause to pause or resume all patching activities for specified software products and patches. Affects all clients contained in one or more specified Business Units. See Global Pause. |
Rollbacks |
Create a Rollback object to rollback one or more patches to a system determined or specified version. See Rollbacks. |
Adaptiva OneSite Patch includes an extra level of protection for customer devices and patching processes called Blacklisting. The Adaptiva metadata team, as always, reviews all metadata that vendors provide for their new products and patches to verify relevance and integrity.
When a vendor releases products and patches, the Adaptiva metadata team reviews the content and determines whether the patch has any issues that might cause unexpected behavior. The team blacklists patches and products that have issues and automatically creates an exclusion for the patch on all clients. Blacklisting prevents the download and installation of potentially damaging content to customer devices.
The Blacklist Settings workspace provides configuration options for Notifications and Communication Providers. The Notification Chains and Communication Providers configured from this workspace identify the process and delivery of communications related to blacklisted patches. See Managing Blacklist Notification Settings.
Set categories of notification by selecting a Notification Chain to use when Adaptiva blacklists a patch/release. Select the same or different Notification Chain to notify administrators when you blacklist a patch or a release. You can also select specific communication providers for either category of notification.
Blacklist Settings include notification details for blacklisted patches including Notification Chains and Communication Providers. You can use the Adaptiva provided details (Adaptiva Curated) or create your own (Customer). Update these settings as needed for your notification preferences.
-
Navigate to Blacklist Settings.
-
Select Browse next to either Adaptiva Curated Chain or the Customer Chain to list the available Notification Chains. If you need to create a new Notification Chain for these purposes, see Create a Notification Chain.
-
Select the Name of the Notification Chain you want to use for whichever field you are editing – the Adaptiva Curated Chain or the Customer Chain.
-
Select Add Notification Chain on the bottom left of the dialog.
-
Navigate to Blacklist Settings.
-
Select + Add Communication Providers for either Adaptiva Curated Communication Providers or Customer Communication Providers from the Blacklist Settings.
-
Select one or more Names from the Communications Provider table, and then click Add Communication Providers at the bottom left of the dialog.
If you need to add providers to the table, see Create a New Communication Provider.
Blacklisted Patches provides an Adaptiva table and a Customer table. Adaptiva populates the Adaptiva table with all patches that Adaptiva has blacklisted. The Customer table becomes populated when customers add their own blacklisted patches. See Managing Blacklisted Patches.
When a vendor issues a deficient or erroneous patch, Adaptiva blacklists the metadata and notifies customers automatically about the blacklisted patch. Blacklisting prevents inclusion of the patches in Patching Strategies and automatically creates an exclusion for the patch on all clients.
If Adaptiva determines that the vendor has fixed a blacklisted item, the metadata team can revoke the blacklisting. When the updated metadata arrives at the customer device, OneSite automatically removes the patch from the Blacklist, making it available for deployment.
You may not remove a patch from the Adaptiva blacklist. Although strongly discouraged by Adaptiva, you can ignore the Adaptiva recommendations, suppress the blacklisted status, and move forward with inclusion of the patch in your environment.
Customers may also create their own Blacklist for products they do not want deployed in their environment. Customers are responsible for managing their own blacklisted patches.
-
Mouse over or click Flex Controls on the menu, and then select Blacklisting > Blacklisted Patches.
-
Select Blacklisted Patches, and then select Patches.
-
Expand the Blacklisted Patches folder, and then select either the Adaptiva folder or the Customer folder to view blacklisted patches. This example uses the Adaptiva folder.
This displays the list of Adaptiva Blacklisted Patches.
-
Select the Customer folder to view patches blacklisted by the customer.
When you enable Removed from Blacklist in an Adaptiva Blacklisted Patch template, you are expressly allowing clients in your environment to install a patch that Adaptiva has found deficient or erroneous.
Caution
Adaptiva does not recommend removing blacklisted patches.
-
Navigate to the table of Adaptiva Blacklisted Patches (View Blacklisted Patches), and then click the Name of the blacklisted patch you want to suppress. This opens to General Settings in the template.
-
Select the Removed from Blacklist toggle to enable removal of this patch from the blacklist. Defaults to disabled.
Caution
Enabling customer suppression means you expressly choose to ignore this blacklist recommendation from the Adaptiva metadata team.
-
Select Save, and then click <-- Back at the upper left to return to the list of blacklisted patches.
A Customer Blacklist is a customer created list of patch exceptions that applies globally to all customer devices. The red asterisk next to the field name indicates a required field.
-
Navigate to the table of blacklisted patches (View Blacklisted Patches).
-
Select the Customer folder to view the table of patches blacklisted by the customer. Until you add patches, this table is blank.
-
Select + New to add a patch to the blacklist table.
-
Enter a Name and Description for the patch you intend to blacklist.
-
Select Browse next to add Installable Software in the Blacklist Settings of an open Blacklisting template (Add a Patch to Customer Blacklisted Patches).
This opens the Add Installable Software dialog with a list of all available software or patches.
-
Select the Name of the patch to blacklist, and then click Add Installable Software at the bottom left of the dialog.
-
Enter the following information:
-
Name of the person blacklisting this patch
-
Email of the person blacklisting this patch.
-
Describe the reason for the blacklisting of this patch.
-
Enter the vendor URL, if known (optional).
Although you can see the Adaptiva Curated patch toggle on the page, you cannot change this setting because you are creating a customer curated patch.
-
-
Select Save on the upper left:
Includes access to Patching, Deployment, and Rollout Cycle details. Details include a graphical representation of any cycles in progress and a table that lists details for each cycle in progress. Also includes a graphical representation of previously completed cycles and a table that lists a each completed cycle. Select each completed cycle to review details. See Cycle Operations.
Details available for each cycle type include the following:
-
Cycle Information: Provides general information about the Patch Process such as the Current State, the creation date and time, and the Patch Process schedule. This section also contains controls to manually start, stop, or delay a Patch Process.
-
Overall Metrics: This section contains information about the scope of the running process. This screen shows the number of business units and devices affected by this Patch Process, along with Urgency information.
-
Cycle History: This section gives a historical perspective of the results of past runs. This view will show the number of devices that previously were successful, failed, aborted, timed out, or errored.
-
Patch Approvals: One of the key functions of a Patch Process is to execute Approval Chains as defined in the Patching Strategy or Business Unit. This section displays pending Approvals. You cannot grant approvals from this view.
-
Cycle Logs: Display events relating to the Patch Process. For instance, the Cycle Operation Logs can show the administrator who manually started a Patch Cycle and at what time.
This dashboard shows information about the active Patch Processes in the environment. Patch Processes represent the workflow that models and performs the defined patching routine. As part of the overall Patching Strategy, Patch Deployment Bots use configured criteria to identify patches that apply to endpoints. Once approved, the Bot submits those patches to the Patch Process, which creates a Patch Cycle. The Patch Cycle executes at either a scheduled time or you can start it manually.
-
Mouse over or click Flex Controls on the Home menu, and then select Cycle Operations > Patching Cycles.
This opens to the Running tab of the Patching Cycles workspace:
-
The Total Running Patch Processes widget shows an aggregate summary of all patch processes and their corresponding states (Waiting, In Progress, or Paused).
-
The Running Patch Processes table lists the running Patching Strategies by name.
-
-
Enter a Patching Strategy name on the search bar above the Running Patch Processes table, and then click Search.
-
Select the Patching Strategy name in the Running Patch Processes table to see specific details about that process.
-
Mouse over or click Flex Controls in the Home menu, and then select Cycle Operations > Patching Cycles.
-
Select History on the upper left to change to the History tab:
-
The Total Finished Patch Processes widget on top shows an aggregate summary of all completed patch processes and their corresponding states (In Progress, Succeeded, Failed, Aborted, Timed Out, Error Occurred).
-
The Running Patch Processes table lists the completed patch processes by Patching Strategy name.
-
-
Enter a Patching Strategy name on the search bar above the Running Patch Processes table, and then click Search.
-
Select the Patching Strategy name in the Running Patch Processes table to see specific details about that process.
This dashboard shows information about currently running Patch Deployment Channel Processes and the history of completed patch processes. These details show the status of all active Deployment Processes.
-
Mouse over or click Flex Controls in the Home menu, and then select Cycle Operations > Deployment Cycles.
This opens to the Running tab of the Deployment Cycles workspace:
-
The Total Running Deployments widget shows an aggregate summary of all patch processes and their corresponding states (Waiting, In Progress, or Paused).
-
The Running Deployments widget table lists the running Deployment Strategies by name.
-
-
Enter a Deployment Strategy name on the search bar above the Running Patch Processes table, and then click Search.
-
Select the Deployment Strategy name in the Running Patch Processes table to see specific details about that process.
-
Mouse over or click Flex Controls in the Home menu, and then select Cycle Operations > Deployment Cycles.
-
Select History on the upper left to change to the History tab:
-
The Total Running Deployments widget shows an aggregate summary of all deployment processes and their corresponding states (Waiting, In Progress, or Paused).
-
The Running Deployments widget table lists the completed Deployment Strategies by name.
-
-
Enter a Deployment Strategy name on the search bar above the Running Patch Processes table, and then click Search.
-
Select the Deployment Cycle name in the Finished Deployments table to see specific details about that process.
Rollout Processes represent the installation of Patches per Business Unit. Each Business Unit involved in the Patch Deployment includes a Rollout Cycle.
-
Mouse over or click Flex Controls on the Home menu, and then select Cycle Operations > Rollout Cycles.
This opens to the Running tab of the Rollout Cycles workspace:
-
The Total Running Rollout Cycles widget on top shows an aggregate summary of all running Rollout processes and their corresponding states (Waiting, In Progress, Paused).
-
The Running Rollout Cycles table lists the completed patch processes by Rollout name.
-
-
Enter a Rollout Cycle name on the search bar above the Running Rollout Processes table, and then click Search.
-
Select the Rollout Cycle name in the Running Rollout Processes table to see specific details about that process.
-
Mouse over or click Flex Controls on the Home menu, and then select Cycle Operations > Rollout Cycles.
-
Select History on the upper left to change to the History tab:
-
The Total Running Deployments widget shows an aggregate summary of all deployment processes and their corresponding states (Waiting, In Progress, or Paused).
-
The Running Deployments widget table lists the completed Deployment Strategies by name.
-
-
Enter a Rollout Cycle name on the search bar above the Running Rollout Cycles table, and then click Search.
-
Select the Rollout Cycle name in the Finished Cycles table to see specific details about that process.
When Business Units require exemption from specific updates on certain products, or the entire enterprise requires maintenance of a specific version of a product, Patching Exceptions provide a mechanism for creating and implementing these rules.
OneSite Patch includes two options: Desired State Override and Last Allowed Version. In the Patching Exceptions template, you choose the strategy you need, configure the product patches or version, and add Business Units. Configure each option separately to use multiple overrides in one template, and last version in another template.
Desired State Override Options
-
Mandatory Install: Allows endpoints to treat the Patch as mandatory.
-
Do Not Install: Allows endpoints to skip installation of a particular Patch.
-
Rollback: Forces a specific patch version even if OneSite Patch detects higher versions on endpoints.
-
Uninstall: Removes the Patch/Product from endpoints in the specified Business Unit.
Last Allowed Version
Specifies a patch level to consider current and ignores all more recent patches or versions. When specified, the Last Allowed Version sets the state for all patches or releases that are a later version than the one specified to do not install.
-
Select Flex Controls from the menu, and then select Exceptions > Patches.
-
Select + New on the upper-right corner to open a Patching Exception template.
-
Name and describe the exception:
-
Enter a descriptive Name for this exception in the Name field.
-
Enter a detailed Description of the purpose for this exception.
-
-
Select Save on the upper left to save your new template:
-
Choose an Override Strategy:
-
If you choose Override Desired States, see Set Override Details for Patch Exception.
-
If you choose Select Last Allowed Versions, see Set Last Allowed Patch Versions.
-
Important
Choose only one software version per override exception.
-
Select Override Desired States (default) as your Override Strategy in an open Patching Exception template.
-
Select the type of Desired State Override , such as Mandatory Install, and then click +Add Installable Software for that state.
-
Select the tab for either Software Patches (default) or Software Releases to run your search. You may add selections from both tabs to a single override state as long as they are for the same version of software.
-
Select Save on the upper-left corner of the dialog to save your changes:
-
Continue to Add Target Business Units.
-
Choose Select Last Allowed Versions as your Override Strategy in an open Patching Exception template. Defaults to disabled.
-
Select +Add Version Patches to open the Add Version Patches dialog.
-
Select the Search field, and then enter the release name of the product you want to override:
-
Select Search.
-
Select one or more products for the patch exception. You may add items from both Software Patches and Software Releases tab.
-
Select Add Version Patches.
-
-
Select Save on the upper-left corner of the dialog to save your changes:
-
Continue to Target Business Units.
Use this procedure to select one or more Business Units to which the exception applies. With no Business Units specified, the Patching Exception applies to all endpoints where the specified Patches apply.
-
Select + Add Business Units in an open Patching Exception template.
-
Select one or more Business Units to add to the exception.
-
Select Add Business Units at the lower-left corner of the dialog.
-
Select Save at the upper left to save your progress:
Global Pause settings take effect immediately on the clients you identify either globally or within the selected Business Units. Patch cycles continue to run as configured on the Adaptiva Server side, and the Adaptiva Client pauses the deployment of patches identified in the pause settings.
The Global Pause menu item provides access to both a
button and access to configuration details for pausing patch activity for specific products, patches, cycles, or Business Units.When activated, OneSite Patch revokes the Global Pause request and restores normal patching activity to all licensed clients.
immediately stops all patch deployments across all licensed clients. When deactivated ( )In addition, you may create pause configurations for each of the following:
: Pause patch deployments for specified products either globally or for specific Business Units.
: Pause patch deployments for specified patches either globally or for specific Business Units.
: Pause Patching, Deployment, or Rollout Cycles either for specified Business Units or for the Business Units already targeted by the Cycle.
: Pause all patches for specified Business Units.
To stop all patching activity on all licensed clients in the estate, use the following steps to activate
.-
Select Flex Controls on the menu, and then select Global Pause.
This opens the Global Pause dialog:
-
Select Pause All Patching.
-
Select Save to activate Global Pause. This immediately stops all patch deployments across all licensed clients:
-
All patch deployments in progress that have not reached an irreversible state are paused immediately.
-
All newly initiated patch deployments are paused automatically.
-
To resume all paused patching activity on all licensed clients, use the following steps to revoke a
.-
Select Flex Controls on the menu, and then select Global Pause.
This opens the Global Pause dialog:
-
Select Resume Patching.
-
Select Save to revoke the Global Pause. This immediately revokes the Global Pause and allows patching activity to occur as configured.
To stop patching activity for specific objects, such as Products, Patches, Cycles, and Business units, use the following steps to access the
menu items:-
Select Flex Controls on the menu, and then select Global Pause.
This opens the
menu: -
Select the pause you want to configure. You can configure multiple types of pauses, but you must configure them separately.
-
Global Pause: Pause all patching activity immediately (Stop All Patching Activity Immediately).
-
Paused Products: Pause patch deployments for one or more products (Pause Deployment of a Specific Software Product).
-
Pause Patches: Pause deployment of a software patch or release for one or more products (Paused Patches).
-
Paused Cycles: Specify a Patching, Deployment, or Rollout cycle to pause for one or more products.
-
Pause Business Units: Pause patch deployments for one or more Business Units.
-
To stop patching activity for specific software products or patches, complete the following steps:
-
Navigate to the Pause Patching for Specific Objects), and then select Paused Products.
menu (seeThis opens the
dialog:-
Select +Create Product Pause to open the Create Product Pause dialog:
-
Select Browse to find the software product to pause.
-
Select the software product you want to pause using either of the following methods:
-
Use the navigation tools on the bottom right to scroll through the pages and select one or more Software Products from the table.
-
Enter a product name on the search line, and then click Search to find a specific product
-
-
-
Select Add Software Product to return to the Create Product Pause dialog, and then choose one of the following methods to proceed:
-
To create a Global Pause for the selected products, click Create Product Pause. This pauses the deployment of the selected software product on all devices in the estate.
-
To specify a pause for specific devices, continue with the next step to Add Business Units.
-
-
Add or remove Business Units:
-
To remove existing Business Units, select the ellipsis (...) under Actions, and then select Remove Row.
-
To add Business Units, complete the following steps:
-
-
Select Create Product Pause and then click Save to create a global pause for the selected products.
To stop patching activity for a specific patch, complete the following steps:
-
Navigate to the Pause Patching for Specific Objects), and then select Paused Patches.
menu (seeThis opens the
dialog:-
Select +Create Patch Pause to open the Create Product Pause dialog, and then select Browse to find the Software patch you want to pause:
-
Select Browse to find the Software Patch to pause:
-
Select the patch you want to pause:
-
-
Select Add Installable Software Product to return to the Create Patch Pause dialog, and then choose one of the following methods to proceed:
-
To create a Global Pause for the selected products, click Create Patch Pause. This pauses the deployment of the selected software patch on all devices in the estate.
-
To specify a pause for specific devices, continue with the next step to Add Business Units.
-
-
Add or remove Business Units:
-
To remove existing Business Units, select the ellipsis (...) under Actions, and then select Remove Row.
-
To add Business Units, complete the following steps:
-
-
Select Create Patch Pause and then click Save to create a global pause for the selected patch.
OneSite Patch allows you to create Patching Cycles, Deployment Cycles, and Rollout Cycles to customize patching in your estate. Global Pause provides a way to pause these cycles when necessary. You may create a pause for one cycle at a time.
Important
Pausing a cycle that is currently in a WAITING state (has not run yet), prevents that cycle from running until you remove the pause. This is the only server-side behavior related to pausing.
To stop patching activity for a specific patching cycle, complete the following steps:
-
Navigate to the Pause Patching for Specific Objects), and then select Paused Cycles.
menu (seeThis opens the Paused Cycles dialog to the Patching tab:
-
Select +Create Cycle Pause to open the Create Cycle Pause dialog, and then click Browse.
-
Search for and select the patching cycle you want to pause using one of the methods described below:
Important
Cycles do not appear unless you have created them previously. If you do not have a cycle to stop, do not complete this section.
-
Use the navigation tools on the bottom right to scroll through the pages to find and select a Patching Cycle from the table.
-
Enter a cycle name on the search line, and then click Search to find and select a specific cycle.
-
-
Select OK, and then choose one of the following options to proceed:
-
To create a Global Pause for the selected cycle, skip to Step 6. This pauses the deployment of the selected cycle on all devices in the estate.
-
To specify a pause for specific devices, continue with the next step to Add Business Units.
-
-
Add or remove Business Units:
-
To remove existing Business Units, select the ellipsis (...) under Actions, and then select Remove Row.
-
To add Business Units, complete the following steps:
-
-
Select Create Cycle Pause and then click Save to create a pause for the selected cycle.
To stop all patching activity for a specific deployment cycle, complete the following steps:
-
Navigate to the Pause Patching for Specific Objects), and then select Paused Cycles.
menu (seeThis opens the Paused Cycles dialog to the Deployment tab:
-
Select +Create Cycle Pause. This opens the Create Cycle Pause dialog:
-
Select Browse to open the Select a Deployment Cycle dialog, and then use one of the methods below to find and select a cycle.
Important
Cycles do not appear unless you have created them previously. If you do not have a cycle to pause, choose a different pause method.
-
Use the navigation tools on the bottom right to scroll through the pages to find and select a cycle from the table.
-
Enter a cycle name on the search line, and then click Search to find and select a specific cycle
-
-
Select OK to save your entry, and then choose one of the following options to proceed:
-
To create a Global Pause for the selected cycle, skip to Step 6. This pauses the deployment of the selected software product on all devices in the estate.
-
To specify a pause for specific devices, continue with the next step to Add Business Units.
-
-
Add or remove Business Units:
-
To remove existing Business Units, select the ellipsis (...) under Actions, and then select Remove Row.
-
To add Business Units, complete the following steps:
-
-
Select Create Cycle Pause and then click Save to create a pause for the selected cycle.
To stop all patching activity for a specific rollout cycle, complete the following steps:
-
Navigate to the Pause Patching for Specific Objects), and then select Paused Cycles.
menu (seeThis opens the Paused Cycles dialog to the Rollout tab:
-
Select +Create Cycle Pause. This opens the Create Cycle Pause dialog:
-
Select Browse to select the rollout cycle you want to pause. This opens the Select a Rollout Cycle dialog.
Important
Cycles do not appear unless you have created them previously. If you do not have a cycle to stop, do not complete this section.
-
Use the navigation tools on the bottom right to scroll through the pages to find and select a Rollout Cycle from the table.
-
Enter a cycle name on the search line, and then click Search to find and select a specific cycle.
-
-
Select OK , and then choose one of the following options to proceed:
-
To create a Global Pause for the selected cycle, skip to Step 6. This pauses the deployment of the selected software product on all devices in the estate.
-
To specify a pause for specific devices, continue with the next step to Add Business Units.
-
-
Add or remove Business Units:
-
To remove existing Business Units, select the ellipsis (...) under Actions, and then select Remove Row.
-
To add Business Units, complete the following steps:
-
-
Select Create Cycle Pause and then click Save to create a pause for the selected rollout cycle.
To stop patching deployment for specific business units, complete the following steps:
-
Navigate to the Pause Patching for Specific Objects), and then select Paused Business Units.
menu (seeThis opens the
dialog: -
Add or remove Business Units:
-
To remove existing Business Units, select the ellipsis (...) under Actions, and then select Remove Row.
-
To add Business Units, complete the following steps:
-
-
Select Save to create a global pause for the selected business unit or business units.
The Rollbacks feature of OneSite Patch allows you to rollback one or more patches or releases to a previous version (Rollback), or you may rollback one or more patches or releases to an earlier, non-sequential version (Rollback to Version).
In either case, you may configure Rollback activities across your entire estate or limit a rollback to one or more Business Units.
Use the Rollback template to rollback a patch or release to the previous version. To rollback to a specific, earlier version, see Rollback to Version.
Use the Rollback template to configure a patch or release rollback to the previous version:
-
Select Flex Controls on the left navigation menu of the OneSite Patch Dashboard, and then select Rollbacks > Rollback.
This opens the Patching Rollbacks table. Until you create a rollback, the table is empty.
-
Select +New to open the Rollback template, and then enter a Name and a detailed Description of the rollback.
Notice
A red asterisk next to a field name indicates a required field.
-
Locate the patch or release you want to roll back:
-
Select a Software patch or release :
-
Add one or more Business Units to specify the devices to rollback.
-
Select Save to save the Rollback configuration. This returns you to the Patching Rollbacks table, which lists your new rollback.
-
Select a Rollback template from the Patching Rollbacks table of an open Patching Rollbacks template.
This opens the template.
Note
A red asterisk next to a field name indicates a required field.
-
Modify the Rollback settings:
-
Select Browse to choose a different patch or release to roll back.
-
Select +Add Business Units to add or remove target devices.
-
-
Select Save on the upper-left corner of the template to save the new settings.
-
Select a Rollback template from the Patching Rollbacks table of an open Patching Rollbacks template.
This opens the template.
Note
A red asterisk next to a field name indicates a required field.
-
Select More, and then select Save Rollback As.
-
Enter a new Name for the template, and then click Save as.
-
Revise the Description to reflect any changes needed for the copy, and then click Save.
-
Select Back to Rollbacks on the upper-left corner of the template to return to the Rollbacks table and view your changes.
-
Open the Patching Rollbacks table ( ).
-
Select the ellipsis (...) next to Name in the Patching Rollbacks table, and then click Set Display Columns.
This opens the Set Table Columns dialog.
-
Select the column names you want the Patching Rollbacks table to display, and then click OK.
-
Select a Rollback template from the Patching Rollbacks table of an open Patching Rollbacks template.
-
Select the Ellipsis (...) next to Name, and then select Delete Selected.
-
Review the Are you sure? dialog:
-
Select Export Logs on the top-right corner of the Are you sure? dialog to export trace logs. The trace logs download to your device as a file with a
.log
extension. -
Select OK to delete the Rollback.
-
-
Select Back to Rollbacks on the upper-left corner of the template to return to the Rollbacks table and view your changes.
-
Open the Patching Rollbacks table ( ).
-
Select the ellipsis (...) next to Name, and then click Select All.
-
Select the ellipsis (...) again, and then choose what you want to do with the selected Rollbacks:
-
To export the selected Rollbacks, see Select All Rollback to Version Objects.
-
To delete the Selected templates, see Bulk Delete Rollbacks.
-
To customize the display columns of the Patching Rollbacks table, see Customize Patching Rollback Table Settings.
-
-
Open the Patching Rollbacks table (Flex Controls > Rollbacks > Rollback).
-
Select the ellipsis (...) next to Name, and then click Select All.
-
Select the ellipsis (...) next to Name, and then select Delete Selected.
This opens the Delete Selected Objects dialog:
-
(Optional) Select Export Logs on the top-right corner of the Delete Selected Objects dialog to export trace logs. The trace logs download to your device as a file with a
.log
extension. -
Select OK to delete the Rollbacks. This returns you to the Patching Rollbacks to table where the deleted Rollbacks no longer appear.
-
Open the Patching Rollbacks table ( ).
-
Select a single Patching Rollback from the table, or click the ellipsis (...) next to Name, and then click Select All to export all Rollbacks
-
Select the ellipsis (...) next to Name again, and then click Export Selected.
This opens the Object Export Settings:
If Object Export Settings command returns an error similar to the following, see Resolve Export Errors errors:
-
Continue to Configure the Object Export Settings.
-
Complete the steps in Export Rollback to open the Object Export Settings template.
-
Enter an Exporting Organization Name and a Description of the settings you intend to create.
-
Toggle the Export as JSON switch to enable or disable (default) whether to export the settings as a JSON file.
-
Toggle the Automatically Import ... switch to enable or disable whether to select a specific folder to save the import.
-
Select Export on the bottom left corner of the Object Export Settings to export the selected objects.
Important
Adaptiva no longer supports the Export to Linked Servers functionality. Do not make any changes to the default settings.
To view the folder location of a Rollback to Version template, complete the following steps:
-
Open the Patching Rollbacks table ( ).
-
Select the ellipses (...) in the Actions column of the Patching Rollbacks table, and then select Show References.
This opens the [Rollback Name] Object References dialog.
-
Select the caret next to a Folder icon to expand the folder and view the contents, if needed.
-
Select OK to return to the Patching Rollbacks table.
Use the Rollback to Version template to rollback a patch or release to a specific release or version. To rollback to an earlier version, see Rollback.
To rollback a patch to a previous patch or release version, complete the following steps:
-
Select Flex Controls on the left navigation menu of the OneSite Patch Dashboard, and then select Rollbacks > Rollback to Version.
This opens the Patching Rollbacks to Version table. Until you create a rollback, the table is empty..
-
Select +New to open the Rollback template, and then enter a Name and a detailed Description of the rollback.
Notice
A red asterisk next to a field name indicates a required field.
-
Enter a Name and a detailed Description of your Rollback to Version.
-
Select Browse next to Add Installable Software in an open Rollback to Version template.
-
Choose the Software Patch or Software Release from the Add Installable Software table to roll back from. You can select only one Patch or Release to roll back from.
-
Select Add Installable Software to return to the Rollback to Version template.
-
Choose the software patch or release version to roll back to.
-
Select Browse next to Rollback in an open Rollback to Version template.
-
Select a Patch or Release version from the Add Installable Software table to roll back to. The only visible versions are those that match the item you selected for Patch. You can select only one Patch or Release to roll back to.
-
Select Add Installable Software.
-
Select a Rollback to Version template from the Patching Rollbacks to Version table of an open Patching Rollbacks template.
This opens the template.
-
Modify the Rollback settings:
-
Select Browse for Patch to choose a patch or release to roll back from.
-
Select Browse for Rollback to choose the version of the patch or release to roll back to.
-
Select +Add Business Units to add or remove target devices.
-
-
Select Save top-left corner of template to save the changes.
-
Select a Rollback template from the Patching Rollbacks to Version table of an open Patching Rollbacks template.
This opens the template.
-
Select More, and then select Save Rollback As.
-
Enter a new Name for the template, and then click Save as.
-
Revise the Description to reflect any changes needed for the copy, and then click Save.
-
Select Back to Rollbacks on the upper-left corner of the template to return to the Rollbacks table and view your changes.
-
Open the Patching Rollbacks table ( ).
-
Select the ellipsis (...) next to Name in the Patching Rollbacks table, and then click Set Display Columns.
This opens the Set Table Columns dialog.
-
Select the column names you want the Patching Rollbacks table to display, and then click OK.
-
Select a Rollback to Version template from the Patching Rollbacks to Version table of an open Patching Rollbacks template.
-
Select the Ellipsis (...) next to Name, and then select Delete Selected.
-
Review the Are you sure? dialog:
-
Select Export Logs on the top-right corner of the Are you sure? dialog to export trace logs. The trace logs download to your device as a file with a
.log
extension. -
Select OK to delete the Rollback.
-
-
Select Back to Rollbacks on the upper-left corner of the template to return to the Rollbacks table and view your changes.
-
Open the Patching Rollbacks table ( ).
-
Select the ellipsis (...) next to Name, and then click Select All.
-
Select the ellipsis (...) again, and then choose what you want to do with the selected Rollbacks:
-
To export the selected Rollbacks, see Select All Rollback to Version Objects.
-
To delete the Selected templates, see Bulk Delete Rollbacks.
-
To customize the display columns of the Patching Rollbacks table, see Customize Patching Rollback Table Settings.
-
Use the following task to delete all Rollback to Version templates.
-
Open the Patching Rollbacks table (Flex Controls > Rollbacks > Rollback to Version).
-
Select the ellipsis (...) next to Name, and then click Select All.
-
Select the ellipsis (...) next to Name, and then select Delete Selected.
This opens the Delete Selected Objects dialog:
-
(Optional) Select Export Logs on the top-right corner of the Delete Selected Objects dialog to export trace logs. The trace logs download to your device as a file with a
.log
extension. -
Select OK to delete the Rollbacks. This returns you to the Patching Rollbacks to Version table where the deleted Rollbacks no longer appear.
-
Open the Patching Rollbacks table ( ).
-
Select a single Patching Rollback from the table, or click the ellipsis (...) next to Name, and then click Select All to export all Rollbacks
-
Select the ellipsis (...) next to Name again, and then click Export Selected.
This opens the Object Export Settings:
If Object Export Settings command returns an error similar to the following, see Resolve Export Errors errors:
-
Continue to Configure the Object Export Settings.
-
Complete the steps in Export Rollback to Version to open the Object Export Settings template.
-
Enter an Exporting Organization Name and a Description of the settings you intend to create.
-
Toggle the Export as JSON switch to enable or disable (default) whether to export the settings as a JSON file.
-
Toggle the Automatically Import ... switch to enable or disable whether to select a specific folder to save the import.
-
Select Export on the bottom left corner of the Object Export Settings to export the selected objects.
Important
Adaptiva no longer supports the Export to Linked Servers functionality. Do not make any changes to the default settings.
To view the folder location of a Rollback to Version template, complete the following steps:
-
Open the Patching Rollbacks table ( ).
-
Select the ellipses (...) in the Actions column in the Patching Rollbacks to Version table, and then select Show References.
This opens the [Rollback Name] Object References dialog.
-
Select the caret next to the Folder icon to expand the folder and view the contents, if needed.
-
Select OK to return to the Patching Rollbacks to Version table.
Comments
0 comments
Article is closed for comments.