Task Sequence Steps – Apply Driver Package
This post is part of our Task Sequence – Beyond the Docs series.
Similar to Auto Apply Drivers, this step adds drivers to the Windows Driver Store to be applied during the Windows Setup (OOBE) that will happen after the restart. This step is typically used to apply a specific driver package to a model of computer. Typically a step is duplicated per model, and conditions control which one is run.
Both Apply Driver Package and Auto Apply Driver rely on DISM to add drivers to the Windows Driver Store, however, they work completely differently. Auto Apply does a compare of the hardware id on the machine with all of the drivers you have imported in CM, while Apply Driver Package downloads the drivers in the package, and just has DISM hammer though all of them trying to apply them all and seeing if they land, more on that later.
<div class=”NOTE alert alert-note”><h5>NOTE</h5><p><p>Many organizations have dropped using this step and creating driver packages and gone with using legacy packages to store driver files, then running a command line step to have DISM recursively apply the drivers in the package contents. This essentially does the same thing without the need of importing the drivers into CM.</p>
<div class=”TIP alert alert-tip”><h5>TIP</h5><p><p>More information about Driver Package Creation can be found <a href=”docs/ConfigMgr-Docs/Content/SCCM-Content-Driver-Packages.md”>here in the content area.</a></p>
Demo – Install driver package w/ Recurse
Lets go to the logs!
We start by showing the pre-step condition evaluation, which determined which Apply Driver Package step should run, the one that matches the hardware it’s running on.
It then downloads the payload and runs the dism command to add the drivers to the windows driver store, recursing the driver package content.
The DISM Log will show all of the Drivers that were processed and applied.
So overall, it’s a straight forward process. The Task Sequence downloads the drivers in a driver package, then leverages DISM to apply them to the Offline Image, which then get installed during the Windows Setup Process.
Because the Task Sequence is just leveraging DISM, this is what has opened up the community to doing all sorts of variants for managing and deploying drivers. Personally, we only use standard packages now, containing drivers, and no longer import drivers themselves into CM.
More Task Sequence Steps – Beyond the Docs
Find all of our Task Sequence – Beyond the Docs series posts here.
Related Vendor Links
Community Blog Posts
- ConfigMgr Driver Management in just four steps – By Matthew Teegarden
- Speed Up Driver Package Downloads for ConfigMgr OSD