Windows Deployment Service (WDS) vs Microsoft Deployment Toolkit 2012 (MDT) Choose The Right Tool

Rhonda Layfield Sr. Deployment Architect Deployment Done Right

Rhonda Layfield
I live in Washington DC in the States Been in the IT industry for 30 years US Navy for 7 years Setup and Deployment MVP Desktop Deployment Product Specialist (DDPS) I am self employed
I provide training and consulting services

The Free Giveaway

Almost 16 hours WAIK MDT WDS SCCM

2 sets to giveaway Valued at $400.00 each

The Goal For This Session

To help you decide which tool is right for you
All tools deploy both Server and Desktop Operating Systems (OSs) All tools are either FREE or In-The-Box

But First

Windows Image Formats

There are two
Windows Image
.Wim

Virtual hard disk

.Vhd

.Wim Compared to .Vhd

.Wim
Contain a single volume (c: d: e:) Multiple images may be stored in a single .wim file Single instancing
No redundant file storage

.Vhd

Service image offline

Contain an entire hard drive (multiple volumes) Service image offline

Three Types of Images: Thick, Thin, Hybrid

Thick images contain an OS and all applications Thin images usually contain only the OS
Applications are deployed after the OS
Group Policy deployment MDT 2010 U1 Manually

More difficult to make changes to later

Hybrid images contain OS and corporate approved applications

Like line of business (LOB) applications created in-house

Microsoft DEPLOYMENT TOOLKIT 2012 (MDT

2012)

Setting Up MDT 2012: as easy as 1-2-3

1

Install WAIK Install MDT Create a Deployment Share

2
3

MDT 2012 Deployment Server

Operating Systems: Server 2008 R2 Server 2003 R2 Vista Windows 7

Create a Deployment Share Open Deployment Share

1 Add an OS
W7 DVD W7 DVD Windows Server 2003 R2 Windows Server 2008 & R2 XP SP3 Vista SP1 Windows 7 & SP1

MDT 2012 Deployment Server

2
Deploy OS

SYSPREP

3
Store Image Create A Reference

Add Components
Applications Drivers
Office 2010 Adobe Reader 3rd party OS patches Language packs

Packages

Over Time You Will Have Multiple Images To Deploy:

Multiple OSs
Windows 7 SP1 base DVD Windows 7 custom Hybrid .wim image Windows Server 2008 R2

Drivers for different models of machines Applications for different groups of users So you will need a way to group components together for a specific deployment This is called a Task Sequence

Update The Deployment Share

Updating the deployment share creates a custom MDT Windows Pre Installation Environment (WinPE) This WinPE is very intelligent
Pre-configured to know who the MDT server is and the name of the Deployment Share

Add an OS, Application, Drivers Create a Task Sequence Update the Deployment Share

1 Copy
MDT WinPE

WinPE

2 Boot

Target

MDT 2012 Deployment Server

Connect to MDT Server and Download Image

Quick Note on Using USB Hard Drives

Different BIOS number the USB hard drives differently
When numbered 0 they can show up as fixed drives and you dont want that ConfigMgr OSD does not support booting from USB hard drives

Boot Client With WinPE Walk Through The Deployment Wizard

OR
MDT Deployment Image

Bare Metal

Pro Con

No network connectivity needed No version control

Automate the Clients Experience

When you run the Deployment Wizard Choose which screens are displayed during the deployment Suppress the ones you dont want anyone to see or change like:
Product Key Administrators password

Customize the words displayed on the pages

Linked Deployment Shares (LDS)

Branch Offices

Washington DC
OS Application Drivers Task Sequences

MDT DS

Good WAN Links

New York

Dallas

Linked Deployment Shares (LDS)

LDS allows you to copy a subset (or all if you choose) of components to another machine Even Windows 7 can host a LDS But, if you host the LDS on a server you can integrate WDS with it To create a LDS Begin on the target computer

MDT Database Feature

MDT Database Feature

Im 00-FF-B0-2B-48-09 Server1

DHCP

MDT WinPE

