c




 
 
 




 
Microsoft® Deployment Toolkit (MDT) 2010 is a free Solution Accelerator from Microsoft that provides a
framework for using the deployment tools in the Windows® 7 operating system and the Windows
Automated Installation Kit (Windows AIK). Although MDT 2010 is an advanced tool that large organizations
can use in extremely complex deployment scenarios, it also is a simple tool that can provide a high level of
automation in simpler deployment scenarios. This guide describes a straight path through MDT 2010 that
you can use to automate the installation of Windows 7. As you become more comfortable with MDT 2010,
you can learn more about customizing MDT 2010 by reading the documentation that comes with it.

You perform all steps in this guide on a single computer, except for the actual installation of Windows 7 from
the deployment share, which is the last step in this guide. You install MDT 2010 on that single computer,
and it hosts the deployment share. The requirements for the computer are low. It can be running Windows
Vista® with Service Pack 1 (SP1), Windows 7, Windows Server® 2008, or Windows Server 2008 R2. It does
not need to be a high-performance computer. All the computer really needs is about 10 gigabytes (GB) of
free disk space and a network connection that each destination computer can reach. (The actual hard disk
requirements depend on the number of operating system images and applications you add to the
deployment share.) You can even install MDT 2010 on a laptop computer to take from location to location.

This guide describes how to use MDT 2010 to automate Windows 7 installation from the image that Microsoft
ships on retail or volume license (VL) media, including automatically installing applications, device drivers,
and updates after installation. This approach is called thin imaging, and it¶s a best practice because it is
easier to build and maintain over time. This guide does not describe how to build custom images that
contain applications, device drivers, and updates by using MDT 2010. This is a more advanced scenario
called thick imaging, which this guide does not recommend for small or medium organizations lacking a
dedicated information technology (IT) staff. For more information about building custom disk images by
using MDT 2010, see the documentation that comes with it.

Note

This guide often directs you to choose between 32-bit and 64-bit software. To make this choice, you must know whether you
32-bit or a 64-bit version of Windows. Determine the version of Windows you¶re using by clicking Start, right-clicking Compu
clicking Properties. The System area indicates the type of operating system you¶re using, as shown in Figure 1.

Figure 1. Determining the operating system type

Watch the companion video tutorial for more information.

Also see the following related documents:

R? ÷pgrading to Windows 7 for Small and Midsize Businesses

R? Automated Installation of Windows 7: Overview

R? Manual Installation of Windows 7: Overview

R? ÷pgrading to Windows 7 with a Standard Image: Overview

 R? Building a Standard Image of Windows 7: Step-by-Step Guide

For a complete view of Windows 7 resources, articles, demos, and guidance, please visit the Springboard
Series for Windows 7 on the Windows Client TechCenter.

For a downloadable version of this document, see the Automated Installation of Windows 7: Step-by-Step
Guide in the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=162745).

V
tall the Micro
oft Deployme t Toolkit

R? Microsoft Deployment Toolkit 2010. There are two files, MicrosoftDeploymentToolkit_x86 for 32-bit
computers and MicrosoftDeploymentToolkit_x64 for 64-bit computers.

R? Windows Automated Installation Kit. Windows Automated Installation Kit. The file is called
KB3AIK_EN.iso. You must burn this file to a DVD. In Windows 7 and Windows Server 2008 R2,
right-click ¢
V¢N.i
o, click Ope With, and then click Wi ow
Di
c Vmage ur er.
Follow the instructions to burn the .iso file to a DVD. In earlier Windows versions, you must use
third-party DVD burning software.

MDT 2010 also requires Windows PowerShellΠcommand-line interface:

R? If you¶re installing MDT 2010 on computers running Windows 7 or Windows Server 2008 R2,
Windows PowerShell is already installed and you have to do nothing extra.

R? If you¶re installing MDT 2010 on computers running Windows Vista with SP1 or Service Pack 2
(SP2), download and install the 32-bit version or the 64-bit version from article 928439 in the
Microsoft Knowledge base. Installing Windows PowerShell as an optional update from Windows
÷pdate is easier than manually downloading and installing it from the Microsoft Download Center.

R? If you¶re running Windows Server 2008 with SP1 or SP2, you must add the Windows PowerShell
feature.

