We are about to import the last of the pieces.  Our drivers.  Because up to this point, we are building a pile of well organized bricks to assemble our image.   One of the MOST important pieces is the drivers.

Our link to choose is “Out-of-Box Drivers”.  Like other portions of MDT 2010 we can (and SHOULD) create folders to sort this into manageable piles,  I like by Driver Type, Operating system and variant (x86 / x64) but you choose what makes most sense to you.

Importing drivers is identical to importing Updates (other than the location) and has the wonderful Powershell script at the end as well.

One of the nicest parts about the Import Drivers feature is that it will dig through and pull in driver structures.  This can be very nice if you have a vendor giving a single folder for multiple drivers but you’re not quite sure which is the RIGHT one for your particular card.

“A Lesson Learned”

But here’s a tip I learned from a great Master of MDT, the one who taught me.   See what the O/S has built in and what will come down from Windows Update.   You need to keep you driver base as clean as possible.


Well let me tell you a story about an ItPro.   An ItPro who shall (for this story) remain nameless.  This nameless ItPro had built an image in MDT 2008.  They were so proud it worked the first time. 

“Muah hah haa" the ITPro cackled. “Muah ha ha haaaa.  I am the Greatest ITPro! I have MASTERED MDT in moments!”

Then the silly fool went mad and imported every Dell driver on the planet.  All of them.  Even ones for components Dell hadn’t even thought of.  For some reason, the previously working “Perfect” install of Windows Vista Enterprise just started hanging on that “oh so perfect” WDS PXE boot.

No matter what the silly fool did.

All seemed dire until the Master of MDT walked to follow up.   The install was so messed up it had to be erased.    But not before he took a good look at hit.

“Young one…” the Master shook his head “Why does your deployment point have 25 gigabytes of drivers for three types of computers?”

It was then the ItPro learned from the Master, to keep it simple.

Drivers are easy to import.   Just learn to keep your list as LEAN and CLEAN as possible.  import what you NEED not what you WANT.

Take that from someone who might just know that poor fellow.

This was a fun story that was true to give us break.   But the facts are true.  Import your drivers, organize them well, keep the list as lean and clean as possible for best results.

We’ll take a quick look into setting up Dependencies on applications next time and then dive into the fun stuff afterwards.  The TASK sequence.