Microsoft Deployment

Quick Start Guide

Published: November 2007

For the latest information, please see microsoft.com/technet/SolutionAccelerators
The information in this document and any document referenced herein is provided for informational purposes
only, is provided AS IS AND WITH ALL FAULTS and cannot be understood as substituting for customized service
and information that might be developed by Microsoft Corporation for a particular user based upon that user’s
particular environment. RELIANCE UPON THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN IS AT
THE USER’S OWN RISK.

© 2007 Microsoft Corporation. All rights reserved.

If the user of this work is using the work SOLELY FOR NON-COMMERCIAL PURPOSES INTERNALLY WITHIN A
COMPANY OR ORGANIZATION, then this work is licensed under the Creative Commons Attribution-
NonCommercial License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/2.5 or
send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.

MICROSOFT CORPORATION PROVIDES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE

INFORMATION CONTAINED IN THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN. Microsoft
Corporation provides no warranty and makes no representation that the information provided in this document
or any document referenced herein is suitable or appropriate for any situation, and Microsoft Corporation
cannot be held liable for any claim or damage of any kind that users of this document or any document
referenced herein may suffer. Your retention of and/or use of this document and/or any document referenced
herein constitutes your acceptance of these terms and conditions. If you do not accept these terms and
conditions, Microsoft Corporation does not provide you with any right to use any part of this document or any
document referenced herein.

Complying with the applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise), or for
any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights or other intellectual property rights
covering subject matter within this document. Except as provided in any separate written license agreement
from Microsoft, the furnishing of this document does not give you, the user, any license to these patents,
trademarks, copyrights or other intellectual property.

Information in this document, including URL and other Internet Web site references, is subject to change
without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-
mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real
company, organization, product, domain name, e-mail address, logo, person, place or event is intended or
should be inferred.

Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective
owners.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Contents

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Overview
Microsoft® Deployment Solution Accelerator provides technology for deploying
Windows® operating systems, the 2007 Microsoft Office system, and Microsoft
Office 2003. Microsoft Deployment is the next version of Business Desktop Deployment
(BDD) 2007. However, the larger focus of Microsoft Deployment is on methodology and
best practices. By following the guidance in Microsoft Deployment, teams are putting into
action proven best practices that Microsoft uses in its own development projects and that
are based on the Microsoft Solutions Framework (MSF). Figure 1 shows the top-level
organization of the Microsoft Deployment documentation, which describes these
methodologies and best practices.

Figure 1. Microsoft Deployment documentation

Microsoft Deployment includes a great deal of documentation—more than 1,000 pages.
Many IT pros try to plow through all of this documentation just to determine whether they
want to use Microsoft Deployment in their deployment project. Although team members
should thoroughly read all the documentation before using Microsoft Deployment in a
production deployment, sometimes, they just want to evaluate or learn about it. This
quick-start guide helps team members quickly evaluate Microsoft Deployment by
providing condensed, step-by-step instructions for using Microsoft Deployment to install
Windows operating systems.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

2 Microsoft Deployment

Note In this document, Windows applies to the Windows Vista®, Windows XP Professional,
Windows XP Tablet PC Edition, Windows Server® 2008, and Windows Server 2003 operating
systems unless otherwise noted.

Team members use one of three processes to install an operating system:

• Zero Touch Installation (ZTI) deployment for Microsoft System Center
Configuration Manager 2007. If the organization has an existing System Center
Configuration Manager infrastructure, teams can use that infrastructure to capture the
reference operating system image and efficiently deploy it to client computers. This
process is described in the section, “Quick Start for ZTI Deployments with System
Center Configuration Manager,” later in this guide.
• ZTI deployment for Microsoft Systems Management Server (SMS) 2003. If the
organization has an existing Systems Management Server 2003 infrastructure, use
ZTI deployment to capture the reference operating system image, and then deploy it
using Systems Management Server 2003. This process is described in the section,
“Quick Start for ZTI Deployments with Systems Management Server 2003,” later in
this guide.
• Lite Touch Installation (LTI) deployment. If the organization does not have a
System Center Configuration Manager or Systems Management Server 2003
infrastructure, teams can use the LTI process to capture reference operating system
images, and then deploy them across the network. This process is described in the
section, “Quick Start for LTI Deployments,” in this guide.
Note Because of the increased complexity of using ZTI deployments with Systems Management
Server 2003 or System Center Configuration Manager, only summary information is provided for
ZTI deployments in this guide.