R? Installing MDT 2010 on computers running Windows XP is not supported; however, MDT 2010 can
refresh computers running Windows XP with a new installation of Windows 7.

To i
tall the Wi ow
V¢ from the Wi ow
V¢ DVD

1.? Insert the Windows AIK DVD into the computer, and open it in Windows Explorer.

2.? Perform one of the following tasks based on the computer on which you are installing the
Windows AIK:

R? For a 32-bit computer, right-click wV¢.m
i, and then click V
tall.

R? For a 64-bit computer, right-click wV¢MD.m
i, and then click V
tall.

3.? Click Next.

4.? On the 'ice
e greeme t page, click V gree, and then click Next.

5.? On the `elect V
tallatio Foler page, click Next to install to the default installation folder for
anyone who uses the computer.

6.? On the ‰o firm V
tallatio page, click Next to begin installation.

7.? Click ‰lo
e to finish installation.

To i
tall the Micro
oft Deployme t Toolkit after i
talli g the Wi ow
V¢
1.? In Windows Explorer, open the folder in which you downloaded or copied the MDT 2010 installation
files. This folder contains MicrosoftDeploymentToolkit_x86.msi,
MicrosoftDeploymentToolkit_x64.msi, or both files.

2.? Perform one of the following tasks based on the computer on which you¶re installing MDT 2010:

R? For a 32-bit computer, right-click Micro
oftDeployme tToolkitx.m
i, and then

click V
tall.

R? For a 64-bit computer, right-click Micro
oftDeployme tToolkitx.m
i, and then

click V
tall.

3.? Click Next.

4.? On the  
er 'ice
e greeme t page, click V accept the term
i the 'ice
e
greeme t, and then click Next.

5.? On the ‰u
tom `etup page, click Next to install the typical MDT 2010 features. The typical
features include the MDT 2010 documentation as well as the tools and templates.

6.? On the Veay to V
tall page, click V
tall to begin installation.

7.? Click Fi i
h to complete the installation.

To a the Wi ow
Power`hell feature to Wi ow
`erver 200

1.? Click `tart, click mi i
trative Tool
, and then click `erver Ma ager.

2.? In the console tree, click Feature
.

3.? In the details pane, click  Feature
to start the  Feature
Wizar.

4.? In the Feature
list, select the Wi ow
Power`hell check box, and then click V
tall.

‰reate a Deployme t `hare for Wi ow
7

With MDT 2010, you create and edit deployment shares by using Deployment Workbench:

R? To open the Deployment Workbench, click `tart, click ll Program
, click Micro
oft Deployme t
Toolkit, and then click Deployme t Workbe ch.

R? To read the MDT 2010 documentation, click `tart, click ll Program
, click Micro
oft
Deployme t Toolkit, and then click Micro
oft Deployme t Toolkit Docume tatio .

Before continuing, take a moment to review the information in the Deployment Workbench (Figure 2). In the
console tree, click etti g `tarte,Docume tatio , and New
. These are under V formatio
‰e ter. Deployme t `hare
will be empty until you create a deployment share.
Figure 2. Deployment Workbench

Deployment shares contain all of your source files (application, operating system, device drivers, and update
files). They also contain settings that customize the Windows Deployment Wizard, which is the wizard that
actually installs Windows 7 on each computer, and tools that you can use to manage the deployment share.
This guide shows you the most direct path through the Deployment Workbench. ÷ntil you¶re more
comfortable with Deployment Workbench, you can ignore settings and tools that this guide doesn¶t describe.
When you are more comfortable, however, see the MDT 2010 documentation to learn about the thousands
of ways in which you can customize the deployment experience.

To create a ew eployme t
hare

1.? In the console tree, right-click Deployme t `hare
, and click New Deployme t `hare to start
the New Deployment Share Wizard.

2.? On the Path page, type the path and name of the folder in which you want to create the
deployment share, and click Next. The Deployment Workbench will not create the folder, so make
sure it already exists, or click row
e to create it.

