If you have read any of my articles on MDT and drivers you know that, for most environments, I like to have total control of my drivers (rather than the Total Chaos method which is default in MDT).
This means that I normally create a more detailed folder structure in the deployment workbench, that matches the drivers folder that I have on disk.Of course I could use old school DriverPaths method on MDT to avoid importing the drivers all together, but I kind of like the single instance store in MDT, and being able to use additional filter if I want to.
Here is a powershell script that imports drivers into MDT from a folder structure on disk…
Note: This script is written to import drivers into a clean driver store, the current version does not handle updates, so if you need to add more drivers, simply clean the store, and run the script again.
The structure on disk looks like this:
After running the script, it will look like this in the deployment workbench
You need to edit the following information in the script to reflect your environment
$DriverStore = “C:\Drivers”
$MDTDSRoot = “C:\MDTBuildLab”
$PSDriveName = “DS001”