diff --git a/windows/deploy/TOC.md b/windows/deploy/TOC.md index 2c908f1104..86ea7532e1 100644 --- a/windows/deploy/TOC.md +++ b/windows/deploy/TOC.md @@ -80,57 +80,57 @@ ##### [Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md) ##### [Scenario 3: KMS Client Activation](scenario-kms-activation-vamt.md) #### [VAMT Known Issues](vamt-known-issues.md) -### [User State Migration Tool (USMT) Technical Reference](user-state-migration-tool--usmt--technical-reference.md) -#### [User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md) -##### [User State Migration Tool (USMT) Overview](user-state-migration-tool--usmt--overview.md) -##### [Getting Started with the User State Migration Tool (USMT)](getting-started-with-the-user-state-migration-tool--usmt-.md) -##### [Windows Upgrade and Migration Considerations](windows-upgrade-and-migration-considerations-win8.md) -#### [User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md) -##### [Exclude Files and Settings](exclude-files-and-settings-usmt.md) -##### [Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md) -##### [Include Files and Settings](include-files-and-settings-usmt.md) +### [User State Migration Tool (USMT) Technical Reference](usmt-technical-reference.md) +#### [User State Migration Tool (USMT) Overview Topics](usmt-topics.md) +##### [User State Migration Tool (USMT) Overview](usmt-overview.md) +##### [Getting Started with the User State Migration Tool (USMT)](getting-started-with-the-user-state-migration-tool.md) +##### [Windows Upgrade and Migration Considerations](windows-upgrade-and-migration-considerations.md) +#### [User State Migration Tool (USMT) How-to topics](usmt-how-to.md) +##### [Exclude Files and Settings](usmt-exclude-files-and-settings.md) +##### [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md) +##### [Include Files and Settings](usmt-include-files-and-settings.md) ##### [Migrate Application Settings](migrate-application-settings.md) -##### [Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md) -##### [Migrate User Accounts](migrate-user-accounts-usmt.md) -##### [Reroute Files and Settings](reroute-files-and-settings-usmt.md) +##### [Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md) +##### [Migrate User Accounts](usmt-migrate-user-accounts.md) +##### [Reroute Files and Settings](usmt-reroute-files-and-settings.md) ##### [Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md) -#### [User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md) -##### [Common Issues](common-issues-usmt-win8.md) -##### [Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) -##### [Log Files](log-files-usmt-win7-usmt-win8.md) -##### [Return Codes](return-codes-usmt-win8.md) -##### [USMT Resources](usmt-resources-usmt-win8.md) -#### [User State Migration Toolkit (USMT) Reference](user-state-migration-toolkit--usmt--reference.md) -##### [USMT Requirements](usmt-requirements-usmt-win7-usmt-win8.md) -##### [USMT Best Practices](usmt-best-practices-usmt-win7-usmt-win8.md) -##### [How USMT Works](how-usmt-works-usmt-win7-usmt-win8.md) -##### [Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) -###### [Common Migration Scenarios](common-migration-scenarios-usmt-win7-usmt-win8.md) -###### [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) -###### [Choose a Migration Store Type](choose-a-migration-store-type-usmt-win7-usmt-win8.md) +#### [User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md) +##### [Common Issues](usmt-common-issues.md) +##### [Frequently Asked Questions](usmt-faq.md) +##### [Log Files](usmt-log-files.md) +##### [Return Codes](usmt-return-codes.md) +##### [USMT Resources](usmt-resources.md) +#### [User State Migration Toolkit (USMT) Reference](usmt-reference.md) +##### [USMT Requirements](usmt-requirements.md) +##### [USMT Best Practices](usmt-best-practices.md) +##### [How USMT Works](usmt-how-it-works.md) +##### [Plan Your Migration](usmt-plan-your-migration.md) +###### [Common Migration Scenarios](usmt-common-migration-scenarios.md) +###### [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md) +###### [Choose a Migration Store Type](usmt-choose-migration-store-type.md) ####### [Migration Store Types Overview](migration-store-types-overview.md) -####### [Estimate Migration Store Size](estimate-migration-store-size-usmt-win7-usmt-win8.md) -####### [Hard-Link Migration Store](hard-link-migration-store-usmt-win8.md) -####### [Migration Store Encryption](migration-store-encryption-usmt-win8.md) -###### [Determine What to Migrate](determine-what-to-migrate-usmt-win7-usmt-win8.md) -####### [Identify Users](identify-users-usmt-win7-usmt-win8.md) -####### [Identify Applications Settings](identify-applications-settings-usmt-win7-usmt-win8.md) -####### [Identify Operating System Settings](identify-operating-system-settings-usmt-win7-usmt-win8.md) -####### [Identify File Types, Files, and Folders](identify-file-types-files-and-folders-usmt-win8.md) -###### [Test Your Migration](test-your-migration-usmt-win7-usmt-win8.md) -##### [User State Migration Tool (USMT) Command-line Syntax](user-state-migration-tool--usmt--command-line-syntax.md) -###### [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) -###### [LoadState Syntax](loadstate-syntax-usmt-win7-usmt-win8.md) -###### [UsmtUtils Syntax](usmtutils-syntax-usmt-win8.md) -##### [USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +####### [Estimate Migration Store Size](usmt-estimate-migration-store-size.md) +####### [Hard-Link Migration Store](usmt-hard-link-migration-store.md) +####### [Migration Store Encryption](usmt-migration-store-encryption.md) +###### [Determine What to Migrate](usmt-determine-what-to-migrate.md) +####### [Identify Users](usmt-identify-users.md) +####### [Identify Applications Settings](usmt-identify-application-settings.md) +####### [Identify Operating System Settings](usmt-identify-operating-system-settings.md) +####### [Identify File Types, Files, and Folders](usmt-identify-file-types-files-and-folders.md) +###### [Test Your Migration](usmt-test-your-migration.md) +##### [User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.md) +###### [ScanState Syntax](usmt-scanstate-syntax.md) +###### [LoadState Syntax](usmt-loadstate-syntax.md) +###### [UsmtUtils Syntax](usmt-utilities.md) +##### [USMT XML Reference](usmt-xml-reference.md) ###### [Understanding Migration XML Files](understanding-migration-xml-files.md) -###### [Config.xml File](configxml-file-usmt-win7-usmt-win8.md) -###### [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) -###### [Custom XML Examples](custom-xml-examples-usmt-win7-usmt-win8.md) -###### [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) -###### [General Conventions](general-conventions-usmt-win7-usmt-win8.md) +###### [Config.xml File](usmt-configxml-file.md) +###### [Customize USMT XML Files](usmt-customize-xml-files.md) +###### [Custom XML Examples](usmt-custom-xml-examples.md) +###### [Conflicts and Precedence](usmt-conflicts-and-precedence.md) +###### [General Conventions](usmt-general-conventions.md) ###### [XML File Requirements](xml-file-requirements.md) -###### [Recognized Environment Variables](recognized-environment-variables-usmt-win7-usmt-win8.md) -###### [XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) +###### [Recognized Environment Variables](usmt-recognized-environment-variables.md) +###### [XML Elements Library](usmt-xml-elements-library.md) ##### [Offline Migration Reference](offline-migration-reference.md) diff --git a/windows/deploy/getting-started-with-the-user-state-migration-tool--usmt-.md b/windows/deploy/getting-started-with-the-user-state-migration-tool.md similarity index 82% rename from windows/deploy/getting-started-with-the-user-state-migration-tool--usmt-.md rename to windows/deploy/getting-started-with-the-user-state-migration-tool.md index 4655b7d762..6cc2bf4352 100644 --- a/windows/deploy/getting-started-with-the-user-state-migration-tool--usmt-.md +++ b/windows/deploy/getting-started-with-the-user-state-migration-tool.md @@ -25,13 +25,13 @@ This topic outlines the general process that you should follow to migrate files ## Step One: Plan Your Migration -1. [Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.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](common-migration-scenarios-usmt-win7-usmt-win8.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](determine-what-to-migrate-usmt-win7-usmt-win8.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. -3. Determine where to store data. Depending on the size of your migration store, you can store the data remotely, locally in a hard-link migration store or on a local external storage device, or directly on the destination computer. For more information, see [Choose a Migration Store Type](choose-a-migration-store-type-usmt-win7-usmt-win8.md). +3. Determine where to store data. Depending on the size of your migration store, you can store the data remotely, locally in a hard-link migration store or on a local external storage device, or directly on the destination computer. For more information, see [Choose a Migration Store Type](usmt-choose-migration-store-type.md). -4. Use the **/GenMigXML** command-line option to determine which files will be included in your migration, and to determine whether any modifications are necessary. For more information see [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) +4. Use the **/GenMigXML** command-line option to determine which files will be included in your migration, and to determine whether any modifications are necessary. For more information see [ScanState Syntax](usmt-scanstate-syntax.md) 5. Modify copies of the Migration.xml and MigDocs.xml files and create custom .xml files, if it is required. To modify the migration behavior, such as migrating the **Documents** folder but not the **Music** folder, you can create a custom .xml file 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. @@ -40,9 +40,9 @@ This topic outlines the general process that you should follow to migrate 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-usmt-win7-usmt-win8.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](configxml-file-usmt-win7-usmt-win8.md) if you want to exclude any components from the migration. To create this file, use the [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.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: `scanstate /genconfig:config.xml /i:migdocs.xml /i:migapp.xml /v:13 /l:scanstate.log` @@ -65,7 +65,7 @@ This topic outlines the general process that you should follow to migrate files `scanstate \\server\migration\mystore /config:config.xml /i:migdocs.xml /i:migapp.xml /v:13 /l:scan.log` **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](how-usmt-works-usmt-win7-usmt-win8.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).   @@ -90,7 +90,7 @@ This topic outlines the general process that you should follow to migrate files   -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](how-usmt-works-usmt-win7-usmt-win8.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: diff --git a/windows/deploy/migrate-application-settings.md b/windows/deploy/migrate-application-settings.md index 8624b4ca16..af79e440f7 100644 --- a/windows/deploy/migrate-application-settings.md +++ b/windows/deploy/migrate-application-settings.md @@ -109,7 +109,7 @@ We recommend that you migrate the settings after you install the application, bu ## Step 4: Create the migration XML component for the application -After you have completed steps 1 through 3, you will need to create a custom migration .xml file that migrates the application based on the information that you now have. You can use the MigApp.xml file as a model because it contains examples of many of the concepts discussed in this topic. You can also see [Custom XML Examples](custom-xml-examples-usmt-win7-usmt-win8.md) for another sample .xml file. +After you have completed steps 1 through 3, you will need to create a custom migration .xml file that migrates the application based on the information that you now have. You can use the MigApp.xml file as a model because it contains examples of many of the concepts discussed in this topic. You can also see [Custom XML Examples](usmt-custom-xml-examples.md) for another sample .xml file. **Note**   We recommend that you create a separate .xml file instead of adding your script to the **MigApp.xml** file. This is because the **MigApp.xml** file is a very large file and it will be difficult to read and edit. In addition, if you reinstall USMT for some reason, the **MigApp.xml** file will be overwritten by the default version of the file and you will lose your customized version. @@ -137,25 +137,25 @@ Your script should do the following: - If you must install the application before migrating the settings, delete any settings that are already on the destination computer using the <`destinationCleanup`> element. -For information about the .xml elements and helper functions, see [XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md). +For information about the .xml elements and helper functions, see [XML Elements Library](usmt-xml-elements-library.md). ## Step 5: Test the application settings migration On a test computer, install the operating system that will be installed on the destination computers. For example, if you are planning on migrating from Windows 7 to Windows 10, install Windows 10 and the application. Next, run LoadState on the test computer and verify that all settings migrate. Make corrections if necessary and repeat the process until all the necessary settings are migrated correctly. -To speed up the time it takes to collect and migrate the data, you can migrate only one user at a time, and you can exclude all other components from the migration except the application that you are testing. To specify only User1 in the migration, type: **/ue:\*\\\* /ui:user1**. For more information, see [Exclude Files and Settings](exclude-files-and-settings-usmt.md) and User options in the [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) topic. To troubleshoot a problem, check the progress log, and the ScanState and LoadState logs, which contain warnings and errors that may point to problems with the migration. +To speed up the time it takes to collect and migrate the data, you can migrate only one user at a time, and you can exclude all other components from the migration except the application that you are testing. To specify only User1 in the migration, type: **/ue:\*\\\* /ui:user1**. For more information, see [Exclude Files and Settings](usmt-exclude-files-and-settings.md) and User options in the [ScanState Syntax](usmt-scanstate-syntax.md) topic. To troubleshoot a problem, check the progress log, and the ScanState and LoadState logs, which contain warnings and errors that may point to problems with the migration. ## Related topics -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md) -[Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) +[Conflicts and Precedence](usmt-conflicts-and-precedence.md) -[XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) +[XML Elements Library](usmt-xml-elements-library.md) -[Log Files](log-files-usmt-win7-usmt-win8.md) +[Log Files](usmt-log-files.md)   diff --git a/windows/deploy/migration-store-types-overview.md b/windows/deploy/migration-store-types-overview.md index ec76f7eaee..cf0c52812e 100644 --- a/windows/deploy/migration-store-types-overview.md +++ b/windows/deploy/migration-store-types-overview.md @@ -39,7 +39,7 @@ The compressed migration store is a single image file that contains all files be A hard-link migration store functions as a map that defines how a collection of bits on the hard disk are “wired” into the file system. You use the new USMT hard-link migration store in the PC Refresh scenario only. This is because the hard-link migration store is maintained on the local computer while the old operating system is removed and the new operating system is installed. Using a hard-link migration store saves network bandwidth and minimizes the server use needed to accomplish the migration. -You use a command-line option,**/hardlink** , to create a hard-link migration store, which functions the same as an uncompressed migration store. Files are not duplicated on the local computer when user state is captured, nor are they duplicated when user state is restored. For more information, see [Hard-Link Migration Store](hard-link-migration-store-usmt-win8.md). +You use a command-line option,**/hardlink** , to create a hard-link migration store, which functions the same as an uncompressed migration store. Files are not duplicated on the local computer when user state is captured, nor are they duplicated when user state is restored. For more information, see [Hard-Link Migration Store](usmt-hard-link-migration-store.md). The following flowchart illustrates the procedural differences between a local migration store and a remote migration store. In this example, a hard-link migration store is used for the local store. @@ -59,12 +59,12 @@ If possible, have users store their data within their %UserProfile%\\My Document ### The /localonly Command-Line Option -You should use this option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify **/LocalOnly**, see [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md). +You should use this option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify **/LocalOnly**, see [ScanState Syntax](usmt-scanstate-syntax.md). ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md)   diff --git a/windows/deploy/offline-migration-reference.md b/windows/deploy/offline-migration-reference.md index 5c0149bf07..6ad60f1704 100644 --- a/windows/deploy/offline-migration-reference.md +++ b/windows/deploy/offline-migration-reference.md @@ -57,7 +57,7 @@ The following user data and settings migrate offline, similar to an online migra - Internet Explorer® Favorites -For exceptions to what you can migrate offline, see [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) +For exceptions to what you can migrate offline, see [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md) ## What Offline Environments are Supported? @@ -115,7 +115,7 @@ User-group membership is not preserved during offline migrations. You must confi ``` -For information about the format of a Config.xml file, see [Config.xml File](configxml-file-usmt-win7-usmt-win8.md). +For information about the format of a Config.xml file, see [Config.xml File](usmt-configxml-file.md). ## Command-Line Options @@ -251,7 +251,7 @@ The following XML example illustrates some of the elements discussed earlier in ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md)   diff --git a/windows/deploy/understanding-migration-xml-files.md b/windows/deploy/understanding-migration-xml-files.md index a3e06e6d3c..528c77f8d3 100644 --- a/windows/deploy/understanding-migration-xml-files.md +++ b/windows/deploy/understanding-migration-xml-files.md @@ -45,7 +45,7 @@ This topic provides an overview of the default and custom migration XML files an ## Overview of the Config.xml file -The Config.xml file is the configuration file created by the `/genconfig` option of the ScanState tool; it can be used to modify which operating-system components are migrated by USMT. The Config.xml file can be used in conjunction with other XML files, such as in the following example: `scanstate /i:migapps.xml /i:migdocs.xml /genconfig:c:\myFolder\config.xml`. When used this way, the Config.xml file tightly controls aspects of the migration, including user profiles, data, and settings, without modifying or creating other XML files. For more information about the Config.xml file, see [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) and [Config.xml File](configxml-file-usmt-win7-usmt-win8.md). +The Config.xml file is the configuration file created by the `/genconfig` option of the ScanState tool; it can be used to modify which operating-system components are migrated by USMT. The Config.xml file can be used in conjunction with other XML files, such as in the following example: `scanstate /i:migapps.xml /i:migdocs.xml /genconfig:c:\myFolder\config.xml`. When used this way, the Config.xml file tightly controls aspects of the migration, including user profiles, data, and settings, without modifying or creating other XML files. For more information about the Config.xml file, see [Customize USMT XML Files](usmt-customize-xml-files.md) and [Config.xml File](usmt-configxml-file.md). **Note**   When modifying the XML elements in the Config.xml file, you should edit an element and set the **migrate** property to **no**, rather than deleting the element from the file. If you delete the element instead of setting the property, the component may still be migrated by rules in other XML files. @@ -55,7 +55,7 @@ When modifying the XML elements in the Config.xml file, you should edit an eleme ## Overview of the MigApp.xml file -The MigApp.xml file installed with USMT includes instructions to migrate the settings for the applications listed in [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md). You must include the MigApp.xml file when using the ScanState and LoadState tools, by using the `/i` option in order to migrate application settings. The MigDocs.xml and MigUser.xml files do not migrate application settings. You can create a custom XML file to include additional applications. For more information, see [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md). +The MigApp.xml file installed with USMT includes instructions to migrate the settings for the applications listed in [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md). You must include the MigApp.xml file when using the ScanState and LoadState tools, by using the `/i` option in order to migrate application settings. The MigDocs.xml and MigUser.xml files do not migrate application settings. You can create a custom XML file to include additional applications. For more information, see [Customize USMT XML Files](usmt-customize-xml-files.md). **Important**   The MigApps.xml file will only detect and migrate .pst files that are linked to Microsoft Office Outlook. See the [Sample migration rules for customized versions of XML files](#bkmk-samples) section of this document for more information about migrating .pst files that are not linked to Outlook. @@ -199,7 +199,7 @@ You can use multiple XML files with the ScanState and LoadState tools. Each of t

