Automated Installation en Deployment            Windows 7
Agenda•   Imaging Approaches•   Imaging C.R.A.P.•   WAIK•   MDT 2010•   WDS
Lucky number 7
Traditional vs. Modular Approach              Traditional                    Modular   •   OS + Applications in      •   1...
Traditional Approach   •   Quick Win   •   1 x image per model   •   high maintenance
Traditional vs. Modular Approach                                Maintenance                                Deployment     ...
Imaging Strategy• Thick image  – Core applications and language packs included  – Updates included  – Drivers included• Th...
Imaging C.R.A.P.
Imaging C.R.A.P•   Disk Controllers drivers (STOP 0x0000007B)•   HAL (Uniprocessor, Multiprocessor)•   x64 and x86 support...
Platform Components
Windows Imaging (.WIM)
Microsoft Windows Imaging (WIM)• Microsoft’s own image format• File-based disk imaging is a core capability of  Windows Vi...
Microsoft Windows Imaging (WIM)• This WIM image format is hardware-agnostic,  meaning that you need only one image to addr...
Microsoft Windows Imaging (WIM)• The WIM image format also lets you store multiple  images within one actual file.• For ex...
Microsoft Windows Imaging (WIM)• The WIM image format enables compression and  single instancing, thus reducing the size o...
Microsoft Windows Imaging (WIM)• The WIM image format allows you to service an image  offline. You can add or delete certa...
Microsoft Windows Imaging (WIM)• The WIM image format lets you install a disk image on  partitions of any size, unlike sec...
WAIK
Windows Automated Installation Kit• The Windows® Automated Installation Kit (Windows AIK)  is a set of tools and documenta...
Windows Automated Installation Kit• By using Windows AIK, you can automate Windows  installations, capture Windows images ...
ImageX
ImageX
ImageX
ImageX
ImageX
ImageX
ImageX
ImageX
DISM• Deployment Image Servicing and Management Tool
DISM
DISM
DISM
DISM
DISM
DISM
DISM
DISM
Platform Components
Attended Windows setup
Windows XP Setup Manager
Windows SIM
Unattended Windows setup• Unattend.xml• AutoUnattend.xml• As a rule, only answer files named Unattend.xml are used.• Howev...
Unattend Windows setup
Unattend Windows setup
Unattend Windows setup
Unattend Windows setup
Unattend Windows setup
Unattend Windows setup
Unattend Windows setup
Windows SIM
Passes•   windowsPE•   offlineServicing•   generalize•   Specialize•   auditSystem•   auditUser•   oobeSystem
Windows PE• Windows PE is a minimal Win32 subsystem with limited  services, based on the Windows 7 kernel running in  prot...
Windows PE
Passes – windowsPE• Configures Windows PE options as well as basic Windows Setup  options. These options can include confi...
Passes - offlineServicing• Applies updates to a Windows 7 image.• Also applies packages, including software fixes,  langua...
Passes - generalize• The generalize pass runs only if you run sysprep  /generalize. In this pass, you can minimally config...
Passes - specialize• Creates and applies system-specific information.• For example, you can configure:   – network setting...
Passes - auditSystem• Processes unattended Setup settings while Windows 7 is  running in system context, before a user log...
Passes - auditUser• Processes unattended Setup settings after a user logs on  to the computer in audit mode.• The auditUse...
Passes - oobeSystem• Applies settings to Windows 7 before  Windows Welcome starts.
Mini Setup Phase• Windows XP  – driver installation  – Joining domain  – Sysprep.inf was the answer file for this phase• W...
Windows SIM
Windows SIM
Windows SIM
Windows SIM
Windows SIM
Windows SIM
Windows SIM
Include custom files• If you wish to include custom files to include in the  Windows 7 installation (such as files in the ...
Include custom files• $$  Contains files that Windows Setup copies to the  %WINDIR% (for example, C:windows) folder during...
Include custom files• $1  Represents the root of the drive on which you installed  Windows (also called the boot partition...
Include custom files• drive_lettersubfolder• A subfolder of the drive that contains files that Windows  Setup copies to th...
Platform Components
Microsoft Deployment Toolkit 2010• Microsoft Deployment Toolkit 2010 (MDT 2010) provides a  common console with the compre...
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
MDT 2010 Requirements• Microsoft Management Console (MMC)  version 3.0• Microsoft .NET Framework 2.0 or later• Windows Pow...
Deployment scenario’s - LTI• Lite Touch Installation• Allows selection of the level of automation• Has minimal infrastruct...
Deployment scenario’s - ZTI• Zero Touch Installation• Supports only fully automated deployments• Requires System Center Co...
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
DeploymentWorkbench
WSF
WinPE
WinPE
Boot Image
Boot Image
Boot Image
Boot Image
Lite Touch Installation (LTI) deployments
Lite Touch Installation (LTI) deployments
Lite Touch Installation (LTI) deployments
Microsoft Deployment Toolkit 2010
Lite Touch Installation (LTI) deployments
Lite Touch Installation (LTI) deployments
Rules
Lite Touch Installation (LTI) deployments
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010• MDT Teamblog:  http://blogs.technet.com/msdeployment/default.aspx
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Platform Components
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Microsoft Deployment Toolkit 2010
Thnx !!  
Windows 7 deployment
Upcoming SlideShare
Loading in …5
×

Windows 7 deployment

1,134 views

Published on

Slidedeck used for several Windows events about Deploying Windows 7.

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
1,134
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • Continuous Repetitive Automated Process
  • http://en.wikipedia.org/wiki/LZX_%28algorithm%29LZX was publicly released as an Amiga file archiver in 1995, while the authors (Jonathan Forbes, TomiPoutanen) were studying at the University of Waterloo in Canada. The software was shareware, which was common for compression software at the time. The registered version contained fixes and improvements not available in the evaluation version. In 1997, the authors gave away a free keyfile, which allowed anyone to use the registered version, as they had stopped work on the archiver and stopped accepting registrations. In 1997, Forbes went to work for Microsoft, and Microsoft's cabinetarchiver was enhanced to include the LZX compression method.
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx
  • http://www.magalan.co.uk/Create_Custom_Windows_7_DVD_with_Unattend_Service_Pack.html
  • Windows 7 deployment

    1. 1. Automated Installation en Deployment Windows 7
    2. 2. Agenda• Imaging Approaches• Imaging C.R.A.P.• WAIK• MDT 2010• WDS
    3. 3. Lucky number 7
    4. 4. Traditional vs. Modular Approach Traditional Modular • OS + Applications in • 1 base image (OS) for 1 image all hardware • Image per hardware type • Apps/drivers delivered as add-ons • Time to integrate new hardware • Easily integrate new hardware • High maintenance • Reduced maintenance • Requires a visit to costs the desktop • Automated build process • Storage requirements • Easy to customise
    5. 5. Traditional Approach • Quick Win • 1 x image per model • high maintenance
    6. 6. Traditional vs. Modular Approach Maintenance Deployment Development Time Traditional Modular
    7. 7. Imaging Strategy• Thick image – Core applications and language packs included – Updates included – Drivers included• Thin image – Core applications and language packs NOT included – Updates NOT included – Drivers NOT included• Hybrid image – Mixes thin and thick strategies
    8. 8. Imaging C.R.A.P.
    9. 9. Imaging C.R.A.P• Disk Controllers drivers (STOP 0x0000007B)• HAL (Uniprocessor, Multiprocessor)• x64 and x86 support• Disk and Partition Setup• Windows Updates• Drivers (Built-In, ‘to be connected’ hardware)• Custom Registry Settings• Applications• AMD and Intel support• Applications
    10. 10. Platform Components
    11. 11. Windows Imaging (.WIM)
    12. 12. Microsoft Windows Imaging (WIM)• Microsoft’s own image format• File-based disk imaging is a core capability of Windows Vista, Windows 7, Windows 2008• Compared to sector-based formats, a WIM image is file-based
    13. 13. Microsoft Windows Imaging (WIM)• This WIM image format is hardware-agnostic, meaning that you need only one image to address many different hardware configurations.
    14. 14. Microsoft Windows Imaging (WIM)• The WIM image format also lets you store multiple images within one actual file.• 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.• 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.
    15. 15. Microsoft Windows Imaging (WIM)• The WIM image format enables compression and single instancing, thus reducing the size of image files significantly.• Single instancing is a technique that allows you to store two or more copies of a file for the space cost of one copy.• 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.
    16. 16. Microsoft Windows Imaging (WIM)• 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.• Rather than spending a few hours updating an image, which you do now with Microsoft Windows XP, for example, you can update an image in minutes.• 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.• With Windows 7, you can simply service the image offline.
    17. 17. Microsoft Windows Imaging (WIM)• 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 thats the same size or larger than the source disk.
    18. 18. WAIK
    19. 19. Windows Automated Installation Kit• The Windows® Automated Installation Kit (Windows AIK) is a set of tools and documentation that support the configuration and deployment of Windows® operating systems.
    20. 20. Windows Automated Installation Kit• 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).• 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).
    21. 21. ImageX
    22. 22. ImageX
    23. 23. ImageX
    24. 24. ImageX
    25. 25. ImageX
    26. 26. ImageX
    27. 27. ImageX
    28. 28. ImageX
    29. 29. DISM• Deployment Image Servicing and Management Tool
    30. 30. DISM
    31. 31. DISM
    32. 32. DISM
    33. 33. DISM
    34. 34. DISM
    35. 35. DISM
    36. 36. DISM
    37. 37. DISM
    38. 38. Platform Components
    39. 39. Attended Windows setup
    40. 40. Windows XP Setup Manager
    41. 41. Windows SIM
    42. 42. Unattended Windows setup• Unattend.xml• AutoUnattend.xml• As a rule, only answer files named Unattend.xml are used.• 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.• 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.
    43. 43. Unattend Windows setup
    44. 44. Unattend Windows setup
    45. 45. Unattend Windows setup
    46. 46. Unattend Windows setup
    47. 47. Unattend Windows setup
    48. 48. Unattend Windows setup
    49. 49. Unattend Windows setup
    50. 50. Windows SIM
    51. 51. Passes• windowsPE• offlineServicing• generalize• Specialize• auditSystem• auditUser• oobeSystem
    52. 52. Windows PE• Windows PE is a minimal Win32 subsystem with limited services, based on the Windows 7 kernel running in protected mode.• It contains the minimal functionality that you need to run Setup, install Windows from a network share, automate basic processes, and perform hardware validation.• Windows PE was developed specifically to address desktop and server deployment scenarios.
    53. 53. Windows PE
    54. 54. Passes – windowsPE• Configures Windows PE options as well as basic Windows Setup options. These options can include configuring a disk or language settings.
    55. 55. Passes - offlineServicing• Applies updates to a Windows 7 image.• Also applies packages, including software fixes, language packs, and other security updates.
    56. 56. Passes - generalize• 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.• The sysprep /generalize command removes system- specific information. For example, the unique SID and other hardware-specific settings are removed from the image.
    57. 57. Passes - specialize• Creates and applies system-specific information.• For example, you can configure: – network settings – international settings – domain information.
    58. 58. Passes - auditSystem• Processes unattended Setup settings while Windows 7 is running in system context, before a user logs on to the computer in audit mode.• The auditSystem pass runs only if you boot in audit mode.
    59. 59. Passes - auditUser• Processes unattended Setup settings after a user logs on to the computer in audit mode.• The auditUser pass runs only if you boot in audit mode.
    60. 60. Passes - oobeSystem• Applies settings to Windows 7 before Windows Welcome starts.
    61. 61. Mini Setup Phase• Windows XP – driver installation – Joining domain – Sysprep.inf was the answer file for this phase• Windows 7 – This phase is now called the ‘Specialize’ pass – (Auto)Unattend.xml is the answer file for this pass
    62. 62. Windows SIM
    63. 63. Windows SIM
    64. 64. Windows SIM
    65. 65. Windows SIM
    66. 66. Windows SIM
    67. 67. Windows SIM
    68. 68. Windows SIM
    69. 69. Include custom files• 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.• From there, the following folder structures must apply (many changed from Windows 2000 and Windows XP $OEM$ days) …..
    70. 70. Include custom files• $$ Contains files that Windows Setup copies to the %WINDIR% (for example, C:windows) folder during installation.• $$System32 Contains files that Windows Setup copies to the %WINDIR%System32 folder during installation.
    71. 71. Include custom files• $1 Represents 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.• $1Pnpdrivers Contains 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.
    72. 72. Include custom files• drive_lettersubfolder• 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.• $$SetupScriptsSetupComplete.cmd
    73. 73. Platform Components
    74. 74. Microsoft Deployment Toolkit 2010• 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.• Microsoft Deployment Toolkit 2010 is the recommended process and toolset to automate desktop and server deployment.• Microsoft Deployment Toolkit 2010 provides detailed guidance and job aids for every organizational role involved with large-scale deployment projects.
    75. 75. Microsoft Deployment Toolkit 2010
    76. 76. Microsoft Deployment Toolkit 2010
    77. 77. MDT 2010 Requirements• Microsoft Management Console (MMC) version 3.0• Microsoft .NET Framework 2.0 or later• Windows PowerShell™ command-line interface (CLI) version 1.0 or 2.0, Community Technology Preview 3 (CTP3) or later• Windows Automated Installation Kit (Windows AIK) for Windows 7
    78. 78. Deployment scenario’s - LTI• Lite Touch Installation• Allows selection of the level of automation• Has minimal infrastructure requirements• Supports deployments over a network using a shared folder or locally using removable storage such as a CD, DVD, or UFD• The deployment process can be initiated manually or automatically using Windows Deployment Services• Requires little or no infrastructure to support deployment
    79. 79. Deployment scenario’s - ZTI• Zero Touch Installation• Supports only fully automated deployments• Requires System Center Configuration Manager• Supports deployments only from System Center Configuration Manager distribution points• The installation process can be initiated by System Center Configuration Manager or Windows Deployment Services• Requires an infrastructure sufficient to deploy operating system images
    80. 80. DeploymentWorkbench
    81. 81. DeploymentWorkbench
    82. 82. DeploymentWorkbench
    83. 83. DeploymentWorkbench
    84. 84. DeploymentWorkbench
    85. 85. DeploymentWorkbench
    86. 86. DeploymentWorkbench
    87. 87. DeploymentWorkbench
    88. 88. DeploymentWorkbench
    89. 89. DeploymentWorkbench
    90. 90. DeploymentWorkbench
    91. 91. DeploymentWorkbench
    92. 92. DeploymentWorkbench
    93. 93. DeploymentWorkbench
    94. 94. DeploymentWorkbench
    95. 95. DeploymentWorkbench
    96. 96. DeploymentWorkbench
    97. 97. DeploymentWorkbench
    98. 98. DeploymentWorkbench
    99. 99. DeploymentWorkbench
    100. 100. DeploymentWorkbench
    101. 101. WSF
    102. 102. WinPE
    103. 103. WinPE
    104. 104. Boot Image
    105. 105. Boot Image
    106. 106. Boot Image
    107. 107. Boot Image
    108. 108. Lite Touch Installation (LTI) deployments
    109. 109. Lite Touch Installation (LTI) deployments
    110. 110. Lite Touch Installation (LTI) deployments
    111. 111. Microsoft Deployment Toolkit 2010
    112. 112. Lite Touch Installation (LTI) deployments
    113. 113. Lite Touch Installation (LTI) deployments
    114. 114. Rules
    115. 115. Lite Touch Installation (LTI) deployments
    116. 116. Microsoft Deployment Toolkit 2010
    117. 117. Microsoft Deployment Toolkit 2010
    118. 118. Microsoft Deployment Toolkit 2010• MDT Teamblog: http://blogs.technet.com/msdeployment/default.aspx
    119. 119. Microsoft Deployment Toolkit 2010
    120. 120. Microsoft Deployment Toolkit 2010
    121. 121. Microsoft Deployment Toolkit 2010
    122. 122. Platform Components
    123. 123. Microsoft Deployment Toolkit 2010
    124. 124. Microsoft Deployment Toolkit 2010
    125. 125. Microsoft Deployment Toolkit 2010
    126. 126. Microsoft Deployment Toolkit 2010
    127. 127. Microsoft Deployment Toolkit 2010
    128. 128. Microsoft Deployment Toolkit 2010
    129. 129. Thnx !! 

    ×