What is New in USMT 3.0
In this topic
- Overall changes from USMT 2.6
- ScanState changes
- New command-line options
- Changed command-line options
- LoadState changes
- New command-line options
- Changed command-line options
Overall changes from USMT 2.6
- The migration behavior is now controlled by .xml files instead of .inf files. Because of this change, there are also the following changes:
- You can use the same MigUser.xml and MigApp.xml files to migrate to computers running Windows XP and computers running Windows Vista. This means that the migration will require fewer resources for organizations that are migrating to both operating systems. (MigSys.xml is not applicable when the destination computer is Windows Vista.)
- Unlike previous versions of USMT, the .xml files are not copied to the store. Because LoadState needs the .xml files to control the migration, you will need to specify the same set of .xml files on the ScanState and LoadState command lines.
- You can select what to migrate and what to exclude by creating a Config.xml file using the /genconfig option.
- Must run from administrator account.
- When running ScanState and LoadState on Windows Vista, you need to run the tools in “Administrator” mode from an account with administrative credentials.To run in this mode, click the start button, click All Programs, click Accessories, right-click Command Prompt, click Run as administrator, and then specify your LoadState or ScanState command.
- In addition, you must run ScanState on Windows XP from an account with administrative credentials, or some operating system settings will not migrate.
- USMT 3.0 migrates EFS files and certificates to computers running Windows Vista. EFS files and certificates are migrated automatically to computers running Windows Vista when you specify the /efs:copyraw option on the ScanState command line.
- You can encrypt the store. You can encrypt the store with the /encrypt option using an encryption key (password). You can specify the key using either a file or in plain text.
- USMT 3.0 is faster and more robust than previous versions. For example, USMT 3.0 can migrate more user accounts than USMT 2.6.
- By default, all users are migrated. You can use /ui, /ue and /uel to change this behavior.
- For the most part, the .xml files migrate the same settings that the .inf files migrated in version 2.6. However, there are a few changes. For more information, see What Does USMT 3.0 Migrate?.
- USMT 3.0 migrates access control lists (ACL's).
- The following features that were present in USMT 2.6 will not be available in USMT 3.0:
- Some of the older applications that were supported by USMT 2.6 are not supported with USMT 3.0. For more information, see applications settings.
- You can only specify which users to include and exclude using the command line. You cannot specify users in the migration .xml files or in Config.xml.
- USMT 3.0 does not migrate files and settings from computers running Windows 95, Windows 98, Windows Millennium Edition, or Windows NT Workstation 4.0.
- USMT 3.0 does not migrate files and settings to computers running Windows 2000 and older operating systems.
- When the destination computer is Windows XP, USMT 3.0 will not migrate users’ cookies, network drives and printers. Also, for Outlook Express and RAS settings, USMT 3.0 will only migrate the mail (.dbx) files and phone book (.pbk) files.
ScanState changes
ScanState has new command-line options, and command-line options that have changed.
New command-line options
The following are new command-line options for ScanState.
Option | Explanation |
---|---|
Specifies the Config.xml file that ScanState should use to create the store. |
|
Encrypts the store with the specified key. |
|
Generates a Config.xml file, but does not create a store. |
|
Optimizes ScanState when the destination computer is running Windows XP. |
|
(User exclude based on last login) Migrates only the users that had logged onto the source computer within the specified time period. |
|
(User exclude) Excludes the specified user(s). |
|
Disables compression of data. |
Command-line options that have changed
The following command-line options have been changed for ScanState in USMT 3.0.
Option in USMT 2.6 | Explanation for USMT 3.0 |
---|---|
This option is now the default. |
|
/user |
This option has been replaced by the /ui option. |
This option now specifies to include the specified users. |
|
/compress[+/-] |
This option has been replaced by the /nocompress.
|
When migrating to a computer running Windows Vista, EFS certificates migrate automatically when you specify this option. For more information, see How To Migrate EFS Files and Certificates. |
|
The accepted values for VerbosityLevel have changed in this version. |
|
/test
|
These options are no longer supported. |
LoadState changes
In this version of USMT, there are new LoadState command-line options and options that have changed.
New command-line options
The following are new command-line options for LoadState.
Option | Explanation |
---|---|
Specifies the Config.xml file that LoadState should use. |
|
Decrypts the store with the specified key. |
|
Specifies that the store is not compressed. |
|
(User include) Migrates the specified user(s). |
|
(User exclude) Excludes the specified user(s). |
|
(User exclude based on last login) Migrates only the users that had logged onto the source computer within the specified time period.. |
Command-line options that have changed
The following command-line options have changed in LoadState in USMT 3.0. For more detailed information about these options, see LoadState Syntax.
Option in USMT 2.6 | Explanation for USMT 3.0 |
---|---|
/compress[+/-] |
This option has been replaced by the /nocompress option. |
This option has been modified so that OldUserName is never optional. |
|
This option has been modified so that OldDomain is never optional, and you can now specify this option more than once on the command line. |
|
This option is now the default. |
|
/user |
This option has been replaced with the /ui, /uel, and /ue options. |
The accepted values for VerbosityLevel have changed in this version. |
|
/test
|
These options are no longer supported. |