Intune Driver Packs — Automated OEM Driver Packaging for Microsoft Intune
Automate Intune driver packs with the Driver Automation Tool. Download OEM drivers, package them as Win32 apps, create detection rules and Intune assignment filters, and deploy model-specific driver packs through Microsoft Intune — for HP, Dell, Lenovo, Microsoft Surface, and Acer.
Microsoft Intune doesn't ship traditional OEM driver packs the way Configuration Manager task sequences historically did. The Driver Automation Tool closes that gap by bringing model-specific OEM driver-pack automation to Intune — turning raw vendor driver catalogues into ready-to-deploy Win32 apps.
Choose your driver source: SCCM Driver Packs or Latest Drivers
From build 10.2.4 onwards, the Driver Automation Tool lets you choose how each driver pack is built. Keep the OEM's SCCM Driver Pack — the Configuration Manager release refreshed roughly monthly — or switch Dell, HP, and Lenovo to Latest Drivers to pull the newest individual drivers straight from each vendor's live source: the Dell Command | Update catalog, the HP Client Management Script Library (CMSL), or the Lenovo System Update catalog. Other manufacturers continue to use their SCCM driver pack.
SCCM Driver Pack
The OEM's monthly Configuration Manager driver-pack release — the broadly validated baseline.
Latest Drivers
The newest Dell, HP, and Lenovo drivers pulled straight from each vendor's live catalog, so packs aren't held back by the OEM's SCCM release cadence.
Update cadence
Re-evaluate Latest Drivers packs Daily, Weekly, or Monthly on scheduled builds — a new pack is only rebuilt when the driver set actually changes.
What the tool automates for Intune
OEM driver download
Pulls the latest model-specific driver packs directly from HP, Dell, Lenovo, Surface, and Acer catalogues with hash verification and resume support.
Win32 app packaging
Wraps each driver pack as an .intunewin Win32 app with install/uninstall commands, ready to upload to Microsoft Intune.
Detection rules
Generates reliable detection logic so Intune correctly reports install state for every model-specific driver pack.
Assignment filters
Auto-creates Intune assignment filters keyed on model so each driver pack only targets matching hardware — no manual filter authoring.
Model-specific targeting
Builds one driver pack per model rather than a bloated universal pack, keeping downloads small and installs reliable.
Repeatable & scheduled
Run unattended via the command-line runner or a Windows Scheduled Task to keep Intune driver packs current as OEMs publish updates.
How Intune driver packs are built
- 1
Select the model and OS build
Choose the manufacturer, model, and Windows 11 build. The tool resolves the correct OEM driver pack from the live catalogue.
- 2
Download and extract
The driver pack is downloaded, verified against its hash, and extracted into a clean, deployable structure.
- 3
Package as a Win32 app
The extracted drivers are wrapped into an .intunewin package with install commands and a detection rule.
- 4
Upload to Intune
The Win32 app is uploaded to Microsoft Intune using device-code or app-registration authentication, with chunked Azure Blob uploads.
- 5
Create the assignment filter
An Intune assignment filter is generated for the model so the driver pack only installs on matching devices.
Building Intune driver packs as Win32 apps
Frequently asked questions
Does Microsoft Intune have OEM driver packs?
Not natively. Intune manages driver updates through Windows Update for Business driver policies, but it does not provide traditional model-specific OEM driver packs. The Driver Automation Tool fills this gap by downloading OEM driver packs and packaging them as Intune Win32 apps with detection rules and assignment filters.
How do I create Intune driver packs?
Select the manufacturer, model, and Windows build in the Driver Automation Tool. It downloads the OEM driver pack, extracts it, packages it as a Win32 app (.intunewin) with a detection rule, uploads it to Intune, and creates a model-based assignment filter — all automatically.
Which manufacturers are supported for Intune driver packs?
HP, Dell, Lenovo, Microsoft Surface, and Acer are supported out of the box, with automatic catalogue discovery and per-manufacturer extraction logic.
Can I build Intune driver packs from the latest OEM drivers instead of the SCCM driver pack?
Yes. From build 10.2.4 onwards, the Driver Package Build Type setting lets you pick SCCM Driver Pack or Latest Drivers. For Dell, HP, and Lenovo, Latest Drivers pulls the newest individual drivers from the Dell Command | Update catalog, the HP Client Management Script Library (CMSL), or the Lenovo System Update catalog — so your Intune packs are not limited to the OEM’s monthly release cadence.
How do Intune assignment filters work with driver packs?
The tool creates an assignment filter for each model so a driver pack only targets devices that match that hardware. This prevents driver packs from installing on the wrong models and keeps assignments manageable at scale.
Is it free?
Yes. The Driver Automation Tool is a free community tool distributed via GitHub.
Related pages
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