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

1. Windows Deployment Service (WDS) vs Microsoft Deployment Toolkit 2012 (MDT) Choose The Right Tool Rhonda Layfield Sr. Deployment Architect Deployment Done Right

2. Rhonda Layfield • I live in Washington DC • 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 • Twitter handle - @DeploymentDr.com

3. 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) • Both tools are either FREE or In-The-Box

4. What We Won’t Cover: • Windows Automated Installation Kit (WAIK) WDS MDT But First …

5. Windows Deployment Service (WDS)

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

7. WDS Requirements DHCP 1 3 2 AD/DNS Bare-Metal WDS

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

9. Configuring WDS WDS snap-in Right-click Servers Add Server – defaults to local server Right-click your server and choose Configure Server.

10. Store Your Images Store your images on a drive other than where the OS resides

11. WDS Server also a DHCP Server?

12. WDS Server Responds To…

13. Known Clients - Active Directory

14. Prestaging and The GUID 564D49219C768546A956C310ED7D2BF6

15. Use a Specific WDS Server

16. 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

17. Add a Boot Image Compare WinPEs

18. Adding an OS Image • Both .wim and .vhd are supported • Adding a .wim • Right–click 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"

19. Add Drivers & Applications • 3rd party drivers only • No Applications can be deployed from WDS • Only a Thick image containing your applications

20. From The Client • Perform a Network Boot • Sometimes called a Pre Execution Boot Process • OR • PXE Boot

21. WDS Client Deployment

22. WDSServer sends packet 1 to client1 WDSServer sends packet 1 to client2 WDSServer sends packet 1 to client3 Multicast Transmissions WDSServer sends packet 1 to all clients WDSServersends packet 1 to client1, client2, client3

23. Windows Deployment Services Multicast Enhancements • Multiple streams of traffic • Optimized rates based onclient connection • Client Auto Removal • Slower clients can be dropped to unicast or entirely (only in standard multicast) • Boot Image Multicast • Windows PE boot images can use multicast (clients with EFI) Fast Medium Slow

24. Multicast WDS Server First client joins “transmission”

25. Multicast WDS Server Fast Medium Slow Medium

26. Multicast WDS Server Fast Fast Medium Medium Medium Slow Medium

27. Multicast WDS Server Medium Medium Slow

28. Multicast WDS Server

29. Microsoft DEPLOYMENT TOOLKIT 2012 (MDT 2012)

30. Setting Up MDT 2012:as easy as 1-2-3 Operating Systems: Server 2008 R2 Server 2003 R2 Vista Windows 7 Install WAIK 1 MDT 2012 Deployment Server Install MDT 2 Create a Deployment Share 3

31. Create An Image To Deploy Create A Reference MDT 2012 Deployment Server SYSPREP W7 DVD W7 DVD Windows Server 2003 R2 Windows Server 2008 & R2 XP SP3 Vista SP1 Windows 7 & SP1 2 1 Deploy OS Add an OS 3 Store Image

32. Add Components • Applications • Office 2010 • Adobe Reader • Drivers • 3rd party • Packages • OS patches • Language packs

33. 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

34. 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

35. MDT Network Deployment 1 Copy WinPE 2 Boot Target 3 MDT 2012 Deployment Server MDT WinPE Connect to MDT Server and Download Image

36. 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 don’t want that • ConfigMgr OSD does not support booting from USB hard drives

37. Boot Client With WinPEWalk Through The Deployment Wizard

38. OR MDT Deployment Image Bare Metal

39. Automate the Clients Experience • When you run the Deployment Wizard • Choose which screens are displayed during the deployment • Suppress the ones you don’t want anyone to see or change like: • Product Key • Administrator’s password • Customize the words displayed on the pages

40. Linked Deployment Shares (LDS)

41. Branch Offices Toronto OS Application Drivers Task Sequences OS Application Drivers Task Sequences OS Application Drivers Task Sequences MDT DS Good WAN Links Hamilton Oakville

42. 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

43. MDT Database Feature

44. MDT Database Feature Server1 I’m 00-FF-B0-2B-48-09 MDT WinPE DHCP MDT Deployment Server I’m 53-FF-C0-27-59-38 2K8R2 Server3 DNS DC

45. MDT Database • Automate what gets installed on a computer • Original image and re-imaging • How it works: • 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

46. New To MDT 2012

47. MDT 2012 & ConfigManager • Aligned more closely with Config Manager 2012 • Shipping times: • RTM after Config Manager 2012 ships • Still need to integrate MDT 2012 into Config Manager 2012 • New Terminology • Advertise = Deploy • Packages can either be optional or mandatory • Optional = available • Mandatory = required

48. New Features • New Deployment Wizard • Deploy .vhd images • Supports deploying ThinPC and POSReady • ThinPC – basic Win7 • Citrix or Terminal Services client • POSReady • Point of Sales – cash registers • Cross platform deployment • 32 bit WinPE can deploy 32 or 64 bit OSs

49. More New Features • Diagnosis and Recovery Toolset (DART) • Allows remote control of target machines • Even in the WinPE phase • Deployment Workbench gets a new tab • Monitor deployment clients • 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

50. 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 • 4 primary • 3 primary and 1 extended (break it up into logicals) • GPT allows a maximum disk and partition size of 9.4 ZB • 1 zettabyte = 1 billion terabytes • Supports upto 128 volumes