In This Topic
Supported Operating Systems
Windows® User State Migration Tool (USMT) 4.0 does not have any explicit RAM or CPU speed requirements for either the source or destination computers. If your computer complies with the system requirements of the operating system, it also complies with the requirements for USMT. You need an intermediate store location large enough to hold all of the migrated data and settings, and the same amount of hard disk space on the destination computer for the migrated files and settings.
The following table lists the operating systems supported in USMT 4.0.
Operating Systems | ScanState (source computer) | LoadState (destination computer) | |
---|---|---|---|
Windows® XP Professional |
X |
||
Windows XP Professional x64 Edition |
X |
||
32-bit versions of Windows Vista® |
X |
X |
|
64-bit versions of Windows Vista |
X |
X |
|
32-bit versions of Windows® 7 |
X |
X |
|
64-bit versions of Windows 7 |
X |
X |
Notes | |
|
Software Requirements
- Must run in Administrator mode in
Windows Vista and Windows 7. When manually running
the ScanState and LoadState tools on Windows Vista and
Windows 7, you must run them in Administrator mode from an
account with administrative credentials to ensure that all
specified users are migrated. This is because User Access Control
(UAC) is enabled in Windows Vista and Windows 7 by
default. To run in this mode, click Start, click All
Programs, click Accessories, right-click Command
Prompt, click Run as administrator, and then specify
your LoadState or ScanState command. If you do not run USMT in
Administrator mode, only the user profile that is logged on will be
included in the migration.
Important You must run USMT in Administrator mode from an account with full administrative permissions, including the SeBackupPrivilege and SeRestorePrivilege privileges.
- Must run from an account with
administrative credentials in Windows XP. If you do not
run the ScanState tool from an account with administrative
credentials when Windows XP is the operating system on the
source computer, some operating-system settings will not migrate,
such as wallpaper settings, screen-saver selections, modem options,
media-player settings, and RAS connection phone-book (.pbk) files
and settings.
- Specify the /c option and
<ErrorControl> settings in the Config.xml file. USMT will
fail if it cannot migrate a file or setting, unless you specify the
/c option. When you specify the /c option, USMT logs
an error each time it encounters a file that is in use that did not
migrate, but the migration will not be interrupted. In USMT 4.0,
you can specify in the Config.xml file which types of errors should
allow the migration to continue, and which should cause the
migration to fail. For more information about error reporting, and
the <ErrorControl> element, see Config.xml File,
Log Files,
and XML Elements
Library.
- Install applications before running the
LoadState command. Install all applications on the destination
computer before restoring the user state. This ensures that
migrated settings are preserved.
Hard-Disk Requirements
Ensure that there is enough available space in the migration-store location and on the source and destination computers. For more information, see Estimate Migration Store Size.
User Prerequisites
This documentation assumes that IT professionals using USMT 4.0 understand command-line tools. The documentation also assumes that IT professionals using USMT 4.0 to author MigXML rules understand the following:
- The navigation and hierarchy of the Windows
registry.
- The files and file types that applications
use.
- The methods to extract application and
setting information manually from applications created by internal
software-development groups and non-Microsoft software vendors.
- XML-authoring basics.