OSD Content Push
During the execution of a task sequence, OneSiteDownloader and the Adaptiva Client attempt to retrieve content from local peers on the same subnet. If the content isn't available at the site, a WAN download will be attempted. This is not an ideal scenario as files used during the imaging process tend to be large which will delay the completion of the task sequence.
To avoid this issue, it is highly recommended that a Content Push policy be created and deployed to one or more machines at the local office in advance so that content is available locally prior to the task sequence execution.
Creating a Content Push Policy for a Task Sequence
Prior to creating the Content Push policy, create a collection in ConfigMgr that includes the clients located at the office(s) where you plan to deploy the task sequence. These clients should be up and running so they are able to run the policy, but they are not required to be up during the task sequence execution.
Log in to the Admin Portal at
http[s]://AdaptivaServerFQDN[:port]and click OneSite Anywhere.In the left-hand navigation, click Content Push.
In the detail pane, click + New.
In the new policy editor, enter a Name of Windows 11 OSD Content and Description for the policy.
Scroll down to Content List, and next to Content List, click Add Content > Task Sequences.
Add Content In the Add Task Sequences window, select the OSD task sequence and click OK.
Click Show all Referenced Content to view content included in the Content Push Policy.
Referenced Content Review the referenced content and add any additional additional content items which may be called, but not directly referenced in the task sequence. These can include driver packages, software updates, or packages which may be dynamically requested using an MDT integrated task sequence.
Scroll down to Schedules, and next to Execution Schedules, click Browse.
Select the ASAP schedule to immediately deploy the content and then select a recurring schedule like Daily at 2AM to ensure content is available in the targeted offices. Click OK.
Scroll down to Target Groups, and next to Target Groups, click Browse.
Select the ConfigMgr collection you created earlier and click OK.
Scroll down to the Intellistage and Push Settings section and toggle ON Publish Unpacked Content in P2P.
Publish Unpacked Content in P2P This setting is required for Operating System Deployment. This will unpack the content on the clients that host it, so it is accessible to the OneSiteDownloader.
Click Save to deploy the content push policy. Using the ASAP schedule, clients in the collection will immediately begin to download the content referenced in the task sequence and replicate it to their peers.
Task Sequence Deployment
Once the task sequence content has been distributed and unpacked by the content push policy you can deploy the task sequence in ConfigMgr. It is important to remember to set the deployment to Download content locally when needed by the running task sequence. Otherwise the OneSiteDownloader and the Adaptiva Client will not be called.
OneSiteDownloader and OSD Content Push Shares
When a content push policy is configured for OSD and the setting Publish Unpacked Content in P2P is selected, each piece of content referenced in the policy is unpacked into a folder in the target client's Adaptiva Cache folder. By default, each folder is shared so that OneSiteDownloader can access the unpacked content within the share. In the case where you prefer that shares are not created, you can configure a client settings policy to restrict share creation. In addition to the default share being created during the Adaptiva client installation, a local user is created on each client in order to provide access to the OSD content push shares. You can create a policy to remove the local AdaptivaClient account.
Disable OSD Content Push Shares and Adaptiva Local User Accounts
A Client Settings Policy can be set to disable OSD Content Push shares as well as remove the local AdaptivaClient user account by the following:
Click the gear icon > Settings > Client Settings Policies.
To create a new policy, click + New.
In the General Settings, complete the following:
Name - Disable OSD Content Push.
Description - Enter a description. For this example, Disables OSD Content Push Shares and Adaptiva Local User Accounts.
Priority - To ensure these settings apply to the target groups, set this value greater than 1.
Target Groups - Click Browse and select one or more Groups.
Click OK.
In the Client Settings section, click Add Settings.
Find and expand Content System.
Check Adaptiva Client Account Creation and Create Unpacked Shares.
Click OK.
Select Adaptiva Client Account Creation from the Client Settings to Override table.
In the Settings Details, in the New Value field, enter 1.
Select Create Unpacked Shares and ensure a value of false.
Click Save to create the policy. This will immediately distribute the policy to all target clients.
Manually Disable OSD Content Push Shares and Adaptiva Local User Accounts
You can also disable these settings directly on devices by modifying the following registry values.
To disable OSD Content Push shares manually, the following registry value can be set on clients:
Path: HKEY_LOCAL_MACHINE\Software\Adaptiva\Client
Key: contentsystem.create_unpacked_shares
Value: false
To remove local AdaptivaClient user accounts, the following registry value can be set on clients:
Path: HKEY_LOCAL_MACHINE\Software\Adaptiva\Client
Key: contentsystem.adaptiva_client_account_creation
Value: 1
Last updated
Was this helpful?