Automatically Deploying Windows 7 without theMicrosoft Alphabet Soup<br />Greg Shields<br />Senior Partner & Principal Tec...
Loves the ToolsHates the Names<br />“Microsoft wants you to PXE your machine to WDS, using an Unattend.XML file built from...
It’s Alphabet Soup!<br />“Microsoft wants you to PXE your machine to WDS, using an Unattend.XML file built from WSIM in th...
Windows Deployment’sBiggest Problem<br />
Windows Deployment’sBiggest Problem<br />The Internet.<br />
Windows Deployment’sBiggest Problem<br />The Internet.<br />Each tool evolved through many different versions.<br />Older ...
Windows Deployment’sBiggest Problem<br />The Internet.<br />Each tool evolved through many different versions.<br />Older ...
Greg’s Easy 11 Stepsto Deployment Automation!<br />Installing Windows Deployment Server<br />Configuring Image Deployment<...
Step 1:  Installing Windows Deployment Server<br />WDS is a Windows 2008 R2 role.<br />Remote Installation Folder location...
Stepping Back:  WIM Files?<br />.WIM files are Microsoft’s image file format.<br />Two files are most important, right off...
Step 2:  Configuring Image Deployment<br />WDS can deploy images via USB stick<br />I’m showing you network deployment onl...
DEMO:  Configuring WDS<br />
How to Name the Computer?<br />Requiring Administratorapproval enables thename-at-installfunctionality of WDS.<br />Boot v...
How to Name the Computer?<br />One small permissions change is required.<br />In Active Directory Users and Computers, rig...
Step 3:  Deploying a Computer<br />This lookssuspiciouslysimilar to Ghost.<br />However,Auto-Cast isvery useful.  Willsetu...
DEMO:  DEPLOYMENT!<br />
Stepping Back:  Layering the OS<br />A Case for the Layered Approach to Deploying Windows Desktopshttp://technet.microsoft...
Step 4:  Dealing with Drivers<br />Plug and Play eliminates the need to create multiple images because of driver differenc...
Step 4:  Dealing with Drivers<br />Plug and Play eliminates the need to create multiple images because of driver differenc...
DEMO:  injecting drivers<br />
Boot Image Drivers<br />Sometimes WinPE needs extra drivers to boot.<br />This is not common.<br />…but you’ll know when y...
DEMO:  injecting drivers INTO boot images<br />
Step 5:  Automating WinPE<br />Next Step:  Automating installation prompts.<br />We want this installation to complete fro...
Step 5:  Automating WinPE<br />Next Step:  Automating installation prompts.<br />We want this installation to complete fro...
Step 5:  Automating WinPE<br />
The Right Questions?The Right Answers?<br />
DEMO:  Automating WinPE<br />
Unattending WDS<br />Validate and createyour XML file.<br />Save it toC:RemoteInstall.<br />Point to it in WDS.<br />Note:...
Step 6:  Automating Set Up Windows<br />Next Step:  Automating installation prompts.<br />We want this installation to com...
More Questions!More Answers!<br />
More Questions!More Answers!<br />Visit technet.microsoft.com/en-us/library/cc749073(WS.10).aspx for a list of applicable ...
Further Unattending WDS<br />Validate and createyour XML file.<br />Save it toC:RemoteInstall.<br />Point to it in WDS.<br...
Step 7:  Creating a Thick Image<br />You don’t want to do this!<br />At least…not much…<br />Thick is bad. Does this image...
Step 7:  Creating a Thick Image<br />Your steps to capturing an image…<br />Create that image, configure as needed.<br />R...
DEMO:  Creating A Capture Image<br />
Step 7:  Capturing an Image<br />Phase 1:  Configure and Sysprep<br />
Step 7:  Capturing an Image<br />Phase 2:  PXE Boot <br />
Step 7:  Capturing an Image<br />Phase 3:  Select Stuff to Capture<br />
Step 7:  Capturing an Image<br />Phase 4:  Choose Where to Send Stuff<br />
Step 7:  Capturing an Image<br />Phase 5:  Get Coffee!  Marvel in GUIness.<br />Previous versions required the nasty comma...
Step 8:  Microsoft Deployment Toolkit<br />What you don’t get with WDS alone is the workflow that surrounds an OS installa...
Step 8:  Microsoft Deployment Toolkit<br />What you don’t get with WDS alone is the workflow that surrounds an OS installa...
Step 8:  Microsoft Deployment Toolkit<br />
Step 8:  Microsoft Deployment Toolkit<br />First job:  Import WDS stuff into MDT.<br />Create Deployment Share<br />Import...
Step 8:  Microsoft Deployment Toolkit<br />First job:  Import WDS stuff into MDT.<br />Create Deployment Share<br />Import...
Step 8:  Microsoft Deployment Toolkit<br />Second job:  Deploy an Image!<br />
Step 8:  Microsoft Deployment Toolkit<br />Second job:  Deploy an Image!<br />IN CASE YOU’RE ASKING:MDT uses Windows Deplo...
Step 9:  Silent Installs & Repackaging<br />Repackaging is an ART!<br />You just missed my session on repackaging.<br />Ye...
Step 10:  Layering Apps atop Windows<br />THIN is IN!<br />
Step 10:  Layering Apps atop Windows<br />THIN is IN!<br />Once packaged and added to MDT, applications can be selected du...
Step 10:  Layering Apps atop Windows<br />THIN is IN!<br />Alternatively,app installscan be addedto a TaskSequence.<br />A...
DEMO:  Adding an App to a Task Sequence<br />
Step 11:  Preserving Personality<br />Remember, we’re layering here!<br />
Step 11:  Preserving Personality<br />MDT’s User State Migration Toolkit handles capturing and replacing user data.<br />B...
DEMO:  Preserving User Data During W7 Upgrade<br />
Step 11:  Preserving Personality<br />One can customize what USMT gathers.<br />Doing so is outside the scope of this sess...
Step 11:  Preserving Personality<br />One can customize what USMT gathers.<br />Doing so is outside the scope of this sess...
Step 12:  Inventorying Apps & DriversStep 13:  Resolving App Incompatibilities<br />Microsoft’s final two deployment tools...
Need More?Bring Greg to Your Office!<br />The content here is but a snippet of Greg’s hands-on W7 Automated Deployment Tra...
Your Feedback is Important<br />Please fill out a session evaluation form drop it off at the conference registration desk....
Upcoming SlideShare
Loading in …5
×