After using this guide to evaluate Microsoft Deployment, team members can delve into
the rest of the guidance to learn more about the advanced features of Microsoft
Deployment.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start for LTI Deployments
To follow this guidance, the following elements are required:
• A lab environment. Any two networked computers are required. Although teams can
use physical computers, using virtual machines (VMs) is easier. This guide uses
Microsoft Virtual Server 2005 R2 with Service Pack 1 (SP1). Teams can also use
Microsoft Virtual PC 2007 to follow this guide’s instructions.
• Windows Server 2003, the Microsoft .NET Framework version 2.0, and
Microsoft Management Console (MMC) version 3.0 installed on one of the lab
computers. Install Microsoft Deployment on this computer and create a basic
Windows Vista build on it. This guide refers to this computer as the build server.
Download and install the Microsoft .NET Framework version 2.0 and MMC
version 3.0 by using Windows Update under the Software, Optional update type.
MMC version 3.0 is included with Windows Server 2003 Release Candidate (RC) 2.
• Windows Vista installation media. To follow this guide, Windows Vista is required.
Teams can use any edition of Windows Vista to evaluate Microsoft Deployment.
This guide describes two VMs. The first functions as the domain controller domain and
the distribution server. The second VM functions as the destination computer with an
unformatted hard disk. Also, the administrator account is Administrator, and the password
is a complex password that team members create. Both VMs have 16 gigabyte (GB) hard
disks.
Note This guide assumes that teams are evaluating Microsoft Deployment on x86 VMs or
physical computers. If evaluating Microsoft Deployment on x64 platforms, download and install
the x64 editions of Microsoft Deployment and the components that this guide describes.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Installing Microsoft Deployment
To install Microsoft Deployment, complete the following steps on the build server:
1. Right-click MicrosoftDeploymentToolkit_x86.msi (for 32-bit operating systems) or
MicrosoftDeploymentToolkit_x64.msi (for 64-bit operating systems), and then click
Install.
2. Click Next to skip the welcome page.
3. On the End-User License Agreement page, review the license agreement. If the
terms are agreeable, click I accept the terms in the License Agreement, and then
click Next.
4. On the Custom Setup page, click Next to install the typical features in their default
location at C:\Program Files\Microsoft Deployment Toolkit\:
• Documents. This feature installs Microsoft Deployment guidance and job aids.
• Tools and templates. This feature installs the solution accelerator’s wizards and
template deployment files, such as Unattend.xml.
5. Click Install to install the solution accelerator; then, click Finish to complete the
installation.

Start Deployment Workbench

To use Deployment Workbench for tasks other than reviewing the documentation, log on
to the computer using an account that is a member of the local Administrators group. To
start Deployment Workbench, which is shown in Figure 2, click Start, point to All
Programs, point to Microsoft Deployment Toolkit, and then click Deployment
Workbench. The console tree shows the following items:
• Information Center. This item provides access to the documentation, breaking news
about Microsoft Deployment, and the components required for using Deployment
Workbench.
• Distribution Share. Under this item are the operating systems, applications,
operating system packages, and out-of-box (OOB) drivers that the distribution share
contains. They are source files that Microsoft Deployment uses to install and
configure operating systems.
• Task Sequences. Under this item are installation task sequences, which describe
how to install and configure an operating system.
• Deploy. The Deploy item contains two items beneath it: Deployment Points and
Database. Deployment points provide access to source files and describe how to
install them. Use the database to define settings for individual computers,
geographies, and so on.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start Guide: Installing Microsoft Deployment 5

Figure 2. Deployment Workbench

Install Additional Components

Microsoft Deployment makes it simple to download and install the required components.
The most notable component is the Windows Automated Installation Kit (Windows AIK).
The following steps describe how to download and install the Windows AIK by using the
Components node of Deployment Workbench:
1. In Deployment Workbench, expand Information Center, and then click
Components.
2. In the Available for Download section of the details pane, click Windows
Automated Installation Kit (x86) (for 32-bit operating systems) or Windows
Automated Installation Kit (x64) (for 64-bit operating systems); then, click
Download.
After downloading the Windows AIK, Deployment Workbench copies the files
Msxml6.msi, Waikx86.msi, and Winpe.cab to C:\Program Files\Microsoft Deployment
Toolkit\WAIK.
3. In the Downloaded section of the details pane, click MSXML 6.0, and then click
Browse. In the explorer window that opens, double-click Msxml6.msi, and follow the
prompts to install the Windows AIK.
4. In the Downloaded section of the details pane, click Windows Automated
Installation Kit (x86) (for 32-bit operating systems) or Windows Automated
Installation Kit (x64) (for 64-bit operating systems), and then click Install to install
the Windows AIK. Follow the instructions in the Windows AIK installer to complete
the installation.
Team members can download and install other components on the Components node of
Deployment Workbench. Examples include the Windows User State Migration Tool
(USMT) and the Application Compatibility Toolkit (ACT).