Config.xml file

Operating-system components such as desktop wallpaper and background theme.

-

You can also overload config.xml to include some application and document settings by generating the config.xml file with the other default XML files. For more information, see [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) and [Config.xml File](configxml-file-usmt-win7-usmt-win8.md).

+

You can also overload config.xml to include some application and document settings by generating the config.xml file with the other default XML files. For more information, see [Customize USMT XML Files](usmt-customize-xml-files.md) and [Config.xml File](usmt-configxml-file.md).

MigApps.xml file

@@ -402,7 +402,7 @@ Rules contained in a component that is assigned the user context will be run for ### Sample migration rules for customized versions of XML files **Note**   -For best practices and requirements for customized XML files in USMT, see [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) and [General Conventions](general-conventions-usmt-win7-usmt-win8.md). +For best practices and requirements for customized XML files in USMT, see [Customize USMT XML Files](usmt-customize-xml-files.md) and [General Conventions](usmt-general-conventions.md).   @@ -446,7 +446,7 @@ To exclude Rule 1, there needs to be an exact match of the file name. However, f **Example 2: Use the UnconditionalExclude element to give a rule precedence over include rules** -If you do not know the file name or location of the file, but you do know the file name extension, you can use the **GenerateDrivePatterns** function. However, the rule will be less specific than the default include rule generated by the MigDocs.xml file, so it will not have precedence. You must use the <UnconditionalExclude> element to give this rule precedence over the default include rule. For more information about the order of precedence for XML migration rules, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). +If you do not know the file name or location of the file, but you do know the file name extension, you can use the **GenerateDrivePatterns** function. However, the rule will be less specific than the default include rule generated by the MigDocs.xml file, so it will not have precedence. You must use the <UnconditionalExclude> element to give this rule precedence over the default include rule. For more information about the order of precedence for XML migration rules, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md). ``` syntax @@ -475,7 +475,7 @@ If you want the <UnconditionalExclude> element to apply to both the system ``` -For more examples of exclude rules that you can use in custom migration XML files, see [Exclude Files and Settings](exclude-files-and-settings-usmt.md). +For more examples of exclude rules that you can use in custom migration XML files, see [Exclude Files and Settings](usmt-exclude-files-and-settings.md). ### Include rules usage examples @@ -505,10 +505,10 @@ For locations outside the user profile, such as the Program Files folder, you ca ``` -For more examples of include rules that you can use in custom migration XML files, see [Include Files and Settings](include-files-and-settings-usmt.md). +For more examples of include rules that you can use in custom migration XML files, see [Include Files and Settings](usmt-include-files-and-settings.md). **Note**   -For more information about the order of precedence for XML migration rules, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). +For more information about the order of precedence for XML migration rules, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md).   @@ -517,14 +517,14 @@ For more information about the order of precedence for XML migration rules, see You can include additional rules for the migration in the MigDocs.xml file or other XML migration files. For example, you can use the <locationModify> element to move files from the folder where they were gathered to a different folder, when they are applied to the destination computer. -You can use an XML schema (MigXML.xsd) file to validate the syntax of your customized XML files. For more information, see [USMT Resources](usmt-resources-usmt-win8.md). +You can use an XML schema (MigXML.xsd) file to validate the syntax of your customized XML files. For more information, see [USMT Resources](usmt-resources.md). ## Related topics -[Exclude Files and Settings](exclude-files-and-settings-usmt.md) +[Exclude Files and Settings](usmt-exclude-files-and-settings.md) -[Include Files and Settings](include-files-and-settings-usmt.md) +[Include Files and Settings](usmt-include-files-and-settings.md)   diff --git a/windows/deploy/usmt-best-practices-usmt-win7-usmt-win8.md b/windows/deploy/usmt-best-practices.md similarity index 95% rename from windows/deploy/usmt-best-practices-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-best-practices.md index 806fbde67e..b8772fe9f4 100644 --- a/windows/deploy/usmt-best-practices-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-best-practices.md @@ -22,7 +22,7 @@ This topic discusses general and security-related best practices when using User - **Do not use MigUser.xml and MigDocs.xml together** - If you use both .xml files, some migrated files may be duplicated if conflicting instructions are given about target locations. You can use the **/genmigxml** command-line option to determine which files will be included in your migration, and to determine if any modifications are necessary. For more information, see [Identify File Types, Files, and Folders](identify-file-types-files-and-folders-usmt-win8.md). + If you use both .xml files, some migrated files may be duplicated if conflicting instructions are given about target locations. You can use the **/genmigxml** command-line option to determine which files will be included in your migration, and to determine if any modifications are necessary. For more information, see [Identify File Types, Files, and Folders](usmt-identify-file-types-files-and-folders.md). - **Use MigDocs.xml for a better migration experience** @@ -55,7 +55,7 @@ As the authorized administrator, it is your responsibility to protect the privac - **Encrypting File System (EFS)** - Take extreme caution when migrating encrypted files, because the end user does not need to be logged on to capture the user state. By default, USMT fails if an encrypted file is found. For more information about EFS best practices, see this article in the [Microsoft Knowledge Base](http://go.microsoft.com/fwlink/p/?linkid=163). For specific instructions about EFS best practices, see [Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md). + Take extreme caution when migrating encrypted files, because the end user does not need to be logged on to capture the user state. By default, USMT fails if an encrypted file is found. For more information about EFS best practices, see this article in the [Microsoft Knowledge Base](http://go.microsoft.com/fwlink/p/?linkid=163). For specific instructions about EFS best practices, see [Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md). **Important**   If you migrate an encrypted file without also migrating the certificate, end users will not be able to access the file after the migration. @@ -80,7 +80,7 @@ As the authorized administrator, it is your responsibility to protect the privac - **Local Account Creation** - Before you migrate local accounts, see the Migrating Local Accounts section in the [Identify Users](identify-users-usmt-win7-usmt-win8.md) topic. + Before you migrate local accounts, see the Migrating Local Accounts section in the [Identify Users](usmt-identify-users.md) topic. ## XML File Best Practices @@ -139,9 +139,9 @@ As the authorized administrator, it is your responsibility to protect the privac ## Related topics -[Migration Store Encryption](migration-store-encryption-usmt-win8.md) +[Migration Store Encryption](usmt-migration-store-encryption.md) -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md)   diff --git a/windows/deploy/choose-a-migration-store-type-usmt-win7-usmt-win8.md b/windows/deploy/usmt-choose-migration-store-type.md similarity index 77% rename from windows/deploy/choose-a-migration-store-type-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-choose-migration-store-type.md index 6d33aa02a8..3e3f520ceb 100644 --- a/windows/deploy/choose-a-migration-store-type-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-choose-migration-store-type.md @@ -27,15 +27,15 @@ One of the main considerations for planning your migration is to determine which

Choose the migration store type that works best for your needs and migration scenario.

-

[Estimate Migration Store Size](estimate-migration-store-size-usmt-win7-usmt-win8.md)

+

[Estimate Migration Store Size](usmt-estimate-migration-store-size.md)

Estimate the amount of disk space needed for computers in your organization based on information about your organization's infrastructure.

-

[Hard-Link Migration Store](hard-link-migration-store-usmt-win8.md)

+

[Hard-Link Migration Store](usmt-hard-link-migration-store.md)

Learn about hard-link migration stores and the scenarios in which they are used.

-

[Migration Store Encryption](migration-store-encryption-usmt-win8.md)

+

[Migration Store Encryption](usmt-migration-store-encryption.md)

Learn about the using migration store encryption to protect user data integrity during a migration.

@@ -46,9 +46,9 @@ One of the main considerations for planning your migration is to determine which ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md) -[User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md) +[User State Migration Tool (USMT) How-to topics](usmt-how-to.md)   diff --git a/windows/deploy/user-state-migration-tool--usmt--command-line-syntax.md b/windows/deploy/usmt-command-line-syntax.md similarity index 81% rename from windows/deploy/user-state-migration-tool--usmt--command-line-syntax.md rename to windows/deploy/usmt-command-line-syntax.md index b69af0e3f1..8e62c88e30 100644 --- a/windows/deploy/user-state-migration-tool--usmt--command-line-syntax.md +++ b/windows/deploy/usmt-command-line-syntax.md @@ -23,15 +23,15 @@ The User State Migration Tool (USMT) 10.0 migrates user files and settings duri -

[ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md)

+

[ScanState Syntax](usmt-scanstate-syntax.md)

Lists the command-line options for using the ScanState tool.

-

[LoadState Syntax](loadstate-syntax-usmt-win7-usmt-win8.md)

+

[LoadState Syntax](usmt-loadstate-syntax.md)

Lists the command-line options for using the LoadState tool.

-

[UsmtUtils Syntax](usmtutils-syntax-usmt-win8.md)

