Deploy Windows 7 Using Microsoft s FREE Deployment Tools. Rhonda J. Layfield Sr. Deployment Architect Deployment Done Right

Transcription

1 Deploy Windows 7 Using Microsoft s FREE Deployment Tools Rhonda J. Layfield Sr. Deployment Architect Deployment Done Right

2 Rhonda Layfield I live in Washington DC in the States Been in the IT industry for 30 years US Navy for 7 years Write for Windows IT Pro magazine Setup and Deployment MVP Desktop Deployment Product Specialist (DDPS) I am self employed The name of my company is Deployment Done Right

3 Get In Touch With Me Let me know how your deployments are going: Follow me on Twitter Sign up for one of my hands-on deployment classes September 2011 in Washington DC Contact me for details Bring me into your organization to hear more about deployment For short term consulting and in-house training

4 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 The tools are: Microsoft Deployment Toolkit 2012 (MDT 2012) Windows Deployment Service (WDS) The One Tool Not Covered is System Center Configuration Manager (SCCM) But first

5 Overview Image Formats and Scenarios MDT Installation Configuration Network deployments XP migrations MDT advanced features

6 Overview WDS Installation Configuration Multicast traffic Multicast traffic MDT & WDS integration Differences between MDT & WDS

7 Windows Image Formats There are two Windows Image.Wim Virtual hard disk.vhd

8 .Wim Compared to.vhd.wim Contain a single volume (c: d: e:) Multiple images may be stored in a single.wimfile Single instancing No redundant file storage Service image offline Apply patches quick and easily.vhd Contain an entire hard drive (multiple volumes) Service image offline

9 Three Types of Images: Thick, Thin, Hybrid Thick images contain an OS and all applications More difficult to make changes to later Thin images usually contain only the OS Applications are deployed after the OS Group Policy deployment MDT 2010 U1 Manually Hybrid images contain OS and corporate approved applications Like line of business (LOB) applications created in-house

10 Scenario Bare Metal Refresh Replace Upgrade 4 Deployment Scenarios New machines Description Keeping the old hardware installing a new OS on the existing machine Replacing existing computer with a new computer while maintaining user s settings and data Unless your upgrading from Vista there is no direct upgrade path

11 MICROSOFT DEPLOYMENT TOOLKIT 2010 MICROSOFT DEPLOYMENT TOOLKIT 2010 UPDATE 1 (MDT2010 U1)

12 Setting Up MDT 2010: as easy as Install WAIK Install MDT Create a Deployment Share Operating Systems: Server 2008 R2 Server 2003 R2 Vista Windows 7 MDT 2010 U1 Deployment Server

13 Create a Deployment Share Open Deployment Share

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

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

16 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

17 Then You Need To 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

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

19 Then, Get MDT Ready To Deploy The Custom.wim Image Import the Custom.wim Create a task sequence Deploy

20 MDT WinPE 1 Copy WinPE 2 Boot Target MDT 2010 U1 3 Deployment Server Connect to MDT Server and Download Image

21 Boot Client With WinPE Walk Through The Deployment Wizard

22 Automate The Client

23 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

24 Automate The Client Deployment BootStrap.ini CustomSettings.ini If you make changes to the Boostrap.ini you will need to update the deployment share again to reflect those changes For Help on variables to add to these files: Help Microsoft Deployment Toolkit Reference Properties Property Definitions

25 Automate A Deployment Share

26 XP Migration Refresh Scenario Gather Application Information Configure MDT and Application Information 1 2 Begin MDT Deployment Wizard 3 XP SP2/SP3 Get list of Applications Configured List & Registry Scan = New list Pre Selected USMT Gathers User and Application Settings (local store) MDT 2010 U1 Deployment Server

27 XP Migration Refresh Scenario Boots to WinPE - Win 7 is Installed 7 Windows XP SP2/SP37 Applications are Installed from MDT Deployment Share USMT Applies User and Application Settings (local store) 8 9 MDT 2010 U1 Deployment Server

28 MDT Network Deployment

29 Get MDT Deployment Server Ready Add an Operating System Windows 7 Add Drivers Create a Task Sequence

30 Get MDT Deployment Server Ready

31 XP Migration With Applications Performing Refresh scenario Currently running XP Migrate to Windows 7 Applications that are currently installed on XP should automatically be re-installed on Windows 7

32 1 Gather Application Information Log on as a standard user for read only mode HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall Uninstall key name

33 1 Gather Application Information.Exe sare easy the application name is obvious.msi sare displayed as GUID s look for the DisplayName.MSI EXE

34 1 Copy Key Name to Notepad