Solution Accelerators microsoft.com/technet/SolutionAccelerators

6 Microsoft Deployment

Populate the Distribution Share

Using Deployment Workbench, team members can populate the distribution share with
the following source files, which are combined during installation to install and configure
operating systems on destination computers:
• Operating systems
• Applications
• Operating system packages, including updates and language packs
• OOB device drivers
When adding operating systems, applications, operating system packages, and OOB
device drivers to the distribution share, team members are simply storing the source
files in the distribution share folder specified during Microsoft Deployment installation
(C:\Distribution). Team members will associate them with task sequences later in the
configuration process.
First, create the distribution share by completing the following steps:
1. In the Deployment Workbench console tree, right-click Distribution Share, and then
click Create distribution share directory to start the Create Distribution Share
Wizard.
2. On the Specify Directory page, accept the default location of C:\Distribution, and
then click Finish.
Note The folder location for the distribution share should have sufficient available space to
contain all the components for operating system deployment, such as multiple operating
system source files, application source files, captured Windows Imaging Format (WIM)
images, and deployment scripts and tools.

This guide describes how to install a basic Windows Vista build, so Windows Vista is the
only source that team members must add to the distribution share for LTI deployments.
To populate the distribution share for installing a basic Windows Vista build, complete the
following steps:
1. In the Deployment Workbench console tree, expand Distribution Share, right-click
Operating Systems, and then click New to start the New OS Wizard.
2. On the OS Type page, click Full set of source files, and then click Next.
3. On the Source page, type the path containing the Windows Vista source files to be
added to the distribution share, and then click Next.
4. On the Destination page, click Finish.
This copy process can take several minutes to finish.
5. When copying is complete, click the Operating Systems node to view the list of
operating systems. (It can take several seconds to appear.)
After adding Windows Vista to the distribution share, the operating system appears in the
details pane of Operating Systems. Also, the operating system appears in the distribution
share in Operating Systems\subfolder, where subfolder is the destination specified when
adding the operating system.

Create a Task Sequence

With Windows Vista added to the distribution share, team members are ready to create a
task sequence that describes how to install and configure the operating system. For this
guide, create a basic, default task sequence.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start Guide: Installing Microsoft Deployment 7

To create a default task sequence

1. In the Deployment Workbench console tree, right-click Task Sequences, and then
click New to start the New Task Sequence Wizard.
2. On the General Settings page, provide the following information, and then click
Next:
• Task sequence ID. Type LAB01.
• Task sequence name. Type Windows Vista.
• Task sequence comments. Type Installs a default Windows Vista
configuration.
3. On the Select Template page, click Standard Client Task Sequence, and then click
Next.
Note If deploying Windows Server 2008, choose Standard Server Task Sequence,
instead.

4. On the Select OS page (shown in Figure 3), select a Windows Vista image to use,
and then click Next.
Note Windows Vista was added to the distribution share in the previous section. If
deploying a Windows Server 2008 image, each Windows Server 2008 edition would be listed.

Figure 3. New Task Sequence Wizard

5. On the Specify Product Key page, click Do not specify a product key at this time,
and then click Next.
Note If a team member were installing a retail version of Windows (such as Windows Vista
Ultimate), the team member would need to specify a product key at this step.

6. On the OS Settings page, provide the following information, and then click Next:
• Full Name. Type Valued Woodgrove Bank Employee.
• Organization. Type Woodgrove Bank.
Solution Accelerators microsoft.com/technet/SolutionAccelerators
8 Microsoft Deployment

• Internet Explorer Home Page. Type http://www.woodgrovebank.com/.

7. On the Admin Password page, click Use the specified local Administrator
password, type the password selected in the space provided, and then click Finish.
After adding a task sequence to the distribution share, the task sequence appears in the
Task Sequences details pane. It also appears in the distribution share in
Control\subfolder, where subfolder is the task sequence ID.

