This document summarizes steps for automatically deploying Windows 7 without using complex Microsoft tools. It outlines an 11 step process: 1) Installing Windows Deployment Server, 2) Configuring image deployment, 3) Deploying the first image, 4) Dealing with drivers, 5) Automating the Windows PE boot image, 6) Automating the Windows setup phase, 7) Creating a thick image with applications, 8) Installing Microsoft Deployment Toolkit, 9) Performing silent installations and repackaging applications, 10) Layering applications onto Windows, and 11) Preserving user data. The document emphasizes making the process as simple as possible by leveraging new features in Windows Deployment Server and Microsoft Deployment Toolkit

1. Automatically Deploying Windows 7 without theMicrosoft Alphabet SoupGreg ShieldsSenior Partner & Principal Technologistwww.ConcentratedTech.com

2. This slide deck was used in one of our many conference presentations. We hope you enjoy it, and invite you to use it within your own organization however you like.For more information on our company, including information on private classes and upcoming conference appearances, please visit our Web site, www.ConcentratedTech.com. For links to newly-posted decks, follow us on Twitter:@concentrateddon or @concentratdgregThis work is copyright ©Concentrated Technology, LLC

3. Loves the ToolsHates the Names“Microsoft wants you to PXE your machine to WDS, using an Unattend.XML file built from WSIM in the WAIK after pre-staging your GUID inside the ADUC. Oh, and don’t forget MDT (formerly BDD!), who’s Deployment Workbench wraps around all this ridiculousness.”Automating Windows 7 Installation for Desktopand VDI Environmentshttp://nexus.realtimepublishers.com

4. It’s Alphabet Soup!“Microsoft wants you to PXE your machine to WDS, using an Unattend.XML file built from WSIM in the WAIK after pre-staging your GUID inside the ADUC. Oh, and don’t forget MDT (formerly BDD!), who’s Deployment Workbench wraps around all this ridiculousness.”Automating Windows 7 Installation for Desktopand VDI Environmentshttp://nexus.realtimepublishers.com

5. Windows Deployment’sBiggest Problem

6. Windows Deployment’sBiggest ProblemThe Internet.

7. Windows Deployment’sBiggest ProblemThe Internet.Each tool evolved through many different versions.Older versions had numerous shortcomings.Resolving those required some oddball hackery.Bloggers report hacks that are no longer timely.You’ll find solutions to problems that no longer exist.Confusion abounds!

8. Windows Deployment’sBiggest ProblemThe Internet.Each tool evolved through many different versions.Older versions had numerous shortcomings.Resolving those required some oddball hackery.Bloggers report hacks that are no longer timely.You’ll find solutions to problems that no longer exist.Confusion abounds!The Solution.Don’t trust what you read.You don’t need the command lineas much as you used to.

9. Greg’s Easy 11 Stepsto Deployment Automation!Installing Windows Deployment ServerConfiguring Image DeploymentDeploying your First ImageDealing with DriversAutomating WinPE Boot ImageAutomating the “Set Up Windows” PhaseCreating a Thick Image w. ApplicationsInstalling Microsoft Deployment ToolkitSilent Installations & RepackagingLayering Applications atop WindowsPreserving User Data

10. Step 1: Installing Windows Deployment ServerWDS is a Windows 2008 R2 role.Remote Installation Folder locationPXE Server Initial SettingsAdd Image Wizard

11. Stepping Back: WIM Files?.WIM files are Microsoft’s image file format.Two files are most important, right off DVD media. \sources\boot.wim \sources\install.wimYou maycreate more .WIM files as you create custom images down the road.However, your goal is to not create more.Highest goal: One WIM per processor architecture.

12. Step 2: Configuring Image DeploymentWDS can deploy images via USB stickI’m showing you network deployment only.Caution: Network deployment uses multicast.Multicast consumes bandwidth.Multicast is often not passed between subnets.Thus, YMMV.

13. DEMO: Configuring WDS

14. How to Name the Computer?Requiring Administratorapproval enables thename-at-installfunctionality of WDS.Boot via PXEApprove & Name in WDSEnjoy!

