mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Metadata update deployment/usmt 8
This commit is contained in:
Frank Rojas
@ -17,7 +17,7 @@ This article outlines the general process that you should follow to migrate file
|
||||
|
||||
## In this topic
|
||||
|
||||
- [Step 1: Plan Your Migration](#step-1-plan-your-migration)
|
||||
- [Step 1: Plan your migration](#step-1-plan-your-migration)
|
||||
|
||||
- [Step 2: Collect files and settings from the source computer](#step-2-collect-files-and-settings-from-the-source-computer)
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ This article doesn't contain information about how to migrate applications that
|
||||
|
||||
## In this topic
|
||||
|
||||
- [Before You Begin](#before-you-begin)
|
||||
- [Before you begin](#before-you-begin)
|
||||
|
||||
- [Step 1: Verify that the application is installed on the source computer, and that it's the same version as the version to be installed on the destination computer](#step-1-verify-that-the-application-is-installed-on-the-source-computer-and-that-its-the-same-version-as-the-version-to-be-installed-on-the-destination-computer).
|
||||
|
||||
@ -147,10 +147,10 @@ To speed up the time it takes to collect and migrate the data, you can migrate o
|
||||
|
||||
## Related articles
|
||||
|
||||
[USMT XML Reference](usmt-xml-reference.md)
|
||||
[USMT XML reference](usmt-xml-reference.md)
|
||||
|
||||
[Conflicts and Precedence](usmt-conflicts-and-precedence.md)
|
||||
[Conflicts and precedence](usmt-conflicts-and-precedence.md)
|
||||
|
||||
[XML Elements Library](usmt-xml-elements-library.md)
|
||||
[XML elements library](usmt-xml-elements-library.md)
|
||||
|
||||
[Log Files](usmt-log-files.md)
|
||||
[Log files](usmt-log-files.md)
|
||||
|
||||
@ -17,11 +17,11 @@ When planning your migration, you should determine which migration store type be
|
||||
|
||||
## In this topic
|
||||
|
||||
[Migration Store Types](#migration-store-types)
|
||||
[Migration store types](#migration-store-types)
|
||||
|
||||
[Local Store vs. Remote Store](#local-store-vs-remote-store)
|
||||
[Local store vs. remote store](#local-store-vs-remote-store)
|
||||
|
||||
[The /localonly Command-Line Option](#the-localonly-command-line-option)
|
||||
[The /localonly command-line option](#the-localonly-command-line-option)
|
||||
|
||||
## Migration store types
|
||||
|
||||
@ -60,4 +60,4 @@ You should use this option to exclude the data from removable drives and network
|
||||
|
||||
## Related articles
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
|
||||
@ -29,17 +29,17 @@ When you use User State Migration Tool (USMT) 10.0 to gather and restore user st
|
||||
|
||||
## In this topic
|
||||
|
||||
- [What Will Migrate Offline?](#what-will-migrate-offline)
|
||||
- [What will migrate offline?](#what-will-migrate-offline)
|
||||
|
||||
- [What Offline Environments are Supported?](#what-offline-environments-are-supported)
|
||||
- [What offline environments are supported?](#what-offline-environments-are-supported)
|
||||
|
||||
- [User-Group Membership and Profile Control](#user-group-membership-and-profile-control)
|
||||
- [User-group membership and profile control](#user-group-membership-and-profile-control)
|
||||
|
||||
- [Command-Line Options](#command-line-options)
|
||||
- [Command-line options](#command-line-options)
|
||||
|
||||
- [Environment Variables](#environment-variables)
|
||||
- [Environment variables](#environment-variables)
|
||||
|
||||
- [Offline.xml Elements](#offlinexml-elements)
|
||||
- [Offline.xml elements](#offlinexml-elements)
|
||||
|
||||
## What will migrate offline?
|
||||
|
||||
@ -173,4 +173,4 @@ The following XML example illustrates some of the elements discussed earlier in
|
||||
|
||||
## Related articles
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
|
||||
@ -11,7 +11,7 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Understanding Migration XML Files
|
||||
# Understanding migration XML files
|
||||
|
||||
You can modify the behavior of a basic User State Migration Tool (USMT) 10.0 migration by using XML files; these files provide instructions on where and how the USMT tools should gather and apply files and settings. USMT includes three XML files that you can use to customize a basic migration: the `MigDocs.xml` and `MigUser.xml` files, which modify how files are discovered on the source computer, and the MigApps.xml file, which is required in order to migrate supported application settings. You can also create and edit custom XML files and a `Config.xml` file to further customize your migration.
|
||||
|
||||
@ -445,6 +445,6 @@ You can use an XML schema (MigXML.xsd) file to validate the syntax of your custo
|
||||
|
||||
## Related articles
|
||||
|
||||
[Exclude Files and Settings](usmt-exclude-files-and-settings.md)
|
||||
[Exclude files and settings](usmt-exclude-files-and-settings.md)
|
||||
|
||||
[Include Files and Settings](usmt-include-files-and-settings.md)
|
||||
[Include files and settings](usmt-include-files-and-settings.md)
|
||||
|
||||
@ -12,11 +12,11 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# USMT Best Practices
|
||||
# USMT best practices
|
||||
|
||||
This article discusses general and security-related best practices when using User State Migration Tool (USMT) 10.0.
|
||||
|
||||
## General Best Practices
|
||||
## General best practices
|
||||
|
||||
- **Install applications before running the LoadState tool**
|
||||
|
||||
@ -24,7 +24,7 @@ This article discusses general and security-related best practices when using Us
|
||||
|
||||
- **Don't 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](usmt-identify-file-types-files-and-folders.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**
|
||||
|
||||
@ -50,7 +50,7 @@ This article discusses general and security-related best practices when using Us
|
||||
|
||||
If you decide to perform the migration while users are using the network, it's best to migrate user accounts in groups. To minimize the impact on network performance, determine the size of the groups based on the size of each user account. Migrating in phases also allows you to make sure each phase is successful before starting the next phase. Using this method, you can make any necessary modifications to your plan between groups.
|
||||
|
||||
## Security Best Practices
|
||||
## Security best practices
|
||||
|
||||
As the authorized administrator, it is your responsibility to protect the privacy of the users and maintain security during and after the migration. In particular, you must consider the following issues:
|
||||
|
||||
@ -132,6 +132,6 @@ As the authorized administrator, it is your responsibility to protect the privac
|
||||
|
||||
## Related articles
|
||||
|
||||
[Migration Store Encryption](usmt-migration-store-encryption.md)
|
||||
[Migration store encryption](usmt-migration-store-encryption.md)
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
|
||||
@ -11,11 +11,11 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Choose a Migration Store Type
|
||||
# Choose a migration store type
|
||||
|
||||
One of the main considerations for planning your migration is to determine which migration store type best meets your needs. As part of these considerations, determine how much space is required to run the User State Migration Tool (USMT) 10.0 components on your source and destination computers, and how much space is needed to create and host the migration store, whether you're using a local share, network share, or storage device. The final consideration is ensuring that user date integrity is maintained by encrypting the migration store.
|
||||
|
||||
## In This Section
|
||||
## In this section
|
||||
|
||||
| Link | Description |
|
||||
|--- |--- |
|
||||
@ -26,6 +26,6 @@ One of the main considerations for planning your migration is to determine which
|
||||
|
||||
## Related articles
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
|
||||
[User State Migration Tool (USMT) How-to topics](usmt-how-to.md)
|
||||
[User State Migration Tool (USMT) how-to topics](usmt-how-to.md)
|
||||
|
||||
@ -11,7 +11,7 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# User State Migration Tool (USMT) Command-line Syntax
|
||||
# User State Migration Tool (USMT) command-line syntax
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 migrates user files and settings during large deployments of Windows. To improve and simplify the migration process, USMT captures desktop, network, and application settings in addition to a user's files. USMT then migrates these items to a new Windows installation.
|
||||
|
||||
@ -19,6 +19,6 @@ The User State Migration Tool (USMT) 10.0 migrates user files and settings durin
|
||||
|
||||
| Link | Description |
|
||||
|--- |--- |
|
||||
|[ScanState Syntax](usmt-scanstate-syntax.md)|Lists the command-line options for using the ScanState tool.|
|
||||
|[LoadState Syntax](usmt-loadstate-syntax.md)|Lists the command-line options for using the LoadState tool.|
|
||||
|[UsmtUtils Syntax](usmt-utilities.md)|Lists the command-line options for using the UsmtUtils tool.|
|
||||
|[ScanState syntax](usmt-scanstate-syntax.md)|Lists the command-line options for using the ScanState tool.|
|
||||
|[LoadState syntax](usmt-loadstate-syntax.md)|Lists the command-line options for using the LoadState tool.|
|
||||
|[UsmtUtils syntax](usmt-utilities.md)|Lists the command-line options for using the UsmtUtils tool.|
|
||||
|
||||
@ -42,9 +42,9 @@ When you encounter a problem or error message during migration, you can use the
|
||||
> [!NOTE]
|
||||
> Running the ScanState and LoadState tools with the `/v:5` option creates a detailed log file. Although this option makes the log file large, the extra detail can help you determine where migration errors occurred.
|
||||
|
||||
- Use the `/Verify` option with 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 `/Verify` option with 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 with 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).
|
||||
- Use the `/Extract` option with 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.
|
||||
|
||||
@ -63,7 +63,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](usmt-migrate-user-accounts.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
|
||||
|
||||
@ -182,15 +182,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 articles:
|
||||
|
||||
[Conflicts and Precedence](usmt-conflicts-and-precedence.md)
|
||||
[Conflicts and precedence](usmt-conflicts-and-precedence.md)
|
||||
|
||||
[Exclude Files and Settings](usmt-exclude-files-and-settings.md)
|
||||
[Exclude files and settings](usmt-exclude-files-and-settings.md)
|
||||
|
||||
[Reroute Files and Settings](usmt-reroute-files-and-settings.md)
|
||||
[Reroute files and settings](usmt-reroute-files-and-settings.md)
|
||||
|
||||
[Include Files and Settings](usmt-include-files-and-settings.md)
|
||||
[Include files and settings](usmt-include-files-and-settings.md)
|
||||
|
||||
[Custom XML Examples](usmt-custom-xml-examples.md)
|
||||
[Custom XML examples](usmt-custom-xml-examples.md)
|
||||
|
||||
### After LoadState completes, the new desktop background doesn't appear on the destination computer
|
||||
|
||||
@ -246,7 +246,7 @@ The following sections describe common offline migration problems. Expand the se
|
||||
|
||||
### Some of my system settings don't migrate in an offline migration
|
||||
|
||||
**Cause:** Some system settings, such as desktop backgrounds and network printers, aren't supported in an offline migration. For more information, see [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)
|
||||
**Cause:** Some system settings, such as desktop backgrounds and network printers, aren't 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.
|
||||
|
||||
@ -268,7 +268,7 @@ Scanstate.exe /ui:S1-5-21-124525095-708259637-1543119021*
|
||||
|
||||
The wild card (\*) at the end of the SID will migrate the *SID*\_Classes key as well.
|
||||
|
||||
You can also use patterns for SIDs that identify generic users or groups. For example, you can use the `/ue:*-500` option to exclude the local administrator accounts. For more information about Windows SIDs, see [this Microsoft Web site](/troubleshoot/windows-server/identity/security-identifiers-in-windows).
|
||||
You can also use patterns for SIDs that identify generic users or groups. For example, you can use the `/ue:*-500` option to exclude the local administrator accounts. For more information about Windows SIDs, see [Security identifiers](/windows-server/identity/ad-ds/manage/understand-security-identifiers).
|
||||
|
||||
### My script to wipe the disk fails after running the ScanState tool on a 64-bit system
|
||||
|
||||
@ -304,10 +304,10 @@ You should also reboot the machine.
|
||||
|
||||
## Related articles
|
||||
|
||||
[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)
|
||||
[User State Migration Tool (USMT) troubleshooting](usmt-troubleshooting.md)
|
||||
|
||||
[Frequently Asked Questions](usmt-faq.yml)
|
||||
[Frequently asked questions](usmt-faq.yml)
|
||||
|
||||
[Return Codes](usmt-return-codes.md)
|
||||
[Return codes](usmt-return-codes.md)
|
||||
|
||||
[UsmtUtils Syntax](usmt-utilities.md)
|
||||
[UsmtUtils syntax](usmt-utilities.md)
|
||||
|
||||
@ -123,8 +123,8 @@ A company is allocating 20 new computers to users in the accounting department.
|
||||
|
||||
## Related articles
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
|
||||
[Choose a Migration Store Type](usmt-choose-migration-store-type.md)
|
||||
[Choose a migration store type](usmt-choose-migration-store-type.md)
|
||||
|
||||
[Offline Migration Reference](offline-migration-reference.md)
|
||||
[Offline migration reference](offline-migration-reference.md)
|
||||
|
||||
@ -487,4 +487,4 @@ Refer to the following sample `Config.xml` file for more details about items you
|
||||
|
||||
## Related articles
|
||||
|
||||
[USMT XML Reference](usmt-xml-reference.md)
|
||||
[USMT XML reference](usmt-xml-reference.md)
|
||||
|
||||
@ -11,7 +11,7 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Conflicts and Precedence
|
||||
# Conflicts and precedence
|
||||
|
||||
When you include, exclude, and reroute files and settings, it's important to know how User State Migration Tool (USMT) 10.0 deals with conflicts and precedence. When working with USMT, the following are the most important conflicts and precedence guidelines to keep in mind.
|
||||
|
||||
@ -260,4 +260,4 @@ During LoadState, all the files will be restored, overwriting the existing files
|
||||
|
||||
## Related articles
|
||||
|
||||
[USMT XML Reference](usmt-xml-reference.md)
|
||||
[USMT XML reference](usmt-xml-reference.md)
|
||||
|
||||
@ -276,6 +276,6 @@ The behavior for this custom .xml file is described within the `<displayName>` t
|
||||
|
||||
## Related articles
|
||||
|
||||
[USMT XML Reference](usmt-xml-reference.md)
|
||||
[USMT XML reference](usmt-xml-reference.md)
|
||||
|
||||
[Customize USMT XML Files](usmt-customize-xml-files.md)
|
||||
[Customize USMT XML files](usmt-customize-xml-files.md)
|
||||
|
||||
@ -11,9 +11,9 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Customize USMT XML Files
|
||||
# Customize USMT XML files
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
[Overview](#overview)
|
||||
|
||||
@ -102,7 +102,7 @@ In addition, note the following functionality with the `Config.xml` file:
|
||||
|
||||
`loadstate \\server\share\migration\mystore /i:migapp.xml /i:migdocs.xml /v:5 /decrypt /key:"mykey"`
|
||||
|
||||
## Additional Information
|
||||
## 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](usmt-how-to.md).
|
||||
|
||||
@ -112,6 +112,6 @@ In addition, note the following functionality with the `Config.xml` file:
|
||||
|
||||
## Related articles
|
||||
|
||||
[User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.md)
|
||||
[User State Migration Tool (USMT) command-line syntax](usmt-command-line-syntax.md)
|
||||
|
||||
[USMT Resources](usmt-resources.md)
|
||||
[USMT resources](usmt-resources.md)
|
||||
|
||||
@ -11,7 +11,7 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Determine What to Migrate
|
||||
# Determine what to migrate
|
||||
|
||||
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.
|
||||
|
||||
@ -27,7 +27,7 @@ To reduce complexity and increase standardization, your organization should cons
|
||||
|
||||
Using an SOE can vastly simplify the migration and reduce overall deployment challenges.
|
||||
|
||||
## In This Section
|
||||
## In this section
|
||||
|
||||
| Link | Description |
|
||||
|--- |--- |
|
||||
@ -38,4 +38,4 @@ Using an SOE can vastly simplify the migration and reduce overall deployment cha
|
||||
|
||||
## Related articles
|
||||
|
||||
[What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)
|
||||
[What does USMT migrate?](usmt-what-does-usmt-migrate.md)
|
||||
|
||||
@ -115,4 +115,4 @@ When trying to determine how much disk space you'll need, consider the following
|
||||
|
||||
## Related articles
|
||||
|
||||
[Common Migration Scenarios](usmt-common-migration-scenarios.md)
|
||||
[Common migration scenarios](usmt-common-migration-scenarios.md)
|
||||
|
||||
@ -11,39 +11,43 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# 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?](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).
|
||||
# Exclude files and settings
|
||||
|
||||
In this topic:
|
||||
When you specify the migration .xml files, `MigApp.xml`, `Migdocs.xml`, 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 can't, 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).
|
||||
|
||||
- [Create a custom .xml file](#create-a-custom-xml-file). You can use the following elements to specify what to exclude:
|
||||
## In this topic
|
||||
|
||||
- include and exclude: 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.
|
||||
- [Create a custom .xml file](#create-a-custom-xml-file). You can use the following elements to specify what to exclude:
|
||||
|
||||
- [unconditionalExclude](#example-1-how-to-migrate-all-files-from-c-except-mp3-files): 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.
|
||||
- include and exclude: 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's important to remember that [Conflicts and Precedence](usmt-conflicts-and-precedence.md) apply to these elements.
|
||||
|
||||
- [Create a Config.xml File](#create-a-config-xml-file): You can create and modify a Config.xml file to exclude an entire component from the migration. For example, you can use this file to exclude the settings for one of the default applications. In addition, creating and modifying a Config.xml file is the only way to exclude the operating-system settings that are migrated to computers running Windows. 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.
|
||||
- [unconditionalExclude](#example-1-how-to-migrate-all-files-from-c-except-mp3-files): 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.
|
||||
|
||||
- [Create a Config.xml File](#create-a-config-xml-file): You can create and modify a `Config.xml` file to exclude an entire component from the migration. For example, you can use this file to exclude the settings for one of the default applications. In addition, creating and modifying a `Config.xml` file is the only way to exclude the operating-system settings that are migrated to computers running Windows. Excluding components using this file is easier than modifying the migration .xml files because you don't need to be familiar with the migration rules and syntax.
|
||||
|
||||
## Create a custom .xml file
|
||||
We recommend that you create a custom .xml file instead of modifying the default migration .xml files. When you use a custom .xml file, you can keep your changes separate from the default .xml files, which makes it easier to track your modifications.
|
||||
|
||||
We recommend that you create a custom .xml file instead of modifying the default migration .xml files. When you use a custom .xml file, you can keep your changes separate from the default .xml file, which makes it easier to track your modifications.
|
||||
|
||||
### <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.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.
|
||||
The migration .xml files, `MigApp.xml`, `MigDocs.xml`, 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).
|
||||
|
||||
- [Example 1: How to migrate all files from C:\\ except .mp3 files](#example-1-how-to-migrate-all-files-from-c-except-mp3-files)
|
||||
> [!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.
|
||||
|
||||
- [Example 2: How to migrate all files located in C:\\Data except files in C:\\Data\\tmp](#example-2-how-to-migrate-all-files-located-in-cdata-except-files-in-cdatatmp)
|
||||
- [Example 1: How to migrate all files from C:\\ except .mp3 files](#example-1-how-to-migrate-all-files-from-c-except-mp3-files)
|
||||
|
||||
- [Example 3: How to exclude the files in a folder but include all subfolders](#example-3-how-to-exclude-the-files-in-a-folder-but-include-all-subfolders)
|
||||
- [Example 2: How to migrate all files located in C:\\Data except files in C:\\Data\\tmp](#example-2-how-to-migrate-all-files-located-in-cdata-except-files-in-cdatatmp)
|
||||
|
||||
- [Example 4: How to exclude a file from a specific folder](#example-4-how-to-exclude-a-file-from-a-specific-folder)
|
||||
- [Example 3: How to exclude the files in a folder but include all subfolders](#example-3-how-to-exclude-the-files-in-a-folder-but-include-all-subfolders)
|
||||
|
||||
- [Example 5: How to exclude a file from any location](#example-5-how-to-exclude-a-file-from-any-location)
|
||||
- [Example 4: How to exclude a file from a specific folder](#example-4-how-to-exclude-a-file-from-a-specific-folder)
|
||||
|
||||
- [Example 5: How to exclude a file from any location](#example-5-how-to-exclude-a-file-from-any-location)
|
||||
|
||||
### Example 1: How to migrate all files from C:\\ except .mp3 files
|
||||
|
||||
The following .xml file migrates all files located on the C: drive, except any .mp3 files.
|
||||
|
||||
``` xml
|
||||
@ -68,8 +72,10 @@ The following .xml file migrates all files located on the C: drive, except any .
|
||||
</component>
|
||||
</migration>
|
||||
```
|
||||
### Example 2: How to migrate all files located in C:\\Data except files in C:\\Data\\tmp
|
||||
The following .xml file migrates all files and subfolders in C:\\Data, except the files and subfolders in C:\\Data\\tmp.
|
||||
|
||||
### Example 2: How to migrate all files located in `C:\Data` except files in `C:\Data\tmp`
|
||||
|
||||
The following .xml file migrates all files and subfolders in `C:\Data`, except the files and subfolders in `C:\Data\tmp`.
|
||||
|
||||
``` xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
@ -94,7 +100,8 @@ The following .xml file migrates all files and subfolders in C:\\Data, except th
|
||||
```
|
||||
|
||||
### Example 3: How to exclude the files in a folder but include all subfolders
|
||||
The following .xml file migrates any subfolders in C:\\EngineeringDrafts, but excludes all files that are in C:\\EngineeringDrafts.
|
||||
|
||||
The following .xml file migrates any subfolders in `C:\`EngineeringDrafts`, but excludes all files that are in `C:\EngineeringDrafts`.
|
||||
|
||||
``` xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
@ -119,7 +126,8 @@ The following .xml file migrates any subfolders in C:\\EngineeringDrafts, but ex
|
||||
```
|
||||
|
||||
### Example 4: How to exclude a file from a specific folder
|
||||
The following .xml file migrates all files and subfolders in C:\\EngineeringDrafts, except for the Sample.doc file in C:\\EngineeringDrafts.
|
||||
|
||||
The following .xml file migrates all files and subfolders in `C:\EngineeringDrafts`, except for the `Sample.doc` file in `C:\EngineeringDrafts`.
|
||||
|
||||
``` xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
@ -144,22 +152,26 @@ The following .xml file migrates all files and subfolders in C:\\EngineeringDraf
|
||||
```
|
||||
|
||||
### Example 5: How to exclude a file from any location
|
||||
To exclude a Sample.doc file from any location on the C: drive, use the <pattern> element. If multiple files exist with the same name on the C: drive, all of these files will be excluded.
|
||||
|
||||
To exclude a Sample.doc file from any location on the C: drive, use the **<pattern>** element. If multiple files exist with the same name on the C: drive, all of these files will be excluded.
|
||||
|
||||
``` xml
|
||||
<pattern type="File"> C:\* [Sample.doc] </pattern>
|
||||
```
|
||||
|
||||
To exclude a Sample.doc file from any drive on the computer, use the <script> element. If multiple files exist with the same name, all of these files will be excluded.
|
||||
To exclude a Sample.doc file from any drive on the computer, use the **<script>** element. If multiple files exist with the same name, all of these files will be excluded.
|
||||
|
||||
``` xml
|
||||
<script>MigXmlHelper.GenerateDrivePatterns("* [sample.doc]", "Fixed")</script>
|
||||
```
|
||||
|
||||
#### Examples of how to use XML to exclude files, folders, and registry keys
|
||||
|
||||
Here are some examples of how to use XML to exclude files, folders, and registry keys. For more info, see [USMT XML Reference](usmt-xml-reference.md)
|
||||
|
||||
**Example 1: How to exclude all .mp3 files**<br>
|
||||
The following .xml file excludes all .mp3 files from the migration:
|
||||
##### Example 1: How to exclude all .mp3 files
|
||||
|
||||
The following .xml file excludes all `.mp3` files from the migration:
|
||||
|
||||
``` xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/excludefiles">
|
||||
@ -177,7 +189,9 @@ The following .xml file excludes all .mp3 files from the migration:
|
||||
</component>
|
||||
</migration>
|
||||
```
|
||||
**Example 2: How to exclude all of the files on a specific drive**<br>
|
||||
|
||||
##### Example 2: How to exclude all of the files on a specific drive
|
||||
|
||||
The following .xml file excludes only the files located on the C: drive.
|
||||
|
||||
``` xml
|
||||
@ -196,8 +210,10 @@ The following .xml file excludes only the files located on the C: drive.
|
||||
</component>
|
||||
</migration>
|
||||
```
|
||||
**Example 3: How to exclude registry keys**<br>
|
||||
The following .xml file unconditionally excludes the HKEY_CURRENT_USER registry key and all of its subkeys.
|
||||
|
||||
##### Example 3: How to exclude registry keys
|
||||
|
||||
The following .xml file unconditionally excludes the `HKEY_CURRENT_USER` registry key and all of its subkeys.
|
||||
|
||||
``` xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
@ -221,8 +237,10 @@ The following .xml file unconditionally excludes the HKEY_CURRENT_USER registry
|
||||
</component>
|
||||
</migration>
|
||||
```
|
||||
**Example 4: How to Exclude `C:\Windows` and `C:\Program Files`**<br>
|
||||
The following .xml file unconditionally excludes the system folders of `C:\Windows` and `C:\Program Files`. Note that all \*.docx, \*.xls and \*.ppt files will not be migrated because the <unconditionalExclude> element takes precedence over the <include> element.
|
||||
|
||||
##### Example 4: How to Exclude `C:\Windows` and `C:\Program Files`
|
||||
|
||||
The following .xml file unconditionally excludes the system folders of `C:\Windows` and `C:\Program Files`. Note that all `*.docx`, `*.xls` and `*.ppt` files won't be migrated because the **<unconditionalExclude>** element takes precedence over the **<include>** element.
|
||||
|
||||
``` xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
@ -249,29 +267,24 @@ The following .xml file unconditionally excludes the system folders of `C:\Windo
|
||||
</component>
|
||||
</migration>
|
||||
```
|
||||
|
||||
## Create a Config XML File
|
||||
You can create and modify a Config.xml file if you want to exclude components from the migration. 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. Config.xml is an optional file that you can create using the **/genconfig** command-line option with the ScanState tool. For example, you can use the Config.xml file to exclude the settings for one of the default applications. In addition, creating and modifying this file is the only way to exclude the operating-system settings that are migrated to computers running Windows.
|
||||
|
||||
- **To exclude the settings for a default application:** Specify `migrate="no"` for the application under the <Applications> section of the Config.xml file.
|
||||
You can create and modify a `Config.xml` file if you want to exclude components from the migration. Excluding components using this file is easier than modifying the migration .xml files because you don't need to be familiar with the migration rules and syntax. `Config.xml` is an optional file that you can create using the `/genconfig` command-line option with the ScanState tool. For example, you can use the `Config.xml` file to exclude the settings for one of the default applications. In addition, creating and modifying this file is the only way to exclude the operating-system settings that are migrated to computers running Windows.
|
||||
|
||||
- **To exclude an operating system setting:** Specify `migrate="no"` for the setting under the <WindowsComponents> section.
|
||||
- **To exclude the settings for a default application:** Specify `migrate="no"` for the application under the **<Applications>** section of the `Config.xml` file.
|
||||
|
||||
- **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.
|
||||
- **To exclude an operating system setting:** Specify `migrate="no"` for the setting under the **<WindowsComponents>** section.
|
||||
|
||||
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.
|
||||
|
||||
## Related topics
|
||||
- [Customize USMT XML Files](usmt-customize-xml-files.md)
|
||||
- [USMT XML Reference](usmt-xml-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
- **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 won't.
|
||||
|
||||
For more information, see [Config.xml File](usmt-configxml-file.md).
|
||||
|
||||
> [!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.
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Customize USMT XML files](usmt-customize-xml-files.md)
|
||||
|
||||
- [USMT XML reference](usmt-xml-reference.md)
|
||||
|
||||
@ -11,110 +11,100 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Extract Files from a Compressed USMT Migration Store
|
||||
# Extract files from a compressed USMT migration store
|
||||
|
||||
When you migrate files and settings during a typical PC-refresh migration, you usually create a compressed migration store file on the intermediate store. This migration store is a single image file that contains all files being migrated as well as a catalog file. To protect the compressed file, you can encrypt it by using different encryption algorithms. When you migrate the file back to the source computer after the operating system is installed, you can run the **USMTUtils** command with the `/extract` option to recover the files from the compressed migration store. You can also use the **USMTUtils** command with the `/extract` option any time you need to recover data from a migration store.
|
||||
|
||||
When you migrate files and settings during a typical PC-refresh migration, you usually create a compressed migration store file on the intermediate store. This migration store is a single image file that contains all files being migrated as well as a catalog file. To protect the compressed file, you can encrypt it by using different encryption algorithms. When you migrate the file back to the source computer after the operating system is installed, you can run the **Usmtutils** command with the **/extract** option to recover the files from the compressed migration store. You can also use the **Usmtutils** command with the **/extract** option any time you need to recover data from a migration store.
|
||||
Options used with the `/extract` option can specify:
|
||||
|
||||
Options used with the **/extract** option can specify:
|
||||
- The cryptographic algorithm that was used to create the migration store.
|
||||
|
||||
- The cryptographic algorithm that was used to create the migration store.
|
||||
- The encryption key or the text file that contains the encryption key.
|
||||
|
||||
- The encryption key or the text file that contains the encryption key.
|
||||
- Include and exclude patterns for selective data extraction.
|
||||
|
||||
- Include and exclude patterns for selective data extraction.
|
||||
|
||||
In addition, you can specify the file patterns that you want to extract by using the **/i** option to include file patterns or the **/e** option to exclude file patterns. When both the **/i** option and the **/e** option are used in the same command, include patterns take precedence over exclude patterns. Note that this is different from the include and exclude rules used in the ScanState and LoadState tools.
|
||||
In addition, you can specify the file patterns that you want to extract by using the `/i` option to include file patterns or the `/e` option to exclude file patterns. When both the `/i` option and the `/e` option are used in the same command, include patterns take precedence over exclude patterns. Note that this is different from the include and exclude rules used in the ScanState and LoadState tools.
|
||||
|
||||
## In this topic
|
||||
|
||||
- [To run the USMTUtils tool with the /extract option](#to-run-the-usmtutils-tool-with-the-extract-option)
|
||||
|
||||
- [To run the USMTutils tool with the /extract option](#bkmk-extractsyntax)
|
||||
- [To extract all files from a compressed migration store](#to-extract-all-files-from-a-compressed-migration-store)
|
||||
|
||||
- [To extract all files from a compressed migration store](#bkmk-extractallfiles)
|
||||
- [To extract specific file types from an encrypted compressed migration store](#to-extract-specific-file-types-from-an-encrypted-compressed-migration-store)
|
||||
|
||||
- [To extract specific file types from an encrypted compressed migration store](#bkmk-extractspecificfiles)
|
||||
- [To extract all but one, or more, file types from an encrypted compressed migration store](#to-extract-all-but-one-or-more-file-types-from-an-encrypted-compressed-migration-store)
|
||||
|
||||
- [To extract all but one, or more, file types from an encrypted compressed migration store](#bkmk-excludefilepattern)
|
||||
- [To extract file types using the include pattern and the exclude pattern](#to-extract-file-types-using-the-include-pattern-and-the-exclude-pattern)
|
||||
|
||||
- [To extract file types using the include pattern and the exclude pattern](#bkmk-includeexcludefiles)
|
||||
### To run the USMTUtils tool with the /extract option
|
||||
|
||||
### <a href="" id="bkmk-extractsyntax"></a>To run the USMTutils tool with the /extract option
|
||||
To extract files from the compressed migration store onto the destination computer, use the following USMTUtils syntax:
|
||||
|
||||
To extract files from the compressed migration store onto the destination computer, use the following USMTutils syntax:
|
||||
|
||||
Cd /d <USMTpath> usmtutils /extract <filePath> <destinationPath> \[/i:<includePattern>\] \[/e:<excludePattern>\] \[/l:<logfile>\] \[/decrypt\[:<AlgID>\] {/key:<keystring> | /keyfile:<filename>}\] \[/o\]
|
||||
``` syntax
|
||||
usmtutils.exe /extract <filePath> <destinationPath> [/i:<includePattern>] [/e:<excludePattern>] [/l:<logfile>] [/decrypt[:<AlgID>] {/key:<keystring> | /keyfile:<filename>}] [/o]
|
||||
```
|
||||
|
||||
Where the placeholders have the following values:
|
||||
|
||||
- *<USMTpath>* is the location where you have saved the USMT files and tools.
|
||||
- **<USMTpath>** is the location where you have saved the USMT files and tools.
|
||||
|
||||
- *<filePath>* is the location of the migration store.
|
||||
- **<filePath>** is the location of the migration store.
|
||||
|
||||
- *<destination path>* is the location of the file where you want the **/extract** option to put the extracted migration store contents.
|
||||
- **<destination path>** is the location of the file where you want the **/extract** option to put the extracted migration store contents.
|
||||
|
||||
- *<includePattern>* specifies the pattern for the files to include in the extraction.
|
||||
- **<includePattern>** specifies the pattern for the files to include in the extraction.
|
||||
|
||||
- *<excludePattern>* specifies the pattern for the files to omit from the extraction.
|
||||
- **<excludePattern>** specifies the pattern for the files to omit from the extraction.
|
||||
|
||||
- *<AlgID>* is the cryptographic algorithm that was used to create the migration store on the **ScanState** command line.
|
||||
- **<AlgID>** is the cryptographic algorithm that was used to create the migration store on the `scanstate.exe` command line.
|
||||
|
||||
- *<logfile>* is the location and name of the log file.
|
||||
- **<logfile>** is the location and name of the log file.
|
||||
|
||||
- *<keystring>* is the encryption key that was used to encrypt the migration store.
|
||||
- **<keystring>** is the encryption key that was used to encrypt the migration store.
|
||||
|
||||
- *<filename>* is the location and name of the text file that contains the encryption key.
|
||||
- **<filename>** is the location and name of the text file that contains the encryption key.
|
||||
|
||||
### <a href="" id="bkmk-extractallfiles"></a>To extract all files from a compressed migration store
|
||||
### To extract all files from a compressed migration store
|
||||
|
||||
To extract everything from a compressed migration store to a file on the C:\\ drive, type:
|
||||
|
||||
``` syntax
|
||||
usmtutils /extract D:\MyMigrationStore\USMT\store.mig C:\ExtractedStore
|
||||
usmtutils.exe /extract D:\MyMigrationStore\USMT\store.mig C:\ExtractedStore
|
||||
```
|
||||
|
||||
### <a href="" id="bkmk-extractspecificfiles"></a>To extract specific file types from an encrypted compressed migration store
|
||||
### To extract specific file types from an encrypted compressed migration store
|
||||
|
||||
To extract specific files, such as .txt and .pdf files, from an encrypted compressed migration store, type:
|
||||
|
||||
``` syntax
|
||||
usmtutils /extract D:\MyMigrationStore\USMT\store.mig /i:"*.txt,*.pdf" C:\ExtractedStore /decrypt /keyfile:D:\encryptionKey.txt
|
||||
usmtutils.exe /extract D:\MyMigrationStore\USMT\store.mig /i:"*.txt,*.pdf" C:\ExtractedStore /decrypt /keyfile:D:\encryptionKey.txt
|
||||
```
|
||||
|
||||
In this example, the file is encrypted and the encryption key is located in a text file called encryptionKey.
|
||||
|
||||
### <a href="" id="bkmk-excludefilepattern"></a>To extract all but one, or more, file types from an encrypted compressed migration store
|
||||
### To extract all but one, or more, file types from an encrypted compressed migration store
|
||||
|
||||
To extract all files except for one file type, such as .exe files, from an encrypted compressed migration store, type:
|
||||
|
||||
``` syntax
|
||||
usmtutils /extract D:\MyMigrationStore\USMT\store.mig /e:*.exe C:\ExtractedStore /decrypt:AES_128 /key:password /l:C:\usmtutilslog.txt
|
||||
usmtutils.exe /extract D:\MyMigrationStore\USMT\store.mig /e:*.exe C:\ExtractedStore /decrypt:AES_128 /key:password /l:C:\usmtutilslog.txt
|
||||
```
|
||||
|
||||
### <a href="" id="bkmk-includeexcludefiles"></a>To extract file types using the include pattern and the exclude pattern
|
||||
### To extract file types using the include pattern and the exclude pattern
|
||||
|
||||
To extract files from a compressed migration store, and to exclude files of one type (such as .exe files) while including only specific files, use both the include pattern and the exclude pattern, as in this example:
|
||||
|
||||
``` syntax
|
||||
usmtutils /extract D:\MyMigrationStore\USMT\store.mig /i:myProject.* /e:*.exe C:\ExtractedStore /o
|
||||
usmtutils.exe /extract D:\MyMigrationStore\USMT\store.mig /i:myProject.* /e:*.exe C:\ExtractedStore /o
|
||||
```
|
||||
|
||||
In this example, if there is a myProject.exe file, it will also be extracted because the include pattern option takes precedence over the exclude pattern option.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[UsmtUtils Syntax](usmt-utilities.md)
|
||||
|
||||
[Return Codes](usmt-return-codes.md)
|
||||
|
||||
[Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
[USMTUtils syntax](usmt-utilities.md)
|
||||
|
||||
[Return codes](usmt-return-codes.md)
|
||||
|
||||
[Verify the condition of a compressed migration store](verify-the-condition-of-a-compressed-migration-store.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
### YamlMime:FAQ
|
||||
metadata:
|
||||
title: 'Frequently Asked Questions (Windows 10)'
|
||||
description: 'Learn about frequently asked questions and recommended solutions for migrations using User State Migration Tool (USMT) 10.0.'
|
||||
description: 'Learn about frequently asked questions and recommended solutions for migrations using User State Migration Tool (USMT) 10.0.'
|
||||
ms.assetid: 813c13a7-6818-4e6e-9284-7ee49493241b
|
||||
ms.reviewer:
|
||||
author: frankroj
|
||||
@ -15,7 +15,7 @@ metadata:
|
||||
ms.topic: faq
|
||||
title: Frequently Asked Questions
|
||||
summary: |
|
||||
The following sections provide frequently asked questions and recommended solutions for migrations using User State Migration Tool (USMT) 10.0.
|
||||
The following sections provide frequently asked questions and recommended solutions for migrations using User State Migration Tool (USMT) 10.0.
|
||||
|
||||
|
||||
sections:
|
||||
@ -24,7 +24,7 @@ sections:
|
||||
- question: |
|
||||
How much space is needed on the destination computer?
|
||||
answer: |
|
||||
The destination computer needs enough available space for the following:
|
||||
The destination computer needs enough available space for the following items:
|
||||
|
||||
- Operating system
|
||||
|
||||
@ -35,100 +35,100 @@ sections:
|
||||
- question: |
|
||||
Can I store the files and settings directly on the destination computer or do I need a server?
|
||||
answer: |
|
||||
You do not need to save the files to a server. If you are moving the user state to a new computer, you can create the store on a shared folder, on media that you can remove, such as a USB flash drive (UFD), or you can store it directly on the destination computer, as in the following steps:
|
||||
You don't need to save the files to a server. If you're moving the user state to a new computer, you can create the store on a shared folder, on media that you can remove, such as a USB flash drive (UFD), or you can store it directly on the destination computer, as in the following steps:
|
||||
|
||||
1. Create and share the directory C:\\store on the destination computer.
|
||||
1. Create and share the directory `C:\store` on the destination computer.
|
||||
|
||||
2. Run the ScanState tool on the source computer and save the files and settings to \\\\*DestinationComputerName*\\store
|
||||
2. Run the **ScanState** tool on the source computer and save the files and settings to `\\<DestinationComputerName>\store`
|
||||
|
||||
3. Run the LoadState tool on the destination computer and specify C:\\store as the store location.
|
||||
3. Run the **LoadState** tool on the destination computer and specify `C:\store` as the store location.
|
||||
|
||||
- question: |
|
||||
Can I migrate data between operating systems with different languages?
|
||||
answer: |
|
||||
No. USMT does not support migrating data between operating systems with different languages; the source computer's operating-system language must match the destination computer's operating-system language.
|
||||
No. USMT doesn't support migrating data between operating systems with different languages; the source computer's operating-system language must match the destination computer's operating-system language.
|
||||
|
||||
- question: |
|
||||
Can I change the location of the temporary directory on the destination computer?
|
||||
answer: |
|
||||
Yes. The environment variable USMT\_WORKING\_DIR can be changed to an alternative temporary directory. There are some offline migration scenarios where this is necessary, for example, when the USMT binaries are located on read-only Windows Preinstallation Environment (WinPE) boot media.
|
||||
Yes. The environment variable `USMT\_WORKING\_DIR` can be changed to an alternative temporary directory. There are some offline migration scenarios where changing the temporary directory is necessary, for example, when the USMT binaries are located on read-only Windows Preinstallation Environment (WinPE) boot media.
|
||||
|
||||
- question: |
|
||||
How do I install USMT?
|
||||
answer: |
|
||||
Because USMT is included in Windows Assessment and Deployment Kit (Windows ADK), you need to install the Windows ADK package on at least one computer in your environment. However, the USMT binaries are designed to be deployed using xcopy. This means that they are installed on a computer simply by recursively copying the USMT directory from the computer containing the Windows ADK to each client computer.
|
||||
Because USMT is included in Windows Assessment and Deployment Kit (Windows ADK), you need to install the Windows ADK package on at least one computer in your environment. The USMT binaries can then be copied from the USMT directory located on the original computer where the Windows ADK was installed to additional client computers.
|
||||
|
||||
- question: |
|
||||
How do I uninstall USMT?
|
||||
answer: |
|
||||
If you have installed the Windows ADK on the computer, uninstalling Windows ADK will uninstall USMT. For client computers that do not have the Windows ADK installed, you can simply delete the USMT directory to uninstall USMT.
|
||||
If you've installed the Windows ADK on the computer, uninstalling Windows ADK will uninstall USMT. For client computers that don't have the Windows ADK installed, you can delete the USMT directory to uninstall USMT.
|
||||
|
||||
- name: Files and Settings
|
||||
questions:
|
||||
- question: |
|
||||
How can I exclude a folder or a certain type of file from the migration?
|
||||
answer: |
|
||||
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).
|
||||
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) article. For the syntax of this element, see [XML elements library](usmt-xml-elements-library.md).
|
||||
|
||||
- question: |
|
||||
What happens to files that were located on a drive that does not exist on the destination computer?
|
||||
What happens to files that were located on a drive that don't exist on the destination computer?
|
||||
answer: |
|
||||
USMT migrates the files to the %SystemDrive% while maintaining the correct folder hierarchy. For example, if E:\\data\\File.pst is on the source computer, but the destination computer does not have an E:\\ drive, the file will be migrated to C:\\data\\File.pst, if C:\\ is the system drive. This holds true even when <locationModify> rules attempt to move data to a drive that does not exist on the destination computer.
|
||||
USMT migrates the files to the `%SystemDrive%` while maintaining the correct folder hierarchy. For example, if `E:\data\File.pst` is on the source computer, but the destination computer doesn't have an E:\\ drive, the file will be migrated to `C:\data\File.pst`, if C:\\ is the system drive. This behavior holds true even when **<locationModify>** rules attempt to move data to a drive that doesn't exist on the destination computer.
|
||||
|
||||
- name: USMT .xml Files
|
||||
questions:
|
||||
- question: |
|
||||
Where can I get examples of USMT .xml files?
|
||||
answer: |
|
||||
The following topics include examples of USMT .xml files:
|
||||
The following articles include examples of USMT .xml files:
|
||||
|
||||
- [Exclude Files and Settings](usmt-exclude-files-and-settings.md)
|
||||
- [Exclude files and settings](usmt-exclude-files-and-settings.md)
|
||||
|
||||
- [Reroute Files and Settings](usmt-reroute-files-and-settings.md)
|
||||
- [Reroute files and settings](usmt-reroute-files-and-settings.md)
|
||||
|
||||
- [Include Files and Settings](usmt-include-files-and-settings.md)
|
||||
- [Include files and settings](usmt-include-files-and-settings.md)
|
||||
|
||||
- [Custom XML Examples](usmt-custom-xml-examples.md)
|
||||
- [Custom XML examples](usmt-custom-xml-examples.md)
|
||||
|
||||
- question: |
|
||||
Can I use custom .xml files that were written for USMT 5.0?
|
||||
answer: |
|
||||
Yes. You can use custom .xml files that were written for USMT 5.0 with USMT for Windows 10. However, in order to use new USMT functionality, you must revisit your custom USMT files and refresh them to include the new command-line options and XML elements.
|
||||
Yes. You can use custom .xml files that were written for USMT 5.0 with USMT for Windows 10. However, in order to use new USMT functionality, you must revisit your custom USMT files and refresh them to include the new command-line options and XML elements.
|
||||
|
||||
- question: |
|
||||
How can I validate the .xml files?
|
||||
answer: |
|
||||
You can use the USMT XML Schema (MigXML.xsd) to write and validate migration .xml files.
|
||||
You can use the USMT XML Schema (`MigXML.xsd`) to write and validate migration .xml files.
|
||||
|
||||
- question: |
|
||||
Why must I list the .xml files with both the ScanState and LoadState commands?
|
||||
Why must I list the .xml files with both the `ScanState.exe` and `LoadState.exe` commands?
|
||||
answer: |
|
||||
The .xml files are not copied to the store as in previous versions of USMT. Because the ScanState and LoadState tools need the .xml files to control the migration, you must specify the same set of .xml files for the **ScanState** and **LoadState** commands. If you used a particular set of mig\*.xml files in the ScanState tool, either called through the "/auto" option, or individually through the "/i" option, then you should use same option to call the exact same mig\*.xml files in the LoadState tool. 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 with the **LoadState** command. **LoadState** will migrate only the files and settings that you want to migrate.
|
||||
The .xml files aren't copied to the store as in previous versions of USMT. Because the **ScanState** and **LoadState** tools need the .xml files to control the migration, you must specify the same set of .xml files for the `ScanState.exe` and `LoadState.exe` commands. If you used a particular set of mig\*.xml files in the **ScanState** tool, either called through the `/auto` option, or individually through the `/i` option, then you should use same option to call the exact same mig\*.xml files in the **LoadState** tool. However, you don't 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 type of migration, modify the `Config.xml` file and specify the updated file with the `LoadState.exe` command. **LoadState** will migrate only the files and settings that you want to migrate.
|
||||
|
||||
If you exclude an .xml file from the **LoadState** command, then all of the data that is in the store that was migrated with the missing .xml files will be migrated. However, the migration rules that were specified for the **ScanState** command will not apply. For example, if you exclude a MigApp.xml file that has a rerouting rule such as `MigsysHelperFunction.RelativeMove("c:\data", "%CSIDL_PERSONAL%")`, USMT will not reroute the files. Instead, it will migrate them to C:\\data.
|
||||
If you exclude an .xml file from the `LoadState.exe` command, then all of the data that is in the store that was migrated with the missing .xml files will be migrated. However, the migration rules that were specified for the `ScanState.exe` command won't apply. For example, if you exclude a `MigApp.xml` file that has a rerouting rule such as `MigsysHelperFunction.RelativeMove("c:\data", "%CSIDL_PERSONAL%")`, USMT won't reroute the files. Instead, it will migrate them to `C:\data`.
|
||||
|
||||
- question: |
|
||||
Which files can I modify and specify on the command line?
|
||||
answer: |
|
||||
You can specify the MigUser.xml and MigApp.xml files on the command line. You can modify each of these files. The migration of operating system settings is controlled by the manifests, which you cannot modify. If you want to exclude certain operating-system settings or any other components, create and modify the Config.xml file.
|
||||
You can specify the `MigUser.xml` and `MigApp.xml` files on the command line. You can modify each of these files. The migration of operating system settings is controlled by the manifests, which you can't modify. If you want to exclude certain operating-system settings or any other components, create and modify the `Config.xml` file.
|
||||
|
||||
- question: |
|
||||
What happens if I do not specify the .xml files on the command line?
|
||||
What happens if I don't specify the .xml files on the command line?
|
||||
answer: |
|
||||
- **ScanState**
|
||||
|
||||
If you do not specify any files with the **ScanState** command, all user accounts and default operating system components are migrated.
|
||||
If you don't specify any files with the `ScanState.exe` command, all user accounts and default operating system components are migrated.
|
||||
|
||||
- **LoadState**
|
||||
|
||||
If you do not specify any files with the **LoadState** command, all data that is in the store is migrated. However, any target-specific migration rules that were specified in .xml files with the **ScanState** command will not apply. For example, if you exclude a MigApp.xml file that has a rerouting rule such as `MigsysHelperFunction.RelativeMove("c:\data", "%CSIDL_PERSONAL%")`, USMT will not reroute the files. Instead, it will migrate them to C:\\data.
|
||||
If you don't specify any files with the `LoadState.exe` command, all data that is in the store is migrated. However, any target-specific migration rules that were specified in .xml files with the `ScanState.exe` command won't apply. For example, if you exclude a `MigApp.xml` file that has a rerouting rule such as `MigsysHelperFunction.RelativeMove("c:\data", "%CSIDL_PERSONAL%")`, USMT won't reroute the files. Instead, it will migrate them to `C:\data`.
|
||||
|
||||
- name: Conflicts and Precedence
|
||||
questions:
|
||||
- question: |
|
||||
What happens when there are conflicting XML rules or conflicting objects on the destination computer?
|
||||
answer: |
|
||||
For more information, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md).
|
||||
For more information, see [Conflicts and precedence](usmt-conflicts-and-precedence.md).
|
||||
|
||||
|
||||
additionalContent: |
|
||||
@ -137,6 +137,6 @@ additionalContent: |
|
||||
|
||||
[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)
|
||||
|
||||
[Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-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)
|
||||
[Verify the condition of a compressed migration store](verify-the-condition-of-a-compressed-migration-store.md)
|
||||
|
||||
@ -11,53 +11,49 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# General Conventions
|
||||
|
||||
# General conventions
|
||||
|
||||
This topic describes the XML helper functions.
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
[General XML guidelines](#general-xml-guidelines)
|
||||
|
||||
[General XML Guidelines](#bkmk-general)
|
||||
|
||||
[Helper Functions](#bkmk-helperfunctions)
|
||||
|
||||
## <a href="" id="bkmk-general"></a>General XML Guidelines
|
||||
[Helper functions](#helper-functions)
|
||||
|
||||
## General XML guidelines
|
||||
|
||||
Before you modify the .xml files, become familiar with the following guidelines:
|
||||
|
||||
- **XML schema**
|
||||
- **XML schema**
|
||||
|
||||
You can use the User State Migration Tool (USMT) 10.0 XML schema, MigXML.xsd, to write and validate migration .xml files.
|
||||
You can use the User State Migration Tool (USMT) 10.0 XML schema, MigXML.xsd, to write and validate migration .xml files.
|
||||
|
||||
- **Conflicts**
|
||||
- **Conflicts**
|
||||
|
||||
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).
|
||||
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**
|
||||
- **Required elements**
|
||||
|
||||
The required elements for a migration .xml file are **<migration>**, **<component>**, **<role>**, and **<rules>**.
|
||||
|
||||
- **Required child elements**
|
||||
- **Required child elements**
|
||||
|
||||
- USMT does not fail with an error if you do not specify the required child elements. However, you must specify the required child elements for the parent element to affect the migration.
|
||||
- USMT doesn't fail with an error if you don't specify the required child elements. However, you must specify the required child elements for the parent element to affect the migration.
|
||||
|
||||
- The required child elements apply only to the first definition of the element. If these elements are defined and then referred to using their name, the required child elements do not apply. For example, if you define `<detects name="Example">` in **<namedElements>**, and you specify `<detects name="Example"/>` in **<component>** to refer to this element, the definition inside **<namedElements>** must have the required child elements, but the **<component>** element does not need to have the required child elements.
|
||||
- The required child elements apply only to the first definition of the element. If these elements are defined and then referred to using their name, the required child elements don't apply. For example, if you define `<detects name="Example">` in **<namedElements>**, and you specify `<detects name="Example"/>` in **<component>** to refer to this element, the definition inside **<namedElements>** must have the required child elements, but the **<component>** element doesn't need to have the required child elements.
|
||||
|
||||
- **File names with brackets**
|
||||
- **File names with brackets**
|
||||
|
||||
If you are migrating a file that has a bracket character (\[ or \]) in the file name, you must insert a carat (^) character directly before the bracket for the bracket character to be valid. For example, if there is a file named **file].txt**, you must specify `<pattern type="File">c:\documents\mydocs [file^].txt]</pattern>` instead of `<pattern type="File">c:\documents\mydocs [file].txt]</pattern>`.
|
||||
If you're migrating a file that has a bracket character (\[ or \]) in the file name, you must insert a carat (^) character directly before the bracket for the bracket character to be valid. For example, if there's a file named **file].txt**, you must specify `<pattern type="File">c:\documents\mydocs [file^].txt]</pattern>` instead of `<pattern type="File">c:\documents\mydocs [file].txt]</pattern>`.
|
||||
|
||||
- **Using quotation marks**
|
||||
- **Using quotation marks**
|
||||
|
||||
When you surround code in quotation marks, you can use either double ("") or single (') quotation marks.
|
||||
|
||||
## <a href="" id="bkmk-helperfunctions"></a> Helper Functions
|
||||
## Helper functions
|
||||
|
||||
|
||||
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:
|
||||
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 items:
|
||||
|
||||
- **All of the parameters are strings**
|
||||
|
||||
@ -77,28 +73,18 @@ You can use the XML helper functions in the [XML Elements Library](usmt-xml-elem
|
||||
|
||||
- **The encoded location used in all the helper functions is an unambiguous string representation for the name of an object**
|
||||
|
||||
It is composed of the node part, optionally followed by the leaf enclosed in square brackets. This makes a clear distinction between nodes and leaves.
|
||||
It's composed of the node part, optionally followed by the leaf enclosed in square brackets. This format makes a clear distinction between nodes and leaves.
|
||||
|
||||
For example, specify the file C:\\Windows\\Notepad.exe: **c:\\Windows\[Notepad.exe\]**. Similarly, specify the directory C:\\Windows\\System32 like this: **c:\\Windows\\System32**; note the absence of the \[\] characters.
|
||||
For example, specify the file `C:\Windows\Notepad.exe`: **c:\\Windows\[Notepad.exe\]**. Similarly, specify the directory `C:\Windows\System32` like this: **c:\\Windows\\System32**; note the absence of the **\[\]** characters.
|
||||
|
||||
The registry is represented in a similar way. The default value of a registry key is represented as an empty \[\] construct. For example, the default value for the HKLM\\SOFTWARE\\MyKey registry key is **HKLM\\SOFTWARE\\MyKey\[\]**.
|
||||
The registry is represented in a similar way. The default value of a registry key is represented as an empty **\[\]** construct. For example, the default value for the `HKLM\SOFTWARE\MyKey` registry key is **HKLM\\SOFTWARE\\MyKey\[\]**.
|
||||
|
||||
- **You specify a location pattern in a way that is similar to how you specify an actual location**
|
||||
|
||||
The exception is that both the node and leaf part accept patterns. However, a pattern from the node does not extend to the leaf.
|
||||
|
||||
For example, the pattern **c:\\Windows\\\\*** will match the \\Windows directory and all subdirectories, but it will not match any of the files in those directories. To match the files as well, you must specify **c:\\Windows\\\*\[\*\]**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[USMT XML Reference](usmt-xml-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The exception is that both the node and leaf part accept patterns. However, a pattern from the node doesn't extend to the leaf.
|
||||
|
||||
For example, the pattern **c:\\Windows\\\\\*** will match the `\Windows` directory and all subdirectories, but it will not match any of the files in those directories. To match the files as well, you must specify **c:\\Windows\\\*\[\*\]**.
|
||||
|
||||
## Related articles
|
||||
|
||||
[USMT XML reference](usmt-xml-reference.md)
|
||||
|
||||
Reference in New Issue
Block a user