35 1 This is what you will get: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersio n\uninstall\{fc7bacf0-1ffa-4605-b3b4-a66ab382752d} This is the piece you want: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersio n\uninstall\{fc7bacf0-1ffa-4605-b3b4-a66ab382752d} If your doing a lot of applications at one time: XMLNotepad = {FC7BACF0-1FFA-4605-B3B4-A66AB382752D} NetMon 3.3 = {365C5A F-B975-56EA878D0A06} Office 2007 = { A FF1CE}

36 Gather Application Information

37 2 Configure MDT Server: With Application Information Performed on the MDT deployment server Within the Deployment Workbench Add an application Open the properties of the application Go to the Details tab Input the Uninstall registry key name from your Notepad file

38 Add Application data to MDT Server

39 2 Create the script that will search for applications Create LTIAppDetect.vbs script Download LTIAppDetect.vbs from Copy the LTIAppDetect.vbs script to your deployment share s Scripts folder

40 2 Configure MDT to look for applications -edit the properties of your deployment share From within the Deployment Workbench / Properties of your deployment share / Rules tab [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipAppsOnUpgrade=YES SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES

41 2 Add LTIAppDetect.vbs [Settings] Priority=Default Properties=MyCustomProperty [Default] UserExit=LTIAppDetect.vbs OSInstall=Y SkipAppsOnUpgrade=YES SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES

42 Configure Deployment Workbench With Script

43 3 Begin MDT Deployment Wizard Launch LiteTouch.vbs from the XP workstation Map a drive to your deployment server: Net use P: \\ServerName\DeploymentShareName\Scripts Deployment server = DeploySrv Deployment share = DeploymentShare$ Net use P: \\Deploysrv\DeploymentShare$\Scripts Then from the P: drive double click on LiteTouch.vbs OR Start/ Run /

44 Steps 4 and5 You won t see these 4 5 Get a list of Applications Configured These are the applications you configured on the deployment server in the deployment workbench List & Registry Scan = New list Pre Selected The list of configured applications on the deployment server and the list of applications from the XP registry are compared to create a third list The third list is the list of applications displayed as pre selected during the deployment process

45 6 USMT Gathers User and Application Settings User State Migration Tool v4.0 gathers existing user data, settings and application settings This is called Users State User State is stored locally scanstate.exe C:\MININT\StateStore /v:5 /o /c /hardlink /nocompress/efs:hardlink /i:c:\minint\usmt\migapp.xml /i:c:\minint\usmt\migdocs.xml /l:c:\minint\smsosd\osdlogs\usmtcapture.log /progress:c:\minint\smsosd\osdlogs\usmtcapture.prg

46 Steps 7 and 8 TaskSequence Performs These: 7 Boots to WinPE-Windows 7 is Installed Windows 7 is installed 8 Applications are Installed from MDT Deployment Share Applications selected from the Select one or more applications to install page (Windows Deployment Wizard) are installed

47 USMT Applies Locally Stored Settings 9 USMT applies previously gathered user data, settings and application settings loadstate.exe /v:5/c/lac/hardlink/nocompress /i:c:\minint\usmt\migapp.xml /i:c:\minint\usmt\migdocs.xml /l:c:\minint\smsosd\osdlogs\usmtrestore.log C:\MININT\StateStore /progress:c:\minint\smsosd\osdlogs\usmtrestore.prg

48 Mandatory Applications

49 Make Applications Mandatory If you don t want a person to be able to de-select an application during deployment Edit LTIAppDetect.vbs script Set oapplications = oenvironment.listitem("applications") To: Set oapplications= oenvironment.listitem("mandatoryapplications")

50 Clean Up Active Directory Users and Computers If you rename your newly migrated machine the old name still exists in AD So, you might want to clean that up by deleting the old machine name

51 What We Covered 4 Deployment Scenarios Migrated an XP machine to Windows 7 while also maintaining: User s data User s Settings IE Favorites Desktop settings Application Installations and Settings

52 Selection Profiles

53 MDT Components The MDT components are: Operating Systems Applications Drivers Packages Task Sequences To use some of the Advanced Features of MDT you will need to group MDT components together The way you group MDT components is by creating a Selection Profile

54 MDT s Selection Profiles The MDT components you group will determine what you can do with the selection profile: Group drivers and packages to inject into the MDT generated Windows Pre Installation Environments (WinPEs) Group drivers to inject into an OS task sequence Control which MDT components are included in Media Group MDT components to replicate (and keep in sync) to linked deployment shares

55 Branch Offices Dubai MDT Deployment Server Good WAN Link Unreliable WAN Link London New York

56 MDTs Media Feature Media allows you create a fully deployable image OS Applications Drivers Packages Task sequences

57 MDT MediaDeployment Bare Metal Pro Con No Network Connectivity No Version Control

58 Storage Options If you choose a DVD burn the.iso file to the DVD If you choose: External hard drive UFD (USB flash drive) You will need to prepare the mediafirst

59 Steps For Media Create a selection profile Run the New Media Wizard Update the Media Prepare the media Deploy

60 Create a Selection Profile Create Media

61 Preparing Media Open an elevated command prompt DISKPART List disk(record the number of the external device) Select disk N (N is the disk number Select disk 2 Clean create partition primary select partition 1 Active format fs=ntfs Assign exit Close the command prompt

62 Preparing Media Completed Open Windows Explorer Turn on show hidden files Navigate to the Media Content folder Copy the entire Content folder Boot folder Deploy folder EFI folder Autorun.inf Bootmgr Bootmgr.efi

63 Linked Deployment Shares (LDS)

64 Branch Offices Dubai OS Application Drivers Task Sequences MDT Deployment Server Good WAN Links London New York

65 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 To create a LDS Begin on the target computer

66 On The Target Computer This is the computer you want to copy the LDS to Create a folder Ensure there is enough hard drive space MDT will not check this for you Share the folder Now you are ready to create the LDS on the MDT server

67 Create A LDS on The MDT Server Create a selection profile containing all the MDT components you would like copied (replicated) to the target computer Create a new LDS Type in the UNC path to where you want the new LDS Example \\server\share \\W7\LondonDS Choose your selection profile

68 Create A LDS on The MDT Server -Continued Select one of the options: Merge the selected contents into the target deployment share OR Replace the contents of the target deployment share folders with those selected Rename the LDS R-click the LDS and choose Replicate Content The contents you selected in your selection profile will be copied to the new LDS via ROBOCopy

69 Create a LDS

70 When You Make Changes The changes need to be replicated to the target computer You can either right-click the LDS and choose Replicate This will replicate EVERYTHING again even things that have not changed OR Change the replication technology to use Distributed File System- Replication (DFS-R) Create a scheduled task that will replicate changes whenever you want them replicated Only what has changed will be replicated

71 MDT Database

72 MDT Database Automate what gets installed on a computer Imaged and re-imaged 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

73 Set Up MDT Database SQL is not supported on DCs You ll need a member server Install SQL (Express will work) Configure the database with the computer identifier The computer will check in with the database and perform whatever steps you choose

74 Johan Arwidmark mikael nystrom

75 What We Covered: Create a Master image Automate the Deployment Group MDT Components Put a complete deployment on a USB flash drive Create multiple deployment shares and keep them current MDT Database feature

76 Windows Deployment Service (WDS)

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

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

79 Installing WDS In the box with Server products, well kind of Install WDS on a 2003 SP1Server Install RIS Install patch from the WAIK: windows_deployment_services_update.exe Install WDS on a 2003 SP2Server Control Panel / Add/Remove Programs / Windows Components / WDS Install WDS on a 2008 (& R2) server Server Manager Add Roles Select Windows Deployment Services from the list of roles

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

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

82 WDS Server also a DHCP Server?

83 WDS server responds to

84 Known clients are Prestaged in Active Directory

85 Prestaging and The GUID 564D49219C768546A956C310ED7D2BF6

86 Use a Specific WDS Server

87 Add 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

88 Add 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"

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

90 From The Client Perform a Network Boot Sometimes called a Pre Execution Boot Process OR PXE Boot

91 WDS And Network Deployments

92 Multicast Transmissions Server1 sends packet 1 to client1 Server1 sends packet 1 to client2 Server1 sends packet 1 to client3 Server1 sends packet 1 to all clients Server1 sends packet 1 to client1, client2, client3

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

94 Multicast WDS Server First client joins transmission

95 Multicast WDS Server Fast Medium Slow Medium

96 Multicast WDS Server Medium Slow Medium Fast Medium Fast Medium

97 Multicast WDS Server Slow Medium Medium

98 Multicast WDS Server

99 The Best of Both Worlds Integrating MDT & WDS Together

100 MDT & WDSTogether MDT 2010 U1 Deployment Server WDS Server MDT WinPE MDT WinPE Win 7 Image Download Image PXE Boot Targets

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

102 What We Covered Image Formats and Scenarios MDT Installation Configuration Network deployments XP migrations MDT advanced features

103 WDS Installation Configuration Multicast traffic Multicast traffic MDT & WDS integration Differences between MDT & WDS

104 Thank you for attending my session! Let me help- AND TrainSignal Deployment Training DVD Set I ll tweet about new products as they are released: DeploymentDR@Twitter.com