Content Publication Settings

Content Publication Settings control how content is published. There are four different sources of content and places to publish this content depending on the licensed solution. Content can be published on the Adaptiva Server or on the CDN or both places.

Workspace ONE content is only published on their Content Delivery Network (CDN) 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.

Content Source	Web Portal Setting Location
OneSite ConfigMgr Edition	Select Settings > Publication Select each content type: Packages, Software Updates, Boot Image Packages, OS Images, OS Upgrade Packages, Driver Packages, Applications
Adaptiva	Select the gear in the top right corner then Settings > Adaptiva Content Publication
OneSite for Intune	Select Intune Settings > Cloud Content Settings
Workspace ONE	Not Applicable -- content is published on the Workspace ONE CDN

Use the sections below to configure where Adaptiva will store content.

The section Connecting to Azure Storage in the Installation Guide MUST have been completed first.

ConfigMgr Content

You can enable Automatic Content Publication so that when new ConfigMgr objects are created that have associated content, Adaptiva will detect and automatically publish this content for use by the Adaptiva client’s peer-to-peer content delivery system.

When a content item (package, software update, etc.) is created in ConfigMgr it will be created with the default distribution priority setting of Medium, but the priority can be set to High, Medium, or Low. The administrator can configure OneSite to automatically apply different settings for different priorities for each content type.

Automatic Content Publication of ConfigMgr Content

1. Select Settings > Publication

   

Auto-Publish Settings

• Content Publication Workflow: A workflow can be selected to provide additional functionality when ConfigMgr content is published, for example: to approve or deny publication. No action is required unless the default workflow will not be used.

• Publish Without Source Files: This setting will publish ConfigMgr content without acquiring source files. The setting will be enabled by default when the ConfigMgr Site server is a Central Administration Site (CAS). If Adaptiva is not integrated with any of the child Primary Site servers, disable this setting. If Adaptiva is integrated with the child Primary Site servers, the setting should be disabled.

Publication Settings

If items are unchecked, you can click the Automatically Publish Content button and this will check all of the Automatically Publish Content and Publish All Existing Content boxes for each content type. Otherwise you can individually check the boxes. Below are descriptions for each check box.

• Automatically Publish Content check box

  • When selected, all new or modified items for the respective content type will be published.

• If Automatically Publish Content check box is not checked, then you can select Unpublish Published Content

  • All content within that content type will be removed from OneSite

• Publish All Existing Content check box

  • When selected, all existing content of the specified type in ConfigMgr will be published in Adaptiva. If not selected, only new content within that content type will be published.

1. Click Save

Content Publication Settings for each Content Type and Priority

Only Packages and Applications should be published to Cloud Storage. Please contact our Support Team if you have questions about the other content types.

OneSite allows for a high degree of control when distributing content. You can change settings for individual content items for each priority level.

1. You can select individual content tabs from the Publication Settings pane along with their corresponding priority level from the dropdown.

   

   • The changes made here will only affect content with the same priority in ConfigMgr.

   • For example, All high priority packages will be encrypted and will have a priority of 10.

General Settings

This displays information, status, and encryption settings for a content type and priority.

• Encrypt Packages

  • If the Encrypt Package setting is enabled (slid right), the content will be encrypted during publication.

Enabling this setting on an already published piece of content will force re-publication. Publishing encrypted content items will take longer than publishing a non-encrypted content item due to the resources needed to perform the encryption.

Content Publication Settings

There are two locations where content is published:

• Adaptiva Server

  • Folder on the server where all on-premises content is located.

  • By default, clients will get this content via peer-to-peer sharing. The Adaptiva client on the Adaptiva server will retrieve the requested content from the Content Library. It is thus critical this client service is running.

• Cloud Storage

  • Location in the cloud where content is stored permanently.

  • For internet-based clients or clients in a Location configured with Allow Direct CDN Download enabled.

The content stored in Cloud Storage will be replicated around the globe using Adaptiva Content Delivery Network (CDN) to ensure fast downloads wherever a device is located.

It is NOT recommended to store Software Updates in the Cloud Store. These can be downloaded directly from the Windows Update CDN.The exception to this would be 3rd party software updates.

Please see the steps below, for more information on how to set up Third-party content software updates.

Download Settings

This contains settings that control the download and reporting behavior of a content type and priority.