3.? On the `hare page, click Next to accept the default share name. The default share name is the
name of the folder with a dollar sign ($) suffix, which hides the share from users, and this name is
appropriate in most cases. If you want the share to be visible on the network, remove the dollar
sign.

4.? On the De
criptive Name page, click Next to accept the default name. If you plan to create
multiple deployment shares, you can type a more descriptive name. Otherwise, the default name is
appropriate in most cases.

5.? On the llow Vmage ‰apture page, clear the 
k if image
houl be capture check box, and
then click Next. ÷sing this installation method, you aren¶t building custom images. Instead, you¶re
 deploying the default Windows 7 image via the network and then customizing it after installation
(thin imaging).

6.? On the llow mi Pa

wor page, do one of the following, and then click Next:

R? If you want to allow users to change the local Administrator password during installation,
select the 
k u
er to
et the local mi i
trator Pa

wor check box. Choose this
option only if you allow users to manage the local Administrator account on their
computers.

R? If you don¶t want to allow users to change the local Administrator password during
installation, clear the 
k u
er to
et the local mi i
trator Pa

wor check box.
Choose this option if you want to use a standard local Administrator password for all
computers in your business.

7.? On the llow Prouct ¢ey page, do one of the following, and then click Next:

R? If you want to allow users to specify a product key during installation, select the 
k u
er
for a prouct key check box. Choose this option if you¶re deploying retail media and each
computer must have a unique product key.

R? If you don¶t want to allow users to specify a product key during installation, clear the 
k
u
er for a prouct key check box. Choose this option if you¶re deploying VL media and
you have one product key for all of the computers in your business.

8.? On the `ummary page, shown in Figure 3, review the installation details, and click Next.

Figure
. New Deployment Share Wizard

9.? On the ‰o firmatio page, click Fi i
h to close the New Deployment Share Wizard.
`tock the Deployme t `hare with `ource File

After you create a deployment share, it contains the scripts and tools necessary to install Windows 7. It
doesn¶t contain the application, operating system, device driver, or update source files. In this step, you add
these source files to the deployment share.

Before beginning this step, gather the files you need:

R? Wi ow
7. You need your Windows 7 retail or VL media. You can copy the files directly from the
DVD, or you can copy them from a local or network folder.

R? Application source files. You need the source files for each application that you want to add to the
deployment share and install during deployment. You can copy these files directly from the
application¶s CD or DVD or from a local or network folder. You also need the command that installs
each application silently. (This guide recommends automating installation.) In most cases, software
vendors document how to install their applications silently. You can also use the non-Microsoft Web
site AppDeploy.com to quickly look up the silent installation command for most common
applications.

R? Device river
. You need the source files for each device driver you want to add to the deployment
share. You can download device drivers from each computer¶s hardware vendor¶s Web site. Once
you download the device driver, make sure that it¶s decompressed. For example, if you download a
device driver as a .zip file, extract the file. If you download the file as a compressed .exe file, run
the file to extract the device driver¶s source files. If you can¶t extract the device driver¶s source files,
you must install the device driver as an application.

R? pate
. You¶ll need the .msu files for any packages with which you want to update Windows 7.
For example, you can download the Microsoft Virtual PC update and add that to the deployment
share. Download updates from the Microsoft Download Center.

Note

You can add applications to a deployment share two ways. You can copy the files into the deployment share and install the ap
from there, or you can leave application source files elsewhere on the network and just add a command to the deployment sh
installs them. To keep the process simple and avoid additional complexity, this guide instructs you to copy the application sou
the distribution share.
To a applicatio
to the eployme t
hare
1.? In the console tree, right-click pplicatio
, and click New pplicatio to start the New
Application Wizard. pplicatio
isinDeployme t `hare
under the deployment share you
created earlier.

2.? On the pplicatio Type page, click Next to install an application and copy its source files to the
deployment share.

3.? On the Detail
page, type the application¶s name in the pplicatio Name box, and click Next.
Optionally, you can also type the application¶s publisher, version, and language.

4.? Make sure the application¶s source files are available. If you¶re copying the application¶s source files
from a disk, insert the disk into the computer. If you¶re copying the application¶s source files from a
network location, make sure you can access the folder containing those files.

5.? On the `ource page, type the path of the folder containing the application¶s source files, and
click Next. You can also click row
e to locate the folder.
 6.? On the De
ti atio page, click Next to use the default name for the application in the deployment
share. The default name is the publisher, name, and version concatenated and is the best choice in
most cases.

7.? On the ‰omma  Detail
page, type the command you want to use to install the application, and
click Next. You should type a command that installs the application silently. You can use the non-
Microsoft Web site AppDeploy.com to quickly look up the silent installation command for most
common applications. Don¶t change the Worki g irectory box, because the default value is
correct when you¶re copying application source files to the deployment share.

8.? On the `ummary page, shown in Figure 4, review the application¶s details, and click Next.

