Search English (United States)  Svenska (Sverige)
Thursday, February 23, 2012 ..:: Home ::.. Register  Login
 Text/HTML Minimize

On March 21, the first day of MMS 2011, I announced the immediate availability of the Deployment Research blog and Deployment Research Facebook page. Sites filled with video-tutorials on how to deploy operating systems. Information about this new site, as well a bunch of other deployment related community sites was by the way also printed (thank you FedEx) and put in the attendee-bag (Thank you Microsoft) for every MMS 2011 attendee, about 4000 people.

This also means that the deployvista.com blog will not be much active anymore. It will still exist, but the content will gradually be migrated over to the new site, cleaned-up and converted into the new format…

Happy deployment, and I hope to see you online in the forums…

Regards / Johan Arwidmark
Microsoft MVP – Setup & Deployment


 Print   
 MDT - Drivers - PowerShell is king Minimize
Location: BlogsJohan Arwidmark    
Posted by: johan 2/18/2011

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.

Download the Import Drivers From File System Script

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"

Happy Scripting...

/ Johan

Permalink |  Trackback

Comments (5)  
Re: MDT - Drivers - PowerShell is king    By Chad_Work on 7/20/2011
Johan, I need help with a major hurdle using MDT 2010. What is the best place to post a problem to get your help? I posted here because I didn't see an e-mail address for you. Thanks,
-Chad

Re: MDT - Drivers - PowerShell is king    By johan on 7/24/2011
I have sent an email to the address you reigstered with.

I do try to monitor the technet forums, so that's a good place to ask questions too...

/ Johan

Re: MDT - Drivers - PowerShell is king    By dckwak on 12/7/2011
Johan,
How about a script that does the reverse. Take the MDT OOB drivers store and export it to a FileStore.
Thanks
Dave

Re: MDT - Drivers - PowerShell is king    By Jonas Voll on 2/3/2012
Hey I am looking for some way to install or deploy operating systems!
This will need to be accessible for the blind and other disabled computer usres!
Support for Audio. Screen magnifiers & screen readers will be required.
Support for audio or speech synthesis!
You may find most of these hardware devices in various configurations such as USB or PCI!
Thanks!

Re: MDT - Drivers - PowerShell is king    By johan on 2/4/2012
Hi Jonas,

I'm sorry but WinPE does not support audio, rendering screen readers useless. I haven't seen that being added to future versions of WinPE either. I will meet the product teams at the MVP Summit in Redmond late february. I will raise the questions then...

/ Johan


  
Copyright Deployvista.com 2006-2010 (c)   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2012 by DotNetNuke Corporation