• Send Status Message On

  • The content can be configured to send ConfigMgr status messages when the download starts, when it finishes, if it fails and at any In-Progress completion percent interval. Content download status can be reviewed in ConfigMgr reports.

• Never Download On Battery

  • When toggled ON, laptops running on battery power will not attempt to download the content.

• Never Download Over WAN

  • When toggled ON, the content is set to never download over the WAN or between offices.

• Priority

  • ConfigMgr allows the user to specify Content Distribution Priorities for content relative to one another as High, Medium, or Low.

    OneSite takes this concept a step further and provides more flexibility by allowing an administrator to define 255 levels of priority (with 1 being lowest and 255 being highest priority).

    WAN downloads of lower priority content are automatically paused when a higher priority download starts. By specifying a priority for a content item, you are choosing which content downloads it can preempt, and which content can preempt it.

    Each content type and priority have a default priority:

Content Type	Priority: Low	Priority: Medium	Priority: High
Packages	40	100	180
Software Updates	60	110	200
Boot Images	20	80	160
OS Images	50	80	160
OS Upgrade Packages	20	80	160
Driver Packages	20	80	160
Applications	50	120	190

Transport and Timeout 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.

• WAN Transport: Select the default transport for downloads across the WAN.

• LAN Transport: Select the default transport for downloads across the LAN

• Timeout Settings: Determines how long clients will wait for the package before abandoning the request based on Local, Remote, and Total timeout.

1. Click Save

2. Repeat for each priority and each content type

Third-party content

When using third-party Software Updates content, these can be published when devices will exist on the internet or in Locations where Allow Direct CDN Download has been enabled. Third-party Software Updates need to be manually published to the Adaptiva CDN or automatically by changing the package priority.

Manually publish third-party to the cloud

These steps outline how to manually publish individual software updates to the cloud. This allows for more granular control on specific software updates and how they are published.

1. Select Content Publication > Software Updates.

   
2. Find the third-party package from the folder directory and expand.

3. Select the ellipses (...) next to the first update and select View Details.

   
4. Toggle OFF Use Default Content Publication Settings.

5. Check the box for Cloud Storage

   
6. Click Save.

   • The publication should be automatically updated and when finished will show the published to cloud icon in the table.

7. Repeat for all third-party Software Updates and Packages.

Automatically publish third-party to the cloud

ConfigMgr steps

Prior to setting up auto-publish to the cloud, you first must change the Distribution Settings in ConfigMgr.

1. Select Software Library > Software Updates > Deployment Packages.

   
2. Right click a deployment package and select Properties.

3. Change the Distribution Priority to either Low or High – something different from the default of Medium – from the Distribution Settings tab.

   
4. Click OK.

OneSite Anywhere steps

1. Select Settings > Publication Settings and click the Software Updates tab.

   
2. Select the matching priority setting from ConfigMgr from the steps above.

3. Check Cloud Storage under Content Publication Settings.

   

Verify

1. In OneSite Anywhere, the software update should now have a cloud icon or server/cloud icon (if both Adaptiva Server and Cloud were selected).

   
2. (Optional) Switch back to ConfigMgr and right click on the Update Package and select Update Distribution Points and click Yes.

   • Forcing a DP update will trigger a re-publication request which will update the content in its storage locations.

More Actions

Additional actions can be performed on created content and is accessed by selecting the ellipses (...) next to the content in the table.

Publish or Publish Parent Content

If the content is not published, this action can be used to publish the content. For Applications and Software Updates all content items will be published

Update Publication

This action will update the content in the defined content locations. If the content is not published to the Cloud store and the Default settings for this content type have Cloud store checked, the content will be published in the Cloud store

Unpublish or Unpublish Parent Content

If the content is published, this action can be used to unpublish the content. This will remove the content from the Content Library and the Cloud store

Show References

This will show where the content item is referenced. Specifically, if it is part of a task sequence or Content Push, if not, it will just show the folder the content is in

Refresh

This will refresh the publication status of the select content item

Adaptiva Content

Adaptiva content can be published either on the Adaptiva Server or on Cloud Storage or both.

Using the Adaptiva Web Portal

1. Click and select Settings > Adaptiva Content Publication

   
2. Select either Adaptiva Server, Cloud Storage, or both.

3. Click Save.