CHAPTER 3 Deployment Platform 104 The Specialize pass, which runs during this phase, creates and applies computer-specific information. For example, you can use an unattended setup answer file (Unattend.xml) to configure network settings, international settings, and domain information, as well as run installation programs. During the Online Configuration phase, you can use scripts to configure the destination computer. However, a task sequencer, which enables you to filter tasks based on condi- tions, such as whether a particular device is installed, is better suited to this purpose. A task sequencer also provides advanced features such as the ability to wait until a certain condition arises before continuing, and grouping tasks into folders and then filtering the entire group. on tHe CoMpAnion MediA The companion media includes a script-based task sequencer, Taskseq.wsf, that provides all of these advanced features, among others. It reads tasks sequences from .xml files and then executes them. The file Sample_Task_Sequences.zip includes sample task sequences that demonstrate how to build .xml files for Taskseq.wsf. Do not run these sample task sequences on pro- duction computers. Read the documentation included in the source code for more information about using Taskseq.wsf. Windows Welcome Phase In the Windows Welcome phase, shown in Figure 3-7, the installation is finalized, and any first-use customizations you want to apply are presented. Additionally, Windows 7 prompts for the product key during this phase. You can customize the Windows Welcome screens and messages and store these customizations in an Oobe.xml file. Preinstallation Online Customization Windows Welcome Custom Welcome Internet Configuration Unattend.xml OOBE.XML FIGURE 3-7 Windows Welcome phase Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Basic Deployment Process CHAPTER 3 105 diReCt FRoM tHe SoURCe Text-Mode Setup Is Gone Michael Niehaus, Systems Design Engineer Microsoft Deployment Toolkit T he basic process used to install Windows XP has been unchanged since the earliest days of Microsoft Windows NT. This time-consuming procedure in- volved an initial text-mode installation step in which every operating system file was decompressed and installed, all registry entries were created, and all security was applied. Beginning with Windows Vista, this text-mode installation phase is completely gone. Instead, a new setup program performs the installation, applying a Windows image to a computer. After this image is applied, it needs to be customized for the computer. This customi- zation takes the place of what was called mini-setup in Windows XP and Microsoft Windows 2000. The purpose is the same: the operating system picks the necessary settings and configuration for the specific computer to which it was deployed. The image preparation process has also changed. With Windows XP, you would Sysprep a computer to prepare the reference operating system for deployment. Be- ginning with Windows Vista, you’ll still run Sysprep.exe, but it’s installed by default in C:\Windows\System32\Sysprep. Beginning with Windows Vista, the Windows operating system is provided on the DVD as an already-installed, generalized (Sysprepped) image, ready to deploy to any computer. Some customers may choose to deploy this image as is (possibly injecting fixes or drivers using the servicing capabilities provided by the deploy- ment tools). Basic Deployment Process Figure 3-8 illustrates the basic deployment process using only the Windows 7 deployment tools to build images for high-volume deployments. Although this is useful background infor- mation, direct use of these tools isn’t recommended. Using a framework like MDT 2010 is the best way to deploy Windows 7. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 3 Deployment Platform 106 Technician Computer 1 Master Computer 2 Network Share 3 Destination Computers Windows SIM Windows PE Windows Vista Device Drivers Applications Packages Install, Customize, and Test Image Stored Images Deploy Images 4 FIGURE 3-8 Basic deployment process The following list describes the steps in Figure 3-8: n Technician Computer You build a distribution share on a technician computer. The distribution share includes the Windows 7 source files, applications, device drivers, and packages. You use Windows SIM to configure the distribution share by adding source files to it. You also use Windows SIM to create and customize the Windows 7 answer file to use for installation. n Master Computer On a master computer, you create a master installation by run- ning Windows Setup from the distribution share, using an answer file you created with Windows SIM. The installation should be automated fully to ensure a consistent, repeatable process from one build to the next. After creating the master installation, run Sysprep to prepare it for duplication. In low-volume deployments, you can skip this step and deploy to desktop computers directly from the volume license or retail Windows 7 media that Microsoft provides and then customize the installation during deployment. n Network Share You use ImageX to capture an image of the master installation from the master computer. Then you store the image on a network share accessible to the destination computers to which you’re deploying the image. Alternatives to deploying from a network share include deploying the image from a DVD, a UFD, or Windows Deployment Services. n Destination Computers On the destination computers, run Windows Setup to install Windows 7. Windows Setup accepts the image file and answer file to use as command- line options. Using Windows Setup to apply an image to destination computers is pref- erable to using ImageX to apply the image. Windows Setup includes logic that ImageX does not include, such as properly preparing the BCD. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Microsoft Deployment Toolkit Process CHAPTER 3 107 HoW it WoRKS Configuration Passes W indows Setup uses configuration passes to configure systems. The following list describes each configuration pass that Windows Setup runs: n windowsPE Configures Windows PE options as well as basic Windows Setup options. These options can include configuring a disk or language settings. n offlineServicing Applies updates to a Windows 7 image. Also applies pack- ages, including software fixes, language packs, and other security updates. n 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. n specialize Creates and applies system-specific information. For example, you can configure network settings, international settings, and domain information. n auditSystem Processes unattended Setup settings while Windows 7 is run- ning 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. n 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. n oobeSystem Applies settings to Windows 7 before Windows Welcome starts. Microsoft Deployment Toolkit Process Microsoft Deployment Toolkit 2010 (MDT 2010) is a holistic approach to desktop deployment, bringing together the people, processes, and technology required to perform highly successful, repeatable, and consistent deployment projects. Because of its strong focus on methodology and best practices, MDT 2010 is much more valuable than the sum of its parts. Not only does it have the benefit of decreasing the time required to develop a desktop-deployment project, but it also reduces errors and helps you create a higher-quality desktop-deployment project. Microsoft recommends that you use MDT 2010 to deploy Windows 7 instead of using the basic deployment tools directly. All the deployment tools in Windows 7 and the Windows AIK 2.0 are huge improvements over the deployment tools for earlier versions of Windows. However, they are simply tools without a framework, without any business logic. They have no “glue” to bind them into an end-to-end process. MDT 2010 provides this glue in the form of a complete technology framework. Internally, MDT 2010 is an extremely complex solution. It provides solutions for the problems facing most customers during deployment, including pre- Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 3 Deployment Platform 108 installation phases (disk partitioning, formatting, and so on), installation (disk imaging), and postinstallation phases (user state migration, application installation, customization, and so on). Even though MDT 2010 is complex internally, the solution makes building, customizing, and deploying Windows 7 images easier by masking the details. diReCt FRoM tHe SoURCe Microsoft Deployment Toolkit Manu Namboodiri Windows Product Management M icrosoft has invested a lot to provide innovative technologies that help cus- tomers deploy desktops effectively, especially the new capabilities around file-based imaging, feature-based architectures, hardware independence, and so on. These have significant benefits in reducing image count, costs, and complexity. However, where we have heard a lot of feedback from our customers and partners is regarding the best practices and methodology to use these tools most effectively. We also hear from industry analysts that most of the migration challenges that customers face center around building teams, schedules, project plans, business cases, and the right set of images as well as process and methodology. Technology, in itself, plays a smaller role than we would think in successful deployments. The challenges our customers face are the following: n No standard set of deployment guidelines, which results in widely varying results and costs for desktop deployments n More focus on technology and less on methodology, which has caused vary- ing types of solutions and, therefore, varying results n Customer perception of cost/complexity because of the lack of repeatable and consistent processes around the technology n Unclear guidance about which of our many new tools to use and when Discovering these concerns has made us extremely focused on enhancing our guid- ance around deployments. The result is the significantly improved MDT methodol- ogy for desktop deployment. We are working with industry experts, system integra- tors, and deployment/management software providers to enhance this guidance so that it captures best practices from throughout the industry. Figure 3-9 describes the typical process for using MDT 2010 to deploy Windows 7. The process is the same whether you’re capturing an image in the lab or deploying images in a production environment. Additionally, MDT 2010 provides a user interface to configure all of its processes. Behind the scenes, thousands of lines of code work to implement your choices during deployment. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Microsoft Deployment Toolkit Process CHAPTER 3 109 Deployment Share 1 Build 2 3 Destination Computer Images Applications Device Drivers Packages Answer File Settings Task Sequence Deploy Images FIGURE 3-9 Microsoft Deployment Toolkit process The following list describes each part of the MDT 2010 process. (See Chapter 6 and Chapter 12, “Deploying with Microsoft Deployment Toolkit,” for more information.) n Deployment share After installing MDT 2010 on a build server in a lab environment, you use the Deployment Workbench to stock the deployment share with source files. Source files include Windows 7 images, applications, device drivers, and packages. The Deployment Workbench provides a user interface for adding all source files to the deployment share. The user interface also provides intelligence, such as error checking and building a device driver database for device driver injection during deployment. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 3 Deployment Platform 110 n Task sequence After the deployment share is fully stocked, you use the Deployment Workbench to create a task sequence. A task sequence associates source files from the deployment share with a list of steps to take during installation. The task sequence specifies when to take each step and when to skip it (filtering). The task sequence sup- ports reboots during installation, and data collected during the task sequence persists between reboots. The task sequence represents one of the primary customization points for MDT 2010. n Destination computer With a fully stocked deployment share and a task sequence, you can use MDT 2010 to deploy Windows 7 to destination computers. You can use LTI to deploy Windows 7. To use LTI, you start the destination computer using the deploy- ment share’s Windows PE boot image. You can put the boot image on removable media (DVD, UFD, and so on) or add it to a Windows Deployment Services server. Either way, you start the destination computer using the Windows PE boot image provided by the deployment share to begin the Windows Deployment Wizard. The wizard displays several pages to collect data from you (computer name, domain membership, applica- tions to install, and so on), and then installs the operating system without any further interaction. You can also use ZTI to deploy Windows 7. MDT 2010 integrates directly in System Center Configuration Manager 2007. For more information about using ZTI, see the MDT 2010 documentation. Note that Figure 3-9 makes no reference to creating a master installation and capturing an image. In MDT 2010, creating and capturing an image is an LTI process. You can configure any deployment share to capture an image of an installation and store the image in the deploy- ment share automatically. After you make this choice, the imaging process is fully automated. You don’t have to run Sysprep or ImageX—the Windows Deployment Wizard automatically runs Sysprep and then runs ImageX to capture the image and store it in the deployment share. Then you can simply add the image to the deployment share using Deployment Workbench. note You can download MDT 2010 from http://technet.microsoft.com/en-us /desktopdeployment/default.aspx. Summary The Windows 7 deployment platform and tools will make deploying the operating system in your organization easier than deploying earlier versions of Windows. The .wim file format makes it possible to deploy highly compressed image files. Windows 7 helps reduce image count by removing hardware dependencies from the image. Modularization in Windows 7 makes servicing images easier than legacy methods so that you no longer have to apply, cus- tomize, and recapture an image to update it. The answer file format, Unattend.xml, provides a Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Additional Resources CHAPTER 3 111 more flexible and consistent configuration. Finally, the deployment tools, DISM, ImageX, and Windows SIM, provide a robust way to create, customize, and manage Windows 7 images. Although the Windows AIK 2.0 provides the basic tools for customizing and deploying Windows 7, MDT 2010 provides a more flexible framework for deploying Windows 7 in orga- nizations. With MDT 2010, you can create and customize multiple image builds. The frame- work includes automation common to most organizations and is highly extensible to suit any requirements. Additional Resources These resources contain additional information and tools related to this chapter. Related Information n Windows Automated Installation Kit User’s Guide in the Windows AIK 2.0 includes detailed information about each of the tools described in this chapter. n Chapter 6, “Developing Disk Images,” includes more information about using MDT 2010 to create deployment shares, create builds, and capture images. n Chapter 9, “Preparing Windows PE,” includes more information about customizing Windows PE for Windows 7 deployment. n Chapter 10, “Configuring Windows Deployment Services,” includes more information about installing, configuring, and using Windows Deployment Services to deploy Windows 7. n Chapter 12, “Deploying with Microsoft Deployment Toolkit,” includes more information about using the Microsoft Deployment Toolkit to deploy Windows 7 images. n http://technet.microsoft.com/en-us/desktopdeployment/default.aspx contains the latest information about using the Microsoft Deployment Toolkit to deploy Windows 7. n Deployment Forum at http://www.deploymentforum.com/ is a member-driven commu- nity for IT professionals deploying Windows 7. n Download the Windows Automated Installation Kit 2.0 (Windows AIK 2.0) and the Microsoft Deployment Toolkit 2010 (MDT 2010) from the Microsoft Download Center at http://www.microsoft.com/downloads. On the Companion Media n Taskseq.wsf n Sample_Task_Sequences.zip Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. 113 CHAPTER 4 Planning Deployment n Using the Microsoft Deployment Toolkit 113 n Planning High-Volume Deployment 116 n Planning Low-Volume Deployment 122 n Windows 7 Requirements 125 n Preparing for Development 127 n Installing the Microsoft Deployment Toolkit 133 n Starting Deployment Workbench 135 n Updating Microsoft Deployment Toolkit Components 135 n Summary 137 n Additional Resources 137 T his chapter helps you plan the deployment of the Windows 7 operating system in your organization. Deploying an operating system requires careful planning. Ap- plication compatibility, user state migration, automation, and other issues complicate the process—making deployment more than just installing a new operating system on a handful of desktop computers. This chapter helps you use the best planning tools avail- able and discover issues that require planning so that you can make informed decisions early in the process. Using the Microsoft Deployment Toolkit Microsoft Development Toolkit 2010 (MDT 2010) is Microsoft’s best solution for high- volume Windows 7 deployment projects. It reduces complexity and increases standard- ization by allowing you to deploy a hardware and software baseline to all users and computers. With standard baselines, you can manage the computing environment more easily, spend less time managing and deploying computers, and spend more time on mission-critical tasks. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. [...]... means you can install Windows 7 on a computer running Windows Vista with SP1 and retain your applications, files, and settings Using Windows Easy Transfer or the USMT to migrate user states from Windows XP to Windows 7 is also supported Table 4-2  Windows 7 Migration Paths From Upgrade to Windows 7? Migrate to Windows 7 Using Windows Easy Transfer? Migrate to Windows 7 Using the USMT? Windows XP with SP2... users and modify the deployment plan as appropriate Windows 7 Requirements To plan deployment, you must understand the deployment requirements for Windows 7 The following sections describe the minimum hardware requirements and the migration paths for Windows 7 For more information about Windows 7 hardware requirements and editions, see Chapter 1 Windows 7 Requirements  Chapter 4 Please purchase PDF Split-Merge... desktop deployment of Windows 7 The three major areas of your computing environment to assess include your hardware, software, and network n Hardware  Do your desktop and laptop computers meet the minimum hardware requirements for Windows 7? In addition to meeting these requirements, all hardware must be compatible with Windows 7 For more information, see Chapter 1, “Overview of Windows 7 Improvements.”... graphics processor with Windows Display Driver Model (WDDM) 1.0 or later driver Free Hard Disk Drive Space 16 GB Note  The minimum requirements for Windows 7 are the same across all editions Upgrade Paths Table 4-2 describes the Windows 7 upgrade and migration paths As shown in the table, performing an in-place upgrade from Windows Vista with Service Pack 1 (SP1) or later to Windows 7 is supported This... and manage clients For more information about Windows 7 management features, see Part III of this book, “Desktop Management.” n Networking  You can configure computers that run Windows 7 to participate in a variety of network environments For more information about Windows 7 networking features, see Part V of this book, “Networking.” n Security  Windows 7 includes features to help you secure your network... must install additional prerequisite software Windows Server 2008, Windows Server 2008 R2, and Windows 7 already contain this software The following list describes software that you must install before installing and using MDT 2010 on Windows Server 2003 SP1 (Windows Server 2003 SP2 requires only Microsoft NET Framework 2.0): n Windows PowerShell  Download Windows PowerShell from the Microsoft Download... download and install it The Windows AIK distribution media includes the MSXML Services 6.0 SP1 installation file You can also download MSXML Services 6.0 SP1 from http://www.microsoft.com/downloads/details.aspx?FamilyID=d21c292c368b-4ce1-9dab-3e9827b70604&displaylang=en Download both x86 and x64 versions at this location Windows Vista with SP1, Windows 7, Windows Server 2008, and Windows Server 2008 R2... building a custom Windows 7 image is as simple as installing the operating system from a deployment share by using the Windows Deployment Wizard This is an LTI Installation process that requires minimal user interaction; it automatically captures a Windows 7 image and stores it back in the deployment share Chapter 6, “Developing Disk Images,” describes how to use MDT 2010 to build custom Windows 7 images In... executables, however Chapter 7, “Migrating User State Data,” describes where to place these files Installing the Microsoft Deployment Toolkit MDT 2010 requires Windows PowerShell 2.0 If you’re installing MDT 2010 on Windows Server 2008 or Windows Server 2008 R2, you must also add the Windows PowerShell feature by using the Add Features Wizard If you’re installing MDT 2010 on Microsoft Windows Server 2003 SP1,... secure your network and computers by controlling authentication and access to resources and by encrypting data stored on computers These features include BitLocker Drive Encryption, Windows Firewall with Advanced Security, and so on For more information about Windows 7 security features, see Chapter 2, “Security in Windows 7. ” Testing and Piloting Before rolling out your deployment project, you need . DVD, a UFD, or Windows Deployment Services. n Destination Computers On the destination computers, run Windows Setup to install Windows 7. Windows Setup. use MDT 2010 to deploy Windows 7 instead of using the basic deployment tools directly. All the deployment tools in Windows 7 and the Windows AIK 2.0 are huge