Importing drivers into System Center Configuration Manager R2 (SCCM) is a task I do at least once a month as new models are introduced into my work environment.

In this guide I am going to guide you through a step by step method of exporting drivers from an already existing build (ie vendor supplied, OEM) or from a driver package supplied for operating system deployment purposes from a vendor, such as Hewlett Packard.

How can I extract the drivers from an already existing Operating System?

Download and install Double Driver

_(this is freeware)_on the workstation you would like to extract the drivers from 2. Run Double Driver

Select Backup Select Scan Current System

Double Driver will then go through and scan the OS for drivers. It will automatically de-select all Microsoft drivers and only select those drivers that are not Microsoft signed. This is useful to avoid differences in MS supplied drivers compared to those that will install that are on the WIM and to avoid bloat on your driverstore. Select Backup Now

Select the destination you would like to back up the folder too. In my case I usually extract to a USB device (ie e:\drivers) as long as Structured Folder is selected (as is Default) Double Driver will export the drivers into suitability labelled folders – ie a folder for Bluetooth for the Bluetooth drivers. This will then start the driver back-up which depending on your configuration (amount and size of drivers) may take 5-10 minutes to complete.

Once completed. You have now extracted the drivers from your Windows workstation which can now be imported into a driver package in System Center Configuration Manager.

Where can I find driver packages for new builds for System Center Configuration Manager?

There are times when you won’t be using an already existing workstation as a base for drivers. Depending on the hardware manufacturers you are able to download a driver package directly from the vendor which can then be imported into configuration manager. Below is a list of manufacturer supplied MDT/SCCM driver packages:

Hewlett Packard

Windows 64 bit Driver Packs – http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html

Windows 32 bit Driver Packs – http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x86.html

HP WinPE Driver Packs – http://ftp.hp.com/pub/caps-softpaq/cmit/HP_WinPE_DriverPack.html

Lenovo

Windows 64 & 32bit drivers (inc WinPE) – https://support.lenovo.com/us/en/documents/sccm-index

Microsoft

Surface Pro 3 Driver Packs – https://www.microsoft.com/en-nz/download/details.aspx?id=38826

Surface 3 Driver Packs – https://www.microsoft.com/en-us/download/details.aspx?id=49040

Surface Pro 4 Win 10 Driver Packs – https://www.microsoft.com/en-us/download/details.aspx?id=49498

Surface Book Win 10 Driver Packs – https://www.microsoft.com/en-us/download/details.aspx?id=49497

Dell

Windows Driver Packs – http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-command-deploy-driver-packs-for-enterprise-client-os-deployment

How can I import drivers into System Center Configuration Manager?

Before opening the SCCM console – I would recommend copying the drivers you have either downloaded from the vendor or extracted from the workstation into the drivers source folder on your configuration manager server. You can then use the UNC path to quickly add the drivers in.

For example – my driver folder structure is as follows:

\SERVERNAME\sources$\Drivers\Microsoft

Underneath that folder structure I have the following folders & underneath that is another folder for the specific Model:

_DriverPackages

_

_Drivers

_

_Sources

_

Open SCCM (Configuration Manager 2012 R2)

Navigate to Software Library Expand Operating Systems Right click Driver Packages Select Create Driver Package

The Driver Package creation Wizard will open. Give the Driver Package a name – for example “Microsoft Surface Pro 3 x64” and add the UNC path for the driver package folder (this has to be empty) and click Ok

Once completed – you have created the driver package but now you need to import the drivers to add into the driver package. Navigate to: Software Library, Operating Systems, Drivers Right click Drivers and select Import Driver

You now point the Import New Driver wizard to the location you previously uploaded your drivers to – drivers source folder using a UNC path and click Next.

SCCM will then verify the path and list the drivers you would like to import. Verify the information is correct and if needed specific a Category and click Next Select the Driver package you created to add the drivers into and select Next In the terms of this example – we are skipping adding the drivers to the boot image but if you do have a Network or Storage driver to add to your boot image you can add it here (make sure you tick Update distrubution points when finished option), click Next Verify the summary is correct and click Next to start the import process. This will then import the drivers into the Configuration Manager Driver database and assign them to the specified driver package. Once completed – navigate to: Software Library, Operating Systems, Driver Packages and find your package. Right click and Distribute Content – select your Distribution points to deploy the package too and you are done!

How can I add a driver pack into the task sequence for Operating System Deployment?

Once you have your driver pack added and distributed you want to add it to your operating system task sequence for use.

Navigate to: Software Library, Operating Systems, Task Sequences and find your OS task sequence right click it and select Edit Find the section in the Task Sequence you want to add the drivers to. Select Add and Apply Driver Package

Select Browse… next to Driver Package and find and locate your driver package and Add. Once Added specify an appropriate name and comment.

Click the Options tab up the top Click Add Condition and select Any Condition and click Ok WQL (WMI queries) allow you separate models allows you to specify differnet driver packages to different models in Configuration Manager (SCCM). Even if it is a task sequence for only one device I usually do a WMI query to avoid any mishap in the future and easily allows for additional growth of devices. Once the “Any Condition” has been specified as per the last step.. Click Add Condition again and select: Query WMI.

Add the follow WMI query in – Be aware of any syntax which may be incorrect from copying from the internet (such as “) and in the %% instead of – Surface Pro 3 replace with your model:

SELECT * FROM Win32_ComputerSystem WHERE Model Like “%Surface Pro 3%”

Note: In order to find the model, you can run: “wmic csproduct get name” from a command prompt on a machine that you are about to build and use that output to put in the query.

Or you may have to do some googling or binging to get the correct WMI queries. You can also do it by manufacturer such as:

SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE “%Dell%”