MDT: Use OSDCloud DriverPacks in a Task Sequence
Requires OSD 22.10.7.2+
Modify your Task Sequence to include drivers from the OSDCloud WinPE x64 selection profile that was created in the WinPE Drivers configuration. This will ensure that you have the minimal Network and Disk Controller drivers needed to startup the Operating System to first boot
Add a Run Command Line step to your Task Sequence prior to Install Operating System to load the OSDCloud Sandbox. This will ensure that you have the latest OSDCloud dependencies in your WinPE Session. Use the following for the Command line
PowerShell -ExecutionPolicy Bypass -Command "Invoke-Expression (Invoke-RestMethod 'sandbox.osdcloud.com')"
Make sure you do not 'Continue on error' because if this fails to load, then you will probably not be able to download DriverPacks
After Configure, add a Run Command Line step called OSDCloud DriverPackMDT. Use the following for the Command line
cmd.exe /c start /wait PowerShell -ExecutionPolicy Bypass -Command Invoke-OSDCloudDriverPackMDT
Start in should contain the following path
%OSDisk%\Windows\System32
Options should include Continue on error
Run Command Line
Continue on error
If you want to test downloading and applying a DriverPack in a Virtual Machine, modify the above step to specify a Manufacturer and Product. I select a Lenovo as the DriverPack as HP and Dell do not show progress in the Specialize phase during the DriverPack expansion
cmd.exe /c start /wait PowerShell -ExecutionPolicy Bypass -Command Invoke-OSDCloudDriverPackMDT -Manufacturer Lenovo -Product 21DC
The following screenshots are from a Virtual Machine emulating a Lenovo P1 Gen 5 device
This part may take 5-10 minutes. Most DriverPacks will not show any progress
Lenovo is the exception where you will see the expand of the DriverPack
Complete deployment with no errors
PPKG DriverPack expand and apply in Specialize will be saved in C:\Windows\debug
Last modified 4mo ago