Server3 Im 53-FF-C0-27-59-38 2K8R2 DNS DC

MDT Deployment Server

MDT Database
Automate what gets installed on a computer How it works:

Original image and re-imaging

When a client begins the Deployment Wizard a script runs: ZTIGather.wsf

Gathers all kinds of information from the client like:
Universally Unique ID (UUID) Serial number Asset tag MACAddress

Queries the MDT database for a match Applies the configured settings

New To MDT 2012

MDT 2012 & ConfigManager

Aligned more closely with Config Manager 2012 Shipping times:
RTM after Config Manager 2012 ships Beta 2 around October Still need to integrate MDT 2012 into Config Manager 2012 Advertise = Deploy Packages can either be optional or mandatory
Optional = available Mandatory = required

New Terminology

New Features
New Deployment Wizard Deploy .vhd images Supports deploying ThinPC and POSReady
ThinPC basic Win7
Citrix or Terminal Services client Point of Sales cash registers

POSReady

Cross platform deployment

32 bit WinPE can deploy 32 or 64 bit OSs

More New Features

Diagnosis and Recovery Toolset (DART)
Allows remote control of target machines Even in the WinPE phase Monitor deployment clients

Deployment Workbench gets a new tab Properties of the deployment share are more streamlined New UDI wizard designer Image factory create .wim or .vhd
Vhd can be deployed via Virtual Machine Manager as templates to create new virtual machines

Unified Extensible Firmware Interface (UEFI)

Full support of UEFI
Intels replacement for PC BIOS Offers support for GUID partition tables (GPT)
MBR partition tables restricted disk partition sizes to a maximum of 2.19 TB MBR supports only 4 partitions GPT allows a maximum disk and partition size of 9.4 ZB
1 zettabyte = 1 billion terabytes Supports upto 128 volumes
4 primary 3 primary and 1 extended (break it up into logicals)

512 Byte 4K Misalignment

Legacy drives support 512-byte physical sectors OSs use 4K logical block sizes
virtual memory pages & file systems like NTFS

4K
512 512 512

512

512

512

512

512

512

512

512

512

Sector Overhead
Data ID Information
identify each sector by number and location

Synchronization Fields
ensure data integrity

a single bit is used to indicate if the sector has been marked defective

Error Correcting Code (ECC) Gaps or spacers

Where do I go to find the next piece of a file

separate sector areas and gives the controller time to process what has been read before moving on to process more data

4K
512 516 512 518 512 524 512 512 520 518 512 524 512 522 512 518

Whats The Problem? The Fix

The result is performance is degraded
10% 30%

The fix is for hardware and OSs to both read at a 4K sector size 4K sector sizes are not supported for XP But they are in WinPE 3.0

Windows Deployment Service (WDS)

Windows Deployment Service

WDS replaces Remote Installation Services (RIS) Provides both boot and installation images from the WDS server Supports .WIM and .VHD technology

WDS Requirements
1
2 3

DHCP

AD/DNS WDS

Bare-Metal

Install WDS
Install WDS on a 2008 (& R2) server
Server Manager Add Roles Select Windows Deployment Services from the list of roles

Configuring WDS
WDS snap-in Right-click Servers

Add Server defaults to local server Right-click your server and choose Configure Server.

Store Your Images

Store your images on a drive other than where the OS resides

WDS Server also a DHCP Server?

WDS Server Responds To

Known Clients - Prestaged in Active Directory

Prestaging and The GUID

564D49219C768546A956C310ED7D2BF6

Use a Specific WDS Server

Adding a Boot Image

A boot image is a Windows Pre Installation Environment (WinPE) The most current will always be best Windows 7 SP1 Boot.wim can deploy
Vista SP1 Windows 7 Windows 7 SP1 Windows Server 2003 R2, 2008 and 2008 R2

Use an older WinPE will produce undesired results

Adding an OS Image
Both .wim and .vhd are supported Adding a .wim
Rightclick Install Images
Add Install Image Image Groups

Adding a .vhd

