Another one of the most glaring deficiencies in my opinion with OS deployment using SCCM is the inability to import the same drivers for different models. I personally prefer to import ALL drivers for every model of machine I have versus trying to dig through other imported drivers and piece together what each model actually needs. It can be quite frustrating to say the least. I break up my drivers by model and would love to out of the box (I believe this may be addressed in SP2) simply import the entire driver set in each subfolder, then create a package per model and assign the drivers from the subfolders to their respective package. Well the good news is you CAN! You simply have to trick SCCM into allowing you to do this. Its quite simple actually. SCCM bases whether drivers are the “same” based on the calculated hash value of the driver files. By simply adding a unique text file to the driver folder it creates a different hash value and allows you to import them even if the actual drivers have already been imported. How I do it:
Break your drivers down by model in their own subfolders:
Now open the root folder and create a new txt file based on the model.
\\Server\share$\Drivers\Latitude E4300\Latitude E4300.txt
Now copy this file to your clipboard, then do a windows search within the root directory for “*”. Sort by type to gather all the folders at the top of the search. Right click on EACH folder within the search and past the model specific txt file.
Do this for each of your driver sets and when you import them into their own sub-folder under the drivers node they will import even if the actual driver has already been imported. 🙂 you can now make corresponding packages for each model all with their OWN version of their drivers.
I know this has made my life SO much better with managing drivers in SCCM. I hope it helps someone else.
*UPDATE* – A MUCH quicker and simpler way to create the txt file in your driver folders can be found here: