Setup guide
From download to first package, step by step.
Everything needed to install, configure and run the Driver Automation Tool against Configuration Manager or Microsoft Intune.
Getting Started
Follow these steps to download, extract, and launch the Driver Automation Tool for the first time.
Prerequisites & System Requirements
Before installing, ensure the host machine meets the following requirements. The tool runs entirely locally in PowerShell and needs administrative rights for registry and imaging operations.
| Option | Description |
|---|---|
| Driver Automation Tool version | v10.1.9.0 or later is required to connect to the API — older clients are blocked (HTTP 426) and prompted to upgrade |
| Operating System | Windows 10 or later, or Windows Server 2016 or later |
| PowerShell | Windows PowerShell 5.1 (built-in) or PowerShell 7+ |
| Administrator Privileges | Required — settings are stored in the HKLM registry and DISM WIM operations need elevation |
| Disk Space | Several GB of free space in temporary storage; varies by OEM/model selection |
| Internet Access | Required to download OEM catalogs and driver/BIOS packages |
Required PowerShell Modules
Depending on which OEMs and deployment platforms you use, the following modules must be installed. Missing modules cause the relevant integration to silently fail.
| Option | Description |
|---|---|
| HPCMSL | HP Client Management Script Library — required for HP catalog parsing and SoftPaq discovery. Install-Module -Name HPCMSL |
| ConfigurationManager | Ships with the ConfigMgr console — required for Configuration Manager integration |
| Microsoft.Graph | Required for Microsoft Intune integration (Graph API) |
Install-Module -Name HPCMSL.Download from GitHub
Navigate to the Driver Automation Tool GitHub repository. Click the green
Extract to a Suitable Location
Extract the downloaded ZIP file to a permanent location on your local machine, for example:
Avoid extracting to temporary folders, the Desktop, or deeply nested paths. The tool stores settings per machine, so a consistent location ensures your configuration persists across sessions.
C:\ normally inherits write access for Authenticated Users, so extract under Program Files or remove that permission. To accept the risk for packaging only, set the DWORD AllowUnprotectedTemplates to 1 under HKLM:\SOFTWARE\DriverAutomationTool.Launch from Administrative PowerShell
The Driver Automation Tool requires Administrator privileges for registry access (HKLM) and DISM WIM operations. Open PowerShell as Administrator and navigate to the extracted folder:
# Navigate to the tool directory
cd "C:\Program Files\DriverAutomationTool"
# Launch the tool
.\Start-DriverAutomationTool.ps1
# Or launch with dark theme
.\Start-DriverAutomationTool.ps1 -Theme Dark
If you see an execution policy error, you may need to allow the script to run:
Alternatively, to set the execution policy for all sessions, invoke PowerShell using:
End User License Agreement
On first launch, you will be presented with the End User License Agreement (EULA). Review the terms carefully before proceeding — by accepting, you acknowledge that the Driver Automation Tool is provided as-is, without warranty of any kind, and without formal support. Use of the tool is entirely at your own risk.
Configure Storage Locations
Before building packages, configure your storage paths in the Common Settings view. These paths determine where downloads are staged and where finished packages are stored.
| Option | Description |
|---|---|
| Temporary Storage | Working folder for downloads, extraction and WIM staging — must be a local path (UNC not supported for DISM) |
| Package Storage | Final output location for WIM and .intunewin packages — supports UNC/network paths |
| Long Path Support | Enable Windows long-path (>260 char) support when a deep temp path is detected; a live free-space bar is shown for each path |
| Package Retention | Automatically clean up superseded packages, keeping a configurable number of previous versions (0–5) |
| Backup / Restore | Set a backup path and Export/Import the full configuration for migration or team sharing |
| Purge Downloads | Clear all cached content from temporary storage immediately |
| Clean on Exit | Automatically remove temporary files when the application closes |
Build Your First Package
In Model Selection, choose your OEMs, OS version and architecture, then click Refresh Models to load the catalog. Tick the models to build (use Select All / search to filter), pick a Deployment Platform and Package Type, then click Build Package.
A Build Progress modal shows each model moving through the pipeline — Download → Extract → Package → Upload — with a status circle per stage:
Live detail streams into the Activity Log at the bottom of the view, and the status bar shows elapsed time. Click Abort to cancel a run.
When the build finishes, a summary window shows the package counts, and a per-model summary table — manufacturer, model, OS, and the driver and BIOS versions with whether each was updated, already current, had no update, or failed — is written to the log for every interactive, scheduled and headless run.
Interface Overview
The window has three areas: a title bar (feedback thumbs, theme toggle, support link, window controls), a sidebar grouped into Main (Model Selection, Custom Driver Pack), Configuration (ConfigMgr Settings and Intune Settings — each expandable into their own sub-views — plus Toast Notifications and Common Settings), and Tools (Logs, Modern Driver Mgmt, About), and the content area for the active view. ConfigMgr Settings expands to Environment, Package Management, Package Options and Logic Package; Intune Settings expands to Environment, Package Options, Package Management, BIOS Security and Maintenance Window. Toast Notifications is its own menu item because its settings apply to Intune packages and ConfigMgr Applications alike.
Themes
The tool ships with two themes — Dark (default) and Light — toggled instantly via the sun/moon button in the title bar (no restart). You can also launch directly into a theme:
Check for Updates
On startup the tool checks GitHub for a newer release and, if one is available, prompts you to update. You can re-check any time from the About view via Check for Updates.