TechMentor Fall, 2011 - WDS Tricks You Didn't Know

3,172 views

Published on

Your Windows 7 testing is over and it’s time for rapid deployment! Yet while you’re excited about delivering Windows 7 to users, you might still remember your last upgrade. Deploying Ghost images might have been easy back then, but it wasn’t very flexible. What you want is deployment from a single image, where every computer starts from one golden master. You also want better naming, giving each computer the correct name automatically. Most importantly, you want the process automated so you’re not sitting around waiting to click buttons. You can have all this and more with Microsoft’s free Windows Deployment Services.
Microsoft MVP Greg Shields has been rapidly deploying Windows computers for over a decade. In this session full of tips and tricks, bring your laptop and get HANDS-ON with Windows Deployment Services. You’ll learn the secret tricks for creating that single image that installs everywhere. You’ll find WDS’ hidden solution for automatic naming. You’ll learn the tricks you absolutely must know to automate Windows installation. And you’ll leave with a functioning deployment solution you can take home to begin deploying immediately.
Are you’re ready for Windows deployment, but not ready for the learning curve? Save yourself weeks of time and join this must-see HANDS-ON session. You’ll walk away with exactly what you need to start rapidly deploying Windows 7 the moment you return home.

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

No Downloads
Views
Total views
3,172
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
37
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • TechMentor Las Vegas 2011
  • TechMentor Las Vegas 2011
  • TechMentor Las Vegas 2011
  • TechMentor Fall, 2011 - WDS Tricks You Didn't Know

    1. 1. Windows 7 Deployment Deep Dive WDS Deployment Tricks You Didn’t Know… Greg Shields, MVP, vExpert Concentrated Technology www.ConcentratedTech.com
    2. 2. Your Deployment VM <ul><li>deploy1.autodeploy.pri </li></ul><ul><ul><li>Username: Administrator </li></ul></ul><ul><ul><li>Password: [email_address] </li></ul></ul><ul><li>NAT Network </li></ul><ul><ul><li>Need to reconfigure VMnet4 to NAT and 222-net. </li></ul></ul><ul><ul><li>IP: 192.168.222.10 </li></ul></ul><ul><ul><li>Subnet: 192.168.222.0 </li></ul></ul><ul><ul><li>Gateway: 192.168.222.2 </li></ul></ul><ul><li>No license key, unactivated. </li></ul><ul><ul><li>Use yours, or use “slmgr -rearm” </li></ul></ul>
    3. 3. Windows 7 Deployment Deep Dive Automatically Deploying W7 without the Alphabet Soup Greg Shields, MVP, vExpert Concentrated Technology www.ConcentratedTech.com
    4. 4. Loves the Tools Hates the Names <ul><li>“ 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.” </li></ul><ul><li>Automating Windows 7 Installation for Desktop and VDI Environments </li></ul><ul><li>http://nexus.realtimepublishers.com </li></ul>
    5. 5. It’s Alphabet Soup! <ul><li>“ 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.” </li></ul><ul><li>Automating Windows 7 Installation for Desktop and VDI Environments </li></ul><ul><li>http://nexus.realtimepublishers.com </li></ul>
    6. 6. Windows Deployment’s Biggest Problem
    7. 7. Windows Deployment’s Biggest Problem <ul><li>The Internet. </li></ul>
    8. 8. Windows Deployment’s Biggest Problem <ul><li>The Internet. </li></ul><ul><ul><li>Each tool evolved through many different versions. </li></ul></ul><ul><ul><li>Older versions had numerous shortcomings. </li></ul></ul><ul><ul><li>Resolving those required some oddball hackery. </li></ul></ul><ul><ul><li>Bloggers report hacks that are no longer timely. </li></ul></ul><ul><ul><li>You’ll find solutions to problems that no longer exist. </li></ul></ul><ul><ul><li>Confusion abounds! </li></ul></ul>
    9. 9. Windows Deployment’s Biggest Problem <ul><li>The Internet. </li></ul><ul><ul><li>Each tool evolved through many different versions. </li></ul></ul><ul><ul><li>Older versions had numerous shortcomings. </li></ul></ul><ul><ul><li>Resolving those required some oddball hackery. </li></ul></ul><ul><ul><li>Bloggers report hacks that are no longer timely. </li></ul></ul><ul><ul><li>You’ll find solutions to problems that no longer exist. </li></ul></ul><ul><ul><li>Confusion abounds! </li></ul></ul><ul><li>The Solution. </li></ul><ul><ul><li>Don’t trust what you read. </li></ul></ul><ul><ul><li>You don’t need the command line as much as you used to. </li></ul></ul>
    10. 10. Greg’s Easy 11 Steps to Deployment Automation! <ul><li>Installing Windows Deployment Server </li></ul><ul><li>Configuring Image Deployment </li></ul><ul><li>Deploying your First Image </li></ul><ul><li>Dealing with Drivers </li></ul><ul><li>Automating WinPE Boot Image </li></ul><ul><li>Automating the “Set Up Windows” Phase </li></ul><ul><li>Creating a Thick Image w. Applications </li></ul><ul><li>Installing Microsoft Deployment Toolkit </li></ul><ul><li>Silent Installations & Repackaging </li></ul><ul><li>Layering Applications atop Windows </li></ul><ul><li>Preserving User Data </li></ul>
    11. 11. Our Job Today… <ul><li>Installing Windows Deployment Server </li></ul><ul><li>Configuring Image Deployment </li></ul><ul><li>Deploying your First Image </li></ul><ul><li>Dealing with Drivers </li></ul><ul><li>Automating WinPE Boot Image </li></ul><ul><li>Automating the “Set Up Windows” Phase </li></ul><ul><li>Creating a Thick Image w. Applications </li></ul><ul><li>Installing Microsoft Deployment Toolkit </li></ul><ul><li>Silent Installations & Repackaging </li></ul><ul><li>Layering Applications atop Windows </li></ul><ul><li>Preserving User Data </li></ul>
    12. 12. Step 1: Installing Windows Deployment Server <ul><li>WDS is a Windows 2008 R2 role. </li></ul><ul><ul><li>Remote Installation Folder location </li></ul></ul><ul><ul><li>PXE Server Initial Settings </li></ul></ul><ul><ul><li>Add Image Wizard </li></ul></ul>
    13. 13. Stepping Back: WIM Files? <ul><li>.WIM files are Microsoft’s image file format. </li></ul><ul><ul><li>Two files are most important, right off DVD media. </li></ul></ul><ul><ul><li>sourcesboot.wim </li></ul></ul><ul><ul><li>sourcesinstall.wim </li></ul></ul><ul><li>You may create more .WIM files as you create custom images down the road. </li></ul><ul><ul><li>However, your goal is to not create more. </li></ul></ul><ul><ul><li>Highest goal: One WIM per processor architecture. </li></ul></ul>
    14. 14. Step 2: Configuring Image Deployment <ul><li>WDS can deploy images via USB stick </li></ul><ul><li>I’m showing you network deployment today. </li></ul><ul><ul><li>Caution : Network deployment can use multicast. </li></ul></ul><ul><ul><li>Multicast consumes bandwidth. </li></ul></ul><ul><ul><li>Multicast is often not passed between subnets. </li></ul></ul><ul><ul><li>Thus, YMMV. </li></ul></ul><ul><ul><li>Secret Trick : Multicast isn’t automatically the best answer. </li></ul></ul>
    15. 15. LAB 1: CONFIGURING WDS
    16. 16. How to Name the Computer? <ul><li>Requiring Administrator approval enables the name-at-install functionality of WDS. </li></ul><ul><ul><li>Boot via PXE </li></ul></ul><ul><ul><li>Approve & Name in WDS </li></ul></ul><ul><ul><li>Enjoy! </li></ul></ul>
    17. 17. How to Name the Computer? <ul><li>One small permissions change is required. </li></ul><ul><ul><li>In Active Directory Users and Computers, right-click the domain and then select Delegate Control. </li></ul></ul><ul><ul><li>Change the object type to include computers and add the computer object of the Windows Deployment Services server into the dialog box. Click Next. </li></ul></ul><ul><ul><li>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. </li></ul></ul><ul><ul><li>In the Permissions box select Write all Properties and click Finish. </li></ul></ul>
    18. 18. Step 3: Deploying a Computer <ul><li>This looks suspiciously similar to Ghost. </li></ul><ul><li>However, Auto-Cast can be very useful. Will set up an always- on deployment. </li></ul>
    19. 19. LAB 2: DEPLOYMENT!
    20. 20. Stepping Back: Layering the OS <ul><li>A Case for the Layered Approach to Deploying Windows Desktops http://technet.microsoft.com/en-us/magazine/ee835710.aspx </li></ul>
    21. 21. Step 4: Dealing with Drivers <ul><li>Plug and Play eliminates the need to create multiple images because of driver differences. </li></ul><ul><ul><li>WDS presents a driver database to the deployment. </li></ul></ul><ul><ul><li>Plug and Play detects and installs those it needs. </li></ul></ul>
    22. 22. Step 4: Dealing with Drivers <ul><li>Plug and Play eliminates the need to create multiple images because of driver differences. </li></ul><ul><ul><li>WDS presents a driver database to the deployment. </li></ul></ul><ul><ul><li>Plug and Play detects and installs those it needs. </li></ul></ul><ul><li>Secret Trick : Finding and unpacking the right drivers to add to WDS. </li></ul><ul><ul><li>EXEs/MSIs must be unpacked to INFs. </li></ul></ul><ul><ul><li>WDS will import all INFs in a file path. </li></ul></ul>
    23. 23. LAB 3: INJECTING DRIVERS
    24. 24. Boot Image Drivers <ul><li>Sometimes WinPE needs extra drivers to boot . </li></ul><ul><ul><li>This is not common. </li></ul></ul><ul><ul><li>… but you’ll know when you need it! </li></ul></ul><ul><li>When it does, those drivers must be specially injected into your boot image. </li></ul><ul><ul><li>This is done within WDS before a deployment. </li></ul></ul><ul><ul><li>Be careful! You can corrupt the little guy! </li></ul></ul><ul><ul><li>If you do, get a new one from the DVD. </li></ul></ul>
    25. 25. LAB 4: INJECTING DRIVERS INTO BOOT IMAGES
    26. 26. Step 5: Automating WinPE <ul><li>Next Step: Automating installation prompts. </li></ul><ul><ul><li>We want this installation to complete from start to finish without asking any questions. </li></ul></ul><ul><ul><li>Two areas need automating: </li></ul></ul><ul><ul><ul><li>The WinPE half. </li></ul></ul></ul><ul><ul><ul><li>The Set Up Windows half. </li></ul></ul></ul>
    27. 27. Step 5: Automating WinPE <ul><li>Next Step: Automating installation prompts. </li></ul><ul><ul><li>We want this installation to complete from start to finish without asking any questions. </li></ul></ul><ul><ul><li>Two areas need automating: </li></ul></ul><ul><ul><ul><li>The WinPE half. </li></ul></ul></ul><ul><ul><ul><li>The Set Up Windows half. </li></ul></ul></ul><ul><li>Automate by pre-answering their questions using Windows System Image Manager. </li></ul><ul><ul><li>This tool is hard (unless you have me!). </li></ul></ul>
    28. 28. Step 5: Automating WinPE
    29. 29. The Right Questions? The Right Answers? Windows Image Pane (Question) Upper-Right Pane (Answer) Explanation amd64_Microsoft-Windows-International-Core-WinPE_{version}_neutral InputLocale = en-us SystemLocale = en-us UILanguage = en-us UILanguageFallback = en-us UserLocale = en-us This item configures the WinPE language to US English. amd64_Microsoft-Windows-International-Core-WinPE_{version}_neutral SetupUILanguage UILanguage = en-us   amd64_Microsoft-Windows-Setup_{version}_neutral WindowsDeploymentServices LoginCredentials Domain Username Password Enter here the domain, username, and password of the user that connects to your WDS share. This is the same user as in Chapter 1, Figure 1-10. amd64_Microsoft-Windows-Setup_{version}_neutralDisk ConfigurationDisk DiskID = 0 This item begins working with the first disk in the computer. amd64_Microsoft-Windows-Setup_{version}_neutralDisk ConfigurationDiskCreate PartitionsCreatePartition Extend = true Order = 1 Type = Primary This item creates a single primary disk to install Windows. amd64_Microsoft-Windows-Setup_{version}_neutralDisk ConfigurationDiskModify PartitionsModifyPartition Active = true Format = NTFS Label = Windows Letter = C Order = 1 PartitionID = 1 This item modifies that partition to create the C: drive as the first NTFS drive and partition. amd64_Microsoft-Windows-Setup_{version}_neutral WindowsDeploymentServices ImageSelectionInstallTo DiskID = 0 PartitionID = 1 This item installs Windows to the disk and volume created in the rows above. amd64_Microsoft-Windows-Setup_{version}_neutral WindowsDeploymentServices ImageSelectionInstallImage Filename ImageGroup ImageName See the note below for information about the settings for this question.
    30. 30. LAB 5: AUTOMATING WINPE
    31. 31. Unattend-ing WDS <ul><li>Validate and create your XML file. </li></ul><ul><li>Save it to C:RemoteInstall. </li></ul><ul><li>Point to it in WDS. </li></ul><ul><li>Important : One file per processor architecture. </li></ul><ul><ul><li>Be smart here… </li></ul></ul><ul><ul><li>Secret Trick : Don’t over-configure…. </li></ul></ul>
    32. 32. Step 6: Automating Set Up Windows <ul><li>Next Step: Automating installation prompts. </li></ul><ul><ul><li>We want this installation to complete from start to finish without asking any questions. </li></ul></ul><ul><ul><li>Two areas need automating: </li></ul></ul><ul><ul><ul><li>The WinPE half. </li></ul></ul></ul><ul><ul><ul><li>The Set Up Windows half. </li></ul></ul></ul>Now, for the second half!
    33. 33. More Questions! More Answers! Windows Image Pane (Question) Upper-Right Pane (Answer) Explanation amd64_Microsoft-Windows-Shell-Setup_{version}_neutral (Pass 4) ComputerName = %MACHINENAME% TimeZone Setting ComputerName to %MACHINENAME% will pass through the name you set in WDSs Name and Approve. Set TimeZone to your correct time zone, such as Mountain Standard Time. amd64_Microsoft-Windows-International-Core_{version}_neutral (Pass 7) InputLocale = en-us SystemLocale = en-us UILanguage = en-us UserLocale = en-us This item configures the Windows language to US English. amd64_Microsoft-Windows-Shell-Setup_{version}_neutral oobe (Pass 4) HideEULAPage = true HideWirelessSetupIn OOBE = true NetworkLocation = work ProtectYourPC = 1 Hides the EULA and wireless setup screens, sets the network location to work, and enables Automatic Updates. amd64_Microsoft-Windows-Shell-Setup_{version}_neutral UserAccountsLocalAccounts LocalAccount (Pass 7) DisplayName = LocalAdmin Group = Administrators Name = LocalAdmin This item adds a local administrator account named LocalAdmin. amd64_Microsoft-Windows-Shell-Setup_{version}_neutral UserAccountsLocalAccounts LocalAccountPassword (Pass 7) Value = {Password} This item configures the password for the administrator account created above.
    34. 34. More Questions! More Answers! Visit technet.microsoft.com/en-us/library/cc749073(WS.10).aspx for a list of applicable time zone strings. Windows Image Pane (Question) Upper-Right Pane (Answer) Explanation amd64_Microsoft-Windows-Shell-Setup_{version}_neutral (Pass 4) ComputerName = %MACHINENAME% TimeZone Setting ComputerName to %MACHINENAME% will pass through the name you set in WDSs Name and Approve. Set TimeZone to your correct time zone, such as Mountain Standard Time. amd64_Microsoft-Windows-International-Core_{version}_neutral (Pass 7) InputLocale = en-us SystemLocale = en-us UILanguage = en-us UserLocale = en-us This item configures the Windows language to US English. amd64_Microsoft-Windows-Shell-Setup_{version}_neutral oobe (Pass 4) HideEULAPage = true HideWirelessSetupIn OOBE = true NetworkLocation = work ProtectYourPC = 1 Hides the EULA and wireless setup screens, sets the network location to work, and enables Automatic Updates. amd64_Microsoft-Windows-Shell-Setup_{version}_neutral UserAccountsLocalAccounts LocalAccount (Pass 7) DisplayName = LocalAdmin Group = Administrators Name = LocalAdmin This item adds a local administrator account named LocalAdmin. amd64_Microsoft-Windows-Shell-Setup_{version}_neutral UserAccountsLocalAccounts LocalAccountPassword (Pass 7) Value = {Password} This item configures the password for the administrator account created above.
    35. 35. Further Unattend-ing WDS <ul><li>Validate and create your XML file. </li></ul><ul><li>Save it to C:RemoteInstall. </li></ul><ul><li>Point to it in WDS. </li></ul><ul><li>Important : This XML file is per-image not per-server. </li></ul>
    36. 36. Step 7: Creating a Thick Image <ul><li>Secret Trick : You don’t want to do this! </li></ul><ul><ul><li>At least…not much… </li></ul></ul><ul><ul><li>Thick is bad. Does this image make me look fat? </li></ul></ul><ul><li>Creating thin images that layer applications over the OS is much more flexible. </li></ul><ul><ul><li>Only go thick for core applications everyone needs. </li></ul></ul><ul><ul><li>Examples: Office, Adobe, WinZip, Elf Bowling </li></ul></ul>
    37. 37. Step 7: Creating a Thick Image <ul><li>Your steps to capturing an image… </li></ul><ul><ul><li>Create that image, configure as needed. </li></ul></ul><ul><ul><li>Run c:windowssystem32sysprepsysprep.exe </li></ul></ul><ul><ul><li>Shutdown after Sysprep. </li></ul></ul><ul><ul><li>Create a WDS capture image. </li></ul></ul><ul><ul><li>PXE boot and connect to capture image. </li></ul></ul><ul><ul><li>Choose capture volume, name, description. </li></ul></ul><ul><ul><li>Upload image to WDS server. </li></ul></ul>
    38. 38. LAB 6: CREATING A CAPTURE IMAGE
    39. 39. Step 7: Capturing an Image <ul><li>Phase 1: Configure and Sysprep </li></ul>
    40. 40. Step 7: Capturing an Image <ul><li>Phase 2: PXE Boot </li></ul>
    41. 41. Step 7: Capturing an Image <ul><li>Phase 3: Select Stuff to Capture </li></ul>
    42. 42. Step 7: Capturing an Image <ul><li>Phase 4: Choose Where to Send Stuff </li></ul>
    43. 43. Step 7: Capturing an Image <ul><li>Phase 5: Get Coffee! Marvel in GUIness. </li></ul><ul><li>Previous versions required the nasty command line ImageX tool. </li></ul><ul><ul><li>Complex. Unfriendly. Bad breath. </li></ul></ul><ul><ul><li>WDS today can do most everything with GUIs. </li></ul></ul><ul><ul><li>Some advanced file/driver/stuff injection can still be done with ImageX, but…meh… </li></ul></ul>
    44. 44. LAB 7: CAPTURING A CUSTOM IMAGE
    45. 45. Steps 8 thru 11+, Coming Up: Things Get Awesome-r <ul><li>Installing Windows Deployment Server </li></ul><ul><li>Configuring Image Deployment </li></ul><ul><li>Deploying your First Image </li></ul><ul><li>Dealing with Drivers </li></ul><ul><li>Automating WinPE Boot Image </li></ul><ul><li>Automating the “Set Up Windows” Phase </li></ul><ul><li>Creating a Thick Image w. Applications </li></ul><ul><li>Installing Microsoft Deployment Toolkit </li></ul><ul><li>Silent Installations & Repackaging </li></ul><ul><li>Layering Applications atop Windows </li></ul><ul><li>Preserving User Data </li></ul>
    46. 46. Windows 7 Deployment Deep Dive WDS Deployment Tricks You Didn’t Know… Greg Shields, MVP, vExpert Concentrated Technology www.ConcentratedTech.com

    ×