Figure . New Application Wizard

9.? On the ‰o firmatio page, click Fi i
h to close the New Application Wizard.

Note

After adding the 2007 Microsoft Office system to the deployment share, you can customize its installation. Right-click Office
deployment share, and click Propertie
. On the Office Prouct
tab, customize the 2007 Office release installation as desir
product key, choosing a display level, accepting the license agreement, and so on. Click O¢ when you are finished.
To a Wi ow
7 to the eployme t
hare
1.? In the console tree, right-click Operati g `y
tem
, and click Vmport Operati g `y
tem to start
the Import Operating System Wizard.Operati g `y
tem
is in Deployme t `hare
under the
deployment share you created earlier.

2.? On the O` Type page, click Next to copy the full set of Windows 7 source files to the deployment
share.
 3.? Make sure the Windows 7 source files are available. If you¶re copying the source files from a disk,
insert the disk into the computer. If you¶re copying the source files from a network location, make
sure you can access the folder containing those files.

4.? On the `ource page, type the path of the folder containing the Windows 7 source files, and
click Next. Alternatively, click row
e to locate the Windows 7 source files.

5.? On the De
ti atio page, click Next to use the default folder name for the deployment share. The
default name is appropriate if you¶re copying only one set of Windows 7 source files to the
deployment share. If you¶re copying multiple editions of Windows 7 (retail versus VL) to the
deployment share, change the name to differentiate each edition.

6.? On the `ummary page, shown in Figure 5, review the operating system details, and click Next.

Figure 5. Import Operating System Wizard

7.? On the ‰o firmatio page, click Fi i
h to close the Import Operating System Wizard.

To a evice river
to the eployme t
hare

1.? In the console tree, right-click Outof ox Driver
, and click Vmport Driver
to start the Import
Driver Wizard. Outof ox Driver
is inDeployme t `hare
under the deployment share you
created earlier.

2.? Make sure the device driver source files are available. If you¶re copying them from a disk, insert the
disk into the computer. If you¶re copying them from a network location, make sure you can access
the folder containing those files. You can specify a folder containing multiple device drivers
organized into subfolders, as the Import Driver Wizard imports all of the device drivers that it finds
in the folder and all of is subfolders.
 3.? In the `pecify Directory page, type the path of the folder containing the device driver source files,
and click Next. You can also click row
e to locate the folder.

4.? On the `ummary page, review the device driver details, and click Next.

5.? On the ‰o firmatio page, click Fi i
h to close the Import Driver Wizard.

To a upate
to the eployme t
hare

1.? In the console tree, right-click Package
, and click Vmport O` Package
to start the Import
Package Wizard. Package
isinDeployme t `hare
under the deployment share you created
earlier.

2.? Make sure the update source files are available. If you¶re copying them from a disk, insert the disk
into the computer. If you¶re copying them from a network location, make sure you can access the
folder containing those files. You can specify a folder containing multiple updates organized into
subfolders. The Import Package Wizard imports all of the updates that it finds in the folder and all of
its subfolders.

3.? In the `pecify Directory page, type the path of the folder containing the updates source files, and
click Next. You can also click Browse to locate the folder.

4.? On the `ummary page, review the update details, and click Next.

5.? On the ‰o firmatio page, click Fi i
h to close the Import Package Wizard.