Create a Lab Deployment Point

In Microsoft Deployment, deployment points describe how to access source files and how
to install them using a task sequence. Microsoft Deployment supports different types of
deployment points:
• Lab or single-server deployment. Deploy source files from the distribution share
created on the build server.
• Separate deployment share. Create another distribution share on the build server
or another network-accessible computer. The new distribution share will contain a
subset of the files contained in the local distribution share.
• Removable media. Create a DVD International Organization for Standardization
(ISO) image to deploy source files. This type of deployment point is useful for
deploying source files to mobile users and branch offices.
• SMS 2003 OSD Feature Pack. Create a directory containing all the files required to
customize an SMS 2003 Operating System Deployment (OSD) Feature Pack
program. For more information about using Microsoft Deployment with the SMS 2003
OSD Feature Pack, see the Microsoft Deployment document, Preparing for Microsoft
Systems Management Server 2003.
Always create a lab deployment point in Deployment Workbench. This guide uses a lab
deployment point to install a basic, default Windows Vista build.
To create the lab deployment point
1. In the Deployment Workbench console tree, expand Deploy, right-click Deployment
Points, and then click New to start the New Deployment Point Wizard.
2. On the Choose Type page, click Lab or single-server deployment, and then click
Next.
3. On the Specify Deployment Point Name page, click Next to accept the default
name, LAB.
4. On the Application List page, click Next.
5. On the Allow Image Capture page, click Next.
6. On the Allow Admin Password page, click Next.
7. On the Allow Product Key page, click Next.
8. On the Network Share page, shown in Figure 4, click Next.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start Guide: Installing Microsoft Deployment 9

Figure 4. New Deployment Point Wizard

9. On the Configure User State page, click Do not save data and settings, and then
click Finish.
After creating a lab deployment point in Deployment Workbench, update it to create
the lab deployment point on the file system. Updating a deployment point creates the
folder structure, Windows Preinstallation Environment (Windows PE) boot images,
and so on.
10. To update a deployment point, click the Deploy\Deployment Points node. Then, in
the Deployment Points details pane, right-click the LAB deployment point, and then
click Update.
11. Use the Windows Vista task sequence to install Windows Vista.
To install Windows Vista on a computer, start a lab computer using the Windows PE
bootable images generated by updating the deployment point in the previous section.
Update the deployment point to generate the Windows PE bootable images.
Start the Windows PE bootable images in one of two ways:
• Burn C:\Distribution\Boot\LiteTouchPE_x86.iso to a CD or DVD. If evaluating
Microsoft Deployment using VMs, simply mount the ISO image to the destination
computer after copying the image file to an accessible location. After burning the
image to a CD or DVD or mounting the image, restart the destination computer.
• Add the C:\Distribution\Boot\LiteTouchPE_x86.wim image file to the Boot
Images item of a Windows Deployment Services server. The .wim files reside in
the \Boot folder of the distribution share. For more information about installing and
configuring Windows Deployment Services, see the Windows Deployment Services
Update Step-by-Step Guide for Windows Server at

Solution Accelerators microsoft.com/technet/SolutionAccelerators

10 Microsoft Deployment

http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-
fc80fc2151301033.mspx. Then, restart the computer using the boot image added to
Windows Deployment Services.
After starting the lab computer using the Windows PE image, complete the following
steps to install Windows Vista using the basic Windows Vista task sequence:
1. In the Welcome to Microsoft Deployment dialog box, click Run the Deployment
Wizard to install a new operating system, and then click Next.
2. In the User Credentials dialog box, type the credentials (user name, domain, and
password) necessary to connect to the distribution share, and then click OK.
3. In the lab environment this guide describes, the user account is Administrator, the
password is the password selected, and the domain is Woodgrove.
The Windows Deployment Wizard starts automatically.
4. On the Select a task sequence to execute on this computer page, click Windows
Vista in the list of available builds, and then click Next.
Note This is the task sequence created in the section, “Create a Task Sequence,” earlier in
this guide.

