mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
USMT Refresh 13
This commit is contained in:
Frank Rojas
@ -22,32 +22,32 @@ This article outlines the general process to follow to migrate files and setting
|
||||
|
||||
1. Determine where to store data. Depending on the size of the migration store, data can be stored in one of the following locations:
|
||||
|
||||
- Remotely.
|
||||
- Locally in a hard-link migration store or on a local external storage device.
|
||||
- Directly on the destination computer.
|
||||
- Remotely.
|
||||
- Locally in a hard-link migration store or on a local external storage device.
|
||||
- Directly on the destination computer.
|
||||
|
||||
For more information, see [Choose a Migration Store Type](usmt-choose-migration-store-type.md).
|
||||
For more information, see [Choose a Migration Store Type](usmt-choose-migration-store-type.md).
|
||||
|
||||
1. Use the `/GenMigXML` command-line option to determine which files are included in the migration, and to determine whether any modifications are necessary. For more information, see [ScanState Syntax](usmt-scanstate-syntax.md)
|
||||
|
||||
1. If necessary, modify copies of the `Migration.xml` and `MigDocs.xml` files and create custom **.xml** files. To modify the migration behavior, such as migrating the **Documents** folder but not the **Music** folder, custom **.xml** file can be created or modify the rules in the existing migration **.xml** files. The document finder, or `MigXmlHelper.GenerateDocPatterns` helper function, can be used to automatically find user documents on a computer without creating extensive custom migration **.xml** files.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Microsoft recommends to always make copies of the **.xml** files included in User State Migration Tool (USMT) and then modify the copies. Never modify the original **.xml** files.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Microsoft recommends to always make copies of the **.xml** files included in User State Migration Tool (USMT) and then modify the copies. Never modify the original **.xml** files.
|
||||
|
||||
The `MigXML.xsd` file can be used to help write and validate the **.xml** files. For more information about how to modify these files, see [USMT XML Reference](usmt-xml-reference.md).
|
||||
The `MigXML.xsd` file can be used to help write and validate the **.xml** files. For more information about how to modify these files, see [USMT XML Reference](usmt-xml-reference.md).
|
||||
|
||||
1. Create a [Config.xml File](usmt-configxml-file.md) if to exclude any components from the migration. To create this file, run the `ScanState.exe` command with the following options:
|
||||
|
||||
- [/genconfig](usmt-scanstate-syntax.md#migration-rule-options).
|
||||
- [/i](usmt-scanstate-syntax.md#migration-rule-options) - as arguments specify the **.xml** files that are being used with `ScanState.exe`.
|
||||
|
||||
For example, the following command creates a `Config.xml` file by using the `MigDocs.xml` and `MigApp.xml` files:
|
||||
For example, the following command creates a `Config.xml` file by using the `MigDocs.xml` and `MigApp.xml` files:
|
||||
|
||||
```cmd
|
||||
ScanState.exe /genconfig:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:ScanState.log
|
||||
```
|
||||
```cmd
|
||||
ScanState.exe /genconfig:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:ScanState.log
|
||||
```
|
||||
|
||||
1. Open the `Config.xml` that was generated in the previous step. Review the migration state of each of the components listed in the `Config.xml` file. If necessary, edit the `Config.xml` file and specify `migrate=no` for any components that don't need to be migrated.
|
||||
|
||||
@ -57,19 +57,19 @@ This article outlines the general process to follow to migrate files and setting
|
||||
|
||||
1. Close all applications. If some applications are running when the `ScanState.exe` command is run, USMT might not migrate all of the specified data. For example, if Microsoft Office Outlook is open, USMT might not migrate PST files.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> USMT fails if it can't migrate a file or setting unless the `/c` option is specified. When the `/c` option is specified, USMT ignores the errors, and logs an error every time that it encounters a file that is being used that USMT didn't migrate. The `<ErrorControl>` section in the `Config.xml` file can be used to specify which errors should be ignored, and which should cause the migration to fail.
|
||||
> [!NOTE]
|
||||
>
|
||||
> USMT fails if it can't migrate a file or setting unless the `/c` option is specified. When the `/c` option is specified, USMT ignores the errors, and logs an error every time that it encounters a file that is being used that USMT didn't migrate. The `<ErrorControl>` section in the `Config.xml` file can be used to specify which errors should be ignored, and which should cause the migration to fail.
|
||||
|
||||
1. Run the `ScanState.exe` command on the source computer to collect files and settings. All of the **.xml** files that the `ScanState.exe` command needs to use should be specified. For example,
|
||||
|
||||
```cmd
|
||||
ScanState.exe \\server\migration\mystore /config:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:ScanState.log
|
||||
```
|
||||
```cmd
|
||||
ScanState.exe \\server\migration\mystore /config:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:ScanState.log
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> The `ScanState.exe` command must be run in **Administrator** mode on the source computer. To run in **Administrator** mode, right-click **Command Prompt**, and then select **Run As Administrator**. For more information about how the `ScanState.exe` command processes and stores the data, see [How USMT Works](usmt-how-it-works.md).
|
||||
> [!NOTE]
|
||||
>
|
||||
> The `ScanState.exe` command must be run in **Administrator** mode on the source computer. To run in **Administrator** mode, right-click **Command Prompt**, and then select **Run As Administrator**. For more information about how the `ScanState.exe` command processes and stores the data, see [How USMT Works](usmt-how-it-works.md).
|
||||
|
||||
1. Run the `UsmtUtils.exe` command with the `/Verify` option to ensure that the created store isn't corrupted.
|
||||
|
||||
@ -79,26 +79,26 @@ This article outlines the general process to follow to migrate files and setting
|
||||
|
||||
1. Install all applications that were on the source computer. Although it isn't always required, Microsoft recommends installing all applications on the destination computer before restoring the user state. Installing all applications before restoring user state makes sure that migrated settings are preserved.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> The application version that is installed on the destination computer should be the same version as the one on the source computer. USMT doesn't support migrating the settings for an older version of an application to a newer version. The exception for this rule is Microsoft Office. USMT can migrate from an older version of Microsoft Office to a newer version of Microsoft Office.
|
||||
> [!NOTE]
|
||||
>
|
||||
> The application version that is installed on the destination computer should be the same version as the one on the source computer. USMT doesn't support migrating the settings for an older version of an application to a newer version. The exception for this rule is Microsoft Office. USMT can migrate from an older version of Microsoft Office to a newer version of Microsoft Office.
|
||||
|
||||
1. Close all applications. If some applications are running when the `LoadState.exe` command runs, USMT might not migrate all of the specified data. For example, if Microsoft Office Outlook is open, USMT might not migrate PST files.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Use `/c` to continue the migration if errors are encountered. Use the `<ErrorControl>` section in the `Config.xml` file to specify which errors should be ignored, and which errors should cause the migration to fail.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Use `/c` to continue the migration if errors are encountered. Use the `<ErrorControl>` section in the `Config.xml` file to specify which errors should be ignored, and which errors should cause the migration to fail.
|
||||
|
||||
1. Run the `LoadState.exe` command on the destination computer. Specify the same set of **.xml** files that were specified when the `ScanState.exe` command was used. However, the `Config.xml` file doesn't always need to be specified. The `Config.xml` file only needs to be specified to exclude some of the files and settings that were migrated to the store. For example, the **Documents** folder was migrated to the store, but doesn't need to be migrated to the destination computer. For example, modify the `Config.xml` file and specify the updated file by using the `LoadState.exe` command. Then, the `LoadState.exe` command migrates only the files and settings that need to be migrated. For more information about how the `LoadState.exe` command processes and migrates data, see [How USMT Works](usmt-how-it-works.md).
|
||||
|
||||
For example, the following command migrates the files and settings:
|
||||
For example, the following command migrates the files and settings:
|
||||
|
||||
```cmd
|
||||
LoadState.exe \\server\migration\mystore /config:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:LoadState.log
|
||||
```
|
||||
```cmd
|
||||
LoadState.exe \\server\migration\mystore /config:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:LoadState.log
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Run the `LoadState.exe` command in administrator mode. To do this, right-click **Command Prompt**, and then select **Run As Administrator**.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Run the `LoadState.exe` command in administrator mode. To do this, right-click **Command Prompt**, and then select **Run As Administrator**.
|
||||
|
||||
1. Sign out after running the `LoadState.exe` command. Some settings, such as fonts, wallpaper, and screen saver settings, won't take effect until the next time that the user logs on.
|
||||
|
||||
@ -16,7 +16,7 @@ When planning for your migration, you should identify which operating system set
|
||||
|
||||
- **Appearance**
|
||||
|
||||
The appearance factor includes items such as wallpaper, colors, sounds, and the location of the taskbar.
|
||||
The appearance factor includes items such as wallpaper, colors, sounds, and the location of the taskbar.
|
||||
|
||||
- **Action**
|
||||
|
||||
@ -28,11 +28,11 @@ When planning for your migration, you should identify which operating system set
|
||||
|
||||
- **Internet**
|
||||
|
||||
The Internet factor includes the settings that let you connect to the Internet and control how your browser operates. The settings include items such as your home page URL, favorites, bookmarks, cookies, security settings, and proxy settings. These settings might not be supported in all browsers.
|
||||
The Internet factor includes the settings that let you connect to the Internet and control how your browser operates. The settings include items such as your home page URL, favorites, bookmarks, cookies, security settings, and proxy settings. These settings might not be supported in all browsers.
|
||||
|
||||
- **Mail**
|
||||
|
||||
The mail factor includes the information that you need to connect to your mail server, your signature file, views, mail rules, local mail, and contacts.
|
||||
The mail factor includes the information that you need to connect to your mail server, your signature file, views, mail rules, local mail, and contacts.
|
||||
|
||||
To help determine which settings to migrate, consider any previous migration experiences and the results of any conducted surveys and tests. Also consider the number of help-desk calls related to operating-system settings from the past, and are able to handle in the future. Also decide how much of the new operating-system functionality needs to be taken advantage of.
|
||||
|
||||
|
||||
@ -46,8 +46,9 @@ For more information about previous releases of the USMT tools, see [User State
|
||||
|
||||
## Credentials
|
||||
|
||||
- **Run as administrator**
|
||||
When manually running the **ScanState** and **LoadState** tools, you must run them from an elevated command prompt to ensure that all specified users are migrated. If you don't run USMT from an elevated prompt, only the user profile that is logged on is included in the migration.
|
||||
- **Run as administrator.**
|
||||
|
||||
When manually running the **ScanState** and **LoadState** tools, you must run them from an elevated command prompt to ensure that all specified users are migrated. If you don't run USMT from an elevated prompt, only the user profile that is logged on is included in the migration.
|
||||
|
||||
To open an elevated command prompt:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user