Microsoft Configuration Manager

Configuration Manager driver management, built on WIM packages

The Driver Automation Tool doesn't create ConfigMgr driver packages. It builds one compressed WIM file per model, stores it in a standard package and distributes it to your distribution points — ready for Modern Driver Management to pick up during OSD.

That's a deliberate choice. Nothing is imported into the driver catalog, so the site database stays lean; each model is a single file to download; and the task sequence needs one step for every model instead of one per model with its own WMI filter.

WIM packages, not driver packages

The tool builds WIM files — on purpose.

Configuration Manager's native driver packages import every driver into the site database. The Driver Automation Tool skips that entirely: each model's drivers are captured in a single WIM and stored in a standard package.

Native ConfigMgr driver packages

  • Site database. Every INF is imported into the driver catalog — thousands of driver objects and category rows per model.

  • Content. Hundreds or thousands of loose files per package, each tracked and hashed individually.

  • Task sequence. One Apply Driver Package step per model, each with its own WMI query condition.

  • Adding a model. Import drivers, build the package, edit the task sequence, write and test a WMI filter.

Driver Automation Tool WIM packages

  • Site database. Nothing is imported. The database holds one standard package record per model and OS.

  • Content. A single WIM file per package — one object to distribute, validate and download.

  • Task sequence. One step for every model. The matching package is resolved at runtime.

  • Adding a model. Build the package with the tool. The existing task sequence picks it up automatically.

Modern Driver Management

No more WMI filters. No more sprawling task sequences.

The WIM packages are built for the Modern Driver Management solution. During OSD it reads the device's manufacturer, model and baseboard, finds the matching package, downloads that one WIM and applies it offline.

Before: a step per model
  1. Apply Drivers — Latitude 5550SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
  2. Apply Drivers — Precision 3591SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
  3. Apply Drivers — EliteBook 840 G11SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
  4. Apply Drivers — ProBook 460 G11SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
  5. Apply Drivers — ThinkPad X1 Carbon Gen 12SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
  6. Apply Drivers — Surface Laptop 7SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
  7. …and one more for every model you support.
After: one step for every model
Apply Driver PackageInvoke-CMApplyDriverPackage.ps1
  • Detects the model and baseboard at runtime and matches it to the right package.
  • Downloads only that model's WIM — nothing else is pulled to the device.
  • Resolves packages through the AdminService, or the XML Logic Package when you'd rather not depend on it.
  • New models need no task sequence edits — build the package and it is found.
Logic Package view in the Driver Automation Tool, generating the DriverPackages.xml manifest that maps models and baseboards to their driver packages
The XML Logic Package maps each model and baseboard to its package, so the task sequence can resolve drivers without the AdminService.

Why WIM

Mountable anywhere. Stored once. Downloaded once.

Packaging drivers as a WIM rather than loose files or a vendor archive keeps content portable and efficient from the site server to the device.

  • A native Windows format

    WIM is the same image format Windows itself ships in. DISM mounts it in full Windows and in WinPE with no third-party extractors, vendor self-extracting EXEs or extra tooling in your boot image.

  • Single-instance by design

    A WIM stores identical files once, so drivers shared across INF folders take no extra space. In the content library each package version is one file, which keeps distribution points lean.

  • One file to download

    During OSD the device downloads a single file instead of thousands of loose ones — fewer content lookups, less overhead on the distribution point and faster staging.

Package Management view in the Driver Automation Tool, listing driver and BIOS packages with version, package ID and distribution status
Package Management — each model is a single standard package, moved between pilot and production.

What the tool automates for Configuration Manager

No database bloat

Drivers stay inside the WIM rather than the driver catalog, so the site database holds one package record per model — not thousands of driver objects.

WIM creation

Downloads and extracts the OEM driver pack, then captures it into a WIM. Optionally skip WIM compression and let ConfigMgr compress content itself.

Package and distribute

Creates the standard package, files it in your console folder and distributes it to the distribution point groups you choose.

Runtime package matching

Packages are named and tagged for Modern Driver Management, which matches the device to its package by model and baseboard during OSD.

Pilot and production

Promote packages between pilot and production states from Package Management, so new drivers can be tested before they reach every build.

Custom drivers

Add your own drivers to an existing package — the WIM is mounted, the drivers are added and the package is redistributed in place.

How a ConfigMgr WIM package is built

  1. 1

    Connect to the site server

    The tool connects to your primary site over WinRM and can query hardware inventory to highlight the models you actually run.

  2. 2

    Select models and the OS build

    Choose the manufacturer, models and Windows build. The correct OEM driver pack is resolved from the live catalog.

  3. 3

    Download, extract and create the WIM

    The driver pack is downloaded, verified against its hash, extracted and captured into a single WIM file.

  4. 4

    Create and distribute the package

    A standard package containing the WIM is created and distributed to your selected distribution point groups.

  5. 5

    Deploy with Modern Driver Management

    One Apply Driver Package step in your task sequence finds the package for each device at runtime, downloads it and applies the drivers.

Managing ConfigMgr packages in the Driver Automation Tool

Connecting to the site server and querying known models
Connecting to the site server and querying known models
Choosing console folders and distribution point groups
Choosing console folders and distribution point groups
Adding custom drivers to an existing WIM package
Adding custom drivers to an existing WIM package

Frequently asked questions

The questions that come up most.

Does the Driver Automation Tool create ConfigMgr driver packages?
No — and that is by design. It creates a standard package containing a single WIM file per model. Drivers are never imported into the ConfigMgr driver catalog, which keeps the site database lean and avoids the overhead of tracking thousands of individual driver objects.
How do I apply drivers from a WIM package during OSD?
Use the Modern Driver Management solution. A single step running Invoke-CMApplyDriverPackage.ps1 detects the device model and baseboard, finds the matching package through the AdminService or the XML Logic Package, downloads the WIM, mounts it and applies the drivers to the offline Windows image.
Do I still need WMI filters for each model?
No. Package matching happens at runtime, so one step in the task sequence covers every model. Adding a new model only means building its package with the tool — the task sequence does not change.
Do I need extra tools to open the WIM?
No. WIM is a native Windows image format. DISM, which ships with Windows and WinPE, mounts it directly, so there are no third-party extractors or vendor installers to add to your boot image.
Does a WIM use more distribution point storage than loose drivers?
Usually less. The WIM format stores identical files only once, so drivers shared between INF folders are deduplicated inside the image, and each package version lands in the single-instance content library as one file. You can also disable WIM compression so ConfigMgr applies its own compression during distribution.
Can I use the same tool for Intune?
Yes. The same model selection and catalog drive both platforms; for Intune the WIM is wrapped as a Win32 app with detection rules and assignment filters instead.

Want the full picture?

See everything the Driver Automation Tool can do — driver packs, BIOS updates, ConfigMgr and Intune deployment — on the main site.

Tell me more