deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-29 05:37:22 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'refs/remotes/origin/op-cleanup-eross-msft'

Browse Source
This commit is contained in:
LizRoss 2016-04-08 09:55:55 -07:00
commit 3a36ad6d96
5 changed files with 32 additions and 168 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
windows/deploy/getting-started-with-the-user-state-migration-tool.md
View File

@ -9,22 +9,16 @@ author: CFaw
--- ---
# Getting Started with the User State Migration Tool (USMT) # Getting Started with the User State Migration Tool (USMT)
This topic outlines the general process that you should follow to migrate files and settings. This topic outlines the general process that you should follow to migrate files and settings.
## In this Topic ## In this Topic
- [Step 1: Plan Your Migration](#step-1-plan-your-migration)
- [Step 2: Collect files and settings from the source computer](#step-2-collect-files-and-settings-from-the-source-computer)
- [Step One: Plan Your Migration](#bkmk-planmig) - [Step 3: Prepare the destination computer and restore files and settings](#step-3-prepare-the-destination-computer-and-restore-files-and-settings)
- [Step Two: Collect Files and Settings from the Source Computer](#bkmk-collectfiles)
- [Step Three: Prepare the Destination Computer and Restore Files and Settings](#bkmk-preparedestination)
## <a href="" id="bkmk-planmig"></a>Step One: Plan Your Migration
## Step 1: Plan your migration
1. [Plan Your Migration](usmt-plan-your-migration.md). Depending on whether your migration scenario is refreshing or replacing computers, you can choose an online migration or an offline migration using Windows Preinstallation Environment (WinPE) or the files in the Windows.old directory. For more information, see [Common Migration Scenarios](usmt-common-migration-scenarios.md). 1. [Plan Your Migration](usmt-plan-your-migration.md). Depending on whether your migration scenario is refreshing or replacing computers, you can choose an online migration or an offline migration using Windows Preinstallation Environment (WinPE) or the files in the Windows.old directory. For more information, see [Common Migration Scenarios](usmt-common-migration-scenarios.md).
2. [Determine What to Migrate](usmt-determine-what-to-migrate.md). Data you might consider migrating includes end-user information, applications settings, operating-system settings, files, folders, and registry keys. 2. [Determine What to Migrate](usmt-determine-what-to-migrate.md). Data you might consider migrating includes end-user information, applications settings, operating-system settings, files, folders, and registry keys.
@ -37,9 +31,7 @@ This topic outlines the general process that you should follow to migrate files
**Important**   **Important**  
We recommend that you always make and modify copies of the .xml files included in User State Migration Tool (USMT) 10.0. Never modify the original .xml files. We recommend that you always make and modify copies of the .xml files included in User State Migration Tool (USMT) 10.0. Never modify the original .xml files.
 
You can use the MigXML.xsd file to help you write and validate the .xml files. For more information about how to modify these files, see [USMT XML Reference](usmt-xml-reference.md). You can use the MigXML.xsd file to help you write and validate the .xml files. For more information about how to modify these files, see [USMT XML Reference](usmt-xml-reference.md).
6. Create a [Config.xml File](usmt-configxml-file.md) if you want to exclude any components from the migration. To create this file, use the [ScanState Syntax](usmt-scanstate-syntax.md) option together with the other .xml files when you use the **ScanState** command. For example, the following command creates a Config.xml file by using the MigDocs and MigApp.xml files: 6. Create a [Config.xml File](usmt-configxml-file.md) if you want to exclude any components from the migration. To create this file, use the [ScanState Syntax](usmt-scanstate-syntax.md) option together with the other .xml files when you use the **ScanState** command. For example, the following command creates a Config.xml file by using the MigDocs and MigApp.xml files:
@ -48,9 +40,7 @@ This topic outlines the general process that you should follow to migrate files
7. Review the migration state of the components listed in the Config.xml file, and specify `migrate=no` for any components that you do not want to migrate. 7. Review the migration state of the components listed in the Config.xml file, and specify `migrate=no` for any components that you do not want to migrate.
## <a href="" id="bkmk-collectfiles"></a>Step Two: Collect Files and Settings from the Source Computer ## Step 2: Collect files and settings from the source computer
1. Back up the source computer. 1. Back up the source computer.
2. Close all applications. If some applications are running when you run the **ScanState** command, USMT might not migrate all of the specified data. For example, if Microsoft® Office Outlook® is open, USMT might not migrate PST files. 2. Close all applications. If some applications are running when you run the **ScanState** command, USMT might not migrate all of the specified data. For example, if Microsoft® Office Outlook® is open, USMT might not migrate PST files.
@ -58,8 +48,6 @@ This topic outlines the general process that you should follow to migrate files
**Note**   **Note**  
USMT will fail if it cannot migrate a file or setting unless you specify the **/C** option. When you specify the **/C** option, USMT will ignore the errors, and log an error every time that it encounters a file that is being used that USMT did not migrate. You can use the **&lt;ErrorControl&gt;** section in the Config.xml file to specify which errors should be ignored, and which should cause the migration to fail. USMT will fail if it cannot migrate a file or setting unless you specify the **/C** option. When you specify the **/C** option, USMT will ignore the errors, and log an error every time that it encounters a file that is being used that USMT did not migrate. You can use the **&lt;ErrorControl&gt;** section in the Config.xml file to specify which errors should be ignored, and which should cause the migration to fail.
 
3. Run the **ScanState** command on the source computer to collect files and settings. You should specify all of the .xml files that you want the **ScanState** command to use. For example, 3. Run the **ScanState** command on the source computer to collect files and settings. You should specify all of the .xml files that you want the **ScanState** command to use. For example,
`scanstate \\server\migration\mystore /config:config.xml /i:migdocs.xml /i:migapp.xml /v:13 /l:scan.log` `scanstate \\server\migration\mystore /config:config.xml /i:migdocs.xml /i:migapp.xml /v:13 /l:scan.log`
@ -67,13 +55,9 @@ This topic outlines the general process that you should follow to migrate files
**Note**   **Note**  
If the source computer is running Windows 7, or Windows 8, you must run the **ScanState** command in **Administrator** mode. To run in **Administrator** mode, right-click **Command Prompt**, and then click **Run As Administrator**. If the source computer is running Windows XP, you must run the **ScanState** command from an account that has administrative credentials. For more information about the how the **ScanState** command processes and stores the data, see [How USMT Works](usmt-how-it-works.md). If the source computer is running Windows 7, or Windows 8, you must run the **ScanState** command in **Administrator** mode. To run in **Administrator** mode, right-click **Command Prompt**, and then click **Run As Administrator**. If the source computer is running Windows XP, you must run the **ScanState** command from an account that has administrative credentials. For more information about the how the **ScanState** command processes and stores the data, see [How USMT Works](usmt-how-it-works.md).
 
4. Run the **USMTUtils** command with the **/Verify** option to ensure that the store you created is not corrupted. 4. Run the **USMTUtils** command with the **/Verify** option to ensure that the store you created is not corrupted.
## <a href="" id="bkmk-preparedestination"></a>Step Three: Prepare the Destination Computer and Restore Files and Settings ## Step 3: Prepare the destination computer and restore files and settings
1. Install the operating system on the destination computer. 1. Install the operating system on the destination computer.
2. Install all applications that were on the source computer. Although it is not always required, we recommend installing all applications on the destination computer before you restore the user state. This makes sure that migrated settings are preserved. 2. Install all applications that were on the source computer. Although it is not always required, we recommend installing all applications on the destination computer before you restore the user state. This makes sure that migrated settings are preserved.
@ -81,15 +65,11 @@ This topic outlines the general process that you should follow to migrate files
**Note**   **Note**  
The application version that is installed on the destination computer should be the same version as the one on the source computer. USMT does not support migrating the settings for an older version of an application to a newer version. The exception to this is Microsoft® Office, which USMT can migrate from an older version to a newer version. The application version that is installed on the destination computer should be the same version as the one on the source computer. USMT does not support migrating the settings for an older version of an application to a newer version. The exception to this is Microsoft® Office, which USMT can migrate from an older version to a newer version.
 
3. Close all applications. If some applications are running when you run the **LoadState** command, USMT might not migrate all of the specified data. For example, if Microsoft Office Outlook is open, USMT might not migrate PST files. 3. Close all applications. If some applications are running when you run the **LoadState** command, USMT might not migrate all of the specified data. For example, if Microsoft Office Outlook is open, USMT might not migrate PST files.
**Note**   **Note**  
Use **/C** to continue your migration if errors are encountered, and use the **&lt;ErrorControl&gt;** section in the Config.xml file to specify which errors should be ignored, and which errors should cause the migration to fail. Use **/C** to continue your migration if errors are encountered, and use the **&lt;ErrorControl&gt;** section in the Config.xml file to specify which errors should be ignored, and which errors should cause the migration to fail.
 
4. Run the **LoadState** command on the destination computer. Specify the same set of .xml files that you specified when you used the **ScanState** command. However, you do not have to specify the Config.xml file, unless you want to exclude some of the files and settings that you migrated to the store. For example, you might want to migrate the My Documents folder to the store, but not to the destination computer. To do this, modify the Config.xml file and specify the updated file by using the **LoadState** command. Then, the **LoadState** command will migrate only the files and settings that you want to migrate. For more information about the how the **LoadState** command processes and migrates data, see [How USMT Works](usmt-how-it-works.md). 4. Run the **LoadState** command on the destination computer. Specify the same set of .xml files that you specified when you used the **ScanState** command. However, you do not have to specify the Config.xml file, unless you want to exclude some of the files and settings that you migrated to the store. For example, you might want to migrate the My Documents folder to the store, but not to the destination computer. To do this, modify the Config.xml file and specify the updated file by using the **LoadState** command. Then, the **LoadState** command will migrate only the files and settings that you want to migrate. For more information about the how the **LoadState** 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:
@ -99,15 +79,4 @@ This topic outlines the general process that you should follow to migrate files
**Note**   **Note**  
Run the **LoadState** command in administrator mode. To do this, right-click **Command Prompt**, and then click **Run As Administrator**. Run the **LoadState** command in administrator mode. To do this, right-click **Command Prompt**, and then click **Run As Administrator**.
  5. Log off after you run the **LoadState** command. Some settings (for example, fonts, wallpaper, and screen saver settings) will not take effect until the next time that the user logs on.
5. Log off after you run the **LoadState** command. Some settings (for example, fonts, wallpaper, and screen saver settings) will not take effect until the next time that the user logs on.
 
 

74
windows/deploy/usmt-how-to.md
View File

@ -9,70 +9,22 @@ author: CFaw
--- ---
# User State Migration Tool (USMT) How-to topics # User State Migration Tool (USMT) How-to topics
The following table lists topics that describe how to use User State Migration Tool (USMT) 10.0 to perform specific tasks. The following table lists topics that describe how to use User State Migration Tool (USMT) 10.0 to perform specific tasks.
## In This Section ## In This Section
|Topic |Description|
<table> |------|-----------|
<colgroup> |[Exclude Files and Settings](usmt-exclude-files-and-settings.md)|Create a custom .xml file to exclude files, file types, folders, or registry settings from your migration.|
<col width="50%" /> |[Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md)|Recover files from a compressed migration store after installing the operating system.|
<col width="50%" /> |[Include Files and Settings](usmt-include-files-and-settings.md)|Create a custom .xml file to include files, file types, folders, or registry settings in your migration.|
</colgroup> |[Migrate Application Settings](migrate-application-settings.md)|Migrate the settings of an application that the MigApp.xml file does not include by default.|
<tbody> |[Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md)|Migrate Encrypting File System (EFS) certificates by using USMT.|
<tr class="odd"> |[Migrate User Accounts](usmt-migrate-user-accounts.md)|Specify the users to include and exclude in your migration.|
<td align="left"><p>[Exclude Files and Settings](usmt-exclude-files-and-settings.md)</p></td> |[Reroute Files and Settings](usmt-reroute-files-and-settings.md)|Create a custom .xml file to reroute files and settings during a migration.|
<td align="left"><p>Create a custom .xml file to exclude files, file types, folders, or registry settings from your migration.</p></td> |[Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md)|Determine whether a compressed migration store is intact, or whether it contains corrupt files or a corrupt catalog.|
</tr>
<tr class="even">
<td align="left"><p>[Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md)</p></td>
<td align="left"><p>Recover files from a compressed migration store after installing the operating system.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Include Files and Settings](usmt-include-files-and-settings.md)</p></td>
<td align="left"><p>Create a custom .xml file to include files, file types, folders, or registry settings in your migration.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Migrate Application Settings](migrate-application-settings.md)</p></td>
<td align="left"><p>Migrate the settings of an application that the MigApp.xml file does not include by default.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md)</p></td>
<td align="left"><p>Migrate Encrypting File System (EFS) certificates by using USMT.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Migrate User Accounts](usmt-migrate-user-accounts.md)</p></td>
<td align="left"><p>Specify the users to include and exclude in your migration.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Reroute Files and Settings](usmt-reroute-files-and-settings.md)</p></td>
<td align="left"><p>Create a custom .xml file to reroute files and settings during a migration.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md)</p></td>
<td align="left"><p>Determine whether a compressed migration store is intact, or whether it contains corrupt files or a corrupt catalog.</p></td>
</tr>
</tbody>
</table>
 