Elevated command prompt WDSUTIL /Add-Image /ImageFile:\\Server\Share \Win7.vhd /Server:WDSServer /ImageType:Install /ImageGroup:Windows7 /Filename:"Windows7.vhd"

Add Drivers & Applications

3rd party drivers only

No Applications can be deployed from WDS Only a Thick image containing your applications

From The Client

Perform a Network Boot
Sometimes called a Pre Execution Boot Process OR PXE Boot

WDS Deployments

Multicast Transmissions
WDSServer sends packet 1 to client1 WDSServer sends packet 1 to client2 WDSServer sends packet 1 to client3

WDSServer sends packet 1 to all clients

WDSServer sends packet 1 to client1, client2, client3

Windows Deployment Services Multicast Enhancements

Multiple streams of traffic
Optimized rates based on client connection
Fast

Client Auto Removal

Slower clients can be dropped to unicast or entirely (only in standard multicast)

Medium

Boot Image Multicast

Slow

Windows PE boot images can use multicast (clients with EFI)

Multicast
WDS Server

First client joins transmission

Multicast
WDS Server

Fast

Medium

Slow

Medium

Multicast
WDS Server

Medium

Slow

Medium

Fast

Medium

Fast

Medium

Multicast
WDS Server

Slow

Medium

Medium

Multicast
WDS Server

The Best of Both Worlds

MDT & WDS Together

MDT 2012 Deployment Server
MDT WinPE

WDS Server

MDT WinPE

Win 7 Image Download Image

PXE Boot

Targets

Feature Comparison
Supports .wim images

MDT 2010
YES

MDT 2012
YES

WDS
YES

Supports .vhd images

Requires Infrastructure

NO
NO

YES
NO

YES
YES

Manage images easily

Driver management Provides PXE capabilities Provides Multicast Creates offline or stand alone media Automate Deployments Corporate Deployment Share replicates DS to Branch Offices

YES
Easy W/ WDS W/ WDS YES YES YES

YES
Easy W/WDS W/WDS YES YES YES

NO
Difficult YES YES NO YES NO

What We Covered
Deployment The Basics
Image formats Types of images (thick, thin, hybrid)

Deployment Tools
Microsoft Deployment Toolkit 2010 (MDT) Windows Deployment Service (WDS)

Thank you for attending my session!

Please fill out your evaluations Let me help [email protected] WWW.DeploymentDr.Com TrainSignal Deployment Training DVD Set

Ill tweet about new products as they are released:

[email protected]

Remember To Complete Your Evaluations!

You could WIN a Samsung Focus Windows Phone 7! Let us know what you liked & disliked! Remember, 1=Bad, 5=Good Please provide comments!

No purchase necessary. The contest is open to residents of Canada (excluding government employees). The Toronto TechDays evaluation form contest begins on October 25th, 2011 and ends on October 26th, 2011. The Vancouver TechDays evaluation form contest begins on November 15th, 2011 and ends on November 16th, 2011. The Montreal TechDays evaluation form contest begins on November 29th, 2011 and ends on November 30th, 2011. Participants can enter the contest in one of two ways: (1) complete and submit an evaluation form by the contest close date; or (2) provide contact information by the contest close date. The draw for Toronto will take place on October 31st, 2011. The draw for Vancouver will take place on November 21st, 2011. The draw for Montreal will take place on December 5th, 2011. The chances of being selected depend upon the number of eligible entries. Selected participants will be contacted by phone and/or e-mail and will be required to answer correctly a time-limited skill-testing question. There are three (3) prizes available to be won. One (1) prize will be given away for each TechDays event in Toronto (October 25-26 2011), Vancouver (November 15-16 2011) and Montreal (November 29-30 2011). The prize consists of a Samsung Focus Windows Phone 7 (handset only; voice and/or data plan not included) (approximate retail value of $499 CAD). The prize will be delivered to the shipping address designated by the winner within 6-8 weeks. The winner may be required to sign a declaration and release form. For full contest rules, please see a Microsoft TechDays representative.

You can email any additional comments directly to [email protected] at any time.

Q&A

Enjoy The Conference

66

 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.