When setting up driver repositories in the out of box drivers section in MDT, I can’t recommend enough using the “Total Control” method taught by Mr. Johan Arwidmark, because rather than playing guess and check or worse yet plug and pray, you should simply create a folder hierarcy that at least includes make and model variables as the foldernames. This allows you to then set driver groups using those same variables during the execution of the task sequence so only the folder that corresponds to the exact make and model will be used to inject drivers at deploy time. Now, none of this will work unless the names of these folders match the makes and models recorded in the hardware. Now, traditionally one could get this from ‘msinfo32’ at the run prompt, but did you know this can be done from a shell as well? Well you do now!
wmic computersystem get manufacturer
wmic computersystem get model
Why is this important? Well, in a true “bare metal” scenario where you’ve been shipped hardware with no operating system, you could run this command from WinPE and save yourself lots of valuable time.
Using the DriverGroup variables, you can take TOTAL CONTROL over which drivers the system uses. You can thank me later.
For more information on Orgainizing Drivers, see my post aptly titled, Organizing Drivers.