I thought that I could contribute to the driver saga chapters by writing a little about “washing drivers”. When I say “washing drivers” I mean removing all the garbage from the driver and ending up with a usable driver package for deployment. So the first thing you normally do is downloading drivers for you hardware. There are different methods of downloading drivers with different utilities.
HP: Softpaq download manager – Download HP SoftPaq Download Manager
Lenovo: Lenovo Update retriver – Update Retriever 4.03
Dell: Dell driver cabs: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx
Or you could use their website/ftp servers.
It’s not important how you get your drivers, but what you do with them. In my example I have downloaded all the applicable drivers for Latitude E6220. (I am lazy, so I downloaded the CAB)
The CAB size is 732 mb in download size. After downloading the CAB I extracted it like this (I use 7-zip for this):
The next thing you want to do is to install MDT 2012 Update 1 on your management computer. Can be found here: http://www.microsoft.com/en-us/download/details.aspx?id=25175
right click and import the drivers that you want to wash. In my Example “D:DriversE6220-win7-A05-5DVWKE6220win7”
Watch MDT doing it’s thing. It expands and extract the necessary information from the drivers and imports it. When it is done you will see that all the drivers is added in the deployment workbench like this:
In this case, I want to create X64 driver package for this computer model. So I delete every driver that is only for X86 (do not delete the ones that are for both). Mark them in the console and choose delete.
Now we can navigate to the deploymentshareout-of-box-drivers in explorer and have a look.
If I now compare the size of the X64 package from dell CAB with the one I washed we will see a great difference in size:
Old one 716mb
New one 424mb
The next thing now is to import this into SCCM for deployment. (this will of course not solve the pesky drivers that needs installation)
Remember to delete all the drivers from the workbench every time when you do this. And also remember that this method is not always perfect. It can fail from time to time, because of really bad drivers.
If I someday get the time to do it I will write a script that can export drivers from the MDT workbench so I don’t have to delete the drivers each time I want to create a new driver package. I hope someone finds this useful.
# UPDATE 26.10.2012:
I have finished the MDT Driver Exporter Tool. Read this post: http://msitpros.com/?p=1566