+

[UsmtUtils Syntax](usmt-utilities.md)

Lists the command-line options for using the UsmtUtils tool.

diff --git a/windows/deploy/common-issues-usmt-win8.md b/windows/deploy/usmt-common-issues.md similarity index 92% rename from windows/deploy/common-issues-usmt-win8.md rename to windows/deploy/usmt-common-issues.md index 9fe3b5eeac..a12a77afe4 100644 --- a/windows/deploy/common-issues-usmt-win8.md +++ b/windows/deploy/usmt-common-issues.md @@ -33,7 +33,7 @@ The following sections discuss common issues that you might see when you run the When you encounter a problem or error message during migration, you can use the following general guidelines to help determine the source of the problem: -- Examine the ScanState, LoadState, and UsmtUtils logs to obtain the exact USMT error messages and Windows® application programming interface (API) error messages. For more information about USMT return codes and error messages, see [Return Codes](return-codes-usmt-win8.md). For more information about Windows API error messages, type **nethelpmsg** on the command line. +- Examine the ScanState, LoadState, and UsmtUtils logs to obtain the exact USMT error messages and Windows® application programming interface (API) error messages. For more information about USMT return codes and error messages, see [Return Codes](usmt-return-codes.md). For more information about Windows API error messages, type **nethelpmsg** on the command line. In most cases, the ScanState and LoadState logs indicate why a USMT migration is failing. We recommend that you use the **/v***:5* option when testing your migration. This verbosity level can be adjusted in a production migration; however, reducing the verbosity level might make it more difficult to diagnose failures that are encountered during production migrations. You can use a verbosity level higher than 5 if you want the log files output to go to a debugger. @@ -44,7 +44,7 @@ When you encounter a problem or error message during migration, you can use the - Use the **/Verify** option in the UsmtUtils tool to determine whether any files in a compressed migration store are corrupted. For more information, see [Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md). -- Use the **/Extract** option in the UsmtUtils tool to extract files from a compressed migration store. For more information, see [Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md). +- Use the **/Extract** option in the UsmtUtils tool to extract files from a compressed migration store. For more information, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md). - Create a progress log using the **/Progress** option to monitor your migration. @@ -66,7 +66,7 @@ The following sections describe common user account problems. Expand the section ### I'm having problems creating local accounts on the destination computer. -**Resolution:** For more information about creating accounts and migrating local accounts, see [Migrate User Accounts](migrate-user-accounts-usmt.md). +**Resolution:** For more information about creating accounts and migrating local accounts, see [Migrate User Accounts](usmt-migrate-user-accounts.md). ### Not all of the user accounts were migrated to the destination computer. @@ -92,7 +92,7 @@ Any user accounts on the computer that have not been used will not be migrated. **Cause:** The command that you specified might have had conflicting **/ui** and **/ue** options. If a user is specified with the **/ui** option and is also specified to be excluded with either the **/ue** or **/uel** options, the user will be included in the migration. For example, if you specify `/ui:domain1\* /ue:domain1\user1`, then User1 will be migrated because the **/ui** option takes precedence. -**Resolution:** For more information about how to use the **/ui** and **/ue** options together, see the examples in the [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) topic. +**Resolution:** For more information about how to use the **/ui** and **/ue** options together, see the examples in the [ScanState Syntax](usmt-scanstate-syntax.md) topic. ### I am using the /uel option, but many accounts are still being included in the migration. @@ -165,7 +165,7 @@ The following sections describe common XML file problems. Expand the section to ### I am having problems with a custom .xml file that I authored, and I cannot verify that the syntax is correct. -**Resolution:** You can load the XML schema (MigXML.xsd), included with USMT, into your XML authoring tool. For examples, see the [Visual Studio Development Center](http://go.microsoft.com/fwlink/p/?LinkId=74513). Then, load your .xml file in the authoring tool to see if there is a syntax error. In addition, see [USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) for more information about using the XML elements. +**Resolution:** You can load the XML schema (MigXML.xsd), included with USMT, into your XML authoring tool. For examples, see the [Visual Studio Development Center](http://go.microsoft.com/fwlink/p/?LinkId=74513). Then, load your .xml file in the authoring tool to see if there is a syntax error. In addition, see [USMT XML Reference](usmt-xml-reference.md) for more information about using the XML elements. ### I am using a MigXML helper function, but the migration isn’t working the way I expected it to.  How do I troubleshoot this issue? @@ -182,7 +182,7 @@ The following sections describe common migration problems. Expand the section to **Cause:** There might be another rule that is including the files. If there is a more specific rule or a conflicting rule, the files will be included in the migration. -**Resolution:** For more information, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) and the Diagnostic Log section in [Log Files](log-files-usmt-win7-usmt-win8.md). +**Resolution:** For more information, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md) and the Diagnostic Log section in [Log Files](usmt-log-files.md). ### I specified rules to move a folder to a specific location on the destination computer, but it has not migrated correctly. @@ -190,15 +190,15 @@ The following sections describe common migration problems. Expand the section to **Resolution:** You can use the USMT XML schema (MigXML.xsd) to write and validate migration .xml files. Also see the XML examples in the following topics: -[Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) +[Conflicts and Precedence](usmt-conflicts-and-precedence.md) -[Exclude Files and Settings](exclude-files-and-settings-usmt.md) +[Exclude Files and Settings](usmt-exclude-files-and-settings.md) -[Reroute Files and Settings](reroute-files-and-settings-usmt.md) +[Reroute Files and Settings](usmt-reroute-files-and-settings.md) -[Include Files and Settings](include-files-and-settings-usmt.md) +[Include Files and Settings](usmt-include-files-and-settings.md) -[Custom XML Examples](custom-xml-examples-usmt-win7-usmt-win8.md) +[Custom XML Examples](usmt-custom-xml-examples.md) ### After LoadState completes, the new desktop background does not appear on the destination computer. @@ -229,7 +229,7 @@ The following sections describe common offline migration problems. Expand the se ### Some of my system settings do not migrate in an offline migration. -**Cause:** Some system settings, such as desktop backgrounds and network printers, are not supported in an offline migration. For more information, see [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) +**Cause:** Some system settings, such as desktop backgrounds and network printers, are not supported in an offline migration. For more information, see [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md) **Resolution:** In an offline migration, these system settings must be restored manually. @@ -289,13 +289,13 @@ You should also reboot the machine. ## Related topics -[User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md)) +[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)) -[Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) +[Frequently Asked Questions](usmt-faq.md) -[Return Codes](return-codes-usmt-win8.md) +[Return Codes](usmt-return-codes.md) -[UsmtUtils Syntax](usmtutils-syntax-usmt-win8.md) +[UsmtUtils Syntax](usmt-utilities.md)   diff --git a/windows/deploy/common-migration-scenarios-usmt-win7-usmt-win8.md b/windows/deploy/usmt-common-migration-scenarios.md similarity index 98% rename from windows/deploy/common-migration-scenarios-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-common-migration-scenarios.md index 117f0e492c..dd61667933 100644 --- a/windows/deploy/common-migration-scenarios-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-common-migration-scenarios.md @@ -133,9 +133,9 @@ A company is allocating 20 new computers to users in the accounting department. ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md) -[Choose a Migration Store Type](choose-a-migration-store-type-usmt-win7-usmt-win8.md) +[Choose a Migration Store Type](usmt-choose-migration-store-type.md) [Offline Migration Reference](offline-migration-reference.md) diff --git a/windows/deploy/configxml-file-usmt-win7-usmt-win8.md b/windows/deploy/usmt-configxml-file.md similarity index 99% rename from windows/deploy/configxml-file-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-configxml-file.md index 4620637f55..dea99cd9e0 100644 --- a/windows/deploy/configxml-file-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-configxml-file.md @@ -572,7 +572,7 @@ Refer to the following sample Config.xml file for additional details about items ## Related topics -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md)   diff --git a/windows/deploy/conflicts-and-precedence-usmt-win7-usmt-win8.md b/windows/deploy/usmt-conflicts-and-precedence.md similarity index 99% rename from windows/deploy/conflicts-and-precedence-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-conflicts-and-precedence.md index 812254b16e..9de02f7dca 100644 --- a/windows/deploy/conflicts-and-precedence-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-conflicts-and-precedence.md @@ -447,7 +447,7 @@ For this example, the following table describes the resulting behavior if you ad ## Related topics -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md)   diff --git a/windows/deploy/custom-xml-examples-usmt-win7-usmt-win8.md b/windows/deploy/usmt-custom-xml-examples.md similarity index 98% rename from windows/deploy/custom-xml-examples-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-custom-xml-examples.md index 98f2a55bcd..c1fa2bd582 100644 --- a/windows/deploy/custom-xml-examples-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-custom-xml-examples.md @@ -299,9 +299,9 @@ The behavior for this custom .xml file is described within the <`displayName` ## Related topics -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md) -[Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) +[Customize USMT XML Files](usmt-customize-xml-files.md)   diff --git a/windows/deploy/customize-usmt-xml-files-usmt-win7-usmt-win8.md b/windows/deploy/usmt-customize-xml-files.md similarity index 90% rename from windows/deploy/customize-usmt-xml-files-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-customize-xml-files.md index bae37705ba..f504d7c992 100644 --- a/windows/deploy/customize-usmt-xml-files-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-customize-xml-files.md @@ -41,7 +41,7 @@ To modify the migration, do one or more of the following. - **Create and modify a Config.xml file.** Do this if you want to exclude an entire component from the migration. For example, you can use a Config.xml file to exclude the entire My Documents folder, or exclude the settings for an application. Excluding components using a Config.xml file is easier than modifying the migration .xml files because you do not need to be familiar with the migration rules and syntax. In addition, using a Config.xml file is the only way to exclude the operating system settings from being migrated. -For more information about excluding data, see the [Exclude Files and Settings](exclude-files-and-settings-usmt.md) topic. +For more information about excluding data, see the [Exclude Files and Settings](usmt-exclude-files-and-settings.md) topic. ## Migration .xml Files @@ -60,7 +60,7 @@ You can use the asterisk (\*) wildcard character in each of these files. However - **The MigUser.xml file.** Specify this file with both the **ScanState** and **LoadState** commands to migrate user folders, files, and file types. You can modify the MigUser.xml file. This file does not contain rules that migrate specific user accounts. The only way to specify which user accounts to migrate is on the command line using the **ScanState** and the **LoadState** user options. **Note**   - Do not use the MigUser.xml and MigDocs.xml files together. For more information, see the [Identify File Types, Files, and Folders](identify-file-types-files-and-folders-usmt-win8.md) and [USMT Best Practices](usmt-best-practices-usmt-win7-usmt-win8.md) topics. + Do not use the MigUser.xml and MigDocs.xml files together. For more information, see the [Identify File Types, Files, and Folders](usmt-identify-file-types-files-and-folders.md) and [USMT Best Practices](usmt-best-practices-usmt-win7-usmt-win8.md) topics.   @@ -72,13 +72,13 @@ You can create custom .xml files to customize the migration for your unique need ## The Config.xml File -The Config.xml file is an optional file that you create using the **/genconfig** option with the **ScanState** command. You should create and modify this file if you want to exclude certain components from the migration. In addition, you must create and modify this file if you want to exclude any of the operating system settings from being migrated. The Config.xml file format is different from that of the migration .xml files because it does not contain any migration rules. It contains only a list of the operating system components, applications, and the user documents that can be migrated. For an example, see the [Config.xml File](configxml-file-usmt-win7-usmt-win8.md) topic. For this reason, excluding components using this file is easier than modifying the migration .xml files because you do not need to be familiar with the migration rules and syntax. However, you cannot use wildcard characters in a Config.xml file. +The Config.xml file is an optional file that you create using the **/genconfig** option with the **ScanState** command. You should create and modify this file if you want to exclude certain components from the migration. In addition, you must create and modify this file if you want to exclude any of the operating system settings from being migrated. The Config.xml file format is different from that of the migration .xml files because it does not contain any migration rules. It contains only a list of the operating system components, applications, and the user documents that can be migrated. For an example, see the [Config.xml File](usmt-configxml-file.md) topic. For this reason, excluding components using this file is easier than modifying the migration .xml files because you do not need to be familiar with the migration rules and syntax. However, you cannot use wildcard characters in a Config.xml file. If you want to include all of the default components, you do not need to create the Config.xml file. Alternatively, if you are satisfied with the default migration behavior defined in the MigApp.xml, MigDocs.xml, and MigUser.xml files, and you want to exclude only some components, you can create and modify a Config.xml file and leave the other .xml files in their original state. When you run the **ScanState** command with the **/genconfig** option, **ScanState** reads the other .xml files that you specify using the **/i** option to create a custom list of components that can be migrated from the computer. This file will contain only operating system components, applications, and the user document sections that are in both of the .xml files and that are installed on the computer when you run the **ScanState** command with the **/genconfig** option. Therefore, you should create this file on a source computer that contains all of the components, applications, and settings that will be present on the destination computers. This will ensure that this file contains every component that can be migrated. The components are organized into sections: <Applications>, <WindowsComponents>, and <Documents>. To choose not to migrate a component, change its entry to `migrate="no"`. -After you create this file, you need to specify it only with the **ScanState** command using the **/Config** option for it to affect the migration. However, if you want to exclude additional data that you migrated to the store, modify the Config.xml file and specify the updated file with the **LoadState** command. For example, if you collected the My Documents folder in the store, but you decide that you do not want to migrate the My Documents folder to a destination computer, you can modify the Config.xml file to indicate `migrate="no"` before you run the **LoadState** command, and the file will not be migrated. For more information about the precedence that takes place when excluding data, see the [Exclude Files and Settings](exclude-files-and-settings-usmt.md) topic. +After you create this file, you need to specify it only with the **ScanState** command using the **/Config** option for it to affect the migration. However, if you want to exclude additional data that you migrated to the store, modify the Config.xml file and specify the updated file with the **LoadState** command. For example, if you collected the My Documents folder in the store, but you decide that you do not want to migrate the My Documents folder to a destination computer, you can modify the Config.xml file to indicate `migrate="no"` before you run the **LoadState** command, and the file will not be migrated. For more information about the precedence that takes place when excluding data, see the [Exclude Files and Settings](usmt-exclude-files-and-settings.md) topic. In addition, note the following functionality with the Config.xml file: @@ -86,7 +86,7 @@ In addition, note the following functionality with the Config.xml file: - If you mistakenly have two lines of code for the same component where one line specifies `migrate="no" `and the other line specifies `migrate="yes"`, the component will be migrated. -- In USMT there are several migration policies that can be configured in the Config.xml file. For example, you can configure additional **<ErrorControl>**, **<ProfileControl>**, and **<HardLinkStoreControl>** options. For more information, see the [Config.xml File](configxml-file-usmt-win7-usmt-win8.md) topic. +- In USMT there are several migration policies that can be configured in the Config.xml file. For example, you can configure additional **<ErrorControl>**, **<ProfileControl>**, and **<HardLinkStoreControl>** options. For more information, see the [Config.xml File](usmt-configxml-file.md) topic. **Note**   To exclude a component from the Config.xml file, set the **migrate** value to **"no"**. Deleting the XML tag for the component from the Config.xml file will not exclude the component from your migration. @@ -110,18 +110,18 @@ To exclude a component from the Config.xml file, set the **migrate** value to ** ## Additional Information -- For more information about how to change the files and settings that are migrated, see the [User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md). +- For more information about how to change the files and settings that are migrated, see the [User State Migration Tool (USMT) How-to topics](usmt-how-to.md). -- For more information about each .xml element, see the [XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) topic. +- For more information about each .xml element, see the [XML Elements Library](usmt-xml-elements-library.md) topic. -- For answers to common questions, see ".xml files" in the [Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) topic. +- For answers to common questions, see ".xml files" in the [Frequently Asked Questions](usmt-faq.md) topic. ## Related topics -[User State Migration Tool (USMT) Command-line Syntax](user-state-migration-tool--usmt--command-line-syntax.md) +[User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.md) -[USMT Resources](usmt-resources-usmt-win8.md) +[USMT Resources](usmt-resources.md)   diff --git a/windows/deploy/determine-what-to-migrate-usmt-win7-usmt-win8.md b/windows/deploy/usmt-determine-what-to-migrate.md similarity index 76% rename from windows/deploy/determine-what-to-migrate-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-determine-what-to-migrate.md index 68d5092f42..24c81b0742 100644 --- a/windows/deploy/determine-what-to-migrate-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-determine-what-to-migrate.md @@ -11,7 +11,7 @@ author: CFaw # Determine What to Migrate -By default, User State Migration Tool (USMT) 10.0 migrates the items listed in [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md), depending on the migration .xml files you specify. These default settings are often enough for a basic migration. +By default, User State Migration Tool (USMT) 10.0 migrates the items listed in [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md), depending on the migration .xml files you specify. These default settings are often enough for a basic migration. However, when considering what settings to migrate, you should also consider what settings you would like the user to be able to configure, if any, and what settings you would like to standardize. Many organizations use their migration as an opportunity to create and begin enforcing a better-managed environment. Some of the settings that users can configure on unmanaged computers prior to the migration can be locked on the new, managed computers. For example, standard wallpaper, Internet Explorer security settings, and desktop configuration are some of the items you can choose to standardize. @@ -27,19 +27,19 @@ To reduce complexity and increase standardization, your organization should cons -

