USMT Components

  • Article

You use ScanState to collect the files and settings from the source computer. You use LoadState to restore the user state onto the destination computer. This section describes the components and files that ScanState and LoadState use. For ScanState and LoadState to use an .xml file, you will need to specify it on both command lines.

USMT Components

Component Explanation

ScanState.exe

ScanState scans the source computer, collects the files and settings and creates a store. ScanState does not modify the source computer. By default, ScanState compresses the files and stores them as an image file (USMT3.MIG).

LoadState.exe

LoadState migrates the files and settings from the store to the destination computer. LoadState migrates each file (one by one) from the store to a temporary location on the destination computer — the files are decompressed (and decrypted if necessary) during this process. Next, LoadState transfers the file to the correct location, deletes the temporary copy, and begins migrating the next file.

Compression improves performance by reducing network bandwidth usage as well as the required space in the store. However, for testing purposes, you can choose to turn off compression with /nocompress.

Migration .xml files

MigSys.xml, MigApp.xml, MigUser.xml, and any Custom .xml files that you create.

Config.xml

If you want to exclude components from the migration, you can create and modify this file using the /genconfig option on the ScanState command line. This optional file has a different format than the migration .xml files because it does not contain any migration rules. Config.xml contains a list of the components that can be migrated and allows you to specify migrate = "no" for those you wish to exclude from the migration.

Component Manifests for Windows Vista

When the source or destination computer is running Windows Vista, these files control which operating system and browser settings are migrated and how. These files are located on computers running Windows Vista and you cannot modify these files. If you want to exclude certain operating system settings when the source computer is running Windows Vista, you will need to create and modify a Config.xml file.

Note
These files are not used when the destination computer is running Windows XP. For Windows XP, MigSys.xml contains information that controls which operating system and browser settings to migrate.

Downlevel Manifests

When the source computer is running Windows 2000 or Windows XP, these manifests control which operating system and browser settings are migrated and how. For example, when the destination computer is running Windows Vista, ScanState collects the data using the Downlevel Manifests, and then LoadState migrates the data using the corresponding Component Manifest for Windows Vista . The Downlevel Manifests are not used during LoadState.

This set of files is located in the USMT\dlmanifests folder. You cannot modify these files. If you want to exclude certain operating system settings when the destination computer is running Windows Vista, you will need to create and modify a Config.xml file.

Note

These files are not used when the destination computer is running Windows XP. For Windows XP, MigSys.xml contains information that controls which operating system and browser settings to migrate.

USMT internal files

All other .dll, .xml, .dat, .mui, .inf files that are included with USMT are for internal use. You cannot modify these files.