How-To-Config

Out-Of-Box Driver Selector

If you don’t have many different Computer Models / Brands to maintain in your organization it is common to import all drivers into one MDT Out-Of-Box Driver folder. But what if drivers from different models overlap each other? In this article I’ll explain how to create a Driver Selector based on Brand & Model.

Personally I’d like to keep things clean. That’s why I created a folder for each Operating system / Architecture. The structure looks as follows:
(OPERATING SYSTEM)
–| (ARCHITECTURE)
—| (BRAND)
—-| (MODEL)
mdt-1

I added all drivers in the specific folders. To speed up the deployment process I delete all x86 drivers in the x64 folders and vice versa. Especially when it comes down to Lenovo drivers it could be that duplicate drivers will get imported. Remove also the duplicates as this will also speed up the deployment process.

To find out the MAKE & MODEL from your computer you can either run a CMD command or via MSInfo32:
CMD Command:

wmic computersystem get model

mdt-2

MSInfo32:
Go to Start -> Run -> msinfo32
The following dialog will appear:
mdt-3

Next go to your customsettings.ini:
Right click MDT Deployment Share -> Properties
mdt-4
Then go to the Rules tab
mdt-5
We’re only using 64 bit Windows 8.1 installations in our Deployment Server so by default I add the following lines to the customsettings.ini file:

DriverGroup001=Windows 8\x64\%Model%
DriverSelectionProfile=nothing

If you want to select a different driver folder for every model you can add the model on top of every DriveGroup:

[HP Notebook 123]
DriverGroup001=Windows 7\x64\%model%
DriverSelectionProfile=nothing

[HP Desktop 234]
DriverGroup002=Windows 8\x64\%model%
DriverSelectionProfile=nothing

[Dell Laptop 345]
DriverGroup003=Windows 7\x86\%model%
DriverSelectionProfile=nothing

[Lenovo Laptop 456]
DriverGroup004=Windows 8\x86\%model%
DriverSelectionProfile=nothing

Another thing to note is that when using this procedure to deploy Lenovo machines, other special considerations may need to be made. This is due to the fact the Lenovo reports back a model string that frequently changes. This is explained further in the following blog which also has a recommended solution for dealing with this scenario:
http://blogs.technet.com/b/mniehaus/archive/2009/07/17/querying-the-mdt-database-using-a-custom-model.aspx

I used the following article as reference:
https://blogs.technet.com/b/askcore/archive/2013/05/09/how-to-manage-out-of-box-drivers-with-the-use-of-model-specific-driver-groups-in-microsoft-deployment-toolkit-2012-update-1.aspx

Leave a Reply