[Identify Users](identify-users-usmt-win7-usmt-win8.md)

+

[Identify Users](usmt-identify-users.md)

Use command-line options to specify which users to migrate and how they should be migrated.

-

[Identify Applications Settings](identify-applications-settings-usmt-win7-usmt-win8.md)

+

[Identify Applications Settings](usmt-identify-application-settings.md)

Determine which applications you want to migrate and prepare a list of application settings to be migrated.

-

[Identify Operating System Settings](identify-operating-system-settings-usmt-win7-usmt-win8.md)

+

[Identify Operating System Settings](usmt-identify-operating-system-settings.md)

Use migration to create a new standard environment on each of the destination computers.

-

[Identify File Types, Files, and Folders](identify-file-types-files-and-folders-usmt-win8.md)

+

[Identify File Types, Files, and Folders](usmt-identify-file-types-files-and-folders.md)

Determine and locate the standard, company-specified, and non-standard locations of the file types, files, folders, and settings that you want to migrate.

@@ -50,7 +50,7 @@ To reduce complexity and increase standardization, your organization should cons ## Related topics -[What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) +[What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)   diff --git a/windows/deploy/estimate-migration-store-size-usmt-win7-usmt-win8.md b/windows/deploy/usmt-estimate-migration-store-size.md similarity index 97% rename from windows/deploy/estimate-migration-store-size-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-estimate-migration-store-size.md index ecc4a77d16..1dbd440416 100644 --- a/windows/deploy/estimate-migration-store-size-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-estimate-migration-store-size.md @@ -25,7 +25,7 @@ The disk space requirements for a migration are dependent on the size of the mig ## Hard Disk Space Requirements -- **Store.** For non-hard-link migrations, you should ensure that there is enough available disk space at the location where you will save your store to contain the data being migrated. You can save your store to another partition, an external storage device such as a USB flash drive or a server. For more information, see [Choose a Migration Store Type](choose-a-migration-store-type-usmt-win7-usmt-win8.md). +- **Store.** For non-hard-link migrations, you should ensure that there is enough available disk space at the location where you will save your store to contain the data being migrated. You can save your store to another partition, an external storage device such as a USB flash drive or a server. For more information, see [Choose a Migration Store Type](usmt-choose-migration-store-type.md). - **Source Computer.** The source computer needs enough available space for the following: @@ -76,7 +76,7 @@ You can use the ScanState tool to calculate the disk space requirements for a pa The migration store will not be created by running this command, but `StorePath` is a required parameter. -The ScanState tool also allows you to estimate disk space requirements based on a customized migration. For example, you might not want to migrate the My Documents folder to the destination computer. You can specify this in a configuration file when you run the ScanState tool. For more information, see [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md). +The ScanState tool also allows you to estimate disk space requirements based on a customized migration. For example, you might not want to migrate the My Documents folder to the destination computer. You can specify this in a configuration file when you run the ScanState tool. For more information, see [Customize USMT XML Files](usmt-customize-xml-files.md). **Note**   To preserve the functionality of existing applications or scripts that require the previous behavior of USMT, the **/p** option, without specifying *<path to a file>* is still available in USMT. @@ -122,7 +122,7 @@ When trying to determine how much disk space you will need, consider the followi ## Related topics -[Common Migration Scenarios](common-migration-scenarios-usmt-win7-usmt-win8.md) +[Common Migration Scenarios](usmt-common-migration-scenarios.md)   diff --git a/windows/deploy/exclude-files-and-settings-usmt.md b/windows/deploy/usmt-exclude-files-and-settings.md similarity index 91% rename from windows/deploy/exclude-files-and-settings-usmt.md rename to windows/deploy/usmt-exclude-files-and-settings.md index ac1e728397..9d0436d922 100644 --- a/windows/deploy/exclude-files-and-settings-usmt.md +++ b/windows/deploy/usmt-exclude-files-and-settings.md @@ -11,13 +11,13 @@ author: CFaw # Exclude Files and Settings -When you specify the migration .xml files, MigApp.xml, Migdocs, and MigUser.xml, the User State Migration Tool (USMT) 10.0 migrates the settings and components listed, as discussed in [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) You can create a custom .xml file to further specify what to include or exclude in the migration. In addition you can create a Config.xml file to exclude an entire component from a migration. You cannot, however, exclude users by using the migration .xml files or the Config.xml file. The only way to specify which users to include and exclude is by using the User options on the command line in the ScanState tool. For more information, see [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md). +When you specify the migration .xml files, MigApp.xml, Migdocs, and MigUser.xml, the User State Migration Tool (USMT) 10.0 migrates the settings and components listed, as discussed in [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md) You can create a custom .xml file to further specify what to include or exclude in the migration. In addition you can create a Config.xml file to exclude an entire component from a migration. You cannot, however, exclude users by using the migration .xml files or the Config.xml file. The only way to specify which users to include and exclude is by using the User options on the command line in the ScanState tool. For more information, see [ScanState Syntax](usmt-scanstate-syntax.md). In this topic: - [Create a custom .xml file](#options). You can use the following elements to specify what to exclude: - - [include and exclude](#bkmk-includeexclude): You can use the <include> and <exclude> elements to exclude objects with conditions. For example, you can migrate all files located in the C:\\ drive, except any .mp3 files. It is important to remember that [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) apply to these elements. + - [include and exclude](#bkmk-includeexclude): You can use the <include> and <exclude> elements to exclude objects with conditions. For example, you can migrate all files located in the C:\\ drive, except any .mp3 files. It is important to remember that [Conflicts and Precedence](usmt-conflicts-and-precedence.md) apply to these elements. - [unconditionalExclude](#exone): You can use the <unconditionalExclude> element to globally exclude data. This element takes precedence over all other include and exclude rules in the .xml files. Therefore, this element excludes objects regardless of any other <include> rules that are in the .xml files. For example, you can exclude all .mp3 files on the computer, or you can exclude all files from C:\\UserData. @@ -30,7 +30,7 @@ We recommend that you create a custom .xml file instead of modifying the default ### <include> and <exclude> -The migration .xml files, MigApp.xml, MigDocs, and MigUser.xml, contain the <component> element, which typically represents a self-contained component or an application such as Microsoft® Office Outlook® and Word. To exclude the files and registry settings that are associated with these components, use the <include> and <exclude> elements. For example, you can use these elements to migrate all files and settings with pattern X except files and settings with pattern Y, where Y is more specific than X. For the syntax of these elements, see [USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md). +The migration .xml files, MigApp.xml, MigDocs, and MigUser.xml, contain the <component> element, which typically represents a self-contained component or an application such as Microsoft® Office Outlook® and Word. To exclude the files and registry settings that are associated with these components, use the <include> and <exclude> elements. For example, you can use these elements to migrate all files and settings with pattern X except files and settings with pattern Y, where Y is more specific than X. For the syntax of these elements, see [USMT XML Reference](usmt-xml-reference.md). **Note**   If you specify an <exclude> rule, always specify a corresponding <include> rule. Otherwise, if you do not specify an <include> rule, the specific files or settings will not be included. They will already be excluded from the migration. Thus, an unaccompanied <exclude> rule is unnecessary. @@ -166,9 +166,7 @@ To exclude a Sample.doc file from any drive on the computer, use the <script& ``` -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) - -### Example 1: How to exclude all .mp3 files +[USMT XML Reference](usmt-xml-reference-uusmt-xml-reference.mdid="exone">Example 1: How to exclude all .mp3 files The following .xml file excludes all .mp3 files from the migration: @@ -278,7 +276,7 @@ You can create and modify a Config.xml file if you want to exclude components fr - **To exclude My Documents:** Specify `migrate="no"` for My Documents under the <Documents> section. Note that any <include> rules in the .xml files will still apply. For example, if you have a rule that includes all the .docx files in My Documents, then only the .docx files will be migrated, but the rest of the files will not. -See [Config.xml File](configxml-file-usmt-win7-usmt-win8.md) for more information. +See [Config.xml File](usmt-configxml-file.md) for more information. **Note**   To exclude a component from the Config.xml file, set the **migrate** value to **"no"**. Deleting the XML tag for the component from the Config.xml file will not exclude the component from your migration. @@ -288,11 +286,9 @@ To exclude a component from the Config.xml file, set the **migrate** value to ** ## Related topics -[Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) +[Customize USMT XML Files](usmt-customize-xml-files.md) -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) - -[Config.xml File](configxml-file-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.musmt-xml-reference.mdmt-win7-usmt-win8.md)   diff --git a/windows/deploy/extract-files-from-a-compressed-usmt-migration-store.md b/windows/deploy/usmt-extract-files-from-a-compressed-migration-store.md similarity index 98% rename from windows/deploy/extract-files-from-a-compressed-usmt-migration-store.md rename to windows/deploy/usmt-extract-files-from-a-compressed-migration-store.md index 70d6bc7564..8bd8e87680 100644 --- a/windows/deploy/extract-files-from-a-compressed-usmt-migration-store.md +++ b/windows/deploy/usmt-extract-files-from-a-compressed-migration-store.md @@ -101,9 +101,9 @@ In this example, if there is a myProject.exe file, it will also be extracted bec ## Related topics -[UsmtUtils Syntax](usmtutils-syntax-usmt-win8.md) +[UsmtUtils Syntax](usmt-utilities.md) -[Return Codes](return-codes-usmt-win8.md) +[Return Codes](usmt-return-codes.md) [Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md) diff --git a/windows/deploy/frequently-asked-questions-usmt-win7-usmt-win8.md b/windows/deploy/usmt-faq.md similarity index 91% rename from windows/deploy/frequently-asked-questions-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-faq.md index bccf30d684..5d04ac7b33 100644 --- a/windows/deploy/frequently-asked-questions-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-faq.md @@ -57,7 +57,7 @@ If you have installed the Windows ADK on the computer, uninstalling Windows AD ### How can I exclude a folder or a certain type of file from the migration? -You can use the **<unconditionalExclude>** element to globally exclude data from the migration. For example, you can use this element to exclude all MP3 files on the computer or to exclude all files from C:\\UserData. This element excludes objects regardless of any other <include> rules that are in the .xml files. For an example, see <unconditionalExclude> in the [Exclude Files and Settings](exclude-files-and-settings-usmt.md) topic. For the syntax of this element, see [XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md). +You can use the **<unconditionalExclude>** element to globally exclude data from the migration. For example, you can use this element to exclude all MP3 files on the computer or to exclude all files from C:\\UserData. This element excludes objects regardless of any other <include> rules that are in the .xml files. For an example, see <unconditionalExclude> in the [Exclude Files and Settings](usmt-exclude-files-and-settings.md) topic. For the syntax of this element, see [XML Elements Library](usmt-xml-elements-library.md). ### What happens to files that were located on a drive that does not exist on the destination computer? @@ -70,13 +70,13 @@ USMT migrates the files to the %SystemDrive% while maintaining the correct folde The following topics include examples of USMT .xml files: -- [Exclude Files and Settings](exclude-files-and-settings-usmt.md) +- [Exclude Files and Settings](usmt-exclude-files-and-settings.md) -- [Reroute Files and Settings](reroute-files-and-settings-usmt.md) +- [Reroute Files and Settings](usmt-reroute-files-and-settings.md) -- [Include Files and Settings](include-files-and-settings-usmt.md) +- [Include Files and Settings](usmt-include-files-and-settings.md) -- [Custom XML Examples](custom-xml-examples-usmt-win7-usmt-win8.md) +- [Custom XML Examples](usmt-custom-xml-examples.md) ### Can I use custom .xml files that were written for USMT 5.0? @@ -111,14 +111,14 @@ You can specify the MigUser.xml and MigApp.xml files on the command line. You ca ### What happens when there are conflicting XML rules or conflicting objects on the destination computer? -For more information, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). +For more information, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md). ## Related topics -[User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md)) +[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)) -[Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md) +[Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md) [Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md) diff --git a/windows/deploy/general-conventions-usmt-win7-usmt-win8.md b/windows/deploy/usmt-general-conventions.md similarity index 93% rename from windows/deploy/general-conventions-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-general-conventions.md index 147cdf05e2..ab6c9ad6b3 100644 --- a/windows/deploy/general-conventions-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-general-conventions.md @@ -31,7 +31,7 @@ Before you modify the .xml files, become familiar with the following guidelines: - **Conflits** - In general, when there are conflicts within the XML schema, the most specific pattern takes precedence. For more information, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). + In general, when there are conflicts within the XML schema, the most specific pattern takes precedence. For more information, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md). - **Required elements** @@ -54,7 +54,7 @@ Before you modify the .xml files, become familiar with the following guidelines: ## Helper Functions -You can use the XML helper functions in the [XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) to change migration behavior. Before you use these functions in an .xml file, note the following: +You can use the XML helper functions in the [XML Elements Library](usmt-xml-elements-library.md) to change migration behavior. Before you use these functions in an .xml file, note the following: - **All of the parameters are strings** @@ -89,7 +89,7 @@ You can use the XML helper functions in the [XML Elements Library](xml-elements- ## Related topics -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md)   diff --git a/windows/deploy/hard-link-migration-store-usmt-win8.md b/windows/deploy/usmt-hard-link-migration-store.md similarity index 98% rename from windows/deploy/hard-link-migration-store-usmt-win8.md rename to windows/deploy/usmt-hard-link-migration-store.md index e1b2f13561..afddeaf45d 100644 --- a/windows/deploy/hard-link-migration-store-usmt-win8.md +++ b/windows/deploy/usmt-hard-link-migration-store.md @@ -144,7 +144,7 @@ To migrate Encrypting File System (EFS) files to a new installation of an operat If the EFS files are being restored to a different partition, you should use the **/efs:copyraw** option instead of the **/efs:hardlink** option. Hard links can only be created for files on the same volume. Moving the files to another partition during the migration requires a copy of the files to be created on the new partition. The **/efs:copyraw** option will copy the files to the new partition in encrypted format. -For more information, see [Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md) and the Encrypted File Options in [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md). +For more information, see [Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md) and the Encrypted File Options in [ScanState Syntax](usmt-scanstate-syntax.md). ### Migrating Locked Files with the Hard-Link Migration Store @@ -218,7 +218,7 @@ The following XML sample specifies that files locked by an application under the ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md)   diff --git a/windows/deploy/how-usmt-works-usmt-win7-usmt-win8.md b/windows/deploy/usmt-how-it-works.md similarity index 96% rename from windows/deploy/how-usmt-works-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-how-it-works.md index a0e7e4e3d7..8e6b12231e 100644 --- a/windows/deploy/how-usmt-works-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-how-it-works.md @@ -18,7 +18,7 @@ USMT includes two tools that migrate settings and data: ScanState and LoadState. - [LoadState Process](#bkmk-lsprocess) **Note**   - For more information about how USMT processes the rules and the XML files, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). + For more information about how USMT processes the rules and the XML files, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md).   @@ -60,7 +60,7 @@ When you run the ScanState tool on the source computer, it goes through the foll 4. For each selected component, ScanState evaluates the <rules> sections. For each <rules> section, if the current user profile is the system profile and the context of the <rules> section is “System” or “UserAndSystem”, the rule is processed further. Otherwise, this rule is ignored. Alternatively, if the current user profile is not the system profile and the context of the <rules> section is “User” or “UserAndSystem”, the rule is processed further. Otherwise, this rule is ignored. - 5. ScanState creates a list of migration units that need to be migrated by processing the various subsections under this <rules> section. Each unit is collected if it is mentioned in an <include> subsection, as long as there is not a more specific rule for it in an <exclude> subsection in the same <rules> section. For more information about precedence in the .xml files, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). + 5. ScanState creates a list of migration units that need to be migrated by processing the various subsections under this <rules> section. Each unit is collected if it is mentioned in an <include> subsection, as long as there is not a more specific rule for it in an <exclude> subsection in the same <rules> section. For more information about precedence in the .xml files, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md). In addition, any migration unit (such as a file, registry key, or set of registry values) that is in an <UnconditionalExclude> section is not migrated. @@ -97,7 +97,7 @@ The LoadState process is very similar to the ScanState process. The ScanState to - The **/md** and **/mu** options are processed to rename the user profile on the destination computer, if they have been included when the LoadState command was specified. - - For each user profile selected from the store, LoadState creates a corresponding user profile on the destination computer. The destination computer does not need to be connected to the domain for domain user profiles to be created. If USMT cannot determine a domain, it attempts to apply the settings to a local account. For more information, see [Identify Users](identify-users-usmt-win7-usmt-win8.md). + - For each user profile selected from the store, LoadState creates a corresponding user profile on the destination computer. The destination computer does not need to be connected to the domain for domain user profiles to be created. If USMT cannot determine a domain, it attempts to apply the settings to a local account. For more information, see [Identify Users](usmt-identify-users.md). 4. In the "Scanning" phase, LoadState does the following for each user profile: @@ -117,7 +117,7 @@ The LoadState process is very similar to the ScanState process. The ScanState to 3. For each selected component, LoadState evaluates the <rules> sections. For each <rules> section, if the current user profile is the system profile and the context of the <rules> section is “System” or “UserAndSystem”, the rule is processed further. Otherwise, this rule is ignored. Alternatively, if the current user profile is not the system profile and the context of the <rules> section is “User” or “UserAndSystem”, the rule is processed further. Otherwise, this rule is ignored. - 4. LoadState creates a master list of migration units by processing the various subsections under the <rules> section. Each migration unit that is in an <include> subsection is migrated as long, as there is not a more specific rule for it in an <exclude> subsection in the same <rules> section. For more information about precedence, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). + 4. LoadState creates a master list of migration units by processing the various subsections under the <rules> section. Each migration unit that is in an <include> subsection is migrated as long, as there is not a more specific rule for it in an <exclude> subsection in the same <rules> section. For more information about precedence, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md). 5. LoadState evaluates the destination computer-specific subsections; for example, the <destinationCleanup> and <locationModify> subsections. @@ -133,7 +133,7 @@ The LoadState process is very similar to the ScanState process. The ScanState to ## Related topics -[User State Migration Tool (USMT) Command-line Syntax](user-state-migration-tool--usmt--command-line-syntax.md) +[User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.md)   diff --git a/windows/deploy/user-state-migration-tool--usmt--how-to-topics.md b/windows/deploy/usmt-how-to.md similarity index 70% rename from windows/deploy/user-state-migration-tool--usmt--how-to-topics.md rename to windows/deploy/usmt-how-to.md index 33ebbb54d7..4a7f0e7dfe 100644 --- a/windows/deploy/user-state-migration-tool--usmt--how-to-topics.md +++ b/windows/deploy/usmt-how-to.md @@ -23,15 +23,15 @@ The following table lists topics that describe how to use User State Migration T -

