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.
- Apply Drivers — Latitude 5550SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
- Apply Drivers — Precision 3591SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
- Apply Drivers — EliteBook 840 G11SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
- Apply Drivers — ProBook 460 G11SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
- Apply Drivers — ThinkPad X1 Carbon Gen 12SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
- Apply Drivers — Surface Laptop 7SELECT * FROM Win32_ComputerSystem WHERE Model LIKE …
- …and one more for every model you support.
- 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.

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.

What the tool automates for Configuration Manager
WIM creation
Package and distribute
Runtime package matching
Pilot and production
Custom drivers
How a ConfigMgr WIM package is built
- 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
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
Download, extract and create the WIM
The driver pack is downloaded, verified against its hash, extracted and captured into a single WIM file.
- 4
Create and distribute the package
A standard package containing the WIM is created and distributed to your selected distribution point groups.
- 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



Frequently asked questions
The questions that come up most.
Does the Driver Automation Tool create ConfigMgr driver packages?
How do I apply drivers from a WIM package during OSD?
Do I still need WMI filters for each model?
Do I need extra tools to open the WIM?
Does a WIM use more distribution point storage than loose drivers?
Can I use the same tool for Intune?
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