‰reate a Ta
k `eque ce to V
tall Wi ow
7

By this point, you¶ve created a deployment share and stocked it with application, operating system, device
driver, and update source files. The next step is creating a task sequence that installs Windows 7 on
computers. Think of a task sequence is a batch file or script that specifies the series of steps necessary to
prepare a computer for installation, install Windows 7, and configure the computer after installation. Of
course, task sequences have many more advanced capabilities that you can learn about after you¶re more
comfortable with MDT 2010. For now, you¶ll create a basic task sequence from a template, and you won¶t
customize the task sequence.A critical choice that you must make when you create a new task sequence is
how to activate Windows. If your business uses VL media with the Key Management Service (KMS), then
you won¶t specify a product key when you create a task sequence. If your business uses VL media with
Multiple Activation Keys (MAKs), then you will specify a product key when you create a task sequence. Last,
if your business uses retail media, then you¶ll specify a product key when you install Windows 7 on each
computer, and each computer must use a unique product key. If you don¶t know which of these three
scenarios applies to your business, contact the person in your organization responsible for licensing Windows
7 from Microsoft. For more information about Volume Activation, see Windows Volume Activation.

To create a ta
k
eque ce for Wi ow
7

1.? In the console tree, right-click Ta
k `eque ce
, and click New Ta
k `eque ce to start the New
Task Sequence Wizard. Ta
k `eque ce
is in Deployme t `hare
under the deployment share
you created earlier.

2.? On the e eral `etti g
page, shown in Figure 6, type a unique ID and a name for the task
sequence, and then click Next. The ID should be short and end with an index number. MDT 2010
uses the ID to identify the task sequence. The name should be descriptive, reflecting what the task
sequence installs. For example, a good ID for a task sequence that installs Windows 7 is simply
WIN7-01, and a good name for this task sequence is Windows 7 Professional. Optionally, type a
description in the Ta
k
eque ce comme t
box, which can provide more details about the task
sequence and what it does.
 Figure . General Settings page of the New Task Sequence Wizard

3.? On the `elect Template page, click Next to use the Standard Client Task Sequence template. This
is a predefined template that is already configured to properly install Windows 7.

4.? On the `elect O` page, click the operating system edition that you want to install by using the task
sequence, and click Next. Windows 7 media usually contains multiple editions in each image file.
Choose the edition that you purchased and that matches your product key. In most cases, you¶ll
choose either Windows 7 Professional or Windows 7 Enterprise.

5.? On the `pecify Prouct ¢ey page, shown in Figure 7, do one of the following, and then click Next:

R? If your company uses the KMS, click Do ot
pecify a prouct key at thi
time.

R? If your company has VL media with MAKs, click `pecify a multiple activatio key (M¢
key) for activati g thi
operati g
y
tem, and type the product key in the M¢
Prouct ¢ey box.

R? If your company is deploying retail media, and, when you created the deployment share,
you chose to allow users to provide a product key during installation, click Do ot
pecify
a prouct key at thi
time.
 Figure 7. Specify Product Key page of the New Task Sequence Wizard

6.? On the O` `etti g
page, type the organization name and the ÷RL of the Windows Internet
Explorer® home page that you want to configure for each user, and then click Next. You don¶t need
to change the Full Name box, as you¶ll provide this value during installation on each computer.

7.? On the mi Pa

wor page, do one of the following, and click Next:

R? If, when you created the deployment share, you chose to allow users to change the local
Administrator password, click Do ot
pecify a mi i
trator pa

wor at thi
time.

R? If, when you created the deployment share, you chose not to allow users to change the
local Administrator password, click 
e the
pecific local mi i
trator pa

wor;
then, type a local Administrator password in the mi i
trator Pa

wor box, and
confirm the local Administrator password in the Plea
e co firm mi i
trator
Pa

wor box.

8.? On the `ummary page, shown in Figure 8, confirm the task sequence details, and click Next.
 Figure . New Task Sequence Wizard

9.? On the ‰o firmatio page, click Fi i
h to close the New Task Sequence Wizard.

‰reate oot Meia

You¶re almost ready to start installing Windows 7 from the deployment share. All you need is a way to start
computers that don¶t have an operating system or that are getting a clean installation of Windows 7.

To start these computers, you¶ll use the Deployment Workbench to create boot images. These boot images
are based on the Windows Preinstallation Environment (Windows PE), and the Deployment Workbench
customizes the images to automatically connect to the deployment share and start the Windows Deployment
Wizard. You¶ll burn these boot images to a CD and optionally copy the boot image from the CD to a bootable
÷SB flash disk (÷FD). Starting computers with a bootable ÷FD is much faster than starting them from a CD.

The boot images that the Deployment Workbench creates are in the Boot folder of the deployment share.
The file LiteTouchPE_x86.iso is for 32-bit computers and the file LiteTouchPE_x64.iso is for 64-bit
computers. Windows 7 and Windows Server 2008 R2 can burn these images to CD without using third-party
software. With earlier Windows versions, you must use third-party CD-burning software.