[Exclude Files and Settings](exclude-files-and-settings-usmt.md)

+

[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.

-

[Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md)

+

[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.

-

[Include Files and Settings](include-files-and-settings-usmt.md)

+

[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.

@@ -39,15 +39,15 @@ The following table lists topics that describe how to use User State Migration T

Migrate the settings of an application that the MigApp.xml file does not include by default.

-

[Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md)

+

[Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md)

Migrate Encrypting File System (EFS) certificates by using USMT.

-

[Migrate User Accounts](migrate-user-accounts-usmt.md)

+

[Migrate User Accounts](usmt-migrate-user-accounts.md)

Specify the users to include and exclude in your migration.

-

[Reroute Files and Settings](reroute-files-and-settings-usmt.md)

+

[Reroute Files and Settings](usmt-reroute-files-and-settings.md)

Create a custom .xml file to reroute files and settings during a migration.

@@ -62,11 +62,11 @@ The following table lists topics that describe how to use User State Migration T ## Related topics -[User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md) +[User State Migration Tool (USMT) Overview Topics](usmt-topics.md) -[User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md)) +[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)) -[User State Migration Toolkit (USMT) Reference](user-state-migration-toolkit--usmt--reference.md) +[User State Migration Toolkit (USMT) Reference](usmt-reference.md)   diff --git a/windows/deploy/identify-applications-settings-usmt-win7-usmt-win8.md b/windows/deploy/usmt-identify-application-settings.md similarity index 93% rename from windows/deploy/identify-applications-settings-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-identify-application-settings.md index 578563ddf2..ca14712f31 100644 --- a/windows/deploy/identify-applications-settings-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-identify-application-settings.md @@ -11,7 +11,7 @@ author: CFaw # Identify Applications Settings -When planning for your migration, you should identify which applications and settings you want to migrate. For more information about how to create a custom .xml file to migrate the settings of another application, see [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md). +When planning for your migration, you should identify which applications and settings you want to migrate. For more information about how to create a custom .xml file to migrate the settings of another application, see [Customize USMT XML Files](usmt-customize-xml-files.md). ## Applications @@ -45,7 +45,7 @@ See [Migrate Application Settings](migrate-application-settings.md) and follow t ## Related topics -[Determine What to Migrate](determine-what-to-migrate-usmt-win7-usmt-win8.md) +[Determine What to Migrate](usmt-determine-what-to-migrate.md)   diff --git a/windows/deploy/identify-file-types-files-and-folders-usmt-win8.md b/windows/deploy/usmt-identify-file-types-files-and-folders.md similarity index 93% rename from windows/deploy/identify-file-types-files-and-folders-usmt-win8.md rename to windows/deploy/usmt-identify-file-types-files-and-folders.md index 444f293d3d..3ab8ded02b 100644 --- a/windows/deploy/identify-file-types-files-and-folders-usmt-win8.md +++ b/windows/deploy/usmt-identify-file-types-files-and-folders.md @@ -29,12 +29,12 @@ Once you have verified which files and file types that the end users work with r 3. On this screen, the registered file types are displayed. -For more information about how to change the file types, files, and folders that are migrated when you specify the MigUser.xml file, see [User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md). +For more information about how to change the file types, files, and folders that are migrated when you specify the MigUser.xml file, see [User State Migration Tool (USMT) How-to topics](usmt-how-to.md). ## Related topics -[Determine What to Migrate](determine-what-to-migrate-usmt-win7-usmt-win8.md) +[Determine What to Migrate](usmt-determine-what-to-migrate.md)   diff --git a/windows/deploy/identify-operating-system-settings-usmt-win7-usmt-win8.md b/windows/deploy/usmt-identify-operating-system-settings.md similarity index 92% rename from windows/deploy/identify-operating-system-settings-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-identify-operating-system-settings.md index 1de2815cf5..232fabdc33 100644 --- a/windows/deploy/identify-operating-system-settings-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-identify-operating-system-settings.md @@ -34,16 +34,16 @@ To help you decide which settings to migrate, you should consider any previous m You should migrate any settings that users need to get their jobs done, those that make the work environment comfortable, and those that will reduce help-desk calls after the migration. Although it is easy to dismiss migrating user preferences, you should consider that users can spend a significant amount of time restoring items such as wallpaper, screen savers, and other customizable user-interface features. Most users do not remember how these settings were applied. Although these items are not critical to migration success, migrating these items increases user productivity and overall satisfaction of the migration process. **Note**   -For more information about how to change the operating-system settings that are migrated, see [User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md). +For more information about how to change the operating-system settings that are migrated, see [User State Migration Tool (USMT) How-to topics](usmt-how-to.md). -For information about the operating-system settings that USMT migrates, see [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) +For information about the operating-system settings that USMT migrates, see [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)   ## Related topics -[Determine What to Migrate](determine-what-to-migrate-usmt-win7-usmt-win8.md) +[Determine What to Migrate](usmt-determine-what-to-migrate.md)   diff --git a/windows/deploy/identify-users-usmt-win7-usmt-win8.md b/windows/deploy/usmt-identify-users.md similarity index 93% rename from windows/deploy/identify-users-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-identify-users.md index ee151348d5..1f23cb942d 100644 --- a/windows/deploy/identify-users-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-identify-users.md @@ -11,7 +11,7 @@ author: CFaw # Identify Users -It is important to carefully consider how you plan to migrate users. By default, all users are migrated by User State Migration Tool (USMT) 5.0. You must specify which users to include by using the command line. You cannot specify users in the .xml files. For instructions on how to migrate users, see [Migrate User Accounts](migrate-user-accounts-usmt.md). +It is important to carefully consider how you plan to migrate users. By default, all users are migrated by User State Migration Tool (USMT) 5.0. You must specify which users to include by using the command line. You cannot specify users in the .xml files. For instructions on how to migrate users, see [Migrate User Accounts](usmt-migrate-user-accounts.md). ## In This Topic @@ -69,11 +69,11 @@ USMT provides several options to migrate multiple users on a single computer. Th ## Related topics -[Determine What to Migrate](determine-what-to-migrate-usmt-win7-usmt-win8.md) +[Determine What to Migrate](usmt-determine-what-to-migrate.md) -[ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) +[ScanState Syntax](usmt-scanstate-syntax.md) -[LoadState Syntax](loadstate-syntax-usmt-win7-usmt-win8.md) +[LoadState Syntax](usmt-loadstate-syntax.md)   diff --git a/windows/deploy/include-files-and-settings-usmt.md b/windows/deploy/usmt-include-files-and-settings.md similarity index 91% rename from windows/deploy/include-files-and-settings-usmt.md rename to windows/deploy/usmt-include-files-and-settings.md index 04eabc2f5b..6142749d13 100644 --- a/windows/deploy/include-files-and-settings-usmt.md +++ b/windows/deploy/usmt-include-files-and-settings.md @@ -11,7 +11,7 @@ author: CFaw # Include Files and Settings -When you specify the migration .xml files, User State Migration Tool (USMT) 10.0 migrates the settings and components specified in [What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) To include additional files and settings, we recommend that you create a custom .xml file and then include this file when using both the ScanState and LoadState commands. By creating a custom .xml file, you can keep your changes separate from the default .xml files, which makes it easier to track your modifications. +When you specify the migration .xml files, User State Migration Tool (USMT) 10.0 migrates the settings and components specified in [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md) To include additional files and settings, we recommend that you create a custom .xml file and then include this file when using both the ScanState and LoadState commands. By creating a custom .xml file, you can keep your changes separate from the default .xml files, which makes it easier to track your modifications. In this topic: @@ -203,13 +203,13 @@ The following examples show how to migrate a file from a specific folder, and ho ## Related topics -[Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) +[Customize USMT XML Files](usmt-customize-xml-files.md) -[Custom XML Examples](custom-xml-examples-usmt-win7-usmt-win8.md) +[Custom XML Examples](usmt-custom-xml-examples.md) -[Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) +[Conflicts and Precedence](usmt-conflicts-and-precedence.md) -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md)   diff --git a/windows/deploy/loadstate-syntax-usmt-win7-usmt-win8.md b/windows/deploy/usmt-loadstate-syntax.md similarity index 98% rename from windows/deploy/loadstate-syntax-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-loadstate-syntax.md index 1c3af506cf..a82a0b4357 100644 --- a/windows/deploy/loadstate-syntax-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-loadstate-syntax.md @@ -37,7 +37,7 @@ Before you run the **LoadState** command, note the following: - To ensure that all operating system settings migrate, we recommend that you run the **LoadState** commands in administrator mode from an account with administrative credentials. -- For information about software requirements for running the **LoadState** command, see [USMT Requirements](usmt-requirements-usmt-win7-usmt-win8.md). +- For information about software requirements for running the **LoadState** command, see [USMT Requirements](usmt-requirements.md). - You should log off after you run the **LoadState** command. Some settings (for example, fonts, wallpaper, and screensaver settings) will not take effect until the next time the user logs in. @@ -107,7 +107,7 @@ USMT provides the following options that you can use to specify how and where th

/decrypt:"encryption strength"

-

The /decrypt option accepts a command-line parameter to define the encryption strength specified for the migration store encryption. For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md).

+

The /decrypt option accepts a command-line parameter to define the encryption strength specified for the migration store encryption. For more information about supported encryption algorithms, see [Migration Store Encryption](usmt-migration-store-encryption.md).

/hardlink

@@ -145,7 +145,7 @@ USMT provides the following options to specify what files you want to migrate.

/i:[Path\]FileName

(include)

Specifies an .xml file that contains rules that define what state to migrate. You can specify this option multiple times to include all of your .xml files (MigApp.xml, MigSys.xml, MigDocs.xml and any custom .xml files that you create). Path can be either a relative or full path. If you do not specify the Path variable, then FileName must be located in the current directory.

-

For more information about which files to specify, see the "XML files" section of the [Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) topic.

+

For more information about which files to specify, see the "XML files" section of the [Frequently Asked Questions](usmt-faq.md) topic.

/config:[Path\]FileName

@@ -272,7 +272,7 @@ USMT provides several command-line options that you can use to analyze problems ## User Options -By default, all users are migrated. The only way to specify which users to include and exclude is by using the following options. You cannot exclude users in the migration .xml files or by using the Config.xml file. For more information, see [Identify Users](identify-users-usmt-win7-usmt-win8.md). +By default, all users are migrated. The only way to specify which users to include and exclude is by using the following options. You cannot exclude users in the migration .xml files or by using the Config.xml file. For more information, see [Identify Users](usmt-identify-users.md). @@ -394,7 +394,7 @@ By default, all users are migrated. The only way to specify which users to inclu

For example:

loadstate /i:migapp.xml /i:migdocs.xml \\server\share\migration\mystore

-

For instructions, see [Migrate User Accounts](migrate-user-accounts-usmt.md).

+

For instructions, see [Migrate User Accounts](usmt-migrate-user-accounts.md).

@@ -403,7 +403,7 @@ By default, all users are migrated. The only way to specify which users to inclu

For example:

loadstate /i:migapp.xml /i:migdocs.xml \\server\share\migration\mystore

/progress:prog.log /l:load.log /lac:password /lae

-

For instructions, see [Migrate User Accounts](migrate-user-accounts-usmt.md).

+

For instructions, see [Migrate User Accounts](usmt-migrate-user-accounts.md).

/lae
@@ -697,7 +697,7 @@ You must specify either the **/key** or **/keyfile** option with the **/encrypt* ## Related topics -[XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) +[XML Elements Library](usmt-xml-elements-library.md)   diff --git a/windows/deploy/log-files-usmt-win7-usmt-win8.md b/windows/deploy/usmt-log-files.md similarity index 98% rename from windows/deploy/log-files-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-log-files.md index 654e113b1d..89fc388cf9 100644 --- a/windows/deploy/log-files-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-log-files.md @@ -55,7 +55,7 @@ The following table describes each command-line option related to logs, and it p

/v[VerbosityLevel]

Not applicable

-

See the "Monitoring Options" section in [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md).

+

See the "Monitoring Options" section in [ScanState Syntax](usmt-scanstate-syntax.md).

/listfiles[Path\]FileName

@@ -80,7 +80,7 @@ You cannot store any of the log files in *StorePath*. If you do, the log will be ## ScanState and LoadState Logs -ScanState and LoadState logs are text files that are create when you run the ScanState and LoadState tools. You can use these logs to help monitor your migration. The content of the log depends on the command-line options that you use and the verbosity level that you specify. For more information about verbosity levels, see Monitoring Options in [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md). +ScanState and LoadState logs are text files that are create when you run the ScanState and LoadState tools. You can use these logs to help monitor your migration. The content of the log depends on the command-line options that you use and the verbosity level that you specify. For more information about verbosity levels, see Monitoring Options in [ScanState Syntax](usmt-scanstate-syntax.md). ## Progress Log @@ -472,11 +472,11 @@ Your revised migration XML script excludes the files from migrating, as confirme ## Related topics -[XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) +[XML Elements Library](usmt-xml-elements-library.md) -[ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) +[ScanState Syntax](usmt-scanstate-syntax.md) -[LoadState Syntax](loadstate-syntax-usmt-win7-usmt-win8.md) +[LoadState Syntax](usmt-loadstate-syntax.md)   diff --git a/windows/deploy/migrate-efs-files-and-certificates-umst.md b/windows/deploy/usmt-migrate-efs-files-and-certificates.md similarity index 88% rename from windows/deploy/migrate-efs-files-and-certificates-umst.md rename to windows/deploy/usmt-migrate-efs-files-and-certificates.md index c97de03965..43a57ddc5d 100644 --- a/windows/deploy/migrate-efs-files-and-certificates-umst.md +++ b/windows/deploy/usmt-migrate-efs-files-and-certificates.md @@ -11,7 +11,7 @@ author: CFaw # Migrate EFS Files and Certificates -This topic describes how to migrate Encrypting File System (EFS) certificates. For more information about the **/efs** For options, see [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md). +This topic describes how to migrate Encrypting File System (EFS) certificates. For more information about the **/efs** For options, see [ScanState Syntax](usmt-scanstate-syntax.md). ## To Migrate EFS Files and Certificates @@ -36,9 +36,9 @@ Where *<Path>* is the full path of the topmost parent directory where the ## Related topics -[What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) +[What Does USMT Migrate?](usmt-what-does-usmt-migrate.md) -[Identify File Types, Files, and Folders](identify-file-types-files-and-folders-usmt-win8.md) +[Identify File Types, Files, and Folders](usmt-identify-file-types-files-and-folders.md)   diff --git a/windows/deploy/migrate-user-accounts-usmt.md b/windows/deploy/usmt-migrate-user-accounts.md similarity index 94% rename from windows/deploy/migrate-user-accounts-usmt.md rename to windows/deploy/usmt-migrate-user-accounts.md index 478cab9257..25c9490cbc 100644 --- a/windows/deploy/migrate-user-accounts-usmt.md +++ b/windows/deploy/usmt-migrate-user-accounts.md @@ -75,11 +75,11 @@ By default, all users are migrated. The only way to specify which users to inclu ## Related topics -[Identify Users](identify-users-usmt-win7-usmt-win8.md) +[Identify Users](usmt-identify-users.md) -[ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) +[ScanState Syntax](usmt-scanstate-syntax.md) -[LoadState Syntax](loadstate-syntax-usmt-win7-usmt-win8.md) +[LoadState Syntax](usmt-loadstate-syntax.md)   diff --git a/windows/deploy/migration-store-encryption-usmt-win8.md b/windows/deploy/usmt-migration-store-encryption.md similarity index 97% rename from windows/deploy/migration-store-encryption-usmt-win8.md rename to windows/deploy/usmt-migration-store-encryption.md index a1ee7f25ab..fc28a1ffe3 100644 --- a/windows/deploy/migration-store-encryption-usmt-win8.md +++ b/windows/deploy/usmt-migration-store-encryption.md @@ -59,7 +59,7 @@ Some encryption algorithms may not be available on your systems. You can verify ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md)   diff --git a/windows/deploy/user-state-migration-tool--usmt--overview.md b/windows/deploy/usmt-overview.md similarity index 84% rename from windows/deploy/user-state-migration-tool--usmt--overview.md rename to windows/deploy/usmt-overview.md index 120fde37d1..832f03ac5f 100644 --- a/windows/deploy/user-state-migration-tool--usmt--overview.md +++ b/windows/deploy/usmt-overview.md @@ -11,15 +11,15 @@ author: CFaw # 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](common-migration-scenarios-usmt-win7-usmt-win8.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: -- Configure your migration according to your business needs by using the migration rule (.xml) files to control exactly which files and settings are migrated and how they are migrated. For more information about how to modify these files, see [USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md). +- Configure your migration according to your business needs by using the migration rule (.xml) files to control exactly which files and settings are migrated and how they are migrated. For more information about how to modify these files, see [USMT XML Reference](usmt-xml-reference.md). -- Fit your customized migration into your automated deployment process by using the ScanState and LoadState tools, which control collecting and restoring the user files and settings. For more information, see [User State Migration Tool (USMT) Command-line Syntax](user-state-migration-tool--usmt--command-line-syntax.md). +- Fit your customized migration into your automated deployment process by using the ScanState and LoadState tools, which control collecting and restoring the user files and settings. For more information, see [User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.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](choose-a-migration-store-type-usmt-win7-usmt-win8.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 @@ -52,7 +52,7 @@ There are some scenarios in which the use of USMT is not recommended. These incl ## Related topics -[User State Migration Tool (USMT) Technical Reference](user-state-migration-tool--usmt--technical-reference.md) +[User State Migration Tool (USMT) Technical Reference](usmt-technical-reference.md)   diff --git a/windows/deploy/plan-your-migration-usmt-win7-usmt-win8.md b/windows/deploy/usmt-plan-your-migration.md similarity index 77% rename from windows/deploy/plan-your-migration-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-plan-your-migration.md index 151d6c6c93..eaed479359 100644 --- a/windows/deploy/plan-your-migration-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-plan-your-migration.md @@ -27,23 +27,23 @@ One of the most important requirements for migrating settings and data is restor -

[Common Migration Scenarios](common-migration-scenarios-usmt-win7-usmt-win8.md)

+

[Common Migration Scenarios](usmt-common-migration-scenarios.md)

Determine whether you will perform a refresh migration or a replace migration.

-

[What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md)

+

[What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)

Learn which applications, user data, and operating system components USMT migrates.

-

[Choose a Migration Store Type](choose-a-migration-store-type-usmt-win7-usmt-win8.md)

+

[Choose a Migration Store Type](usmt-choose-migration-store-type.md)

Choose an uncompressed, compressed, or hard-link migration store.

-

[Determine What to Migrate](determine-what-to-migrate-usmt-win7-usmt-win8.md)

+

[Determine What to Migrate](usmt-determine-what-to-migrate.md)

Identify user accounts, application settings, operating system settings, and files that you want to migrate inside your organization.

-

[Test Your Migration](test-your-migration-usmt-win7-usmt-win8.md)

+

[Test Your Migration](usmt-test-your-migration.md)

Test your migration before you deploy Windows to all users.

@@ -54,7 +54,7 @@ One of the most important requirements for migrating settings and data is restor ## Related topics -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md)   diff --git a/windows/deploy/recognized-environment-variables-usmt-win7-usmt-win8.md b/windows/deploy/usmt-recognized-environment-variables.md similarity index 99% rename from windows/deploy/recognized-environment-variables-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-recognized-environment-variables.md index 2984748171..8246122fd9 100644 --- a/windows/deploy/recognized-environment-variables-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-recognized-environment-variables.md @@ -453,7 +453,7 @@ You can use these variables in the .xml files within sections with `context=User ## Related topics -[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) +[USMT XML Reference](usmt-xml-reference.md)   diff --git a/windows/deploy/user-state-migration-toolkit--usmt--reference.md b/windows/deploy/usmt-reference.md similarity index 64% rename from windows/deploy/user-state-migration-toolkit--usmt--reference.md rename to windows/deploy/usmt-reference.md index c841faf447..0b145982e6 100644 --- a/windows/deploy/user-state-migration-toolkit--usmt--reference.md +++ b/windows/deploy/usmt-reference.md @@ -21,27 +21,27 @@ author: CFaw -

[USMT Requirements](usmt-requirements-usmt-win7-usmt-win8.md)

+

[USMT Requirements](usmt-requirements.md)

Describes operating system, hardware, and software requirements, and user prerequisites.

-

[USMT Best Practices](usmt-best-practices-usmt-win7-usmt-win8.md)

+

[USMT Best Practices](usmt-best-practices.md)

Discusses general and security-related best practices when using USMT.

-

[How USMT Works](how-usmt-works-usmt-win7-usmt-win8.md)

+

[How USMT Works](usmt-how-it-works.md)

Learn about the processes behind the ScanState and LoadState tools.

-

[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md)

+

[Plan Your Migration](usmt-plan-your-migration.md)

Choose what to migrate and the best migration scenario for your enterprise.

-

[User State Migration Tool (USMT) Command-line Syntax](user-state-migration-tool--usmt--command-line-syntax.md)

+

[User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.md)

Explore command-line options for the ScanState, LoadState, and UsmtUtils tools.

-

[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md)

+

[USMT XML Reference](usmt-xml-reference.md)

Learn about customizing a migration with XML files.

@@ -56,11 +56,11 @@ author: CFaw ## Related topics -[User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md) +[User State Migration Tool (USMT) Overview Topics](usmt-topics.md) -[User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md) +[User State Migration Tool (USMT) How-to topics](usmt-how-to.md) -[User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md)) +[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md))   diff --git a/windows/deploy/usmt-requirements-usmt-win7-usmt-win8.md b/windows/deploy/usmt-requirements.md similarity index 91% rename from windows/deploy/usmt-requirements-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-requirements.md index db2c363e71..1ecd866e28 100644 --- a/windows/deploy/usmt-requirements-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-requirements.md @@ -141,14 +141,14 @@ USMT does not support any of the Windows Server® operating systems, Windows 20   -- **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, 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](configxml-file-usmt-win7-usmt-win8.md), [Log Files](log-files-usmt-win7-usmt-win8.md), and [XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md). +- **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, 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](usmt-configxml-file.md), [Log Files](usmt-log-files.md), and [XML Elements Library](usmt-xml-elements-library.md). - **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](estimate-migration-store-size-usmt-win7-usmt-win8.md). +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](usmt-estimate-migration-store-size.md). ## User Prerequisites @@ -166,11 +166,11 @@ This documentation assumes that IT professionals using USMT understand command-l ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md) -[Estimate Migration Store Size](estimate-migration-store-size-usmt-win7-usmt-win8.md) +[Estimate Migration Store Size](usmt-estimate-migration-store-size.md) -[User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md) +[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)   diff --git a/windows/deploy/reroute-files-and-settings-usmt.md b/windows/deploy/usmt-reroute-files-and-settings.md similarity index 96% rename from windows/deploy/reroute-files-and-settings-usmt.md rename to windows/deploy/usmt-reroute-files-and-settings.md index cc0699e990..f56e96fdc0 100644 --- a/windows/deploy/reroute-files-and-settings-usmt.md +++ b/windows/deploy/usmt-reroute-files-and-settings.md @@ -108,9 +108,9 @@ The following custom .xml file migrates the Sample.doc file from C:\\Engineering ## Related topics -[Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) +[Customize USMT XML Files](usmt-customize-xml-files.md) -[Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) +[Conflicts and Precedence](usmt-conflicts-and-precedence.md) [USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) diff --git a/windows/deploy/usmt-resources-usmt-win8.md b/windows/deploy/usmt-resources.md similarity index 90% rename from windows/deploy/usmt-resources-usmt-win8.md rename to windows/deploy/usmt-resources.md index 9c8debc1af..0cb115c915 100644 --- a/windows/deploy/usmt-resources-usmt-win8.md +++ b/windows/deploy/usmt-resources.md @@ -33,7 +33,7 @@ author: CFaw ## Related topics -[User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md) +[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)   diff --git a/windows/deploy/return-codes-usmt-win8.md b/windows/deploy/usmt-return-codes.md similarity index 99% rename from windows/deploy/return-codes-usmt-win8.md rename to windows/deploy/usmt-return-codes.md index 719c949d28..5ae9098d0a 100644 --- a/windows/deploy/return-codes-usmt-win8.md +++ b/windows/deploy/usmt-return-codes.md @@ -13,7 +13,7 @@ author: CFaw This topic describes User State Migration Tool (USMT) 10.0 return codes and error messages. Also included is a table listing the USMT return codes with their associated mitigation steps. In addition, this topic provides tips to help you use the logfiles to determine why you received an error. -Understanding the requirements for running USMT can help minimize errors in your USMT migrations. For more information, see [USMT Requirements](usmt-requirements-usmt-win7-usmt-win8.md). +Understanding the requirements for running USMT can help minimize errors in your USMT migrations. For more information, see [USMT Requirements](usmt-requirements.md). ## In This Topic @@ -686,7 +686,7 @@ The following table lists each return code by numeric value, along with the asso

42

USMT_ERROR_CORRUPTED_STORE

The store contains one or more corrupted files

-

Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see [Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md).

+

Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md).

@@ -767,9 +767,9 @@ The following table lists each return code by numeric value, along with the asso ## Related topics -[User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md)) +[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)) -[Log Files](log-files-usmt-win7-usmt-win8.md) +[Log Files](usmt-log-files.md)   diff --git a/windows/deploy/scanstate-syntax-usmt-win7-usmt-win8.md b/windows/deploy/usmt-scanstate-syntax.md similarity index 98% rename from windows/deploy/scanstate-syntax-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-scanstate-syntax.md index 9b5dd7f428..09eb224de7 100644 --- a/windows/deploy/scanstate-syntax-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-scanstate-syntax.md @@ -41,7 +41,7 @@ Before you run the **ScanState** command, note the following: - If you encrypt the migration store, you will be required to enter an encryption key or a path to a file containing the encryption key. Be sure to make note of the key or the key file location, because this information is not kept anywhere in the migration store. You will need this information when you run the LoadState command to decrypt the migration store, or if you need to run the recovery utility. An incorrect or missing key or key file results in an error message. -- For information about software requirements for running the **ScanState** command, see [USMT Requirements](usmt-requirements-usmt-win7-usmt-win8.md). +- For information about software requirements for running the **ScanState** command, see [USMT Requirements](usmt-requirements.md). - Unless otherwise noted, you can use each option only once when running a tool on the command line. @@ -122,7 +122,7 @@ To create an encrypted store using the Config.xml file and the default migration

/encrypt:<EncryptionStrength>

-

The /encrypt option accepts a command-line parameter to define the encryption strength to be used for encryption of the migration store. For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md).

