MDT 2010 and WDS

Was wondering if someone could explain if WDS part of MDT 2010 or you simply use it to create a .wim file then use that file in MDT 2010 to distribute the image file.

 

From what I have seen is that WDS creates the OS image with the applications and such that you want and then you use MDT to setup the servers or desktops.

 

So WDS is a separate utility from MDT?

 

WDS is a role in Server 2008 and R2, it is used to deploy wim files to clients and servers, R2 can be used to deploy VHDs via the CLI utility.

MDT 2010 is used to create custom images in enterprise deployment projects. MDT 2010 uses the Task Sequencer from System Center Configuration Manager 2010.

Tools used to create custom wim files Windows System Image Manager part of the Windows AIK, used to create unttend.xml files. This is the same tool OEMs use to create their custom images, combined with oobe.xml (OOBE is Out of the Box Experience), MDT 2010, DISM and legacy tool ImageX.

 

Thanks for the input

But doesn't MDT also deploys wim files as well as adding features/drivers to a Windows image? If this is the case, why would anyone use WDS and DISM? I'm pretty certain that MDT can't do PXE booting but there must be more to it than that.

Also, is using oobe.xml the same as sysprep /oobe?

 

MDT doesn't actually deply any images, it is designed to create custom Lite Touch Deployment WIMs that are deployed through a Wizard (i.e. Lite Touch) using USB Thumb Drives, DVDs, and WDS. We create Windows PE boot images and use the Task Squencer to add drivers and applications from the Deployment Share. This way I can deploy Windows 7 in my enterprise to any machine with my Volume License Solution, but the end product is customized (on the fly) for each vendors computer. So using the same Base WIM I can deploy 32bit and 64bit machines with vendor specific drivers and software the only difference is the assigned Task Squence.

MDT can also be used to enhance Configuration Manager 2007 task squencer so that I can do Zero Touch Deployments...

I teach 5 day classes on this stuff and do consulting on Managed Desktop Projects...

 

Thanks again for the clarification Jeff

I'm actually studying for the 70-680 and lots of this stuff is new to me. You don't happen to teach in the Houston area, do you?

 

Another quick question, why would someone want to boot in audit mode during first boot when (I'm assuming) everything can be configured before hand using DISM, WDS or MDT?

 

Hi David,

70-680 is a fun test, I took it way back when it was in Beta. I also taught the Beta Teach for the Microsoft Learning for the courseware for that test, 6492. If you are studying Windows deployment with MDT 2010, add Office 2010 deployment and you're ready for 70-685.

I'm actually in Seattle, I work as a Learning Consultant for Microsoft working with the 32 largest Global System Integrators. My time in the classroom isn't as much as it used to be. Funny thing is I'll be in Dallas next week teaching a group of consultants on Virtualization Architecture and the Private Cloud.

Audit Mode has two options Audit User and Audit System:

Audit System: Is used to install drivers and software the computer context, and can be used to test the image.

Audit User: Used to add drivers or software under the User context, It can also be used to test the image under the User.

Typically you would use it to create a "Gold" Image and then use the "Audit Pass" to customize, This reduces the number of Images needed to maintain. Now real world; it is used by OEMs mostly and enterprises use MDT and/or Configuration Manager.

HTH,

 

BTW: MSDN has a good explanation on the Audit Pass:

Differences between Audit Mode and Windows Welcome

 

Thanks again Jeff for the help
I'll definitely look into the Office 2010 deployment as soon as I familiarize myself with MDT 2010, WDS, VHD and all the other good stuff.