In this post you will learn how to add Apply Driver Package Step to SCCM Task Sequence. When you are installing the clean operating system, It’s important to add the device drivers. It helps the computer to connect with the hardware device like keyboard, mouse, monitor, etc. Device drivers can be used when installing the full OS on the destination computer and using Windows PE in a boot image.
Do you know what is drivers, and why do you need to install drivers? Refer to the following post What are Drivers, and Why do we need Drivers? If you want to start from scratch and explore more about the Driver Creation process using SCCM, Let’s explore SCCM Driver Import Driver Package Creation Process Guide. This post will be helpful to streamline lots of SCCM admins during OSD/Task Sequence/Image creation activities.
Once you are done with the Driver Package creation process, The next step is to Integrate Driver package into Task Sequence. Let’s check the below post to know more about the Integration process and available useful options in Apply Drivers Package Step.
How to Add Apply Driver Package Step to SCCM Task Sequence
The following steps show you how to include the driver package that you have created in your task
sequence –
Create or Edit an Existing Task Sequence
This Guide will help you to create a Configuration Manager task sequence from scratch. Use the following steps to modify an existing task sequence.
- In the Configuration Manager console, go to the Software Library workspace, expand Operating Systems, and then select the Task Sequences node.
- In the Task Sequence list, select the task sequence that you want to edit. Select Edit to modify.
To add this step in the task sequence editor, select Add, select Drivers, and select Apply Driver Package.
Important – Ensure that you place this step after Apply Operating System.
- On the Properties tab for Apply Driver Package step, You can configure the following settings –
- Driver package
- Install driver package via running DISM with recurse option
- Select the mass storage driver within the package that needs to be installed before setup on pre-Windows Vista operating systems
- Do unattended installation of unsigned drivers on version of Windows where this is allowed
I recommended you Create the proper folder structure and step inside your task sequence for better SCCM driver management.
Driver package
Specify the driver package that contains the needed device drivers. Select Browse to launch the Select a Package dialog box. Select an existing driver package to apply. The bottom of the dialog box displays the associated package properties.
Install driver package via running DISM with recurse option – Select this option to add the /recurse parameter to the DISM command line when Windows applies the driver package.
Select the mass storage driver within the package that needs to be installed before setup on pre-Windows Vista operating systems
Specify any mass storage drivers needed to install a classic OS.
Driver : Select the mass storage driver file to install before setup of a classic OS. The drop-down list populates from the specified package.
Model : Specify the boot-critical device that is needed for pre-Windows Vista OS deployments.
Do unattended installation of unsigned drivers on version of Windows where this is allowed – This option allows Windows to install drivers without a digital signature.
Options for Apply Driver Package
On the Apply Driver Package step, Options tab. Here you can configure the additional settings of this task sequence step –
Continue on error – When you select Continue on error on the Options tab of this step, the task sequence continues when driver package fails to apply. When you don’t enable this option, the task sequence fails and will not execute the remaining steps.
Add Condition – Query WMI
This step is most important for applying the driver package step, and It allows you to install the driver package for particular hardware models.
Select Add a condition > Query WMI from the drop-down menu to create a query to target this driver
package to only the model it is intended.
In the query window, type select * from Win32_ComputerSystem where Model like ‘Latitude 5410%’. The query now appears. You can use the Test query button to verify the query. It returns 1 if your ConfigMgr Console is installed on the model being queried or else 0. Click OK.
- Click OK in the Task Sequence Editor window to save the changes to your task sequence.
Task sequence configured to apply driver package step for Dell Latitude 5410 systems. If you have more platforms to support, create additional driver packages using the same process.
About Author -> Jitesh has over 5 years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus area is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.
Resources
- SCCM Driver Management Guide Best Practices ConfigMgr
- SCCM Driver Import Driver Package Creation Process Guide
Is there any way to add a dialog box for unsupported hardware when a local IT guy tries to Image a machine that is not supported in current production env ?
Yes! You can add the custom UI at beginning in Task Sequence step, with WMI Query (Contains Supported Models). If the step meets the requirements or check the supported models then skip to next step else user will get a prompt “The machine is not supported for production”
Hi Jitesh,
Thank you for your reply. I am actually not sure how to add the dialog box for the warning that this model is not supported.
Appreciate your help.
I want to know how to add this prompt “The machine is not supported for production” step..
Appreciate your help.
We’ll have a post coming soon! Hope that will help you to achieve the requirement. Please be in touch. I will keep you updated.
Any update on this?
Can you please help to understand what update are you looking for?
Hello,
We have 2 models: Dell 7320 and 7320 2-in-1.
How should be the query in this case in order to differentiate both models?
Select * From Win32_ComputerSystem Where Model Like “%Latitude 7320 2-in-1%”
Select * From Win32_ComputerSystem Where Model Like “%Latitude 7320%”
I have 1 question – is the pnp driver and driver package both requied fir task sequence or driver package enough for baremetal (Clean) image required in osd.
Another option is:
SELECT * FROM Win32_ComputerSystemProduct WHERE Name LIKE ’21CB%’ OR Name LIKE
’21CC%’
type: system information on your taskbar and look for System Model, enter first 3-4 characters that it starts with. If you have multiple models use the OR Name LIKE for one command line.