+

The /encrypt option accepts a command-line parameter to define the encryption strength to be used for encryption of the migration store. For more information about supported encryption algorithms, see [Migration Store Encryption](usmt-migration-store-encryption.md).

/nocompress

@@ -211,7 +211,7 @@ USMT provides the following options to specify what files you want to migrate.

/i:[Path\]FileName

(include)

-

Specifies an .xml file that contains rules that define what user, application or system state to migrate. You can specify this option multiple times to include all of your .xml files (MigApp.xml, MigDocs.xml, and any custom .xml files that you create). Path can be either a relative or full path. If you do not specify the Path variable, then FileName must be located in the current directory. For more information about which files to specify, see the "XML Files" section of the [Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) topic.

+

Specifies an .xml file that contains rules that define what user, application or system state to migrate. You can specify this option multiple times to include all of your .xml files (MigApp.xml, MigDocs.xml, and any custom .xml files that you create). Path can be either a relative or full path. If you do not specify the Path variable, then FileName must be located in the current directory. For more information about which files to specify, see the "XML Files" section of the [Frequently Asked Questions](usmt-faq.md) topic.

/genconfig:[Path\]FileName

@@ -260,7 +260,7 @@ USMT provides the following options to specify what files you want to migrate.

/localonly

Migrates only files that are stored on the local computer, regardless of the rules in the .xml files that you specify on the command line. You should use this option when you want to exclude the data from removable drives on the source computer, such as USB flash drives (UFDs), some external hard drives, and so on, and when there are network drives mapped on the source computer. If the /localonly option is not specified, then the ScanState command will copy files from these removable or network drives into the store.