To create boot image
for the eployme t
hare

1.? In the console tree, right-click the deployment share that you created earlier, and click pate
Deployme t `hare to start the ÷pdate Deployment Share Wizard.

2.? On the Optio
page, click Next.

3.? On the `ummary page, review the details, and click Next to create the deployment share and build
the boot images. This process can take from several minutes to an hour, depending on the
computer¶s performance.

4.? On the ‰o firmatio page, click Fi i
h to close the ÷pdate Deployment Point Wizard.
To bur boot image
to a ‰D i Wi ow
7 or Wi ow
`erver 200 V2
1.? In Windows Explorer, open the Boot folder in the deployment share. This folder contains the boot
images LiteTouchPE_x86.iso andLiteTouchPE_x64.iso. If you created the deployment share in the
default location, open C:\DeploymentShare\Boot in Windows Explorer.

2.? Do one or both of the following:

R? To burn a CD that starts 32-bit computers, right-click 'iteTouchPx.i
o, click Ope

With, and then click Wi ow
Di
c Vmage ur er. Follow the instructions to burn the
.iso file to a CD.

R? To burn a CD that starts 64-bit computers, right-click 'iteTouchPx.i
o, click Ope

With, and then click Wi ow
Di
c Vmage ur er. Follow the instructions to burn the
.iso file to a CD.

To create a bootable FD co tai i g the boot image

1.? Insert the boot CD that you created earlier into the computer.

2.? Insert a ÷FD into the computer. The ÷FD must be at least 200 megabytes (MB).

War i g

Double-check that the ÷FD doesn¶t contain data that you want to keep. By following these instructions, you will destr
contents of the ÷FD.
3.? Click `tart, click ll Program
, and then click Micro
oft Wi ow
V¢.

4.? Right-click Deployme t Tool
‰omma  Prompt, and then click Vu a
ami i
trator.

5.? Click Ke
to open the Deployment Tools Command Prompt window with elevated permissions.

6.? In the Deployment Tools Command Prompt window, type i
kpart, and then press ENTER.

7.? Perform the following tasks to prepare the ÷FD to start computers:

R? Type li
t i
k, and then press ENTER.

R? From the list of disks, identify the number of the ÷FD. It is important that you identify the
correct disk, as you will be formatting the disk. Make sure the size and free space match
what you expect for the ÷FD.

R? Type
elect i
k umber, where number is the disk number of the ÷FD, and then press
ENTER.

R? Type clea , and then press ENTER.

R? Type create partitio primary, and then press ENTER.

R? Type
elect partitio 1, and then press ENTER.

R? Type format f
fat
2 quick, and then press ENTER.

R? Type active, and then press ENTER.

R? Type exit, and then press ENTER.

 8.? In the Deployment Tools Command Prompt window, type xcopy /
D:\ *.* :\, where ˜ is the
drive letter of the boot CD, and E is the drive letter of the ÷FD. Alternatively, you can copy all the
files in the boot CD to the ÷FD using Windows Explorer.

V
tall Wi ow
7
Now you¶re ready to start installing Windows 7 on computers. You¶ve created and stocked a deployment
share. You¶ve created a task sequence that describes the steps to install and configure Windows 7, and
you¶ve created boot images that can start new computers and automatically start installation.

This guide recommends two ways of installing Windows 7 from the deployment share, and this section
contains instructions for both scenarios:

R? New computer. To use this scenario, follow the instructions titled ³To install Windows 7 on a
computer by using the New Computer scenario´ in this section. In this scenario, you perform a clean
installation of Windows 7 by starting the computer with the boot media and running the Windows
Deployment Wizard. This scenario completely removes the computer¶s existing contents. It does not
preserve applications or users¶ data and settings. ÷se this scenario when you¶re installing Windows
7 on a computer that doesn¶t have an operating system, a computer that has an operating system
that won¶t start, or a computer for which you don¶t want to preserve users¶ data or settings.

R? Vefre
h computer. To use this scenario, follow the instructions titled ³To install Windows 7 on a
computer by using the Refresh Computer scenario´ in this section. In this scenario, you perform a
clean installation of Windows 7 just as in the previous scenario. However, instead of starting the
computer using the boot media, you start the computer using its current version of Windows, and
then start the Windows Deployment Wizard from the deployment share. This scenario doesn¶t
preserve applications, but it does preserve users¶ data and settings. ÷se this scenario when you
want to preserve users¶ existing data and settings and you¶re installing Windows 7 on computers
that have Windows XP with SP2 or Service Pack 3 (SP3) or Windows Vista.

