Windows 7 Deployment

8,694
-1

Published on

Windows 7 Deployment

Published in: Technology

Windows 7 Deployment

  1. 1.
  2. 2. Automated Installation andDeployment Windows 7Roel van BuerenAlex de Jong<br />
  3. 3. Agenda<br />Imaging Approaches<br />Imaging C.R.A.P.<br />WAIK<br />MDT 2010 <br />WDS<br />
  4. 4. Resources<br />
  5. 5. Traditional vs. Modular Approach<br />Traditional<br />Modular<br /><ul><li>1 base image (OS) for all hardware
  6. 6. Apps/drivers delivered as add-ons
  7. 7. Easily integrate new hardware
  8. 8. Reduced maintenance costs
  9. 9. Automated build process
  10. 10. Easy to customise
  11. 11. OS + Applications in 1 image
  12. 12. Image per hardware type
  13. 13. Time to integrate new hardware
  14. 14. High maintenance
  15. 15. Requires a visit to the desktop
  16. 16. Storage requirements</li></li></ul><li>Traditional Approach<br /><ul><li>Quick Win
  17. 17. 1 x image per model
  18. 18. high maintenance</li></li></ul><li>Traditional vs. Modular Approach<br />Maintenance<br />Deployment<br />Development<br />Time<br />Traditional<br />Modular<br />
  19. 19. Imaging Strategy<br />Thick image<br />Core applications and language packs included<br />Updates included<br />Drivers included<br />Thin image<br />Core applications and language packs NOT included<br />Updates NOT included<br />Drivers NOT included<br />Hybrid image<br />Mixes thin and thick strategies<br />
  20. 20. Imaging C.R.A.P.<br />
  21. 21. Imaging C.R.A.P<br />Disk Controllers drivers (STOP 0x0000007B)<br />HAL (Uniprocessor, Multiprocessor)<br />x64 and x86 support<br />Disk and Partition Setup<br />Windows Updates<br />Drivers (Out-of-the-box, ‘to be connected’ hardware)<br />Custom Registry Settings<br />Applications<br />AMD and Intel support<br />
  22. 22. Platform Components<br />
  23. 23. Windows Imaging (.WIM)<br />
  24. 24. Microsoft Windows Imaging (WIM)<br />Microsoft’s own image format<br />File-based disk imaging is a core capability of Windows Vista, Windows 7, Windows 2008 <br />Compared to sector-based formats, a WIM image is file-based<br />
  25. 25. Microsoft Windows Imaging (WIM)<br />This WIM image format is hardware-agnostic, meaning that you need only one image to address many different hardware configurations.<br />
  26. 26. Microsoft Windows Imaging (WIM)<br />The WIM image format also lets you store multiple images within one actual file. <br />For example, Microsoft can ship multiple SKUs in one WIM image file. You store images with and without core applications in a single image file.<br />Also, you can mark one of the images as bootable, allowing you to start a computer from a disk image contained in a WIM file.<br />
  27. 27. Microsoft Windows Imaging (WIM)<br />The WIM image format enables compression and single instancing, thus reducing the size of image files significantly. <br />Single instancing is a technique that allows you to store two or more copies of a file for the space cost of one copy. <br />For example, if images 1, 2, and 3 all contain file A, single-instancing stores a single copy of the file A and points images 1, 2, and 3 to that copy.<br />
  28. 28. Microsoft Windows Imaging (WIM)<br />The WIM image format allows you to service an image offline. You can add or delete certain operating system components, patches, and drivers without creating a new image. <br />For example, to add a patch to a Windows XP image, you must boot the master image, add the patch, and then prepare the image again. <br />
  29. 29. Microsoft Windows Imaging (WIM)<br />The WIM image format lets you install a disk image on partitions of any size, unlike sector-based image formats that require you to deploy a disk image to a partition that&apos;s the same size or larger than the source disk.<br />
  30. 30. WAIK<br />
  31. 31. Windows Automated Installation Kit<br />The Windows® Automated Installation Kit (Windows AIK) is a set of tools and documentation that support the configuration and deployment of Windows® operating systems. <br />
  32. 32. Windows Automated Installation Kit<br />By using Windows AIK, you can automate Windows installations, capture Windows images with ImageX, configure and modify images using Deployment Imaging Servicing and Management (DISM), create Windows PE images, and migrate user profiles and data with the User State Migration Tool (USMT). <br />Windows AIK also includes the Volume Activation Management Tool (VAMT), which enables IT professionals to automate and centrally manage the volume activation process using a Multiple Activation Key (MAK). <br />
  33. 33. ImageX<br />
  34. 34. ImageX<br />
  35. 35. ImageX<br />
  36. 36. ImageX<br />
  37. 37. ImageX<br />
  38. 38. ImageX<br />
  39. 39. ImageX<br />
  40. 40. ImageX<br />
  41. 41. DISM<br />Deployment Image Servicing and Management Tool<br />
  42. 42. DISM<br />
  43. 43. DISM<br />
  44. 44. DISM<br />
  45. 45. DISM<br />
  46. 46. DISM<br />
  47. 47. DISM<br />
  48. 48. DISM<br />
  49. 49. DISM<br />
  50. 50. Platform Components<br />
  51. 51. Attended Windows setup <br />
  52. 52. Windows XP Setup Manager<br />
  53. 53. Windows SIM<br />
  54. 54. Unattended Windows setup <br />Unattend.xml<br />AutoUnattend.xml<br />As a rule, only answer files named Unattend.xml are used. <br />However, because some answer files include destructive actions such as disk partitioning, you must rename your Unattend.xml file to Autounattend.xml in the windowsPE and offlineServicing configuration passes. These passes run when you first run Windows PE or Setup.exe. <br />You typically use the Autounattend.xml file when you use the Windows Setup DVD boot method and supply an answer file on a USB flash drive (UFD) or floppy disk.<br />
  55. 55. Unattend Windows setup <br />
  56. 56. Unattend Windows setup <br />
  57. 57. Unattend Windows setup <br />
  58. 58. Unattend Windows setup <br />
  59. 59. Unattend Windows setup <br />
  60. 60. Unattend Windows setup <br />
  61. 61. Unattend Windows setup <br />
  62. 62. Windows SIM<br />
  63. 63. Passes<br />windowsPE<br />offlineServicing<br />generalize<br />Specialize <br />auditSystem<br />auditUser<br />oobeSystem<br />
  64. 64. Windows PE<br />Windows PE is a minimal Win32 subsystem with limited services, based on the Windows 7 kernel running in protected mode. <br />It contains the minimal functionality that you need to run Setup, install Windows from a network share, automate basic processes, and perform hardware validation.<br />Windows PE was developed specifically to address desktop and server deployment scenarios. <br />
  65. 65. Windows PE<br />
  66. 66. Passes – windowsPE<br />Configures Windows PE options as well as basic Windows Setup options. These options can include configuring a disk or language settings.<br />
  67. 67. Passes - offlineServicing<br />Applies updates to a Windows 7 image. <br />Also applies packages, including software fixes, language packs, and other security updates.<br />
  68. 68. Passes - generalize<br />The generalize pass runs only if you run sysprep/generalize. In this pass, you can minimally configure Windows 7 as well as configure other settings that must persist on your master image. <br />The sysprep /generalize command removes system-specific information. For example, the unique SID and other hardware-specific settings are removed from the image.<br />
  69. 69. Passes - specialize<br />Creates and applies system-specific information. <br />For example, you can configure:<br />network settings<br />international settings<br />domain information.<br />
  70. 70. Passes - auditSystem<br />Processes unattended Setup settings while Windows 7 is running in system context, before a user logs on to the computer in audit mode. <br />The auditSystem pass runs only if you boot in audit mode.<br />
  71. 71. Passes - auditUser<br />Processes unattended Setup settings after a user logs on to the computer in audit mode.<br />The auditUser pass runs only if you boot in audit mode.<br />
  72. 72. Passes - oobeSystem<br />Applies settings to Windows 7 before Windows Welcome starts.<br />
  73. 73. Mini Setup Phase = Specialize Pass<br />Windows XP<br />driver installation<br />Joining domain<br />Sysprep.inf was the answer file for this phase<br />Windows 7<br />This phase is now called the ‘Specialize’ pass<br />(Auto)Unattend.xml is the answer file for this pass<br />
  74. 74. Mini Setup Phase = Specialize Pass<br />
  75. 75. Windows SIM<br />
  76. 76. Windows SIM<br />
  77. 77. Windows SIM<br />
  78. 78. Windows SIM<br />
  79. 79. Windows SIM<br />
  80. 80. Windows SIM<br />
  81. 81. Windows SIM<br />
  82. 82. Include custom files<br />If you wish to include custom files to include in the Windows 7 installation (such as files in the program files, system32 folder, OOBE (Out Of Box Experience) etc.) then make a folder called $OEM$ inside the sources folder. <br />From there, the following folder structures must apply (many changed from Windows 2000 and Windows XP $OEM$ days) ….. <br />
  83. 83. Include custom files<br />$$Contains files that Windows Setup copies to the %WINDIR% (for example, C:windows) folder during installation.<br />$$System32Contains files that Windows Setup copies to the %WINDIR%System32 folder during installation.<br />
  84. 84. Include custom files<br />$1Represents the root of the drive on which you installed Windows (also called the boot partition) and contains files that Windows Setup copies to the boot partition during installation.<br />$1PnpdriversContains new or updated Plug-and-Play (PnP) drivers. The user specifies the folder name in the Unattend.xml file for unattended installations. For example, this folder might be named $OEM$ Folders$1Pnpdrvs.<br />
  85. 85. Include custom files<br />drive_lettersubfolder<br />A subfolder of the drive that contains files that Windows Setup copies to the subfolder during installation. Multiple instances of this type of folder may exist under the $OEM$ Foldersdrive_letter folder, for example, $OEM$ FoldersDMyFolder.<br />$$SetupScriptsSetupComplete.cmd<br />
  86. 86. Platform Components<br />
  87. 87. Microsoft Deployment Toolkit 2010<br />Microsoft Deployment Toolkit 2010 (MDT 2010) provides a common console with the comprehensive tools and guidance needed to efficiently manage deployment of Windows 7 and Windows Server 2008 R2. <br />Microsoft Deployment Toolkit 2010 is the recommended process and toolset to automate desktop and server deployment. <br />Microsoft Deployment Toolkit 2010 provides detailed guidance and job aids for every organizational role involved with large-scale deployment projects.<br />
  88. 88. Microsoft Deployment Toolkit 2010<br />
  89. 89. Microsoft Deployment Toolkit 2010<br />
  90. 90. MDT 2010 Requirements<br />Microsoft Management Console (MMC) version 3.0<br />Microsoft .NET Framework 2.0 or later<br />Windows PowerShell™ command-line interface (CLI) version 1.0 or 2.0, Community Technology Preview 3 (CTP3) or later<br />Windows Automated Installation Kit (Windows AIK) for Windows 7<br />
  91. 91. Deployment scenario’s - LTI<br />Lite Touch Installation<br />Allows selection of the level of automation<br />Has minimal infrastructure requirements<br />Supports deployments over a network using a shared folder or locally using removable storage such as a CD, DVD, or UFD<br />The deployment process can be initiated manually or automatically using Windows Deployment Services<br />Requires little or no infrastructure to support deployment<br />
  92. 92. Deployment scenario’s - ZTI<br />Zero Touch Installation<br />Supports only fully automated deployments<br />Requires System Center Configuration Manager<br />Supports deployments only from System Center Configuration Manager distribution points<br />The installation process can be initiated by System Center Configuration Manager or Windows Deployment Services<br />Requires an infrastructure sufficient to deploy operating system images<br />
  93. 93. DeploymentWorkbench<br />
  94. 94. DeploymentWorkbench<br />
  95. 95. DeploymentWorkbench<br />
  96. 96. DeploymentWorkbench<br />
  97. 97. DeploymentWorkbench<br />
  98. 98. DeploymentWorkbench<br />
  99. 99. DeploymentWorkbench<br />
  100. 100. DeploymentWorkbench<br />
  101. 101. DeploymentWorkbench<br />
  102. 102. DeploymentWorkbench<br />
  103. 103. DeploymentWorkbench<br />
  104. 104. DeploymentWorkbench<br />
  105. 105. DeploymentWorkbench<br />
  106. 106. DeploymentWorkbench<br />
  107. 107. DeploymentWorkbench<br />
  108. 108. DeploymentWorkbench<br />
  109. 109. DeploymentWorkbench<br />
  110. 110. DeploymentWorkbench<br />
  111. 111. DeploymentWorkbench<br />
  112. 112. DeploymentWorkbench<br />
  113. 113. WSF<br />
  114. 114. WinPE<br />
  115. 115. WinPE<br />
  116. 116. Boot Image<br />
  117. 117. Boot Image<br />
  118. 118. Boot Image<br />
  119. 119. Boot Image<br />
  120. 120. Lite Touch Installation (LTI) deployments<br />
  121. 121. Lite Touch Installation (LTI) deployments<br />
  122. 122. Lite Touch Installation (LTI) deployments<br />
  123. 123. Microsoft Deployment Toolkit 2010<br />
  124. 124. Lite Touch Installation (LTI) deployments<br />
  125. 125. Lite Touch Installation (LTI) deployments<br />
  126. 126. Rules<br />
  127. 127. Lite Touch Installation (LTI) deployments<br />
  128. 128. Microsoft Deployment Toolkit 2010<br />
  129. 129. Microsoft Deployment Toolkit 2010<br />
  130. 130. Microsoft Deployment Toolkit 2010<br />MDT Teamblog:http://blogs.technet.com/msdeployment/default.aspx<br />
  131. 131. Microsoft Deployment Toolkit 2010<br />
  132. 132. Microsoft Deployment Toolkit 2010<br />
  133. 133. Microsoft Deployment Toolkit 2010<br />
  134. 134. Platform Components<br />
  135. 135. Microsoft Deployment Toolkit 2010<br />
  136. 136. Microsoft Deployment Toolkit 2010<br />
  137. 137. Microsoft Deployment Toolkit 2010<br />
  138. 138. Microsoft Deployment Toolkit 2010<br />
  139. 139. Microsoft Deployment Toolkit 2010<br />
  140. 140. Microsoft Deployment Toolkit 2010<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×