WinConnections Spring, 2011 - Deploying Windows 7 without the Ridiculous Microsoft Alphabet Soup

999 views

Published on

Greg Shields may be most known for his books, magazine articles, and conference sessions. But he started his career deploying thousands of computers from a basement of a building with no windows. His passion for deploying Windows is fed by his desire to automate everything. You can do that with Microsoft’s free tools. But while the tools are fantastic, their alphabet soup of acronyms is confusing and their documentation isn’t much better. Learn Greg’s Seven Simple Steps in 75 minutes or less, and leave with a framework for automating everything in Windows 7 deployment.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
999
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

WinConnections Spring, 2011 - Deploying Windows 7 without the Ridiculous Microsoft Alphabet Soup

  1. 1. Automatically Deploying Windows 7 without theMicrosoft Alphabet Soup<br />Greg Shields<br />Senior Partner & Principal Technologist<br />www.ConcentratedTech.com<br />
  2. 2. Loves the ToolsHates the Names<br />“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.”<br />Automating Windows 7 Installation for Desktopand VDI Environments<br />http://nexus.realtimepublishers.com<br />
  3. 3. It’s Alphabet Soup!<br />“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.”<br />Automating Windows 7 Installation for Desktopand VDI Environments<br />http://nexus.realtimepublishers.com<br />
  4. 4. Windows Deployment’sBiggest Problem<br />
  5. 5. Windows Deployment’sBiggest Problem<br />The Internet.<br />
  6. 6. Windows Deployment’sBiggest Problem<br />The Internet.<br />Each tool evolved through many different versions.<br />Older versions had numerous shortcomings.<br />Resolving those required some oddball hackery.<br />Bloggers report hacks that are no longer timely.<br />You’ll find solutions to problems that no longer exist.<br />Confusion abounds!<br />
  7. 7. Windows Deployment’sBiggest Problem<br />The Internet.<br />Each tool evolved through many different versions.<br />Older versions had numerous shortcomings.<br />Resolving those required some oddball hackery.<br />Bloggers report hacks that are no longer timely.<br />You’ll find solutions to problems that no longer exist.<br />Confusion abounds!<br />The Solution.<br />Don’t trust what you read.<br />You don’t need the command lineas much as you used to.<br />
  8. 8. Greg’s Easy 11 Stepsto Deployment Automation!<br />Installing Windows Deployment Server<br />Configuring Image Deployment<br />Deploying your First Image<br />Dealing with Drivers<br />Automating WinPE Boot Image<br />Automating the “Set Up Windows” Phase<br />Creating a Thick Image w. Applications<br />Installing Microsoft Deployment Toolkit<br />Silent Installations & Repackaging<br />Layering Applications atop Windows<br />Preserving User Data<br />
  9. 9. Step 1: Installing Windows Deployment Server<br />WDS is a Windows 2008 R2 role.<br />Remote Installation Folder location<br />PXE Server Initial Settings<br />Add Image Wizard<br />
  10. 10. Stepping Back: WIM Files?<br />.WIM files are Microsoft’s image file format.<br />Two files are most important, right off DVD media.<br /> sourcesboot.wim<br /> sourcesinstall.wim<br />You maycreate more .WIM files as you create custom images down the road.<br />However, your goal is to not create more.<br />Highest goal: One WIM per processor architecture.<br />
  11. 11. Step 2: Configuring Image Deployment<br />WDS can deploy images via USB stick<br />I’m showing you network deployment only.<br />Caution: Network deployment uses multicast.<br />Multicast consumes bandwidth.<br />Multicast is often not passed between subnets.<br />Thus, YMMV.<br />
  12. 12. DEMO: Configuring WDS<br />
  13. 13. How to Name the Computer?<br />Requiring Administratorapproval enables thename-at-installfunctionality of WDS.<br />Boot via PXE<br />Approve & Name in WDS<br />Enjoy!<br />
  14. 14. How to Name the Computer?<br />One small permissions change is required.<br />In Active Directory Users and Computers, right-click the domain and then select Delegate Control. <br />Change the object type to include computers and add the computer object of the Windows Deployment Services server into the dialog box. Click Next. <br />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. <br />In the Permissions box select Write all Properties and click Finish.<br />
  15. 15. Step 3: Deploying a Computer<br />This lookssuspiciouslysimilar to Ghost.<br />However,Auto-Cast isvery useful. Willsetup an always-on deployment.<br />
  16. 16. DEMO: DEPLOYMENT!<br />
  17. 17. Stepping Back: Layering the OS<br />A Case for the Layered Approach to Deploying Windows Desktopshttp://technet.microsoft.com/en-us/magazine/ee835710.aspx<br />
  18. 18. Step 4: Dealing with Drivers<br />Plug and Play eliminates the need to create multiple images because of driver differences.<br />WDS presents a driver database to the deployment. <br />Plug and Play detects and installs those it needs.<br />
  19. 19. Step 4: Dealing with Drivers<br />Plug and Play eliminates the need to create multiple images because of driver differences.<br />WDS presents a driver database to the deployment. <br />Plug and Play detects and installs those it needs.<br />Hardest part: Finding and unpacking the right drivers to add to WDS.<br />EXEs/MSIs must be unpacked to INFs.<br />WDS will import all INFs in a file path.<br />
  20. 20. DEMO: injecting drivers<br />
  21. 21. Boot Image Drivers<br />Sometimes WinPE needs extra drivers to boot.<br />This is not common.<br />…but you’ll know when you need it!<br />When it does, those drivers must be specially injected into your boot image.<br />This is done within WDS before a deployment.<br />Be careful! You can corrupt the little guy!<br />If you do, get a new one from the DVD.<br />
  22. 22. DEMO: injecting drivers INTO boot images<br />
  23. 23. Step 5: Automating WinPE<br />Next Step: Automating installation prompts.<br />We want this installation to complete from start to finish without asking any questions.<br />Two areas need automating:<br />The WinPE half.<br />The Set Up Windows half.<br />
  24. 24. Step 5: Automating WinPE<br />Next Step: Automating installation prompts.<br />We want this installation to complete from start to finish without asking any questions.<br />Two areas need automating:<br />The WinPE half.<br />The Set Up Windows half.<br />Automate by pre-answering their questions using Windows System Image Manager.<br />This tool is hard (unless you have me!).<br />
  25. 25. Step 5: Automating WinPE<br />
  26. 26. The Right Questions?The Right Answers?<br />
  27. 27. DEMO: Automating WinPE<br />
  28. 28. Unattending WDS<br />Validate and createyour XML file.<br />Save it toC:RemoteInstall.<br />Point to it in WDS.<br />Note: One file perprocessor architecture.<br />
  29. 29. Step 6: Automating Set Up Windows<br />Next Step: Automating installation prompts.<br />We want this installation to complete from start to finish without asking any questions.<br />Two areas need automating:<br />The WinPE half.<br />The Set Up Windows half.<br />Now, for the second half!<br />
  30. 30. More Questions!More Answers!<br />
  31. 31. More Questions!More Answers!<br />Visit technet.microsoft.com/en-us/library/cc749073(WS.10).aspx for a list of applicable time zone strings.<br />
  32. 32. Further Unattending WDS<br />Validate and createyour XML file.<br />Save it toC:RemoteInstall.<br />Point to it in WDS.<br />Note: This XMLfile is per-image notper-server.<br />
  33. 33. Step 7: Creating a Thick Image<br />You don’t want to do this!<br />At least…not much…<br />Thick is bad. Does this image make me look fat?<br />Creating thin images that layer applications over the OS is much more flexible.<br />Only go thick for core applications everyone needs.<br />Examples: Office, Adobe, WinZip, Elf Bowling<br />
  34. 34. Step 7: Creating a Thick Image<br />Your steps to capturing an image…<br />Create that image, configure as needed.<br />Run c:windowssystem32sysprepsysprep.exe<br />Shutdown after Sysprep.<br />Create a WDS capture image.<br />PXE boot and connect to capture image.<br />Choose capture volume, name, description.<br />Upload image to WDS server.<br />
  35. 35. DEMO: Creating A Capture Image<br />
  36. 36. Step 7: Capturing an Image<br />Phase 1: Configure and Sysprep<br />
  37. 37. Step 7: Capturing an Image<br />Phase 2: PXE Boot <br />
  38. 38. Step 7: Capturing an Image<br />Phase 3: Select Stuff to Capture<br />
  39. 39. Step 7: Capturing an Image<br />Phase 4: Choose Where to Send Stuff<br />
  40. 40. Step 7: Capturing an Image<br />Phase 5: Get Coffee! Marvel in GUIness.<br />Previous versions required the nasty command line ImageX tool.<br />Complex. Unfriendly. Bad breath.<br />WDS today can do most everything with GUIs.<br />Some advanced file/driver/stuff injection can still be done with ImageX, but…meh…<br />
  41. 41. Step 8: Microsoft Deployment Toolkit<br />What you don’t get with WDS alone is the workflow that surrounds an OS installation.<br />
  42. 42. Step 8: Microsoft Deployment Toolkit<br />What you don’t get with WDS alone is the workflow that surrounds an OS installation.<br />During installation you might…<br />“…want to inject an application!”<br />“…want to preload some files or drivers!”<br />“…want to configure some settings!”<br />“…want to preserve user personality data!”<br />MDT does this via Task Sequences.<br />
  43. 43. Step 8: Microsoft Deployment Toolkit<br />
  44. 44. Step 8: Microsoft Deployment Toolkit<br />First job: Import WDS stuff into MDT.<br />Create Deployment Share<br />Import Operating System | Custom Image File<br />Copy setup files from DVD media (important!)<br />Upload Drivers<br />Create a Standard Client Task Sequence<br />Enable Multicast for Deployment Share<br />Update Deployment Share<br />Disable WDS boot images<br />Add MDT boot images<br />
  45. 45. Step 8: Microsoft Deployment Toolkit<br />First job: Import WDS stuff into MDT.<br />Create Deployment Share<br />Import Operating System | Custom Image File<br />Copy setup files from DVD media (important!)<br />Upload Drivers<br />Create a Standard Client Task Sequence<br />Enable Multicast for Deployment Share<br />Update Deployment Share<br />Disable WDS boot images<br />Add MDT boot images<br />
  46. 46. Step 8: Microsoft Deployment Toolkit<br />Second job: Deploy an Image!<br />
  47. 47. Step 8: Microsoft Deployment Toolkit<br />Second job: Deploy an Image!<br />IN CASE YOU’RE ASKING:MDT uses Windows Deployment Services to actually deploy its images.<br />That’s why we started there first!<br />
  48. 48. Step 9: Silent Installs & Repackaging<br />Repackaging is an ART!<br />You just missed my session on repackaging.<br />Yes, I know the order was reversed… <br />
  49. 49. Step 10: Layering Apps atop Windows<br />THIN is IN!<br />
  50. 50. Step 10: Layering Apps atop Windows<br />THIN is IN!<br />Once packaged and added to MDT, applications can be selected during the installation.<br />
  51. 51. Step 10: Layering Apps atop Windows<br />THIN is IN!<br />Alternatively,app installscan be addedto a TaskSequence.<br />Adding thereeliminates thequestionsduring install.<br />
  52. 52. DEMO: Adding an App to a Task Sequence<br />
  53. 53. Step 11: Preserving Personality<br />Remember, we’re layering here!<br />
  54. 54. Step 11: Preserving Personality<br />MDT’s User State Migration Toolkit handles capturing and replacing user data.<br />Built directly into MDT. Updatable.<br />Is only available when a deployment is started within the old operating system.<br />Launch this to begin:{server}deploymentshare$scriptsLiteTouch.vbs<br />Enables seamless XP-to-W7 upgrades,OS refreshes, and hardware swaps!<br />
  55. 55. DEMO: Preserving User Data During W7 Upgrade<br />
  56. 56. Step 11: Preserving Personality<br />One can customize what USMT gathers.<br />Doing so is outside the scope of this session.<br />
  57. 57. Step 11: Preserving Personality<br />One can customize what USMT gathers.<br />Doing so is outside the scope of this session.<br />Four Files:<br />MigApp.xml<br />MigUser.xml<br />MigDocs.xml<br />Custom.xml<br />More info at:<br />http://technet.microsoft.com/en-us/library/dd560778(WS.10).aspx<br />http://technet.microsoft.com/en-us/library/dd560762(WS.10).aspx<br />http://technet.microsoft.com/en-us/library/dd560801(WS.10).aspx<br />Application Settings<br />User Folders, Files, File Types<br />System-wide Files<br />Your Custom Settings<br />
  58. 58. Step 12: Inventorying Apps & DriversStep 13: Resolving App Incompatibilities<br />Microsoft’s final two deployment tools help you locate applications and drivers and resolve incompatibilities.<br />The Microsoft Assessment and Planning Toolkit is an automated solution for finding those drivers and apps.<br />The Application Compatibility Toolkit creates a workbench for injecting “fixes” to incompatible apps.<br />Great tools with overlapping functionality.<br />ACT > MAP<br />
  59. 59. Need More?Bring Greg to Your Office!<br />The content here is but a snippet of Greg’s hands-on W7 Automated Deployment Training.<br />http://www.concentratedtech.com/training<br />Three to five days. All hands-on!<br />
  60. 60. Your Feedback is Important<br />Please fill out a session evaluation form drop it off at the conference registration desk.<br />Thank you!<br />

×