Support using OSDDownloadContent.exe outside of Download Package Content TS step
A number of organizations are using OSDDownloadContent.exe outside of Download Package Content TS Step to download dynamic driver content (made popular by http://www.scconfigmgr.com/modern-driver-management/). In this scenario, driver package version information is missing in the TS environment during TS runtime (i.e. SMSTSSourceVersion%PackageID% TS variables are not set). When an Alternate Content Provider is called using SMSTSDownloadProgram to download content, the ACP is unable to determine which version of the package needs to be downloaded and can result in download failure or downloading the incorrect version of a driver.
Ideally, OSDDownloadContent.exe would be able to retrieve the current version and update the SMSTSSourceVersion%PackageID% TS variable before calling the ACP.
Updating status to declined.
We do not support running any of our task sequence binaries outside the task sequence environment. The task sequence environment is needed for communicating with the management point and distribution points, also downloaded content would not be hash verified as there’s no policy.
Dave Fuller commented
Perhaps a misunderstanding here. The request was not to support using OSDDownloadContent.exe outside the Task Sequence environment. The Modern Driver Management method referenced runs in a Task Sequence so the TS environment is present. It runs a PowerShell script in the TS that runs OSDDownloadContent.exe.