15. How to Name the Computer?One small permissions change is required.In Active Directory Users and Computers, right-click the domain and then select Delegate Control. Change the object type to include computers and add the computer object of the Windows Deployment Services server into the dialog box. Click Next. When prompted, select Create a custom task to delegate. Select Only the following objects in the folder. Then select the Computer Objects check box, and then Create selected objects in this folder. Click Next. In the Permissions box select Write all Properties and click Finish.

16. Step 3: Deploying a ComputerThis lookssuspiciouslysimilar to Ghost.However,Auto-Cast isvery useful. Willsetup an always-on deployment.

17. DEMO: DEPLOYMENT!

18. Stepping Back: Layering the OSA Case for the Layered Approach to Deploying Windows Desktopshttp://technet.microsoft.com/en-us/magazine/ee835710.aspx

19. Step 4: Dealing with DriversPlug and Play eliminates the need to create multiple images because of driver differences.WDS presents a driver database to the deployment. Plug and Play detects and installs those it needs.

20. Step 4: Dealing with DriversPlug and Play eliminates the need to create multiple images because of driver differences.WDS presents a driver database to the deployment. Plug and Play detects and installs those it needs.Hardest part: Finding and unpacking the right drivers to add to WDS.EXEs/MSIs must be unpacked to INFs.WDS will import all INFs in a file path.

21. DEMO: injecting drivers

22. Boot Image DriversSometimes WinPE needs extra drivers to boot.This is not common.…but you’ll know when you need it!When it does, those drivers must be specially injected into your boot image.This is done within WDS before a deployment.Be careful! You can corrupt the little guy!If you do, get a new one from the DVD.

23. DEMO: injecting drivers INTO boot images

24. Step 5: Automating WinPENext Step: Automating installation prompts.We want this installation to complete from start to finish without asking any questions.Two areas need automating:The WinPE half.The Set Up Windows half.

25. Step 5: Automating WinPENext Step: Automating installation prompts.We want this installation to complete from start to finish without asking any questions.Two areas need automating:The WinPE half.The Set Up Windows half.Automate by pre-answering their questions using Windows System Image Manager.This tool is hard (unless you have me!).

26. Step 5: Automating WinPE

27. The Right Questions?The Right Answers?

28. DEMO: Automating WinPE

29. Unattending WDSValidate and createyour XML file.Save it toC:\RemoteInstall.Point to it in WDS.Note: One file perprocessor architecture.

30. Step 6: Automating Set Up WindowsNext Step: Automating installation prompts.We want this installation to complete from start to finish without asking any questions.Two areas need automating:The WinPE half.The Set Up Windows half.Now, for the second half!

31. More Questions!More Answers!

32. More Questions!More Answers!Visit technet.microsoft.com/en-us/library/cc749073(WS.10).aspx for a list of applicable time zone strings.

33. Further Unattending WDSValidate and createyour XML file.Save it toC:\RemoteInstall.Point to it in WDS.Note: This XMLfile is per-image notper-server.

34. Step 7: Creating a Thick ImageYou don’t want to do this!At least…not much…Thick is bad. Does this image make me look fat?Creating thin images that layer applications over the OS is much more flexible.Only go thick for core applications everyone needs.Examples: Office, Adobe, WinZip, Elf Bowling

35. Step 7: Creating a Thick ImageYour steps to capturing an image…Create that image, configure as needed.Run c:\windows\system32\sysprep\sysprep.exeShutdown after Sysprep.Create a WDS capture image.PXE boot and connect to capture image.Choose capture volume, name, description.Upload image to WDS server.

36. DEMO: Creating A Capture Image

37. Step 7: Capturing an ImagePhase 1: Configure and Sysprep

38. Step 7: Capturing an ImagePhase 2: PXE Boot

39. Step 7: Capturing an ImagePhase 3: Select Stuff to Capture

40. Step 7: Capturing an ImagePhase 4: Choose Where to Send Stuff

41. Step 7: Capturing an ImagePhase 5: Get Coffee! Marvel in GUIness.Previous versions required the nasty command line ImageX tool.Complex. Unfriendly. Bad breath.WDS today can do most everything with GUIs.Some advanced file/driver/stuff injection can still be done with ImageX, but…meh…

42. Step 8: Microsoft Deployment ToolkitWhat you don’t get with WDS alone is the workflow that surrounds an OS installation.