5. On the Configure the computer name page, accept the default computer name,
and then click Next.
6. On the Join the computer to a domain or workgroup page, click Join a
workgroup. In the Workgroup box, accept the default workgroup name, and then
click Next.
7. On the Specify whether to restore user data page, click Do not restore user data
and settings, and then click Next.
8. On the Locale Selection page, click Next.
9. On the Set the Time Zone page, click Next.
10. On the Specify whether to capture an image page, click Do not capture an image
of this computer, and then click Next.
If a team member clicks Capture an image of this reference computer, Microsoft
Deployment installs the build on the computer, runs the System Preparation Tool
(Sysprep) to prepare it for imaging, and automatically captures and stores the image.
11. On the Ready to begin page, click Begin.
After clicking Begin, Microsoft Deployment begins the task sequence, which installs
Windows Vista. By default, Microsoft Deployment begins by partitioning and formatting
the hard disk. Then, it installs and configures the operating system.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Overview of ZTI Deployments
ZTI requires System Center Configuration Manager or Systems Management
Server 2003 with SP2 and the SMS 2003 OSD Feature Pack. The team deploys
operating systems from System Center Configuration Manager or Systems Management
Server 2003 distribution points. System Center Configuration Manager, Systems
Management Server 2003, or Windows Deployment Services can initiate the installation
process. The ZTI deployment process is typically initiated automatically.
With ZTI, Microsoft Deployment adds features and scenarios to existing Systems
Management Server 2003 or System Center Configuration Manager environments. This
section is meant to be a brief walk-through of the high-level tasks of using ZTI with either
environment.
Note For complete and detailed instructions of ZTI deployments with either Systems
Management Server 2003 or System Center Configuration Manager, see the Microsoft
Deployment documents, Workbench Imaging Guide and either Preparing for Microsoft Systems
Management Server 2003 or Preparing for Microsoft System Center Configuration Manager 2007.

To follow this guidance, a lab environment appropriate to Microsoft Deployment is

required. For ZTI deployments, this lab environment must include all necessary
infrastructure to support either Systems Management Server 2003 or System Center
Configuration Manager. For details of the required environment, see Preparing for
Systems Management Server 2003 and Preparing for Microsoft System Center
Configuration Manager 2007 as well as the Microsoft Deployment document,
Infrastructure Remediation Feature Team Guide.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start for ZTI Deployments with
Systems Management Server 2003
When performing ZTI deployments with Microsoft Deployment and Systems Management
Server 2003, many of the beginning steps are identical to those for LTI deployments.
Therefore, begin this process by following the steps in the section, “Quick Start for LTI
Deployments,” earlier in this guide. For SMS 2003 OSD Feature Pack, do not run
Sysprep or capture the system, because the SMS 2003 OSD Feature Pack capture CD
incorporates those steps. In addition, perform the following steps to complete the
Deployment Workbench configuration for SMS 2003 OSD Feature Pack:
1. Add necessary content to Deployment Workbench as detailed in Workbench Imaging
Guide:
• Add Windows PE 2004 or Windows PE 2005 source media to Deployment
Workbench.
• Add Windows XP with SP2 or Windows Server 2003 with SP1 source media to
Deployment Workbench.
• Create an SMS 2003 OSD Feature Pack deployment point in Deployment
Workbench.
• Update the SMS 2003 OSD Feature Pack deployment point to generate an
updated Windows PE image to use with SMS 2003 OSD Feature Pack (using the
Update option instead of the Update (Files Only) option generates the
Windows PE image) as detailed in the section, “Creating a Customized
Windows PE Image for the SMS 2003 OSD Feature Pack,” in Preparing for
Microsoft Systems Management Server 2003.
2. In SMS Administrator Console, complete the following steps:
a. Update the Windows PE image that SMS 2003 OSD Feature Pack uses with the
updated source in the SMS 2003 OSD Feature Pack deployment point as
detailed in the section, “Import the Customized Version of Windows PE into the
SMS 2003 OSD Feature Pack,” in Preparing for Microsoft Systems Management
Server 2003.
b. Create an SMS 2003 OSD Feature Pack image capture CD ISO image for
Sysprep to use and to capture a master reference image as detailed in the
section, “Create the SMS 2003 OSD Feature Pack Operating System Installation
CD,” in Preparing for Microsoft Systems Management Server 2003.
c. Create an OSD image installation CD ISO image to be used in New Computer
scenarios.
3. Prepare and build a reference image using a LAB deployment point, as detailed in
the section, “Create a Lab Deployment Point,” earlier in this guide. In step 9 of that
section, choose the option to prepare for capture, which completely builds the image
and leaves the system logged on so that the SMS 2003 OSD Feature pack image
capture CD can be used to capture the image into a .wim file.
4. Capture a reference image using the image capture CD, as detailed in the section,
“Capture the Image,” in Workbench Imaging Guide.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start Guide: Installing Microsoft Deployment 13