To i
tall Wi ow
7 o a computer by u
i g the New ‰omputer
ce ario

1.? Insert the boot CD or bootable ÷FD into the computer.

2.? Turn on the computer, and do one of the following:

R? If you¶re using a boot CD, press a key when prompted to press any key to boot from CD or
DVD. If you don¶t see this prompt and you¶ve inserted the boot CD into the computer, you
must enable the basic input/output system (BIOS) to boot from CD. For more information,
see the computer¶s documentation.

R? If you¶re using a bootable ÷FD, open the boot device list when prompted. (In most cases,
pressing F12 during the BIOS splash screen opens the computer¶s boot device list.) From
the list of boot devices, select the bootable ÷FD that you inserted in step 1 to start the
computer using boot media that you created earlier. If you don¶t see a prompt to display a
boot device list, you must enable the boot menu in the computer¶s BIOS. For more
information, see the computer¶s documentation.

3.? Click Vu the Deployme t Wizar to i
tall a ew Operati g `y
tem.

4.? In the 
er ‰ree tial
dialog box, type the user name, password, and domain you want to use to
connect to the deployment share; then, click O¢.

Tip

If you can¶t connect to the deployment share, make sure that the computer can contact the deployment share. To do
click ‰a celto return to a Command Prompt window. Then, type pi g computer ame, where computer_name is
 computer hosting the deployment share. If the pi g command displays ³Ping request could not find host computer_n
network problem is preventing the Windows Deployment Wizard from connecting to the computer hosting the deploy
additional troubleshooting tips, see the MDT 2010 documentation.
5.? On the `elect a ta
k
eque ce page, shown in Figure 9, click the task sequence that you created
earlier, and click Next.

Figure 9. Select a task sequence to run on this computer

6.? If, when you created the deployment share, you chose to allow the user to specify a product key
during installation, do one of the following, and then click Next:

R? If your company uses VL media with KMS, click No prouct key i
require.

R? If your company uses VL media with MAKs, click ctivate the machi e with a multiple
activatio key (M¢), and type the product key in the MAK activation key box.

R? If your company is deploying retail media, click 
e a
pecific prouct key, and type the
product key in the Prouct key box.

7.? On the ‰o figure the computer ame page, type a name for the computer, and click Next.
Although you can use the suggested computer name, this guide recommends against it because the
suggested name doesn¶t help you identify the computer on the network. If you already have a
computer naming standard in your business, name the computer according to that standard. A
simple naming scheme you can use isÈL-PC-NN, where È is the user¶s first initial, L is the user¶s last
initial, and NN is a sequential number beginning with 01.

8.? On the §oi the computer to a omai or workgroup page, shown in Figure 10, do one of the
following, and click Next:

R? If your organization has a domain, click §oi a omai . Then, type its name in
the Domai box. Additionally, provide the credentials necessary to join the computer to
the domain in the 
er Name, Pa

wor, and Domai boxes.
 R? If your organization doesn¶t have a domain, click §oi a workgroup. Additionally, type the
name of the workgroup you want to join in the Workgroup box.

Figure
10. Join the computer to a domain or workgroup

9.? On the `pecify whether to re
tore u
er ata page, click Next. Since this is a clean installation,
you aren¶t restoring users¶ data or settings.

10.? On the 'ocale `electio page, select your location from the What i
your 'ocale list and your
keyboard layout from the ¢eyboar list. Then, click Next.

11.? On the `et the Time Zo e page, click the time zone, and click Next.

12.? On the `elect o e or more applicatio
to i
tall page, select the check box next to each
application that you want to install on the computer, and click Next. The applications you see in this
list are the applications that you previously added to the deployment share.

13.? If, when you created the deployment share, you allowed users to change the local Administrator
password during installation, type the local Administrator password in the mi i
trator
Pa

wor box, confirm the password in the Plea
e co firm mi i
trator Pa

wor box, and
then click Next.

14.? On the Veay to begi page, click egi to
tart i
talli g Wi ow
7. Optionally,
click Detail
to review the installation details as shown in Figure 11.
 Figure 11. Ready to begin

