Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Windows Deployment Service (WDS) vs Microsoft Deployment Toolkit 2012 (MDT) Choose The Right Tool Rhonda Layfield Sr. Deployment Architect Deployment Done."— Presentation transcript:

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

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 But First … What We Won’t Cover:
MDT WDS What We Won’t Cover: Windows Automated Installation Kit (WAIK) 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 AD/DNS 2 3 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 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 IGMP = Internet Group Management Protocol 22

23 Windows Deployment Services Multicast Enhancements
Multiple streams of traffic Optimized rates based on client 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 First client joins “transmission”
Multicast WDS Server First client joins “transmission”

25 Multicast WDS Server Fast Medium Slow Medium

26 Multicast WDS Server Medium Slow Medium Fast Medium Fast Medium

27 Multicast WDS Server Slow Medium Medium

28 Multicast WDS Server

29 Microsoft DEPLOYMENT TOOLKIT 2012 (MDT 2012)

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

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

32 Add Components Applications Drivers Packages Office 2010 Adobe Reader
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 Boot Target 2 MDT WinPE MDT 2012 Deployment Server 3 Connect to MDT Server and Download Image 35

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 WinPE Walk Through The Deployment Wizard

38 OR MDT Deployment Image Bare Metal Pro No network connectivity needed
No version control

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 Oakville Hamilton Good WAN Links MDT DS OS
Application Drivers Task Sequences OS Application Drivers Task Sequences OS Application Drivers Task Sequences MDT DS Good WAN Links Oakville Hamilton

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 DHCP MDT
MDT WinPE DHCP Server3 MDT Deployment Server I’m 53-FF-C 2K8R2 DNS DC

45 MDT Database Automate what gets installed on a computer How it works:
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 A zettabyte (symbol ZB, derived from the SI prefix zetta-) is a unit of information or computer storage equal to one sextillion (one long scale trilliard) bytes.[1][2][3][4] As of 2011, no storage system has achieved one zettabyte of information. The combined space of all computer hard drives in the world was estimated at approximately 160 exabytes in 2006.[5] This has increased rapidly however, as during the 2011 Fiscal Year, Seagate reported selling a combined total of 330 exabytes of hard drives. This does not include shipments from any other manufacturer, and only includes those sold during [6] As of 2009, the entire Internet was estimated to contain close to 500 exabytes.[7] 1,000,000,000,000,000,000,000 bytes = bytes = 1021 bytes The term "zebibyte" (ZiB), using a binary prefix, is used for the corresponding power of 1024. [edit] Comparisons for scale A zettabyte is equal to 1 billion terabytes. The world’s technological capacity to receive information through one-way broadcast networks was zettabytes of (optimally compressed) information in 1986, in 1993, 1.2 in 2000, and 1.9 (optimally compressed) zettabytes in 2007 (this is the informational equivalent to every person on earth receiving 174 newspapers per day). [8] According to the annual survey of the global digital output by International Data Corporation, the total amount of global data was expected to pass 1.2 zettabytes sometime during This is equivalent to the amount of data that would be generated by everyone in the world posting messages on the microblogging site Twitter continuously for a century.[9] Mark Liberman calculated the storage requirements for all human speech ever spoken at 42 zettabytes if digitized as 16 kHz 16-bit audio. This was done in response to a popular expression that states "all words ever spoken by human beings" could be stored in approximately 5 exabytes of data (see exabyte for details). Liberman did "freely confess that maybe the authors [of the exabyte estimate] were thinking about text."[10] Research from the University of Southern California reports that in 2007, humankind successfully sent 1.9 zettabytes of information through broadcast technology such as televisions and GPS. [11] Research from the University of California, San Diego reports that in 2008, Americans consumed 3.6 zettabytes of information.[12]

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

52 Sector Overhead 4K 4K Data ID Information Synchronization Fields
identify each sector by number and location a single bit is used to indicate if the sector has been marked defective Synchronization Fields Where do I go to find the next piece of a file Error Correcting Code (ECC) ensure data integrity Gaps or spacers separate sector areas and gives the controller time to process what has been read before moving on to process more data 522 518 524 520 516 4K 512 4K

53 What’s 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

54 Integrate MDT & WDS Together
The Best of Both Worlds Integrate MDT & WDS Together

55 MDT & WDS Together Targets PXE Boot WDS Server Win 7 Image
MDT 2012 Deployment Server MDT WinPE MDT WinPE Win 7 Image Download Image PXE Boot Targets 55

56 Feature Comparison MDT 2010 MDT 2012 WDS
Supports .wim images YES Supports .vhd images NO Requires Infrastructure Manage images easily Driver management Easy Difficult Provides PXE capabilities W/ WDS W/WDS Provides Multicast Creates offline or stand alone media Automate Deployments Corporate Deployment Share replicates DS to Branch Offices

57 See Rhonda For sessions I’ve presented visit:
New MDT 2012 training video Release date Mar 30, 2012 Check for more information I’ll tweet about it when it’s ready to sale $ US

58 MDT 2012 Video Installation and upgrade
Create and upgrade deployment shares Network deployments Automate network deployments Customize network deployments Branch office deployment shares No network needed deployments XP migrations to Windows 7 Server OS deployments MDT database MDT & WDS integration MDT & ConfigMgr 2012 integration

59 NEW 5 day DEPLOYMENT CLASS
5 days ACT MAP USMT Setup.exe architecture Windows AIK Windows SIM Sysprep ImageX DISM MDT 2010 MDT 2012 WDS WDS Windows 8 ConfigMgr 2007 R3 ConfigMgr 2012 KMS and Activation

60 Information & registration For Class
May 7-11 Washington DC area (Greenbelt Maryland) For more information on the class or to register visit More classes to come @DeploymentDR

61 Questions? Please don’t forget your evaluations …
4/21/2017 2:37 PM Please don’t forget your evaluations … Speaker Blog: Need more information on DMVMUG Visit or send a question to Questions? © 2007 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.


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

Similar presentations


Ads by Google