MDT: Use OSDCloud DriverPacks in a Task Sequence

Preinstall Phase

Modify Inject Drivers step

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

Install Phase

Add Run Command Line step

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

Postinstall Phase

Add Run Command Line step

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

OSDCloud DriverPackMDT Step for VM Testing

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

Test a Deployment

The following screenshots are from a Virtual Machine emulating a Lenovo P1 Gen 5 device