Adding Custom Migration Files
MDT 2010 will use only the MigApp .xml and MigDocs.xml files unless you indicate the path to your custom .xml files . As with other properties in MDT 2010, you can configure them in each deployment point's CustomSettings .ini file or add them to the MDT 2010 database. Set the property USMTMigFiles to the name of each custom migration .xml file. If you don't configure this property, MDT 2010 uses the default migration files MigApp .xml and MigDocs .xml. If you do configure this option, MDT 2010...
Migration Files
Both ScanState and LoadState use three migration xml files to control migrations In addition to these three files, you can specify one or more custom xml files to migrate custom applications or customize the standard migrations. The following section, Developing Migration Files, describes the .xml files that come with USMT and how to build custom migration files. USMT ships with three standard migration xml files You can customize these files to control the behavior of USMT during migration In...
Importing Install Images
Windows 7 includes an installation image on the media. The installation image Install.wim can include multiple editions of Windows 7. You can import one or more of these editions into Windows Deployment Services for deployment over the network. ON THE COMPANION MEDIA This book's companion media includes a sample script, VRKAddlnstalllmage.vbs, that demonstrates how to script the addition of installation images to Windows Deployment Services. A similar script, VRKListlmages.vbs, demonstrates how...
Adding Packages
Packages include operating system updates and language packs The Windows Deployment Wizard can automatically install operating system updates during deployment. Users can also choose which language packs to install during LTI deployment. The following sections include more information about updates and languages. To add a package to the deployment share, perform the following steps 1. In Deployment Workbench, right-click the Packages folder or a subfolder you created under this folder in your...
New Features of Windows PE
The following features are changes to Windows PE 3. 0 since Windows PE 2 .1, the version that shipped with Windows Vista Deployment Image Servicing and Management DISM DISM is a new command-line tool that you can use to customize a Windows PE 3 . 0 image offline. DISM replaces Pkgmgr. exe, Intlcfg. exe, and PEImg. exe. Smaller default size Windows PE version 2 1 contains staged optional features that add additional size and required additional effort to remove The Windows PE 3 . 0 default image...
Installing USMT
USMT 4 . 0 is included in the Windows Automated Installation Kit 2 . 0 Windows AIK 2 . 0 . You can download the Windows AIK from the Microsoft Download Center at http www.microsoft.com downloads. After downloading and installing the Windows AIK, the USMT source files are in C Program Files Windows AIK Tools USMT Platform, where Platform is either amd64 or x86 . You can stage USMT directly on each client computer or on a network share. If you're using MDT 2010, it can install USMT in deployment...
Other Tools
Windows 7 and the Windows AIK 2 . 0 also provide various command-line tools that are useful during deployment BCDboot BCDboot can set up a system partition or repair the boot environment on a system partition quickly. It copies a small set of boot environment files from the installed Windows 7 image to the system partition. It also creates a boot configuration data BCD store on the system partition, which includes a new boot entry that enables the Windows image to boot . Bootsect Bootsect exe...
Replicating a Deployment Share
For LTI, you need to replicate the deployment share in the production environment or copy it to removable media. This process enables you to develop in a controlled environment and then easily move the deployment share into the production environment when you're ready to deploy Windows 7. MDT 2010 provides both capabilities . When you replicate a deployment share, you can replicate everything or you can choose which folders in the deployment share to replicate. You choose folders to replicate...
Deploying Migration Files
The following list describes how to deploy custom migration xml files for stand-alone use, with MDT 2010, and with Configuration Manager Stand-alone use You can store the migration .xml files in the USMT program folder or place them in a central location. You must specify the full path to each migration Microsoft Deployment Toolkit MDT 2010 has a specific organization for deployment shares . You must store custom migration .xml files in the USMT platform folder of the deployment share, where...
Configuring the Database Access
After you have configured the property values in the MDT 2010 database, you need to configure CustomSettings . ini to perform the appropriate database queries . You can do this easily by using the Configure DB Wizard in Deployment Workbench. Run the Configure DB Wizard for each deployment share defined in Deployment Workbench with which you want to use the database . To configure CustomSettings .ini for database queries, perform the following steps 1. In the Deployment Workbench console tree,...
Adding Applications 1
When you add an application to a deployment share, you're simply describing for MDT 2010 how to install the application by using the command line and optionally copying the application source files to the deployment share. If you don't copy the application source files to the deployment share, MDT 2010 installs the application from the source location you specify, such as a network share. To add an application to a deployment share, perform the following steps 1. In the Deployment Workbench...
User State Migration Tool
Use USMT to migrate user state in high-volume deployment projects . It can execute complex, repeatable migrations of user state data between operating systems. You can script USMT you can execute it as part of an MDT 2010 Lite Touch Installation LTI or Zero Touch Installation ZTI or you can execute it directly at the command prompt. In addition to document and settings migration, USMT can migrate application preferences for Microsoft Office applications between versions of Office . For example,...
Scope and Objectives
The scope is the baseline for creating a specification for your deployment project . The scope of your deployment project is defined largely by your answers to the following questions What business needs do you want to address with Windows 7 What are the long-term goals for the deployment project How will your Windows 7 client computers interact with your IT infrastructure What parts of your IT infrastructure will the project touch, and how will this happen The scope is simply a statement of...
Managing Driver Groups and Driver Packages
You can use Windows Deployment Services in Windows Server 2008 R2 to manage driver groups . For example, you can Enable or disable a driver group . Duplicate a driver group . This creates a new group with the same driver packages and filters. It doesn't make any copies of the files, but just references them again. Modify the filters for a driver group. Configure the applicability of a driver group . You can also use Windows Deployment Services in Windows Server 2008 R2 to manage driver packages...
Program Compatibility Troubleshooter
The Program Compatibility troubleshooter can help resolve many application issues . Using the troubleshooter, you can test various compatibility options on various programs to find the setting that allows the programs to run under Windows 7 To start the Program Compat ibility troubleshooter, click Start, Control Panel, Programs, and then Run Programs Made For Previous Versions Of Windows The Program Compatibility troubleshooter starts as shown in Figure 5-2 . To begin the application...
Performing LTI Deployments
To deploy a computer using LTI, start the destination computer by running LiteTouch.vbs from the deployment share or by using the Windows PE boot image generated by updating the deployment share . Start the Windows PE boot image in any of three ways Burn the .iso images to a DVD . This process is slow and tedious. These ISO image files reside in the Boot folder of the deployment share . Copy the contents of the Windows PE boot image to a bootable USB Flash drive UFD . This is far more...
Building a Test Lab
Your test environment should be a long-term investment in the overall deployment process Retain the test environment after the deployment to assist in future deployment projects. To create the test environment, you must determine how to model the production environment in the test environment and configure the test environment to support automated testing of the mitigation strategies Microsoft recommends that you establish a dedicated and isolated lab environment for use in developing and...
Understanding USMT Components
After downloading and installing the Windows AIK, the USMT source files are in C Program Files Windows AIK Tools USMT Platform, where Platform is either amd64 or x86 . The installer copies many files into this folder, including . dll files, feature manifests, and other application initialization files. See Figure 7-3 . Most of the files support the two main executables Scanstate. exe and Loadstate. exe . Use to load a subset of original configuration In addition to ScanState and LoadState, USMT...
Setting the Deployment Status
You can set your organization's deployment status for each application, application installation report, Web site, and Windows update . Setting your deployment status enables you to determine where each item is in your testing process . Additionally, setting your deployment status enables you to organize your data better, for both a more customized ACT compatibility report and for filtering purposes. Your deployment status choices include the following Not Reviewed Your organization has not yet...
Selecting a Grouping Method
You can use different methods to group client computers . After you determine how you want to group computers, select the appropriate properties. Using the processing rules in MDT 2010, you can group computers based on any property that might be applied to a group of computers such as Make, Model, DefaultGateway, and so on . Table 12-2 lists methods of grouping computers, descriptions of the methods, and the properties that you can use to group the computers . TABLE 12-2 Grouping Methods...
Repackaging Tools
You must use tools that are not included with Windows Installer to create Windows Installer packages . The following list includes some of the variety of tools available AdminStudio Available in multiple versions, including a free download, AdminStudio is a powerful and flexible repackaging tool. The following versions are available AdminStudio Configuration Manager Edition This free download from Microsoft integrates with System Center Configuration Manager 2007 to simplify repackaging....
Refresh Computer Scenario
The Refresh Computer scenario is similar to the New Computer scenario The differences are that the destination computer contains a Windows operating system, and this scenario preserves users' existing files and settings, as shown in Figure 3-3 . FIGURE 3-3 Preserving user state during migration FIGURE 3-3 Preserving user state during migration You can use migration technologies, such as USMT 4 . 0, to migrate users' files and settings from the previous version of Windows to Windows 7. This...
Hybrid Images
Hybrid images mix thin- and thick-image strategies . In a hybrid image, you configure the disk image to install applications on first run, giving the illusion of a thick image but installing the applications from a network source . Hybrid images have most of the advantages of thin images . However, they aren't as complex to develop and do not require a software distribution infrastructure . They do require longer installation times, however, which can raise initial deployment costs. An...
KMS activation Thresholds
KMS can activate both physical computers and virtual machines VMs To qualify for KMS activation, a network must have a minimum number of qualifying computers, called the activation threshold. KMS hosts activate clients only after meeting this threshold. To ensure that the activation threshold is met, a KMS host counts the number of computers requesting activation on the network. The Windows Server operating systems starting with Windows Server 2008 and Windows client operating systems starting...
Creating Bootable Media
Many Windows maintenance and troubleshooting utilities can make use of Windows PE, including utilities created for managing disks and recovering systems Windows RE is one example of a recovery tool that uses Windows PE. Many other utilities created by third-party manufacturers also use Windows PE This section covers the creation of bootable Windows PE media based on CDs, DVDs, UFDs, and hard disks You can use all of these technologies for Windows 7 deployment, creating an array of possible...
Operating Modes
To provide a clear path between legacy RIS functionality and Windows Deployment Services functionality, Windows Deployment Services supports three modes legacy and mixed modes are available only in Windows Server 2003 legacy mode This mode uses the Client Installation Wizard OSChooser and Riprep sector-based images . This mode is compatible with RIS . Moving from RIS-only functionality to legacy mode happens when you install the Windows Deployment Services update on a server running RIS Mixed...
Choosing a Version of Windows Deployment Services
Windows Deployment Services is included as an installable server role in Windows Server 2008 and Windows Server 2008 R2 . Windows Deployment Services is also available as a separate update for Windows Server 2003 SP1 . This update is included in Windows Server 2003 SP2 . The version of Windows Deployment Services that you use in your environment will depend upon your business needs, budget, and existing network infrastructure . The Windows operating systems that can be deployed vary with the...
Migrating User State Data
Evaluating Migration Technologies 224 Using Windows Easy Transfer 226 Planning User State Migration Using USMT 230 Understanding USMT Components 238 Developing Migration Files 240 Using USMT in Microsoft Deployment Toolkit 242 Operating system deployment always involves user state migration the process of migrating users' documents and settings from one operating system to another. Even when you don't migrate user state during deployment, users will spend countless hours trying to restore...
Customizing USMT
You manage USMT through command-line options and the migration .xml files . You could modify the default files to control some aspects of the migration, but this is not recommended The better option is to create custom xml files to migrate specific application settings and data. The following list describes customization points for USMT Command-Line Control You can use command-line options, such as ui and ue, to include and exclude specific users during the migration process You can also...
Adding Packages 1
The next step is to add the packages that you require. You add packages by using the DISM Add-Package option. Additionally, for every feature you want to add to Windows PE, you must add a language-neutral package and a language-specific package. In a default installation of the Windows AIK, you find the language-neutral packages in the folder C Program Files Windows AIK Tools PETools x86 WinPE_FPs and the language-specific packages in C Program Files Windows where language is the language...
Creating the MDT Database
Before configuring the database, you must create it in SQL Server. Deployment Workbench creates this database automatically by using the New DB Wizard. Of course, this section assumes that SQL Server is already installed and configured locally or remotely in your environment and that you have permission to create databases . To create the MDT 2010 database in SQL Server, perform the following steps 1. In Deployment Workbench, right-click Database and then click New Database. Database is located...
The Repackaging Process
Windows Installer provides no functionality for repackaging applications . However, numerous vendors sell repackaging products for Windows Installer. See the next section, Repackaging Tools, for a list of vendors . Repackaging is not new. Organizations have historically repackaged applications to customize their installation and configuration . However, Windows Installer transforms eliminate the need to repackage Windows Installer-based applications just to customize them. In fact, repackaging...
Preinstallation Phase
During the Preinstallation phase, Windows Setup loads and prepares the target system for installation . Figure 3-5 illustrates where this phase fits in the installation process. Tasks performed during the Preinstallation phase include Windows Setup configuration Windows Setup is configured by using either the Windows Setup dialog boxes interactive or an answer file unattended . Windows Setup configurations include configuring a disk or language settings . Windows PE configuration Answer file...
preparing Windows pE
Setting Up the Environment 279 Working with Windows PE 281 Using Windows PE with Microsoft Deployment Toolkit 291 Half the job of installing the Windows 7 operating system or building disk images is starting the computer and preparing for installation. You use Windows Preinstallation Environment Windows PE 3 .0 to start computers, which is similar to using MS-DOS in the old days . Windows PE allows you to fully automate the preparation and installation process . This chapter describes how to...
Replace Computer Scenario
Windows migration technologies such as the Windows Easy Transfer tool and USMT 4 . 0 allow side-by-side data migration between an old computer running Windows XP or Windows Vista and a new computer running Windows 7. This scenario, which is called Replace Computer, allows you to perform a clean installation on the new computer and simply migrate files and settings from the old one . Figure 3-4 shows an overview of this scenario . FIGURE 3-4 Side-by-side upgrades begin with a clean, new system ....
Adding OutofBox Drivers
Depending on the type of computer in the environment and the hardware it contains, you require software from the hardware vendors to make computers in the production environment fully functional. Some of this software may be provided on a CD-ROM or DVD-ROM by the hardware manufacturer other software must be downloaded from the vendor's Web site . Deployment Workbench makes adding device drivers to the deployment share an easy process . You simply specify a folder containing one or more device...
Updating Microsoft Deployment Toolkit Components
After installing MDT 2010 and becoming familiar with Deployment Workbench, download and install the additional components that MDT 2010 requires. The following components are mandatory in MDT 2010 Windows AIK 2.0 You can install Windows AIK 2 . 0 manually by downloading it from the Microsoft Download Center at http www.microsoft.com downloads or use Deployment Workbench to download and install it automatically. Updating Microsoft Deployment Toolkit Components CHAPTER 4 135 MSXML Services 6.0...
Adding Applications
You must add each application to the deployment share that you intend to deploy by using MDT 2010. Deployment Workbench gives you the option to copy the application source files directly into the deployment share or to just add a reference to the application source files to the deployment share and leave them in their original location. Generally, if the network location containing the application source files will not be available during deployment, you should copy the application source files...
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 information, direct use of these tools isn't recommended. Using a framework like MDT 2010 is the best way to deploy Windows 7. Windows SIM Windows PE Windows Vista Device Drivers Applications Packages The following list describes the steps in Figure 3-8 Technician Computer You build a distribution share on a technician...
Windows Deployment Services
Windows Deployment Services is the updated and redesigned version of Remote Installation Services RIS in Windows Server 2008. Windows Deployment Services helps organizations rapidly deploy Windows operating systems, particularly Windows 7. Using Windows Deployment Services, you can deploy Windows operating systems over a network without having to be physically present at the destination computer and without using the media. Windows Deployment Services delivers a better in-box deployment...
Capabilities
Windows PE is a bootable image that you can start by using removable media CD, DVD, or UFD . You can also use Windows Deployment Services to start Windows PE . Because the Windows 7 deployment tools do not work in 16-bit environments, Windows PE replaces the MS-DOS-bootable disk in all deployment scenarios . It's a lightweight 32-bit or 64-bit environment that supports the same set of networking and mass-storage device drivers that Windows 7 supports, and it provides access to similar features,...
Volume Licensing
Volume Licensing offers customized programs tailored to the size and purchasing preference of the organization . These programs provide simple, flexible, and affordable solutions that enable organizations to manage their licenses . To become a Volume Licensing customer, an organization needs to set up a Volume License agreement with Microsoft . There are only two legal ways to acquire a full Windows desktop license for a new computer system. The first and most economical way is preinstalled...
Infrastructure Remediation
Understanding the network environment is critical with any project that introduces changes. To plan and prepare to incorporate these changes, first understand the current status of the organization's environment, identify other sources of change that may affect this project, perform a risk-mitigation approach to the changes, and then incorporate the proposed changes . Organizations can solve and possibly avoid most networking problems by creating and maintaining adequate network documentation...
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. Michael Niehaus, Systems Design Engineer The basic process used to install Windows XP has been unchanged since the earliest days of Microsoft Windows NT. This...
Specifying the Data Store Location
Performing hard-link migrations is the recommended action in Refresh Computer scenarios, and this is the default behavior of MDT 2010. For other scenarios, you can create the data stores within the MDT 2010 deployment share. However, creating a share for the data stores on a separate server is better than putting the data stores in the deployment share because it spreads the load and allows you to dedicate resources to user state migration more easily. After creating the share for the data...
Updating the Deployment Share
The Windows AIK 2 . 0 comes with Windows PE 3 .0, so no additional files are necessary to create Windows PE boot images for MDT 2010. When you update your deployment share in the Deployment Workbench, MDT 2010 automatically generates the following custom Windows PE images here platform is x86 or x64 Lite Touch Windows PE platform .wim file If you want, you can configure the deployment share to also generate the following Windows PE images Generic Windows PE platform You don't need to manually...
Deploying Driver Packages to Clients
You can use Windows Deployment Services in Windows Server 2008 R2 to deploy driver packages to client computers using the following methods Method 1 Make all driver packages available to all clients. This is the simplest approach, and each type of client will use Plug and Play to install the driver package it needs . This method assumes that the devices that need the driver packages are connected to or attached to the clients before you deploy Windows to them. However, this method can cause...
Configuring the Options Tab
Groups and tasks have the following settings on the Options tab shown in Figure 6-5 Disable This Step Select the Disable This Step check box to disable the step or group, including all groups and steps that it contains. Success Codes steps only List the return codes that indicate successful completion . The Windows Deployment Wizard determines whether a step completed successfully by comparing its return code to each code in the Success Codes box. If it finds a match, the step completed...
Online Configuration Phase
During the Online Configuration phase, Windows 7 performs customization tasks related to the computer's identity. Figure 3-6 shows where this phase fits into the overall process . 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...
Volume Activation Scenarios
Each Volume Activation method is best suited to a particular network configuration To select the best activation method or methods for the organization, assess the network environment to identify how different groups of computers connect to the network Connectivity to the corporate network, Internet access, and the number of computers that regularly connect to the corporate network are some of the important characteristics to identify Most medium-sized to large organizations use a combination...