This document provides an overview of automating Windows 7 deployment using various Microsoft tools. It begins with an introduction to the tools and challenges of the process. It then provides a 12 step guide to automating deployment, covering tools like Windows Deployment Services (WDS), Windows System Image Manager (WSIM), Microsoft Deployment Toolkit (MDT) and more. Each step includes explanations and demos of key tasks like capturing images, configuring WDS, adding drivers, automating installations and preserving user data.

1. Automatically Deploying Windows 7 without theMicrosoft Alphabet Soup Greg Shields Senior Partner & Principal Technologist www.ConcentratedTech.com

2. 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 Environments http://nexus.realtimepublishers.com

3. 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 Environments http://nexus.realtimepublishers.com

4. Windows Deployment’sBiggest Problem

5. Windows Deployment’sBiggest Problem The Internet.

6. Windows Deployment’sBiggest Problem The 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!

7. Windows Deployment’sBiggest Problem The 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.

8. Greg’s Easy 11 Stepsto Deployment Automation! Installing Windows Deployment Server Configuring Image Deployment Deploying your First Image Dealing with Drivers Automating WinPE Boot Image Automating the “Set Up Windows” Phase Creating a Thick Image w. Applications Installing Microsoft Deployment Toolkit Silent Installations & Repackaging Layering Applications atop Windows Preserving User Data

9. Step 1: Installing Windows Deployment Server WDS is a Windows 2008 R2 role. Remote Installation Folder location PXE Server Initial Settings Add Image Wizard

10. Stepping Back: WIM Files? .WIM files are Microsoft’s image file format. Two files are most important, right off DVD media. ourcesoot.wim ourcesnstall.wim You 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.

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

12. DEMO: Configuring WDS

13. How to Name the Computer? Requiring Administratorapproval enables thename-at-installfunctionality of WDS. Boot via PXE Approve & Name in WDS Enjoy!

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

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

16. DEMO: DEPLOYMENT!

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

18. Step 4: Dealing with Drivers Plug 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.

19. Step 4: Dealing with Drivers Plug 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.

20. DEMO: injecting drivers

21. Boot Image Drivers Sometimes 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.

22. DEMO: injecting drivers INTO boot images

23. Step 5: Automating WinPE Next 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.

24. Step 5: Automating WinPE Next 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!).

25. Step 5: Automating WinPE

26. The Right Questions?The Right Answers?

27. DEMO: Automating WinPE

28. Unattending WDS Validate and createyour XML file. Save it toC:emoteInstall. Point to it in WDS. Note: One file perprocessor architecture.

29. Step 6: Automating Set Up Windows Next 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!

30. More Questions!More Answers!

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

32. Further Unattending WDS Validate and createyour XML file. Save it toC:emoteInstall. Point to it in WDS. Note: This XMLfile is per-image notper-server.

33. Step 7: Creating a Thick Image You 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

34. Step 7: Creating a Thick Image Your steps to capturing an image… Create that image, configure as needed. Run c:indowsystem32ysprepysprep.exe Shutdown after Sysprep. Create a WDS capture image. PXE boot and connect to capture image. Choose capture volume, name, description. Upload image to WDS server.

35. DEMO: Creating A Capture Image

36. Step 7: Capturing an Image Phase 1: Configure and Sysprep

37. Step 7: Capturing an Image Phase 2: PXE Boot

38. Step 7: Capturing an Image Phase 3: Select Stuff to Capture

39. Step 7: Capturing an Image Phase 4: Choose Where to Send Stuff

40. Step 7: Capturing an Image Phase 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…

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

42. Step 8: Microsoft Deployment Toolkit What 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.

43. Step 8: Microsoft Deployment Toolkit

44. Step 8: Microsoft Deployment Toolkit First job: Import WDS stuff into MDT. Create Deployment Share Import Operating System | Custom Image File Copy setup files from DVD media (important!) Upload Drivers Create a Standard Client Task Sequence Enable Multicast for Deployment Share Update Deployment Share Disable WDS boot images Add MDT boot images

45. Step 8: Microsoft Deployment Toolkit First job: Import WDS stuff into MDT. Create Deployment Share Import Operating System | Custom Image File Copy setup files from DVD media (important!) Upload Drivers Create a Standard Client Task Sequence Enable Multicast for Deployment Share Update Deployment Share Disable WDS boot images Add MDT boot images

46. Step 8: Microsoft Deployment Toolkit Second job: Deploy an Image!

47. Step 8: Microsoft Deployment Toolkit Second 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!

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

49. Step 10: Layering Apps atop Windows THIN is IN!

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

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

52. DEMO: Adding an App to a Task Sequence

53. Step 11: Preserving Personality Remember, we’re layering here!

54. Step 11: Preserving Personality MDT’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}eploymentshare$criptsiteTouch.vbs Enables seamless XP-to-W7 upgrades,OS refreshes, and hardware swaps!

55. DEMO: Preserving User Data During W7 Upgrade

56. Step 11: Preserving Personality One can customize what USMT gathers. Doing so is outside the scope of this session.

57. Step 11: Preserving Personality One can customize what USMT gathers. Doing so is outside the scope of this session. Four Files: MigApp.xml MigUser.xml MigDocs.xml Custom.xml More info at: http://technet.microsoft.com/en-us/library/dd560778(WS.10).aspx http://technet.microsoft.com/en-us/library/dd560762(WS.10).aspx http://technet.microsoft.com/en-us/library/dd560801(WS.10).aspx Application Settings User Folders, Files, File Types System-wide Files Your Custom Settings

58. Step 12: Inventorying Apps & DriversStep 13: Resolving App Incompatibilities Microsoft’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

59. 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/training Three to five days. All hands-on!

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