-

Anything that is not considered a fixed drive by the OS will be excluded by /localonly. In some cases large external hard drives are considered fixed drives. These drives can be explicitly excluded from migration by using a custom.xml file. For more information about how to exclude all files on a specific drive, see [Exclude Files and Settings](exclude-files-and-settings-usmt.md).

+

Anything that is not considered a fixed drive by the OS will be excluded by /localonly. In some cases large external hard drives are considered fixed drives. These drives can be explicitly excluded from migration by using a custom.xml file. For more information about how to exclude all files on a specific drive, see [Exclude Files and Settings](usmt-exclude-files-and-settings.md).

The /localonly command-line option includes or excludes data in the migration as identified in the following table:

@@ -410,7 +410,7 @@ The ScanState log is created by default, but you can specify the name and locati @@ -425,7 +425,7 @@ The ScanState log is created by default, but you can specify the name and locati ## User Options -By default, all users are migrated. The only way to specify which users to include and exclude is by using the following options. You cannot exclude users in the migration .xml files or using the Config.xml file. For more information, see [Identify Users](identify-users-usmt-win7-usmt-win8.md) and [Migrate User Accounts](migrate-user-accounts-usmt.md). +By default, all users are migrated. The only way to specify which users to include and exclude is by using the following options. You cannot exclude users in the migration .xml files or using the Config.xml file. For more information, see [Identify Users](usmt-identify-users.md) and [Migrate User Accounts](usmt-migrate-user-accounts.md).

When the ScanState command runs, it will create an .xml file in the path specified. This .xml file includes improved space estimations for the migration store. The following example shows how to create this .xml file:

Scanstate.exe C:\MigrationLocation [additional parameters]

/p:"C:\MigrationStoreSize.xml"

-

For more information, see [Estimate Migration Store Size](estimate-migration-store-size-usmt-win7-usmt-win8.md).

+

For more information, see [Estimate Migration Store Size](usmt-estimate-migration-store-size.md).

