Installing USMT
You can install USMT
directly on each client computer or stage it on a network share. If
you’re using BDD 2007, it can download USMT for you and install it in
the distribution share automatically.
USMT supports both the x86
and x64 platforms. Each platform uses two installation files—one for
Windows Vista and one for Windows 2000 and Windows XP. The Windows Vista
installation file is InstallUSMT30_Platform_vista.msu, where Platform is either x86 or x64. The Windows 2000 and Windows XP installation file is InstallUSMT30_Platform_2000andXP.exe. The following list describes how to obtain USMT installation files for each platform:
You can install USMT in a
number of ways to support use in your organization: locally, on a
network share, on a BDD 2007 distribution share, or with the SMS 2003
OSD Feature Pack. The last two options enable migration during LTI and
ZTI deployment projects. The following sections describe each option in
more detail.
|
In the initial release,
BDD 2007 is unable to install USMT on computers silently during
deployment. Until this issue is resolved in USMT 3.0, use the following
steps for the x86 and x64 versions of USMT 3.0 to repackage their files
in to cabinet files from which BDD 2007 can extract USMT 3.0:
Manually install the
x86 or x64 version USMT 3.0 on a computer running Windows XP or Windows
Vista, depending on which version you’re packaging.
Copy C:\Program Files\BDD 2007\Samples\USMT30_platform.ddf, where platform
is either x86 or x64, from a computer on which BDD 2007 is installed.
If USMT 3.0 is installed in a location other than the default
(C:\Program Files\USMT30), edit USMT30_platform.ddf to indicate its
path.
Run the command makecab /F USMT30_platform.ddf and then, copy the .cab file it creates to \Tools\platform folder in the BDD 2007 distribution share.
|
Local Installation
The USMT installation
file launches a Windows Update–style installer to install USMT on the
computer. This installs the USMT tools to the Program Files folder on
the computer and creates any applicable registry entries. Manually
installing USMT locally is not recommended for high-volume deployment
projects.
Network Staging
Installing
USMT 3.0 to a network share requires an additional step. After
installing USMT on a local computer, you can copy the contents of the
C:\Program Files\USMT30 to a network share. Once the scripts are on the
network, they can run the USMT components.
BDD 2007
Installing USMT in
BDD 2007 is not the same as installing USMT on the local computer. To
install USMT in BDD 2007, you simply copy the two x86 installation files
to the distribution share’s Tools\x86 folder or copy the two x64
installation files to the distribution share’s Tools\x64 folder. BDD
2007 will automatically install and run USMT on each computer during LTI
and ZTI deployments.
In BDD 2007, the
Deployment Workbench can even download the USMT components for you and
automatically store them in the distribution share.
SMS 2003 OSD
You
can use USMT with the SMS 2003 OSD Feature Pack to manage user state
migrations during operating system deployment. For more information, see
the SMS 2003 OSD Feature Pack documentation.
Understanding USMT Components
USMT
is located in C:\Program Files\USMT30 on the local computer. The
installer copies many files into this folder, including .dll files,
component manifests, and other application initialization files. (See Figure 1.) Most of the files support the two main executables: Scanstate.exe and Loadstate.exe.
In
addition to Scanstate and Loadstate, USMT uses three migration .xml
files. These files—MigSys.xml, MigApp.xml, and MigUser.xml—perform basic
file and settings migrations based on default criteria. You can
customize these files, along with custom .xml files, to migrate
additional files and settings or to exclude some of the default files
and settings.
Scanstate and Loadstate
save and restore user state data, respectively. You can run them
directly from a command prompt. They provide several command-line
options that control their behavior.
Scanstate.exe
You use Scanstate to
save user state data. By default, this program places user state data
into the data store location as defined by the three migration .xml
files. The following describes an abbreviated syntax of Scanstate, and Table 1 describes each command-line option:
Scanstate.exe [Store][/i:[path\]filename] [/config:[path\]file] [/o] [/p]
Table 1. Scanstate.exe Command-Line Options
| Option | Description |
|---|
| Store | Specifies a path to the data store. |
| /i:[path\]filename | Identifies a migration .xml to use when saving state data. You can use this option multiple times. |
| /config:[path\]file | Specifies a Config.xml file. |
| /o | Overwrites existing data in the data store. |
| /p | Creates a size estimate file (USMTsize.txt) in the location specified by Store. |
Loadstate.exe
You use Loadstate to
restore user state from the data store. By default, this program
restores user state to the location from which Scanstate originally
saved it—unless the one of the migration .xml files redirects it.
(Loadstate can use different migration .xml files than Scanstate.) The
following describes an abbreviated syntax of Loadstate, and Table 2 describes each command-line option:
Loadstate.exe [Store][/i:[path\]filename]
Table 2. Loadstate.exe Command-Line Options
| Option | Description |
|---|
| Store | Specifies a path to the data store. |
| /i:[path\]filename | Identifies a migration .xml to use when saving state data. You can use this option multiple times. |
| /config:[path\]file | Specifies a Config.xml file. |
XML 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.
