Content Push
Overview
The Content Push feature allows any Adaptiva-published content to be distributed to Adaptiva clients without using a deployment from ConfigMgr or Intune. Content Push pre-stages content to locations where it will be needed for future use. For example, ConfigMgr OSD content can be pre-staged at the location where machines will be imaged, and it will be available to copy from local Adaptiva peers when requested.
Workspace ONE content is only published on their Content Delivery Network and will not be in the Adaptiva Content Library on the Adaptiva server or Cloud store. The Adaptiva Server will receive metadata information so clients can locate the content. Because there is only metadata, content push policies cannot include Workspace ONE content.
When a Content Push Policy is created, the policy is sent to the desired target clients and the content is downloaded on a defined schedule . The content will only cross a WAN link once for each office targeted (except VPN-configured offices) and then shared amongst peers at those locations.
Advanced features of Content Push allow:
Control download parameters
Specify whether and where downloaded content is unpacked
Trigger workflows at different stages of the policy
Execute a command after the download completes
Features
Pre-staging Content
Pre-stage content to Adaptiva clients in any office without requiring ConfigMgr or Intune involvement.
Policy Scheduling
Full control over policy start time, expiration time, and execution schedule.
Content Synchronization
Automatically synchronizes content changes for ConfigMgr content, Task Sequences, and other content types, including Intune apps.
Download Controls
Fine-grained control over download behavior, including priority, timeouts, battery usage restrictions, WAN usage restrictions, and transport protocols.
Post-Download Actions
Unpack content to a specified location and execute commands after the download completes.
Workflow Automation
Use Pre-Download, Download, Post-Download, and Content Push Server workflows to implement highly flexible and customizable automation.
IntelliStage
Intelligently pre-selects a defined number of clients in each office to cache content in advance.
Create a Content Push Policy
In the left-hand navigation, click Content Push.
Click + New to create a new Content Push policy.
General
Enter a Name and Description for the Content Push Policy.
Name (Required) - Enter a display name to identify the Content Push Policy.
Description (Optional) - Add a description for the Content Push Policy.
Click Show More to expand additional configuration settings:
Start Time - The time the policy will start on the target clients. By default this is the current time.
End Time - The time the policy will expire on the target clients. By default this is empty, so the policy will run forever.
Use Server Time (Enabled by default) - All target clients will run the policy at the same time. When this is disabled, clients will run the policy based on their time.
Encrypt Policy (Disabled by default) - Encrypt the policy settings.
Policy Enabled (Enabled by default) - Enable the policy to start immediately upon saving.
Content List
The Content List is used to specify what content will be deployed by this Content Push Policy.
Content Type - Filter the list of content added. Select All Content to show all content items included in this Content Push policy
Content List - Display the Content in the Content Push Policy
Add Content - Add a new content item.
Show All Referenced Content When a Task Sequence has been added to the Content List, this will show all the referenced content in the task sequence along with any individually added items.
Click Add Content | OS Images.
Check the box next to the content item to be added to the Content Push policy (Windows-11-Enterprise en-US OS Image).
Click OK.
Schedules
The Execution Schedule is a required field to set for policy execution.
Click Browse to select the schedule to add.
ASAP and non-recurring schedules run once and are not repeated. Recurring schedules are used for scheduling policies to be run on a regular basis. A recurring schedule is useful in the case where a machine hosting content from a content push policy goes offline and the additional copies of the content should be maintained. When the client runs the policy again, it will verify that the policy settings are being enforced and if additional copies of content need to be made, it will do so at that time.
A recurring schedule will take effect after the configured start time. When a task is scheduled for a particular day, it will run at the time of day provided in the start time. For example, if a policy is scheduled to run on the last day of the month, starting on March 5th, at 5pm, it will fire on March 31st at 5pm, April 30th at 5pm and so on.
Check one or more boxes next to the desired schedule(s) and click OK.
Target Groups
You can select one or more groups to run the policy on, or target all devices.
Use All Devices Enable this setting to target all Adaptiva clients.
Target Groups – Select a specific Adaptiva Group or ConfigMgr collection.
Click Browse.
Click on the Groups folder to list only the Adaptiva Groups.
Check the box by the group name(s) and click OK.
Unpacking Settings
Do Not Unpack (Enabled by default) - Disable this to unpack the content and specify a folder destination. Content unpacking is not available if you have IntelliStage enabled.
Unpacking Folder Name - Enter the folder where the content should be unpacked. We recommend unpacking to the C:\AdaptivaCache folder to not take up additional disk space on the device.
Empty Unpacking Folder Before Use (Disabled by default) - Enable this to delete the content of the Unpacking folder first.
Delete Unpacking Folder After Post-download Command Execution (Disabled by default) - Enable this to delete the unpacking folder after running the command line.
IntelliStage and Push Settings
IntelliStage and Push Settings are enabled by default. They instruct the clients targeted by a Content Push Policy to create a minimum number of copies of the content to the best suited clients in each office.
For example, an administrator needs to ensure that OSD content will be present when machines are scheduled to be imaged. They create a policy to push out the Task Sequence contents to 3 clients per office, and schedule the policy to run periodically. After pre-staging the content, a client goes offline. When the policy runs it will share the content from one of the remaining 2 clients to another source, thereby maintaining the desired number of sources per office.
If IntelliStage is not used, the Content Push policy will pre-stage the content on all machines in the targeted Adaptiva Group. This may be desirable for software that will go to many machines or to just a few.
Enable IntelliStage (Enabled by default)
Allow for Internet Clients (Disabled by default) - When enabled, internet-based clients will execute IntelliStage policies.
Minimum Content Sources Per Office - Enter the minimum number of clients that will receive the content.
Push Content Only if Disk Space Available in Office (Enabled by default) - When enabled the policy will evaluate if there is enough actual free disk space in the virtual SAN in the targeted Office(s) before initiating content download. (Standard determination is based on potential free space which could cause excessive file deletion to make room for the new content).
Autosync Content Changes (Enabled by default) - If enabled, when the Adaptiva Server detects changes to the source content, it will automatically push those changes out to the group(s) and/or collection(s) targeted by the policy. If the content list in the policy is a Task Sequence, any changes to content referenced by the Task Sequence will result in the changes being automatically pushed to the target collections.
Publish Unpacked Content in P2P - An unpacked copy of the latest content will be published in the Adaptiva P2P system. Required for OSD.
Post Download Execution Settings
Post Download Execution Settings - IntelliStage must be disabled first. Enter the command line to be executed after the content is downloaded and unpacked.
Command Working Directory - Enter the working directory, if required.
Wait for Command to Exit (Disabled by default) - Enable to have Adaptiva wait until the executed command completes.
Max Execute Time (seconds) - Enter the number of seconds to wait for the executed command to complete. 3600 seconds is the default.
Advanced Settings
Click Advanced Settings.
These settings override the default download settings, or the download settings set on the content item.
Download Settings
Priority - Enter a priority from 1 to 255. The highest priority will be downloaded first.
Never Download On Battery (Disabled by default) - When selected, laptops running on battery power will not attempt to download the content.
Never Download Over WAN (Disabled by default) - When selected, the content is set to never download over the WAN or between offices.
Use Lightweight Content Verification (Disabled by default) - When enabled only the file size is checked, not the file hash.
Timeout Settings
Timeout Settings - Determines how long clients will wait for the package before abandoning the request.
Transport Settings
These settings control the transport protocol which will be used while downloading content across the WAN and over the LAN. By default, WAN downloads are configured to use Background Adaptive Transport and will prevent interference with other traffic. The speed of the download will automatically adapt to the amount of actual unused bandwidth on that network. The Foreground Adaptive Transport, which is used on LAN connections by default, will still use our UDP based protocol, with checkpoint restart capability but will not perform Predictive Bandwidth Harvesting.
Content Download Receipts Settings
We do NOT recommended you change these settings.
Content Download Status Settings
Content Push Workflows
Content Push is a workflow-based feature. The workflows that are executed by a Content Push Policy can be selected in the Content Push Workflows section. Individual workflows can be edited in the Workflow Designer of the Admin Portal. The following sequence of events takes place when a Content Push Policy schedule fires. Events 2-4 take place asynchronously at the client:
Content Push Server Workflow is executed at the server.
Pre-Download Workflow
Either the Download Workflow or the Office Content Push Download Workflow
Post-Download Workflow
Pre-Download Workflow - The Pre-Download Workflow is executed before content download begins. By default, this workflow does nothing.
Download Workflow - The Download Workflow does the work of downloading the content and reporting status.
Post Download Workflow - The Post-Download Workflow is executed after all content referenced by the policy has been downloaded.
Content Push Server Workflow - This workflow executes whenever the Content Push policy schedule fires. By default, this workflow does nothing.
Office Content Push Download Workflow - If the IntelliStage setting is enabled in the policy, then this workflow replaces the Content Download Workflow in the policy execution.
Server Workflows
Client Workflows
When using IntelliStage, change the Client Policy Execution Workflow to use the Content Push Policy Execution Workflow - SuperRVP Only. This assumes the target group includes all computers in one or more offices.
Close the Advanced Settings page to return to the Content Push Policy
Click Save.
Executing the Policy
After the Content Policy has been created, the policy can be run.
Under Actions, click the ellipses (...) and select Run Policy to execute the policy on all target clients.
Last updated
Was this helpful?