LogoLogo
OSDeploy.comTwitterPowerShell GalleryGitHub
  • Overview
  • Release Notes
  • OSDeploy Home
  • Module
    • Install and Update
    • Functions
      • Get-DellModelPack
      • Get-HpModelPack
      • Save-OSDDriverPack
      • Save-OSDIntelPack
      • Save-OSDModelPack
      • Save-OSDMultiPack
      • Show-OSDWmiQuery
      • Update-ModuleOSDDrivers
      • Update-OSDDriverScripts
      • Update-OSDMultiPack
    • PowerShell Gallery
    • GitHub
  • Docs
    • Driver Basics
      • SystemSKU
      • HardwareID
      • SUBSYS
      • Microsoft Update Catalog
      • OEM Drivers
      • Generic Drivers
      • Audio Drivers
      • Driver Family Packs
      • Security
      • Recommendation
    • AmdPack (AMD Video)
      • AMD Reference
        • Enterprise Drivers
        • CVE
        • ISV Certifications
        • OEM Radeon Compatibility
        • OEM Radeon Pro Compatibility
      • Real World OEM Compatibility
      • AmdPack Download
      • AmdPack Package
    • NvidiaPack (Nvidia Video)
      • Nvidia Enterprise Drivers
      • Nvidia CVE
      • Nvidia vs OEM
      • Standard vs DCH
    • OSDDriver Basics
      • WorkspacePath
      • Save-DellModelPack
      • MultiPack
        • Create a Single Model MultiPack
        • Add a Similar Model Pack
        • Add a Different Model Pack
        • DellMultiPack (Full)
        • DellMultiPack (Size Comparison)
        • Create a Generation Pack
        • Final Results
        • Deployment
    • How I Roll
      • Drivers
        • IntelPack MDT
        • IntelPack 10.0 x64
        • IntelPack 10.0 x86
        • NvidiaPack 10.0 x64
        • NvidiaPacks (MultiOS)
        • DellMultiPack 10.0 x64 MDT
        • MDT - DellMultiPack (MultiOS)
        • Update-DellMultiPack
        • CM - Dell Generation Packs
      • MDT - Microsoft Deployment
        • MDT Integration
        • MDT Deployment
      • CM - Configuration Manager
        • CM Packages
        • CM Task Sequence
        • CM Deployment Test
  • Links
    • Dell
      • Model Packs
      • Family Packs
      • Family Packs (DIA)
    • Intel
      • Bluetooth
      • Ethernet
      • Wireless
    • Nvidia
      • Driver Search
      • Advanced Driver Search
      • Quadro Branch History
      • CVE
  • Development
    • Solutions
      • Deploy Cabs
      • Intel Video - Part 1
      • Intel Video - Tests
      • Remove Intel Video Drivers
      • AMD Video Drivers
      • Nvidia Video Drivers
    • NvidiaPack
      • NvidiaPack Test
    • Examples
      • MDT Dell Win7 + Win10 x64
      • Windows 7 to Windows 10 Upgrade
    • ConfigMgr
      • Packages
        • IntelPack 10.0 x64
        • NvidiaPack 10.0 x64
      • Task Sequence
    • Deployment
      • Integration
        • ConfigMgr Package
        • ConfigMgr Task Sequence
      • Execution
        • Local Test
        • Windows Setup
        • ConfigMgr Package Deploy
  • Real World
    • HPMultiPack
      • Heine Hanevik
Powered by GitBook
On this page
  • Requirements
  • Hyper-V Example
  • Dell Latitude 5400

Was this helpful?

  1. Development
  2. Deployment
  3. Execution

Windows Setup

PreviousLocal TestNextConfigMgr Package Deploy

Last updated 5 years ago

Was this helpful?

OSDDrivers can be used with Windows Setup, and is a good fit due to the small size. You will need to do some customization when it comes to AutoUnattend.xml, but the purpose of this is to show that it is possible to deploy OSDDrivers using this method, completely offline

Requirements

  • PowerShell must be integrated with Windows Setup Environment (WinSE)

  • Drive must be Partitioned before Windows Setup begins using an AutoUnattend.xml

  • Drivers need to be staged to C:\Drivers (or path specified in AutoUnattend.xml)

Hyper-V Example

In this case I have created an ISO for use in Hyper-V. I'm prompted to Partition the Drive first (to prevent accidents)

Once OSDDrivers begins, it imports the Deploy-OSDDrivers Script Module. The system is validated and all HardwareID's are gathered

Apparently no drivers matched, so no Drivers were staged, so this isn't a good example to use except to show a quick overview

Dell Latitude 5400

Time to move onto testing a real computer, the Dell Latitude 5400. This is a rather new model, and I made sure to have MS DaRT added to WinSE so I can take screenshots while connected using Remote Recovery

This is a basic PowerShell script that I use on a USB with AutoUnattend.xml to get things moving. In the image below I am prompted to press Enter before my Drive is partitioned

My Drive Partition script includes a 984MB Recovery Partition

One the Drive has been Partitioned and Formatted, OSDDrivers kicks off gathering some information about the computer before starting to process the DellFamily Driver Packs. You can see the first few Packs didn't meet the criteria

Of all the DellFamily Driver Packs, it found a ModelMatch

Once the DellFamily Driver Packs are processed, its on to some individual Drivers which are evaluated to HardwareID Compatibility

All the Drivers that meet the criteria are then expanded to %SystemDrive%:\Drivers where my AutoUnattend.xml will be looking during Windows Setup

Windows Setup

Windows Setup will then kick off

Holding down Shift + F10 for a few seconds brings up a Command Prompt that I can use to launch Explorer (MS DaRT) to see my Drivers directory

Now off to the races

Windows

Once Windows Setup is complete, I can check the results in Device Manager where everything looks perfect

MS DaRT Remote Recovery
Drive Partition Prompt
Drive Partition Script
Deploy-OSDDrivers.ps1
Processing DellFamily Driver Packs
HardwareID Compatibility Matching
Driver Extraction
Drivers in Explorer