## Related topics ## Related topics
- [User State Migration Tool (USMT) Overview Topics](usmt-topics.md)
- [User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)
[User State Migration Tool (USMT) Overview Topics](usmt-topics.md) - [User State Migration Toolkit (USMT) Reference](usmt-reference.md)
[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)
[User State Migration Toolkit (USMT) Reference](usmt-reference.md)
 
 

10
windows/deploy/usmt-overview.md
View File

@ -9,8 +9,6 @@ author: CFaw
--- ---
# User State Migration Tool (USMT) Overview # User State Migration Tool (USMT) Overview
You can use User State Migration Tool (USMT) 10.0 to streamline and simplify user state migration during large deployments of Windows operating systems. USMT captures user accounts, user files, operating system settings, and application settings, and then migrates them to a new Windows installation. You can use USMT for both PC replacement and PC refresh migrations. For more information, see [Common Migration Scenarios](usmt-common-migration-scenarios.md). You can use User State Migration Tool (USMT) 10.0 to streamline and simplify user state migration during large deployments of Windows operating systems. USMT captures user accounts, user files, operating system settings, and application settings, and then migrates them to a new Windows installation. You can use USMT for both PC replacement and PC refresh migrations. For more information, see [Common Migration Scenarios](usmt-common-migration-scenarios.md).
USMT enables you to do the following: USMT enables you to do the following:
@ -22,8 +20,6 @@ USMT enables you to do the following:
- Perform offline migrations. You can run migrations offline by using the ScanState command in Windows Preinstallation Environment (WinPE) or you can perform migrations from previous installations of Windows contained in Windows.old directories. For more information about migration types, see [Choose a Migration Store Type](usmt-choose-migration-store-type.md) and [Offline Migration Reference](offline-migration-reference.md). - Perform offline migrations. You can run migrations offline by using the ScanState command in Windows Preinstallation Environment (WinPE) or you can perform migrations from previous installations of Windows contained in Windows.old directories. For more information about migration types, see [Choose a Migration Store Type](usmt-choose-migration-store-type.md) and [Offline Migration Reference](offline-migration-reference.md).
## Benefits ## Benefits
USMT provides the following benefits to businesses that are deploying Windows operating systems: USMT provides the following benefits to businesses that are deploying Windows operating systems:
- Safely migrates user accounts, operating system and application settings. - Safely migrates user accounts, operating system and application settings.
@ -39,8 +35,6 @@ USMT provides the following benefits to businesses that are deploying Windows op
- Increases employee satisfaction with the migration experience. - Increases employee satisfaction with the migration experience.
## Limitations ## Limitations
USMT is intended for administrators who are performing large-scale automated deployments. If you are only migrating the user states of a few computers, you can use [Windows Easy Transfer](http://go.microsoft.com/fwlink/p/?LinkId=140248). USMT is intended for administrators who are performing large-scale automated deployments. If you are only migrating the user states of a few computers, you can use [Windows Easy Transfer](http://go.microsoft.com/fwlink/p/?LinkId=140248).
There are some scenarios in which the use of USMT is not recommended. These include: There are some scenarios in which the use of USMT is not recommended. These include:
@ -50,9 +44,7 @@ There are some scenarios in which the use of USMT is not recommended. These incl
- Migrations that require customization on a machine-by-machine basis. - Migrations that require customization on a machine-by-machine basis.
## Related topics ## Related topics
- [User State Migration Tool (USMT) Technical Reference](usmt-technical-reference.md)
[User State Migration Tool (USMT) Technical Reference](usmt-technical-reference.md)
   

49
windows/deploy/usmt-topics.md
View File

@ -9,50 +9,17 @@ author: CFaw
--- ---
# User State Migration Tool (USMT) Overview Topics # User State Migration Tool (USMT) Overview Topics
The User State Migration Tool (USMT) 10.0 provides a highly customizable user-profile migration experience for IT professionals. USMT includes three command-line tools: ScanState.exe, LoadState.exe, and UsmtUtils.exe. USMT also includes a set of three modifiable .xml files: MigApp.xml, MigDocs.xml, and MigUser.xml. Additionally, you can create custom .xml files to support your migration needs. You can also create a Config.xml file to specify files or settings to exclude from the migration. The User State Migration Tool (USMT) 10.0 provides a highly customizable user-profile migration experience for IT professionals. USMT includes three command-line tools: ScanState.exe, LoadState.exe, and UsmtUtils.exe. USMT also includes a set of three modifiable .xml files: MigApp.xml, MigDocs.xml, and MigUser.xml. Additionally, you can create custom .xml files to support your migration needs. You can also create a Config.xml file to specify files or settings to exclude from the migration.
## In This Section ## In This Section
|Topic |Description|
<table> |------|-----------|
<colgroup> |[User State Migration Tool (USMT) Overview](usmt-overview.md)|Describes the benefits and limitations of using USMT.|
<col width="50%" /> |[Getting Started with the User State Migration Tool (USMT)](getting-started-with-the-user-state-migration-tool.md)|Describes the general process to follow to migrate files and settings, and provides links to more information.|
<col width="50%" /> |[Windows Upgrade and Migration Considerations](windows-upgrade-and-migration-considerations.md)|Discusses the Microsoft® tools you can use to move files and settings between installations, as well as special considerations for performing an upgrade or migration.|
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>[User State Migration Tool (USMT) Overview](usmt-overview.md)</p></td>
<td align="left"><p>Describes the benefits and limitations of using USMT.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Getting Started with the User State Migration Tool (USMT)](getting-started-with-the-user-state-migration-tool.md)</p></td>
<td align="left"><p>Describes the general process to follow to migrate files and settings, and provides links to more information.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Windows Upgrade and Migration Considerations](windows-upgrade-and-migration-considerations.md)</p></td>
<td align="left"><p>Discusses the Microsoft® tools you can use to move files and settings between installations, as well as special considerations for performing an upgrade or migration.</p></td>
</tr>
</tbody>
</table>
 
