The Content Prestaging feature enables to provide deployment 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 Server 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 OneSite Patch 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 OneSite Patch 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:
Comments
0 comments
Article is closed for comments.