Updating mdt out of box drivers

27 Oct

When you start the script it will ask for your deploymentshare (C:\Deployment Share).

Have you ever wanted to put every version of Vista, Server 2008, Windows 7, Server 2008 R2, and perhaps a version of XP or two on a single USB key? However, the daunting task of configuring said USB key to boot to some multiboot Linux distro or hacking a bit at bcdedit to boot a Win PE to handle it also made it something to avoid, at least for me, because, well, I tend to be lazy about these things.

We will focus on how drivers get installed via MDT, how to specifically control the drivers that get installed, and general best practices around proper driver management.

We will cover the following topics in this article: Those of us who created images for the deployment of Windows XP were often met with an enormous challenge of dealing with drivers for many different models of hardware.

Another reason being that we were relying on Plug and Play to figure out the right driver to install, which gives us less control of the driver that actually gets installed, based on a driver ranking process.

Fast forward to Windows Vista and current versions of Windows, and we can now utilize the magic of offline servicing to inject drivers into our Windows Imaging Format (WIM) as it is getting deployed.

Back in September back I posted a Power Shell script to allow the automatic querying of Dell client models from your SCCM environment, download the associated drivers and bios updates and import them into SCCM (

The script had the initial task of automating the following steps for your Dell driver imports; I had a lot of great feedback on the script and I am happy to hear it helped a lot of you automate your driver update process.

MDT creates is own folder structure under the deploymentshare.

With this in mind, consider the concept of having your customized Windows image created through your reference image build process, but it contains no drivers.

I wanted to create a powershell script that could export all the drivers inside a folder in the deployment workbench so I could just have all my drivers in the workbench forever and export them when I needed them.

I set about to put all of those versions of Windows one one key, along with some unattended applications (for this blog post, I’m just adding Office 2007 to keep it short).

You’re going to need a few things to start, most notably you’ll need a Windows machine that can install the latest Windows Automated Installation Kit (WAIK) for Windows 7 (that’d be Server 2003 SP1 or newer, Vista SP1 / Server 2008 or newer, or Win7 / Server 2008 R2 – sorry, no XP support, it seems).