So all the fun stuff is over and we’re done…

No wait.  We’re not.  I was mumbling something out using “WDS” or “Windows Deployment Services”

This is simply a Role you add in Server 2008 or Server 2008R2.  This is free to use so flip it on Smile

Just go into the Server Manager, right click on “Roles”, choose “Add Roles”, click next and choose “Windows Deployment Services”


We’re not going to go TOO deep into it’s setup.  Yes you can have multiple servers across many environments, blah blah blah.  Today we’re going to stick with the basics.  So just take all the default settings and move along (“These are not the Droids you’re looking for ….”)

You’ll find “Windows Deployment Services” as a new entry in your Administrative Tools.  Clicking on it you’ll see the name of your server under “Servers” with a Yellow Exclamation mark


So Right click on your server name in the WDS console and choose Configure Server.  This will present a nice simple step by step Wizard to get you going.  It’s going to ask to create a new folder structure for just WDS.  If this is the same server as MDT, LET IT DO THIS.  Remember to treat MDT and WDS as two separate entities.  One CREATES the images, the other is a tool to enable DEPLOYMENT of images.  Just like with another Role or Application.  Give them their own Sandbox.  Perhaps some Chocolate Chip cookies (Or are they no longer on the HCL for Server 2008R2?)

It will create a folder called C:RemoteInstall for it’s stuff and then ask you how you want to respond to PXE requests.  If you need 100% control use “Respond only to known client computers” otherwise just choose “Respond to All” (Don’t worry, you can always turn this on or off as you need it)

When it asks you if you want to add images to Windows Deployment  Server now, clear the box and don’t for the moment.

To make this all work we need three things, a Boot Image, DHCP and a DeploymentShare created by MDT.

Right click on “Boot Images” in the Left hand console in Windows Deployment Services and browse to one of the LiteTouch.wim files that were created earlier in your C:MyMedia folder. They will typically be under ContentDeployBoot . In our case you may find two (One is a 64bit bootable WIM file and one is a 32bit bootable WIM file) You can add in each one, it won’t hurt.

Just browse to each one of these files, follow the step by step simply wizard and you’ll have two new bootable images within WDS

If nothing else is done, your environment should now (as long PXE boot is enabled on a network card) be able to now choose to boot from the WDS server from one of these two WIM files.

Now we haven’t configured them so to make it install from the DeploymentShare you’ll actually have to provide credentials and the UNC pathname of the share.  From this point it will at least be an LTI install if you haven’t configured it otherwise for the DeploymentShare itself.

But like everything in MDT, this can be tweaked even further.

So if you would like to have that bootable file have the USERID and PASSWORD and UNC pathname already known (so this becomes even simpler) just go to the Properties of the C:MyMedia folder, Click on the “Rules” and add in the following lines to your configuration


You’ll have to right click on the MyMedia in MDT and choose “Update” to rebuild the WIM files.   Once this is done just right click on each entry in WDS for the Boot files and choose “Replace Image” and just follow the same procedure as last time to browse to those files in the C:MyMedia folder.

Well it’s now officially the Long Weekend.  My fingers are numb.  My brain is empty and I want to go play with some more Powershell Smile

I’ll post a single posting tomorrow with the entire series and links so you could just access that if you like.   If you have any comments, add them in as this is something I’d like to see the community join in with.  MDT is fantastically amazing and Powerful tool.  If there is any way I can help YOU get off the ground with it, ping me.   Because we all need shorter days and more time to relax

MDT 2010 gives us just that Smile

Thanks Michael Niehaus for creating such a Kick Ass tool! YOU ROCK!