5. In Deployment Workbench, complete the following steps:

a. Add the image newly that the SMS 2003 OSD Feature Pack captured as a new
custom WIM image using the New Operating System Wizard.
b. Create a new task sequence using the newly captured WIM image as the source
operating system.
c. Change the properties of the OSD deployment point to select this newly created
task sequence.
6. In SMS Administrator Console, complete the following steps:
a. Create a new image package with the captured WIM image as the source
operating system by using the full Universal Naming Convention (UNC) path to
the .wim file in the \\servername\Distribution$ share.
b. Create a new program to deploy the operating system image.
c. Configure each deployment phase of the advanced properties of the new
program to run the ZeroTouchInstallation.vbs script and use the SMS 2003 OSD
Feature Pack deployment point as the source for included files, as detailed in the
section, “Configuring the ZTI Operating System Image,” in Preparing for
Microsoft Systems Management Server 2003.
d. Update the appropriate OSD distribution points with the package and program
details.
e. Create an appropriate collection to target an operating system deployment.
f. Create an advertisement of the program to the appropriate collection.
7. Start one of the computers that belong to the collection and test the operating system
deployment.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start for ZTI Deployments with
System Center Configuration Manager
When performing ZTI deployments with Microsoft Deployment and System Center
Configuration Manager, most of the configuration steps are performed within
Configuration Manager Console instead of within Deployment Workbench. In fact, it is
one of the most important features of Microsoft Deployment to be tightly integrated within
System Center Configuration Manager. The following steps are the minimum to deploy
operating systems with System Center Configuration Manager with ZTI.
Note For complete and detailed instructions of ZTI deployments with System Center
Configuration Manager, see the Microsoft Deployment documents, Preparing for Microsoft System
Center Configuration Manager 2007 and Microsoft System Center Configuration Manager 2007
Imaging Guide.

To deploy operating systems with System Center Configuration Manager with ZTI
1. Install and configure System Center Configuration Manager:
• See “Planning and Deploying the Server Infrastructure for Configuration
Manager 2007” in the System Center Configuration Manager online
documentation at http://technet.microsoft.com/en-us/library/bb680397.aspx.
• See the section, “Preparing the Deployment Environment,” in Preparing for
Microsoft System Center Configuration Manager 2007.
2. Gather required source media for each of the following:
• Windows Vista
• Windows AIK (for Windows PE source)
• Any applications required for inclusion in the base reference image
• Any required language pack or updated components for the operating system
• Any required device driver for reference build platform
3. Install and configure the Microsoft Deployment Toolkit:
a. Follow the steps listed in the section, “Installing Microsoft Deployment,” earlier in
this guide.
b. Run the Configure ConfigMgr Integration process from the Microsoft Deployment
Toolkit program group.
4. Install USMT version 3.0.1 on the server hosting Configuration Manager Console and
the Microsoft Deployment Toolkit.
5. Complete additional System Center Configuration Manager configuration, as detailed
in the section, “Preparing System Center Configuration Manager for Deployment,” in
Microsoft System Center Configuration Manager 2007 Imaging Guide.
a. Import the Microsoft Deployment task sequence into Configuration Manager
Console.
Note See the section, “Create New Task Sequences Using the Import Wizard,” in
Microsoft System Center Configuration Manager 2007 Imaging Guide.

Solution Accelerators microsoft.com/technet/SolutionAccelerators

Quick Start Guide: Installing Microsoft Deployment 15

b. Create a new driver package, and import drivers into System Center
Configuration Manager.
Note See the sections, “Create a New Driver Package” and “Import Drivers to System
Center Configuration Manager,” in Microsoft System Center Configuration Manager 2007
Imaging Guide.

c. Add language packs and operating system updates into System Center
Configuration Manager.
Note See the sections, “Add Language Packs” and “Add Updates,” in Microsoft System
Center Configuration Manager 2007 Imaging Guide.

d. Build and capture a new reference image for use with System Center
Configuration Manager.
e. Create a new image package for deployment.
6. Advertise the task sequence as described in the section, “Advertising the Task
Sequence,” in Preparing for Microsoft System Center Configuration Manager 2007.

Solution Accelerators microsoft.com/technet/SolutionAccelerators