43. Step 8: Microsoft Deployment ToolkitWhat you don’t get with WDS alone is the workflow that surrounds an OS installation.During installation you might…“…want to inject an application!”“…want to preload some files or drivers!”“…want to configure some settings!”“…want to preserve user personality data!”MDT does this via Task Sequences.

44. Step 8: Microsoft Deployment Toolkit

45. Step 8: Microsoft Deployment ToolkitFirst job: Import WDS stuff into MDT.Create Deployment ShareImport Operating System | Custom Image FileCopy setup files from DVD media (important!)Upload DriversCreate a Standard Client Task SequenceEnable Multicast for Deployment ShareUpdate Deployment ShareDisable WDS boot imagesAdd MDT boot images

46. Step 8: Microsoft Deployment ToolkitFirst job: Import WDS stuff into MDT.Create Deployment ShareImport Operating System | Custom Image FileCopy setup files from DVD media (important!)Upload DriversCreate a Standard Client Task SequenceEnable Multicast for Deployment ShareUpdate Deployment ShareDisable WDS boot imagesAdd MDT boot images

47. Step 8: Microsoft Deployment ToolkitSecond job: Deploy an Image!

48. Step 8: Microsoft Deployment ToolkitSecond job: Deploy an Image!IN CASE YOU’RE ASKING:MDT uses Windows Deployment Services to actually deploy its images.That’s why we started there first!

49. Step 9: Silent Installs & RepackagingRepackaging is an ART!You just missed my session on repackaging.Yes, I know the order was reversed… 

50. Step 10: Layering Apps atop WindowsTHIN is IN!

51. Step 10: Layering Apps atop WindowsTHIN is IN!Once packaged and added to MDT, applications can be selected during the installation.

52. Step 10: Layering Apps atop WindowsTHIN is IN!Alternatively,app installscan be addedto a TaskSequence.Adding thereeliminates thequestionsduring install.

53. DEMO: Adding an App to a Task Sequence

54. Step 11: Preserving PersonalityRemember, we’re layering here!

55. Step 11: Preserving PersonalityMDT’s User State Migration Toolkit handles capturing and replacing user data.Built directly into MDT. Updatable.Is only available when a deployment is started within the old operating system.Launch this to begin:\\{server}\deploymentshare$\scripts\LiteTouch.vbsEnables seamless XP-to-W7 upgrades,OS refreshes, and hardware swaps!

56. DEMO: Preserving User Data During W7 Upgrade

57. Step 11: Preserving PersonalityOne can customize what USMT gathers.Doing so is outside the scope of this session.

58. Step 11: Preserving PersonalityOne can customize what USMT gathers.Doing so is outside the scope of this session.Four Files:MigApp.xmlMigUser.xmlMigDocs.xmlCustom.xmlMore info at:http://technet.microsoft.com/en-us/library/dd560778(WS.10).aspxhttp://technet.microsoft.com/en-us/library/dd560762(WS.10).aspxhttp://technet.microsoft.com/en-us/library/dd560801(WS.10).aspxApplication SettingsUser Folders, Files, File TypesSystem-wide FilesYour Custom Settings

59. Step 12: Inventorying Apps & DriversStep 13: Resolving App IncompatibilitiesMicrosoft’s final two deployment tools help you locate applications and drivers and resolve incompatibilities.The Microsoft Assessment and Planning Toolkit is an automated solution for finding those drivers and apps.The Application Compatibility Toolkit creates a workbench for injecting “fixes” to incompatible apps.Great tools with overlapping functionality.ACT > MAP

60. Need More?Bring Greg to Your Office!The content here is but a snippet of Greg’s hands-on W7 Automated Deployment Training.http://www.concentratedtech.com/trainingThree to five days. All hands-on!

61. Your Feedback is ImportantPlease fill out a session evaluation form drop it off at the conference registration desk.Thank you!

62. This slide deck was used in one of our many conference presentations. We hope you enjoy it, and invite you to use it within your own organization however you like.For more information on our company, including information on private classes and upcoming conference appearances, please visit our Web site, www.ConcentratedTech.com. For links to newly-posted decks, follow us on Twitter:@concentrateddon or @concentratdgregThis work is copyright ©Concentrated Technology, LLC