## Related topics ## Related topics
- [User State Migration Tool (USMT) How-to topics](usmt-how-to.md)
- [User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)
[User State Migration Tool (USMT) How-to topics](usmt-how-to.md) - [User State Migration Toolkit (USMT) Reference](usmt-reference.md)
[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)
[User State Migration Toolkit (USMT) Reference](usmt-reference.md)
 
 

20
windows/deploy/windows-upgrade-and-migration-considerations.md
View File

@ -9,18 +9,12 @@ author: CFaw
--- ---
# Windows Upgrade and Migration Considerations # Windows Upgrade and Migration Considerations
Files and application settings can be migrated to new hardware running the Windows® operating system, or they can be maintained during an operating system upgrade on the same computer. This topic summarizes the Microsoft® tools you can use to move files and settings between installations in addition to special considerations for performing an upgrade or migration. Files and application settings can be migrated to new hardware running the Windows® operating system, or they can be maintained during an operating system upgrade on the same computer. This topic summarizes the Microsoft® tools you can use to move files and settings between installations in addition to special considerations for performing an upgrade or migration.
## Upgrade from a Previous Version of Windows ## Upgrade from a Previous Version of Windows
You can upgrade from an earlier version of Windows, which means you can install the new version of Windows and retain your applications, files, and settings as they were in your previous version of Windows. If you decide to perform a custom installation of Windows instead of an upgrade, your applications and settings will not be maintained. Your personal files, and all Windows files and directories, will be moved to a Windows.old folder. You can access your data in the Windows.old folder after Windows Setup is complete. You can upgrade from an earlier version of Windows, which means you can install the new version of Windows and retain your applications, files, and settings as they were in your previous version of Windows. If you decide to perform a custom installation of Windows instead of an upgrade, your applications and settings will not be maintained. Your personal files, and all Windows files and directories, will be moved to a Windows.old folder. You can access your data in the Windows.old folder after Windows Setup is complete.
## Migrate Files and Settings ## Migrate Files and Settings
Migration tools are available to transfer settings from one computer that is running Windows to another. These tools transfer only the program settings, not the programs themselves. Migration tools are available to transfer settings from one computer that is running Windows to another. These tools transfer only the program settings, not the programs themselves.
For more information about application compatibility, see the [Application Compatibility Toolkit (ACT)](http://go.microsoft.com/fwlink/p/?LinkId=131349). For more information about application compatibility, see the [Application Compatibility Toolkit (ACT)](http://go.microsoft.com/fwlink/p/?LinkId=131349).
@ -28,36 +22,28 @@ For more information about application compatibility, see the [Application Compa
The User State Migration Tool (USMT) 10.0 is an application intended for administrators who are performing large-scale automated deployments. For deployment to a small number of computers or for individually customized deployments, you can use Windows Easy Transfer. The User State Migration Tool (USMT) 10.0 is an application intended for administrators who are performing large-scale automated deployments. For deployment to a small number of computers or for individually customized deployments, you can use Windows Easy Transfer.
### Migrate with Windows Easy Transfer ### Migrate with Windows Easy Transfer
Windows Easy Transfer is a software wizard for transferring files and settings from one computer that is running Windows to another. It helps you select what to move to your new computer, enables you to set which migration method to use, and then performs the transfer. When the transfer has completed, Windows Easy Transfer Reports shows you what was transferred and provides a list of programs you might want to install on your new computer, in addition to links to other programs you might want to download. Windows Easy Transfer is a software wizard for transferring files and settings from one computer that is running Windows to another. It helps you select what to move to your new computer, enables you to set which migration method to use, and then performs the transfer. When the transfer has completed, Windows Easy Transfer Reports shows you what was transferred and provides a list of programs you might want to install on your new computer, in addition to links to other programs you might want to download.
With Windows Easy Transfer, files and settings can be transferred using a network share, a USB flash drive (UFD), or the Easy Transfer cable. However, you cannot use a regular universal serial bus (USB) cable to transfer files and settings with Windows Easy Transfer. An Easy Transfer cable can be purchased on the Web, from your computer manufacturer, or at an electronics store. With Windows Easy Transfer, files and settings can be transferred using a network share, a USB flash drive (UFD), or the Easy Transfer cable. However, you cannot use a regular universal serial bus (USB) cable to transfer files and settings with Windows Easy Transfer. An Easy Transfer cable can be purchased on the Web, from your computer manufacturer, or at an electronics store.
### Migrate with the User State Migration Tool ### Migrate with the User State Migration Tool
You can use USMT to automate migration during large deployments of the Windows operating system. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they are migrated. You can use USMT for both *side-by-side* migrations, where one piece of hardware is being replaced, or *wipe-and-load* (or *refresh*) migrations, when only the operating system is being upgraded. You can use USMT to automate migration during large deployments of the Windows operating system. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they are migrated. You can use USMT for both *side-by-side* migrations, where one piece of hardware is being replaced, or *wipe-and-load* (or *refresh*) migrations, when only the operating system is being upgraded.
## Upgrade and Migration Considerations ## Upgrade and Migration Considerations
Whether you are upgrading or migrating to a new version of Windows, you must be aware of the following issues and considerations: Whether you are upgrading or migrating to a new version of Windows, you must be aware of the following issues and considerations:
### Application Compatibility ### Application Compatibility
For more information about application compatibility in Windows, see the [Application Compatibility Toolkit (ACT)](http://go.microsoft.com/fwlink/p/?LinkId=131349). For more information about application compatibility in Windows, see the [Application Compatibility Toolkit (ACT)](http://go.microsoft.com/fwlink/p/?LinkId=131349).
### Multilingual Windows Image Upgrades ### Multilingual Windows Image Upgrades
When performing multilingual Windows upgrades, cross-language upgrades are not supported by USMT. If you are upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default user interface (UI) language. For example, if English is the default but you have a Spanish language pack installed, you can upgrade or migrate only to English. When performing multilingual Windows upgrades, cross-language upgrades are not supported by USMT. If you are upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default user interface (UI) language. For example, if English is the default but you have a Spanish language pack installed, you can upgrade or migrate only to English.
If you are using a single-language Windows image that matches the system default UI language of your multilingual operating system, the migration will work. However, all of the language packs will be removed, and you will have to reinstall them after the upgrade is completed. If you are using a single-language Windows image that matches the system default UI language of your multilingual operating system, the migration will work. However, all of the language packs will be removed, and you will have to reinstall them after the upgrade is completed.
### Errorhandler.cmd ### Errorhandler.cmd
When upgrading from an earlier version of Windows, if you intend to use Errorhandler.cmd, you must copy this file into the %WINDIR%\\Setup\\Scripts directory on the old installation. This makes sure that if there are errors during the down-level phase of Windows Setup, the commands in Errorhandler.cmd will run. When upgrading from an earlier version of Windows, if you intend to use Errorhandler.cmd, you must copy this file into the %WINDIR%\\Setup\\Scripts directory on the old installation. This makes sure that if there are errors during the down-level phase of Windows Setup, the commands in Errorhandler.cmd will run.
### Data Drive ACL Migration ### Data Drive ACL Migration
During the configuration pass of Windows Setup, the root access control list (ACL) on drives formatted for NTFS that do not appear to have an operating system will be changed to the default Windows XP ACL format. The ACLs on these drives are changed to enable authenticated users to modify access on folders and files. During the configuration pass of Windows Setup, the root access control list (ACL) on drives formatted for NTFS that do not appear to have an operating system will be changed to the default Windows XP ACL format. The ACLs on these drives are changed to enable authenticated users to modify access on folders and files.
Changing the ACLs may affect the performance of Windows Setup if the default Windows XP ACLs are applied to a partition with a large amount of data. Because of these performance concerns, you can change the following registry value to disable this feature: Changing the ACLs may affect the performance of Windows Setup if the default Windows XP ACLs are applied to a partition with a large amount of data. Because of these performance concerns, you can change the following registry value to disable this feature:
@ -68,12 +54,10 @@ Type: REG_DWORD
Value: "DDACLSys_Disabled" = 1 Value: "DDACLSys_Disabled" = 1
``` ```
This feature is disabled if this registry key value exists and is configured to 1. This feature is disabled if this registry key value exists and is configured to `1`.
## Related topics ## Related topics
- [User State Migration Tool (USMT) Overview Topics](usmt-topics.md)
[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)