To i
tall Wi ow
7 o a computer by u
i g the Vefre
h ‰omputer
ce ario

1.? Start the computer and log on to the previous Windows version.

2.? Run LiteTouch.vbs from the Scripts folder of the deployment share. Figure 12 shows the location of
this script in Windows Explorer. In this example, the computer  in-uy45xud9ldq is hosting the
deployment share, and the deployment share is named ˜eploymentShare$. The
script LiteTouch.vbs is in the subfolder Scripts.

Note

The dollar sign ($) on the end of the share name hides the share, so you won¶t see it in Windows Explorer. Therefore
the full path of the share in the Windows Explorer Address bar to open it. Alternatively, you can click `tart,
type\\computer\Deployme t`hare$, and press ENTER to open the share in Windows Explorer.
3.?
4.? Figure 12. Location of LiteTouch.vbs in the deployment share

5.? On the `elect a ta
k
eque ce page, click the task sequence that you created earlier, and
click Next.

6.? If, when you created the deployment share, you chose to allow the user to specify a product key
during installation, do one of the following, and then click Next:

R? If your company uses VL media with KMS, click No prouct key i
require.

R? If your company uses VL media with MAKs, click ctivate the machi e with a multiple
activatio key (M¢), and type the product key in the M¢ activatio key box.

R? If your company is deploying retail media, click 
e a
pecific prouct key, and type the
product key in the Prouct key box.

7.? On the ‰hoo
e a migratio type page, shown in Figure 13, click Next to refresh the computer.
This guide doesn¶t recommend the second option, which upgrades the previous Windows version to
Windows 7 while preserving existing applications and settings.
 Figure 1
. Choose a migration type

8.? On the ‰o figure the computer ame page, optionally type a computer name in the ‰omputer
ame box, and click Next. If you don¶t type a computer name, the Windows Deployment Wizard
reuses the computer¶s current name.

9.? On the §oi the computer to a omai or workgroup page, do one of the following, and
click Next:

R? If your organization has a domain, click §oi a omai . Then, type its name in
the Domai box. Additionally, provide the credentials necessary to join the computer to
the domain in the 
er Name, Pa

wor, and Domai boxes.

R? If your organization doesn¶t have a domain, click §oi a workgroup. Type the name of the
workgroup you want to join in theWorkgroup box.

10.? On the `pecify where to
ave your ata a 
etti g
page, shown in Figure 14,
click utomatically etermi e the locatio , and click Next.
 Figure 1. Specify where to save your data and settings

11.? On the `pecify where to
ave a complete computer backup page, do one of the following, and
then click Next:

R? To back up the computer and allow the Windows Deployment Wizard to choose the best
location, click utomatically etermi e the locatio .

R? To back up the computer to a specific location, click `pecify a locatio , and type the path
in the 'ocatio box.

R? To prevent the Windows Deployment Wizard from backing up the computer, click Do ot
back up the exi
ti g computer.

12.? On the 'ocale `electio page, select your location from the What i
your 'ocale list and your
keyboard layout from the ¢eyboar list. Then, click Next.

13.? On the `et the Time Zo e page, click the time zone, and click Next.

14.? On the `elect o e or more applicatio
to i
tall page, select the check box next to each
application that you want to install on the computer, and click Next. The applications you see in this
list are the applications that you previously added to the deployment share.

15.? If, when you created the deployment share, you allowed users to change the local Administrator
password during installation, type the local Administrator password in the mi i
trator
Pa

wor box, confirm the password in the Plea
e co firm mi i
trator Pa

wor box, and
then click Next.
 16.? On the `pecify cree tial
for co ecti g to etwork
hare
page, type the user name,
password, and domain you want to use to connect to the deployment share during installation;
then, click Next.

17.? On the Veay to begi page, click egi to start installing Windows 7. Optionally, click Detail
to
review the installation details as shown in Figure 15.

Figure 15. Ready to begin

After completing these steps, the Windows Deployment Wizard installs Windows 7 on the destination
computer. Once it has finished installing Windows 7, the Windows Deployment Wizard displays an
installation summary showing any error or warning messages. If the installation completed with error
messages, see
icrosoft ˜eployment Toolkit Troubleshooting Reference, which is in the MDT 2010
documentation.