UIU Blog

It has come to our attention from more than a few inquiries that there is a bit of confusion over the relationship between Microsoft Windows Deployment Services and Microsoft Deployment Toolkit. Let's see if we can clear some things up.

We'll start with a brief description of each and then discuss the benefits and drawbacks of each.

Windows Deployment Services

Or WDS, is a server-based product designed for implementing Windows operating system image packages across a network. WDS can handle automated (using scripting files) deployment of Windows XP and newer operating systems. WDS also offers PXE (Preboot Execution Environment) services, which allow for network target devices to boot Windows PE (WinPE) for imaging purposes, etc. WDS replaced both Remote Installation Service (RIS) and Automated Deployment Services (ADS).
http://technet.microsoft.com/en-us/library/dd578757(v=ws.10).aspx

Microsoft Deployment Toolkit

Or MDT, is an application that can facilitate the deployment of operating systems and software applications as packages over a network using one of three modes: Zero Touch, Lite Touch or User Driven, in descending order of automation. MDT can operate independently or through a service such as WDS, which is most useful for initiating network-boot WinPE sessions via PXE. MDT replaced Business Desktop Deployment (BDD).
http://technet.microsoft.com/en-us/solutionaccelerators/dd407791.aspx

What MDT and WDS Bring to the Table

WDS is a free tool, so long as you've got Server 2008 or Server 2003 R2 in your environment and it supports multicast deployments. On the other hand, WDS requires a server OS to run, lacks a set of wizards to simplify configuration, only deploys operating systems (and at that only from image files [WIM]), requires heavy scripting to customize operating systems for deployment, and it requires that target machines be on-network. At least you'll gain extensive knowledge of WAIK/WADK!

As for MDT, it is also a free tool, but it can be installed on any PC or server. MDT utilizes structured image creation through templates and it employs deployment packages which can contain operating systems, drivers, updates, and applications. MDT automates script creation through pre-defined task sequences and can also deploy packages off-network. As a bonus, any knowledge gained through the use of WDS will be useful in MDT. Notable detractors with regard to MDT include the requirement of WDS for PXE services, (I know, right?!?), the fact that Zero-Touch and User-Driven methods require Microsoft System Center infrastructure and LTI deployments require user input on each target for each deployment.

How an MDT and WDS Relationship Should Work

It is our opinion that WDS is a very rudimentary, feature-sparse deployment solution that offers very little by the way of easy customization and requires significant knowledge of the inner workings of scripting, Sysprep, and boot image creation, whereas MDT offers a myriad more options for customization, application deployment and driver management and deployment flexibility. Let WDS handle your PXE environment and use MDT to deploy machines for your production environment.

There; that should make it clear as Mississippi mud…