☁️
OSDCloud.com
OSDeploy.comTwitter
  • About
  • Contributors
    • Damien Van Robaeys | MVP
    • Ákos Bakos
    • David Segura | MVP
    • Gary Blok
    • Jérôme Bezet-Torres | MVP
  • OSDCloud
    • Local Setup
      • OSDCloud Template
        • Build Process
        • Logs
        • Named Templates
        • WinRE WiFi
        • Public Content
        • Languages
        • Cumulative Updates
        • ISO Boot Media
        • Universal WinPE
      • OSDCloud Workspace
        • Get-OSDCloudWorkspace
        • Set-OSDCloudWorkspace
        • New-OSDCloudWorkspace
          • Restore from ISO
          • Restore from ISO URL
          • Restore from USB
        • Update-OSDCloudWorkspace
        • Configuration Files
      • OSDCloud WinPE
        • Default Wallpaper
        • Wallpaper
        • Drivers
        • PSModule
        • Startup
      • OSDCloud ISO
      • OSDCloud USB
        • New-OSDCloudUSB
        • Update-OSDCloudUSB
        • USB Drives
        • Secure USB Drives
      • 🚧OSDCloud VM
        • Get-OSDCloudVMDefaults
        • Get-OSDCloudVMSettings
        • Set-OSDCloudVMSettings
        • Reset-OSDCloudVMSettings
        • New-OSDCloudVM
    • Deployment
      • WinPE
        • Start-OSDCloud
          • OS Parameters
          • ZTI
        • Start-OSDCloudGUI
          • Parameters
          • Defaults
          • Global Variable
          • Customize
        • Start-OSDCloud Wrapping
      • First Boot
      • OOBE
      • Windows
  • Sandbox
    • OSDCloud
      • sandbox.osdcloud.com
      • WinPE Usage
      • OOBE Usage
      • Functions
    • OSDCloud Azure
      • az.osdcloud.com
    • WinPE Downloads
  • OSDCloud Automate
    • 🆕Basic Configuration
    • 🆕OSDCloudGUI Defaults
    • 🆕Autopilot
    • 🆕Provisioning
      • 🆕Windows Configuration Designer
      • 🆕MSI Application PPKG
      • 🆕Bulk Enroll PPKG
      • 🆕PowerShell Script PPKG
    • 🚧Scripts
  • OSDCloud Azure
    • Azure Setup
      • Azure Portal
        • Storage Accounts
        • Storage Containers
          • BootImage
          • DriverPack
        • Storage Access Control (IAM)
      • Infrastructure As Code
        • Prerequisites
        • Technicien
        • Workspace
        • Bicep
        • Terraform
        • Configure Azure
    • Deployment
      • Testing
      • OSDCloudRE Azure
    • Deep Dive
      • Cloud Functions and Scripts
      • Connect Azure in WinPE
      • Azure Tags
      • Log Files
  • Offline Deployment
    • ISO: Adding a WIM
  • Integration
    • ADK: Use the OSDCloud Boot.wim
    • MDT: Use the OSDCloud Boot.wim
    • MDT: Add OSDCloud WinPE Drivers
    • MDT: Use OSDCloud DriverPacks in a Task Sequence
    • OSDCloud IPU
      • Windows In-place Upgrades
      • Windows Media Download
  • Archive
    • 💡Tips
      • 🆕Media Cleanup
      • Firmware Update
      • Quick Setup
    • 🌎Community
      • OSDCloud: The ZTI Way
      • OSDCloud - Image devices without need of infrastructure
      • Trying out Windows 10 Deployment with OSDCloud
      • Deploying Windows 10 to bare metal devices with just WinPE & internet
    • 💔Under Review
      • ISO
      • WIM
    • 🪦Recycle Bin
      • Release Notes
      • Enable-OSDCloudODT
      • Deploy
        • OOBE Phase
      • Guides
        • OSDCloud WIM
        • Custom OSDCloud
        • AutoPilot
          • AutoPilot Configuration File
          • AutoPilot in Audit Mode
          • AutoPilot in OOBE
        • WiFi
      • OOBE
        • Start-OOBE.settings
        • Start-OOBE.wifi
        • Start-OOBE.autopilot
      • Concepts
        • K.I.S.S.
        • OSD Disks Logically
        • Office365 Specialize
        • Specialize DriverPacks
        • Model Reference Image
        • MDT OSDCloud DriverPacks
        • MDT DriverPacks
      • Blob SAS URL
      • Storage Containers (Public)
Powered by GitBook
On this page
  • Preinstall Phase
  • Modify Inject Drivers step
  • Install Phase
  • Add Run Command Line step
  • Postinstall Phase
  • Add Run Command Line step
  • OSDCloud DriverPackMDT Step for VM Testing
  • Test a Deployment

Was this helpful?

Export as PDF
  1. Integration

MDT: Use OSDCloud DriverPacks in a Task Sequence

Requires OSD 22.10.7.2+

PreviousMDT: Add OSDCloud WinPE DriversNextOSDCloud IPU

Last updated 1 year ago

Was this helpful?

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 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

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

Add a Run Command Line step to your Task Sequence prior to Install Operating System to load the . This will ensure that you have the latest OSDCloud dependencies in your WinPE Session. Use the following for the Command line

OSDCloud Sandbox
WinPE Drivers
Run Command Line
Continue on error
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