To preserve the functionality of existing applications or scripts that require the previous behavior of USMT, you can use the /p option, without specifying "pathtoafile", in USMT. If you specify only the /p option, the storage space estimations are created in the same manner as with USMT3.x releases.
@@ -604,7 +604,7 @@ The /**uel** option takes precedence over the /**ue** option. If a user has logg You can use the following options to migrate encrypted files. In all cases, by default, USMT fails if an encrypted file is found unless you specify an /**efs** option. To migrate encrypted files, you must change the default behavior. -For more information, see [Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md). +For more information, see [Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md). **Note**   EFS certificates will be migrated automatically when migrating to Windows 7, Windows 8 or Windows 10. Therefore, you should specify the /**efs:copyraw** option with the **ScanState** command to migrate the encrypted files @@ -651,7 +651,7 @@ Take caution when migrating encrypted files. If you migrate an encrypted file wi

ScanState /i:migdocs.xml /i:migapp.xml \\server\share\migration\mystore /efs:copyraw

Important   -

All files must be encrypted if the parent folder is encrypted. If the encryption attribute on a file inside an encrypted folder has been removed, the file will be encrypted during the migration using the credentials of the account used to run the LoadState tool. For more information, see [Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md).

+

All files must be encrypted if the parent folder is encrypted. If the encryption attribute on a file inside an encrypted folder has been removed, the file will be encrypted during the migration using the credentials of the account used to run the LoadState tool. For more information, see [Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md).

  @@ -852,7 +852,7 @@ You must specify either the /**key** or /**keyfile** option with the /**encrypt* ## Related topics -[XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) +[XML Elements Library](usmt-xml-elements-library.md)   diff --git a/windows/deploy/user-state-migration-tool--usmt--technical-reference.md b/windows/deploy/usmt-technical-reference.md similarity index 84% rename from windows/deploy/user-state-migration-tool--usmt--technical-reference.md rename to windows/deploy/usmt-technical-reference.md index c6edf28565..2c0fd475d4 100644 --- a/windows/deploy/user-state-migration-tool--usmt--technical-reference.md +++ b/windows/deploy/usmt-technical-reference.md @@ -33,7 +33,7 @@ USMT 10.0 also includes a set of three modifiable .xml files: 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. -USMT 10.0 tools can be used on several versions of Windows operating systems, for more information, see [USMT Requirements](usmt-requirements-usmt-win7-usmt-win8.md). For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](http://go.microsoft.com/fwlink/p/?LinkId=246564). +USMT 10.0 tools can be used on several versions of Windows operating systems, for more information, see [USMT Requirements](usmt-requirements.md). For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](http://go.microsoft.com/fwlink/p/?LinkId=246564). ## In This Section @@ -45,19 +45,19 @@ USMT 10.0 tools can be used on several versions of Windows operating systems, fo
- + - + - + - + diff --git a/windows/deploy/test-your-migration-usmt-win7-usmt-win8.md b/windows/deploy/usmt-test-your-migration.md similarity index 79% rename from windows/deploy/test-your-migration-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-test-your-migration.md index 099ba79255..05e999a34d 100644 --- a/windows/deploy/test-your-migration-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-test-your-migration.md @@ -13,9 +13,9 @@ author: CFaw Always test your migration plan in a controlled laboratory setting before you deploy it to your entire organization. In your test environment, you need at least one computer for each type of operating system from which you are migrating data. -After you have thoroughly tested the entire migration process on a single computer running each of your source operating systems, conduct a pilot migration with a small group of users. After migrating a few typical user states to the intermediate store, note the space required and adjust your initial calculations accordingly. For details about estimating the space needed for your migration, see [Estimate Migration Store Size](estimate-migration-store-size-usmt-win7-usmt-win8.md). You might also need to adjust the registry-setting and file-location information in your migration-rule files. If you make changes, test the migration again. Then verify that all data and settings have migrated as expected. A pilot migration also gives you an opportunity to test your space estimates for the intermediate store. +After you have thoroughly tested the entire migration process on a single computer running each of your source operating systems, conduct a pilot migration with a small group of users. After migrating a few typical user states to the intermediate store, note the space required and adjust your initial calculations accordingly. For details about estimating the space needed for your migration, see [Estimate Migration Store Size](usmt-estimate-migration-store-size.md). You might also need to adjust the registry-setting and file-location information in your migration-rule files. If you make changes, test the migration again. Then verify that all data and settings have migrated as expected. A pilot migration also gives you an opportunity to test your space estimates for the intermediate store. -If your test migration encounters any errors, examine the ScanState and LoadState logs to obtain the exact User State Migration Tool (USMT) 10.0 return code and associated error messages or Windows application programming interface (API) error message. For more information about USMT return codes and error messages, see [Return Codes](return-codes-usmt-win8.md). You can also obtain more information about a Windows API error message by typing **net helpmsg** and the error message number on the command line. +If your test migration encounters any errors, examine the ScanState and LoadState logs to obtain the exact User State Migration Tool (USMT) 10.0 return code and associated error messages or Windows application programming interface (API) error message. For more information about USMT return codes and error messages, see [Return Codes](usmt-return-codes.md). You can also obtain more information about a Windows API error message by typing **net helpmsg** and the error message number on the command line. In most cases, the ScanState and LoadState logs indicate why a USMT migration is failing. We recommend that you use the **/v***:5* option when testing your migration. This verbosity level can be adjusted in a production migration. Reducing the verbosity level might make it more difficult to diagnose failures that are encountered during production migrations. You can use a higher verbosity level if you want the log files output to go to a debugger. @@ -34,9 +34,9 @@ For testing purposes, you can create an uncompressed store using the **/hardlink ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md) -[Log Files](log-files-usmt-win7-usmt-win8.md) +[Log Files](usmt-log-files.md)   diff --git a/windows/deploy/user-state-migration-tool--usmt--overview-topics.md b/windows/deploy/usmt-topics.md similarity index 79% rename from windows/deploy/user-state-migration-tool--usmt--overview-topics.md rename to windows/deploy/usmt-topics.md index 75e8b87d98..63b25fc8fa 100644 --- a/windows/deploy/user-state-migration-tool--usmt--overview-topics.md +++ b/windows/deploy/usmt-topics.md @@ -23,15 +23,15 @@ The User State Migration Tool (USMT) 10.0 provides a highly customizable user-p - + - + - + @@ -42,11 +42,11 @@ The User State Migration Tool (USMT) 10.0 provides a highly customizable user-p ## Related topics -[User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md) +[User State Migration Tool (USMT) How-to topics](usmt-how-to.md) -[User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md)) +[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)) -[User State Migration Toolkit (USMT) Reference](user-state-migration-toolkit--usmt--reference.md) +[User State Migration Toolkit (USMT) Reference](usmt-reference.md)   diff --git a/windows/deploy/user-state-migration-tool--usmt--troubleshooting.md b/windows/deploy/usmt-troubleshooting.md similarity index 62% rename from windows/deploy/user-state-migration-tool--usmt--troubleshooting.md rename to windows/deploy/usmt-troubleshooting.md index 4e697b76a9..576f9801c9 100644 --- a/windows/deploy/user-state-migration-tool--usmt--troubleshooting.md +++ b/windows/deploy/usmt-troubleshooting.md @@ -23,23 +23,23 @@ The following table describes topics that address common User State Migration To - + - + - + - + - + @@ -50,13 +50,13 @@ The following table describes topics that address common User State Migration To ## Related topics -[USMT Best Practices](usmt-best-practices-usmt-win7-usmt-win8.md) +[USMT Best Practices](usmt-best-practices.md) -[User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md) +[User State Migration Tool (USMT) Overview Topics](usmt-topics.md) -[User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md) +[User State Migration Tool (USMT) How-to topics](usmt-how-to.md) -[User State Migration Toolkit (USMT) Reference](user-state-migration-toolkit--usmt--reference.md) +[User State Migration Toolkit (USMT) Reference](usmt-reference.md)   diff --git a/windows/deploy/usmtutils-syntax-usmt-win8.md b/windows/deploy/usmt-utilities.md similarity index 97% rename from windows/deploy/usmtutils-syntax-usmt-win8.md rename to windows/deploy/usmt-utilities.md index ce45cd93e6..eb9081b082 100644 --- a/windows/deploy/usmtutils-syntax-usmt-win8.md +++ b/windows/deploy/usmt-utilities.md @@ -182,7 +182,7 @@ usmtutils /verify\[:*<reportType>*\] *<filePath>* \[/l:*<logfile&

  • /key:<KeyString> specifies the encryption key. If there is a space in <KeyString>, you must surround the argument with quotation marks.

  • /keyfile: <FileName> specifies the location and name of a text (.txt) file that contains the encryption key.

    • -

    For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md)

    +

    For more information about supported encryption algorithms, see [Migration Store Encryption](usmt-migration-store-encryption.md)

    [User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md)

    [User State Migration Tool (USMT) Overview Topics](usmt-topics.md)

    Describes what’s new in USMT, how to get started with USMT, and the benefits and limitations of using USMT.

    [User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md)

    [User State Migration Tool (USMT) How-to topics](usmt-how-to.md)

    Includes step-by-step instructions for using USMT, as well as how-to topics for conducting tasks in USMT.

    [User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md))

    [User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md))

    Provides answers to frequently asked questions and common issues in USMT, as well as a reference for return codes used in USMT.

    [User State Migration Toolkit (USMT) Reference](user-state-migration-toolkit--usmt--reference.md)

    [User State Migration Toolkit (USMT) Reference](usmt-reference.md)

    Includes reference information for migration planning, migration best practices, command-line syntax, using XML, and requirements for using USMT.

    [User State Migration Tool (USMT) Overview](user-state-migration-tool--usmt--overview.md)

    [User State Migration Tool (USMT) Overview](usmt-overview.md)

    Describes the benefits and limitations of using USMT.

    [Getting Started with the User State Migration Tool (USMT)](getting-started-with-the-user-state-migration-tool--usmt-.md)

    [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.

    [Windows Upgrade and Migration Considerations](windows-upgrade-and-migration-considerations-win8.md)

    [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.

    [Common Issues](common-issues-usmt-win8.md)

    [Common Issues](usmt-common-issues.md)

    Find troubleshooting solutions for common problems in USMT.

    [Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md)

    [Frequently Asked Questions](usmt-faq.md)

    Find answers to questions about how to use USMT.

    [Log Files](log-files-usmt-win7-usmt-win8.md)

    [Log Files](usmt-log-files.md)

    Learn how to enable logging to help you troubleshoot issues in USMT.

    [Return Codes](return-codes-usmt-win8.md)

    [Return Codes](usmt-return-codes.md)

    Learn how to use return codes to identify problems in USMT.

    [USMT Resources](usmt-resources-usmt-win8.md)

    [USMT Resources](usmt-resources.md)

    Find more information and support for using USMT.
    @@ -202,7 +202,7 @@ Some examples of **/verify** commands: ## Extract Options -Use the **/extract** option to recover files from a compressed USMT migration store if it will not restore normally with loadstate. For more information on how to use the **/extract** option, see [Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md). +Use the **/extract** option to recover files from a compressed USMT migration store if it will not restore normally with loadstate. For more information on how to use the **/extract** option, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md). The syntax for **/extract** is: @@ -308,7 +308,7 @@ The syntax for **/extract** is:

  • /key: <KeyString> specifies the encryption key. If there is a space in <KeyString>, you must surround the argument with quotation marks.

  • /keyfile:<FileName> specifies a text (.txt) file that contains the encryption key

    • -

    For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md).

    +

    For more information about supported encryption algorithms, see [Migration Store Encryption](usmt-migration-store-encryption.md).

    /o

    @@ -332,9 +332,9 @@ Some examples of **/extract** commands: ## Related topics -[User State Migration Tool (USMT) Command-line Syntax](user-state-migration-tool--usmt--command-line-syntax.md) +[User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.md) -[Return Codes](return-codes-usmt-win8.md) +[Return Codes](usmt-return-codes.md)   diff --git a/windows/deploy/what-does-usmt-migrate-usmt-win7-usmt-win8.md b/windows/deploy/usmt-what-does-usmt-migrate.md similarity index 98% rename from windows/deploy/what-does-usmt-migrate-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-what-does-usmt-migrate.md index 7e2d85f9a3..83b3851c29 100644 --- a/windows/deploy/what-does-usmt-migrate-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-what-does-usmt-migrate.md @@ -364,7 +364,7 @@ When you specify the MigApp.xml file, USMT migrates the settings for the followi ## What USMT Does Not Migrate -The following is a list of the settings that USMT does not migrate. If you are having a problem that is not listed here, see [Common Issues](common-issues-usmt-win8.md). +The following is a list of the settings that USMT does not migrate. If you are having a problem that is not listed here, see [Common Issues](usmt-common-issues.md). ### Application Settings @@ -400,12 +400,12 @@ You should also note the following: - You should run USMT from an account with administrative credentials. Otherwise, some data will not migrate. When running the ScanState and LoadState tools you must run the tools in Administrator mode from an account with administrative credentials. If you do not run USMT in Administrator mode, only the user profile that is logged on will be included in the migration. In addition, you must run the ScanState tool on Windows XP from an account with administrative credentials. Otherwise, some operating-system settings will not migrate. To run in Administrator mode, click **Start**, click **All Programs**, click **Accessories**, right-click **Command Prompt**, and then click **Run as administrator**. -- You can use the /**localonly** option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify /**localonly**, see [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md). +- You can use the /**localonly** option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify /**localonly**, see [ScanState Syntax](usmt-scanstate-syntax.md). ## Related topics -[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) +[Plan Your Migration](usmt-plan-your-migration.md)   diff --git a/windows/deploy/xml-elements-library-usmt-win7-usmt-win8.md b/windows/deploy/usmt-xml-elements-library.md similarity index 99% rename from windows/deploy/xml-elements-library-usmt-win7-usmt-win8.md rename to windows/deploy/usmt-xml-elements-library.md index 2c2624cb51..87ffc8c9c3 100644 --- a/windows/deploy/xml-elements-library-usmt-win7-usmt-win8.md +++ b/windows/deploy/usmt-xml-elements-library.md @@ -2853,7 +2853,7 @@ Syntax: The <merge> element determines what will happen when a collision occurs. A collision is when an object that is migrated is already present on the destination computer. If you do not specify this element, the default behavior for the registry is for the source object to overwrite the destination object. The default behavior for files is for the source file to be renamed to "OriginalFileName(1).OriginalExtension". This element specifies only what should be done when a collision occurs. It does not include objects. Therefore, for your objects to migrate, you must specify <include> rules along with the <merge> element. When an object is processed and a collision is detected, USMT will select the most specific merge rule and apply it to resolve the conflict. For example, if you have a <merge> rule C:\\\* \[\*\] set to <sourcePriority> and a <merge> rule C:\\subfolder\\\* \[\*\] set to <destinationPriority>, then USMT would use the <destinationPriority> rule because it is the more specific. -For an example of this element, see [Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md). +For an example of this element, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md). - **Number of occurrences:** Unlimited @@ -3286,7 +3286,7 @@ Syntax:

    Yes

    A valid registry or file path pattern, followed by at least one space, followed by brackets [] that contain the object to be migrated.