Lesson 1: Designing a Lite-Touch Deployment   The one LTI scenario that requires a different task sequence template is the Replace Computer scenario. In this type of deployment, you are saving the user state data from an existing workstation and then restoring it to a new workstation after installing Windows 7. Because you are working with two computers, you need two separate task sequences. The rst one, based on the Standard Client Replace Task Sequence template, contains the Capture User State command and skips the process of installing Windows 7, as shown in Figure 7-2. In the second task sequence, which runs on the new computer, the installer skips the Capture User State command, installs Windows 7, and then performs the Restore User State command to copy the user state data from the existing computer to the new one.  A task sequence based on the Standard Client Replace Task Sequence template Technical specialists who have special needs and who are familiar with the task sequence format can also use the Custom Task Sequence template to create a sequence from scratch.  After you have created the task sequences that you need to deploy your captured images to the target computers, you must update your deployment share, if you have not done so already. Updating the deployment share creates the boot images that enable the target work- stations to connect to the deployment share on the build computer.   Designing Lite-Touch and Zero-Touch Deployments Note      Updating the deployment share creates boot images in the Boot folder of the deployment share in both Windows Imaging (wim) and ISO formats, in 32-bit and 64-bit versions, using the following le names: ■ LiteTouchPE_x64.wim ■ LiteTouchPE_x64.iso ■ LiteTouchPE_x86.wim ■ LiteTouchPE_x86.iso  ■     ■     The image les that Deployment Workbench creates when you update the deployment share contain the Windows PE boot les and the Windows Deployment Wizard. This wizard runs on the target computer and enables the installer to control the individual deployment process for each workstation. The next decision that the administrators must make is how they intend to boot each of the target computers.  The LiteTouchPE_x32.iso and LiteTouchPE_x64.iso les that Deployment Workbench creates contain all the boot les the target computer requires in a single, le-based image. You can burn these images to CDs, DVDs, or USB ash drive and use them to boot the target workstations. The resulting boot disks include all of the software necessary to start a computer, load the Windows Deployment Wizard, and connect to the deployment share on the build computer. Note    Lesson 1: Designing a Lite-Touch Deployment   The advantage to this boot method is that the target computers require no special hard- ware other than a disk drive or a USB port from which the system can boot. The disadvantage is that you must have a boot disk for each target computer you want to install. However, you do not necessarily have to create a separate boot disk for each workstation because the disks are not system-specic. After the Windows Deployment Wizard loads, remove the disk or drive and use it to boot another computer. Because some interaction is required at each target computer anyway in an LTI deployment to initiate the installation process, using boot disks to start each workstation is not a terrible inconvenience.  The other boot method for target workstations is to deploy the LiteTouchPE_x86.wim and LiteTouchPE_x64.wim les over the network by using Windows Deployment Services (WDS). This method is much faster and eliminates the need to burn boot disks and carry them to the individual workstations. You can also install large numbers of target computers simultaneously. The disadvantages are that every target computer must be equipped with a network inter- face adapter that supports the Preboot Execution Environment (PXE) standard. The network must also have a WDS server and a DHCP server that is congured to support WDS. You can run both of these services on your build computer or on a separate server.  You can also launch the Windows Deployment Wizard from a computer that is already running an operating system by connecting to the deployment share over the network and running the Litetouch.vbs script, located in the Scripts folder. One example of the commands used to do this appears as follows: net use s: \\server\deploymentshare$ s: cd scripts cscript litetouch.vbs This method of launching the wizard is required when your task sequence needs access to the currently installed operating system on the target computer. For example, in the Refresh Computer scenario, the wizard must capture the target computer’s user state and save it to a remote location before it installs Windows 7. If you use one of the Windows PE boot methods to start the target computer, the wizard skips the Capture User State task because it does not have access to the installed operating system. Starting the wizard with the Litetouch.vbs script while the existing operating system is running enables it to locate the required les and perform the Capture User State task.   Designing Lite-Touch and Zero-Touch Deployments  When you boot the target computer using one of the LiteTouchPE image les, the MDT 2010 Solution Accelerators interface appears, as shown in Figure 7-3. When you boot the computer using one of the ISO images, the initial interface is included on the disk. When you deploy the Windows Imaging le using WDS, the target computer obtains the address of the WDS server from the DHCP server on the network and then downloads the boot les and the interface from the WDS server. Whichever method the target computer uses, the interface is the same, as is the process of deploying Windows 7.  The MDT 2010 Solution Accelerators interface After the interface appears, you can click Run The Deployment Wizard To Install A New Operating System. The User Credentials window appears, in which you must type domain or local credentials in the User Name, Password, and Domain text boxes that provide access to the deployment share. Lesson 1: Designing a Lite-Touch Deployment   At this point, the Windows Deployment Wizard appears displaying the Select A Task Sequence To Execute On This Computer page, as shown in Figure 7-4. If you run the Litetouch.vbs script from within a running operating system, the wizard loads using the credentials with which you logged on to the target computer.  The Select A Task Sequence To Execute On This Computer page in the Windows Deployment Wizard The installer can now proceed with the LTI deployment process as follows:  1. In the Select A Task Sequence To Execute On This Computer page, select the task se- quence to run on the target computer and click Next. Note         Designing Lite-Touch and Zero-Touch Deployments  2. If you have launched the wizard from a running operating system, the Choose A Migration Type page appears, as shown in Figure 7-5. Specify what scenario you want to use for the target computer deployment by selecting the appropriate option.  The Choose A Migration Type page in the Windows Deployment Wizard  3. Click Next. The Specify The Product Key Needed To Install This Operating System page appears, as shown in Figure 7-6. To specify an individual Windows 7 product key or a Multiple Activation Key (MAK) for the installation, select the appropriate option and type the key in the text box provided. Lesson 1: Designing a Lite-Touch Deployment    The Specify The Product Key Needed To Install This Operating System page in the Windows Deployment Wizard  4. Click Next. The Congure The Computer Name page appears, as shown in Figure 7-7.  The Configure The Computer Name page in the Windows Deployment Wizard   Designing Lite-Touch and Zero-Touch Deployments  5. In the Computer Name text box, specify the name you want to assign to the new workstation and click Next. The Join The Computer To A Domain Or Workgroup page appears, as shown in Figure 7-8.  The Join The Computer To A Domain Or Workgroup page in the Windows Deployment Wizard  6. To join the target computer to a domain after the Windows 7 installation, select the Join A Domain option and, in the Domain text box, type the name of the domain you want the computer to join and click Next. ■ The credentials you supplied earlier appear by default in the User Name, Password, and Domain text boxes. If these credentials do not provide administrative access to the AD DS domain you specied, you must change them. ■ If you want the wizard to create the computer object in a specic organizational unit, rather than the Computers container, type its name in the Organizational Unit text box. ■ To join the target computer to a workgroup, leave the Join A Workgroup option selected and type the name of the workgroup you want the computer to join in the Workgroup text box. Lesson 1: Designing a Lite-Touch Deployment    7. If you are using the Refresh Computer scenario, the Specify Where To Save Your Data And Settings page appears, as shown in Figure 7-9. Select the Specify A Location option, and in the Location text box, type a path to the folder to which you want the wizard to copy the user state data from the target computer. Then click Next.  The Specify Where To Save Your Data And Settings page in the Windows Deployment Wizard  8. If you are using the Replace Computer or Refresh Computer scenario, the Specify Whether To Restore User Data page appears, as shown in Figure 7-10. Select the Specify A Location option and, in the Location text box, type the path to the location in which you saved the user state data you want to restore.   Designing Lite-Touch and Zero-Touch Deployments  The Specify Whether To Restore User Data page in the Windows Deployment Wizard  9. Click Next. The Language And Other Preferences page appears, as shown in Figure 7-11.  The Language And Other Preferences page in the Windows Deployment Wizard [...]... three drop-down lists Then click Next The Set The Time Zone page appears, as shown in Figure 7- 1 2 Figure 7- 1 2  The Set The Time Zone page in the Windows Deployment Wizard 11 Select the time zone for the target computer’s ultimate location and click Next The Administrator Password page appears, as shown in Figure 7- 1 3 Lesson 1: Designing a Lite-Touch Deployment CHAPTER 7 283 Figure 7- 1 3  The Administrator. .. Figure 7- 1 5 Figure 7- 1 5  The Ready To Begin page in the Windows Deployment Wizard Lesson 1: Designing a Lite-Touch Deployment CHAPTER 7 285 15 Click Begin An Installation Progress window appears, tracking the various procedures of the installation 16 When the installation is completed, the Operating System Deployment Completed Successfully page appears, as shown in Figure 7- 1 6 Figure 7- 1 6 The Operating... Image Options page appears, as shown in Figure 7- 2 5 3 04 CHAPTER 7 Designing Lite-Touch and Zero-Touch Deployments Figure 7- 2 5  The Image Options page of the Create Microsoft Deployment Task Sequence Wizard 12 Select the Platform option for the target computer you want to install and click Next The MDT Package page appears, as shown in Figure 7- 2 6 Figure 7- 2 6 The MDT Package page of the Create Microsoft... OS Image page appears, as shown in Figure 7- 2 7 Figure 7- 2 7 The OS Image page of the Create Microsoft Deployment Task Sequence Wizard 15 Select the Create A New OS Image option 16 In the OS Image File (WIM) Location text box, type the path to the image you captured from your reference computer 3 06 CHAPTER 7 Designing Lite-Touch and Zero-Touch Deployments 17 In the Package Source Folder To Be Created... the Windows Deployment Wizard 12 In the Administrator Password and Please Confirm Administrator Password text boxes, type the password you want the target computer to use and click Next The Specify The BitLocker Configuration page appears, as shown in Figure 7- 1 4 Figure 7- 1 4  The Specify The BitLocker Configuration page in the Windows Deployment Wizard 2 84 CHAPTER 7 Designing Lite-Touch and Zero-Touch... such as Windows 7 Target Deployment, and click Next The Details page appears, as shown in Figure 7- 2 3 3 02 CHAPTER 7 Designing Lite-Touch and Zero-Touch Deployments Figure 7- 2 3  The Details page of the Create Microsoft Deployment Task Sequence Wizard 5 Select the Join A Domain option, and in the Domain text box, type the name of the domain you want the target computer to join 6 Click Set The Windows. .. sequence to save user state data before installing Windows 7? B LiteTouchPE_x64.wim C LiteTouchPE_x32.iso A Litetouch.vbs D LiteTouchPE_x64.iso Lesson 1: Designing a Lite-Touch Deployment CHAPTER 7 2 97 Lesson 2: Designing a Zero-Touch Deployment As mentioned earlier and in previous chapters, a Zero-Touch Installation follows the same basic steps as a Lite-Touch Installation You still install reference... in Figure 7- 1 8 Then you must update the deployment share in the usual way to create boot images that support multicasting Note Supporting Multicasting To use multicasting successfully with MDT 2010, you must be using Windows AIK version 1.1 or later on your build server This is because earlier versions of Windows AIK include Windows PE boot files that do not support multicasting Figure 7- 1 8  The Enable... ■ Windows Deployment Services ■ BITS Server Extensions ■ Remote Differential Compression ■ System Center Configuration Manager 20 07 ■ SQL Server 2005 SP2 or later ■ Windows 7 Automated Installation Kit ■ Microsoft Deployment Toolkit 2010 Configuring Configuration Manager Integration After you have installed and configured SCCM 20 07 and all of the other software required to run it, you can install Windows. .. computer, which is where you install Microsoft Deployment Toolkit (MDT) 2010 and Windows 7 Automated Installation Kit (Windows AIK) One way of minimizing the amount of network bandwidth the deployment process consumes is to use multicast transmissions to deliver the image files to the target computers CHAPTER 7 Designing Lite-Touch and Zero-Touch Deployments Lesson Review You can use the following questions . both Windows Imaging (wim) and ISO formats, in 32-bit and 64 -bit versions, using the following le names: ■ LiteTouchPE_x64.wim ■ LiteTouchPE_x64.iso ■ LiteTouchPE_x 86. wim ■ LiteTouchPE_x 86. iso  ■ . Next. The Administrator Password page appears, as shown in Figure 7- 1 3.   Designing Lite-Touch and Zero-Touch Deployments  The Administrator Password page in the Windows. the Windows Deployment Wizard  3. Click Next. The Specify The Product Key Needed To Install This Operating System page appears, as shown in Figure 7- 6 . To specify an individual Windows 7 product