mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 11:53:37 +00:00
Updated mete -descriptions
This commit is contained in:
Jeff Reeds (Aquent LLC)
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: User State Migration Tool (USMT) - Getting Started (Windows 10)
|
||||
description: Getting Started with the User State Migration Tool (USMT)
|
||||
description: Plan, collect, and prepare your source computer for migration using the User State Migration Tool (USMT).
|
||||
ms.assetid: 506ff1d2-94b8-4460-8672-56aad963504b
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Understanding Migration XML Files (Windows 10)
|
||||
description: Understanding Migration XML Files
|
||||
description: Modify the behavior of a basic User State Migration Tool (USMT) 10.0 migration by using XML files.
|
||||
ms.assetid: d3d1fe89-085c-4da8-9657-fd54b8bfc4b7
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,139 +1,140 @@
|
||||
---
|
||||
title: Estimate Migration Store Size (Windows 10)
|
||||
description: Estimate Migration Store Size
|
||||
ms.assetid: cfb9062b-7a2a-467a-a24e-0b31ce830093
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Estimate Migration Store Size
|
||||
|
||||
|
||||
The disk space requirements for a migration are dependent on the size of the migration store and the type of migration. You can estimate the amount of disk space needed for computers in your organization based on information about your organization's infrastructure. You can also calculate the disk space requirements using the ScanState tool.
|
||||
|
||||
## In This Topic
|
||||
|
||||
|
||||
- [Hard Disk Space Requirements](#bkmk-spacereqs). Describes the disk space requirements for the migration store and other considerations on the source and destination computers.
|
||||
|
||||
- [Calculate Disk Space Requirements Using the ScanState Tool](#bkmk-calcdiskspace). Describes how to use the ScanState tool to determine how big the migration store will be on a particular computer.
|
||||
|
||||
- [Estimate Migration Store Size](#bkmk-estmigstoresize). Describes how to estimate the average size of migration stores for the computers in your organization, based on your infrastructure.
|
||||
|
||||
## <a href="" id="bkmk-spacereqs"></a>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](usmt-choose-migration-store-type.md).
|
||||
|
||||
- **Source Computer.** The source computer needs enough available space for the following:
|
||||
|
||||
- [E250 megabytes (MB) minimum of hard disk space.](#bkmk-estmigstoresize) Space is needed to support the User State Migration Tool (USMT) 10.0 operations, for example, growth in the page file. Provided that every volume involved in the migration is formatted as NTFS, 250 MB should be enough space to ensure success for almost every hard-link migration, regardless of the size of the migration. The USMT tools will not create the migration store if 250 MB of disk space is not available.
|
||||
|
||||
- [Temporary space for USMT to run.](#bkmk-estmigstoresize) Additional disk space for the USMT tools to operate is required. This does not include the minimum 250 MB needed to create the migration store. The amount of temporary space required can be calculated using the ScanState tool.
|
||||
|
||||
- [Hard-link migration store.](#bkmk-estmigstoresize) It is not necessary to estimate the size of a hard-link migration store. The only case where the hard-link store can be quite large is when non-NTFS file systems exist on the system and contain data being migrated.
|
||||
|
||||
- [Destination computer.](#bkmk-estmigstoresize) The destination computer needs enough available space for the following:
|
||||
|
||||
- [Operating system.](#bkmk-estmigstoresize)
|
||||
|
||||
- [Applications.](#bkmk-estmigstoresize)
|
||||
|
||||
- [Data being migrated.](#bkmk-estmigstoresize) It is important to consider that in addition to the files being migrated, registry information will also require hard disk space for storage.
|
||||
|
||||
- [Temporary space for USMT to run.](#bkmk-estmigstoresize) Additional disk space for the USMT tools to operate is required. The amount of temporary space required can be calculated using the ScanState tool.
|
||||
|
||||
## <a href="" id="bkmk-calcdiskspace"></a>Calculate Disk Space Requirements using the ScanState Tool
|
||||
|
||||
|
||||
You can use the ScanState tool to calculate the disk space requirements for a particular compressed or uncompressed migration. It is not necessary to estimate the migration store size for a hard-link migration since this method does not create a separate migration store. The ScanState tool provides disk space requirements for the state of the computer at the time the tool is run. The state of the computer may change during day to day use so it is recommended that you use the calculations as an estimate when planning your migration.
|
||||
|
||||
**To run the ScanState tool on the source computer with USMT installed,**
|
||||
|
||||
1. Open a command prompt with administrator privileges.
|
||||
|
||||
2. Navigate to the USMT tools. For example, type
|
||||
|
||||
``` syntax
|
||||
cd /d "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\User State Migration Tool\<architecture>"
|
||||
```
|
||||
|
||||
Where *<architecture>* is x86 or amd64.
|
||||
|
||||
3. Run the **ScanState** tool to generate an XML report of the space requirements. At the command prompt, type
|
||||
|
||||
``` syntax
|
||||
ScanState.exe <StorePath> /p:<path to a file>
|
||||
```
|
||||
|
||||
Where *<StorePath>* is a path to a directory where the migration store will be saved and *<path to a file>* is the path and filename where the XML report for space requirements will be saved. For example,
|
||||
|
||||
``` syntax
|
||||
ScanState.exe c:\store /p:c:\spaceRequirements.xml
|
||||
```
|
||||
|
||||
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](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.
|
||||
|
||||
|
||||
|
||||
The space requirements report provides two elements, <**storeSize**> and <**temporarySpace**>. The <**temporarySpace**> value shows the disk space, in bytes, that USMT uses to operate during the migration—this does not include the minimum 250 MB needed to support USMT. The <**storeSize**> value shows the disk space, in bytes, required to host the migration store contents on both the source and destination computers. The following example shows a report generated using **/p:***<path to a file>*.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<PreMigration>
|
||||
<storeSize>
|
||||
<size clusterSize="4096">11010592768</size>
|
||||
</storeSize>
|
||||
<temporarySpace>
|
||||
<size>58189144</size>
|
||||
</temporarySpace>
|
||||
</PreMigration>
|
||||
```
|
||||
|
||||
Additionally, USMT performs a compliance check for a required minimum of 250 MB of available disk space and will not create a store if the compliance check fails.
|
||||
|
||||
## <a href="" id="bkmk-estmigstoresize"></a>Estimate Migration Store Size
|
||||
|
||||
|
||||
Determine how much space you will need to store the migrated data. You should base your calculations on the volume of e-mail, personal documents, and system settings for each user. The best way to estimate these is to survey several computers to arrive at an average for the size of the store that you will need.
|
||||
|
||||
The amount of space that is required in the store will vary, depending on the local storage strategies your organization uses. For example, one key element that determines the size of migration data sets is e-mail storage. If e-mail is stored centrally, data sets will be smaller. If e-mail is stored locally, such as offline-storage files, data sets will be larger. Mobile users will typically have larger data sets than workstation users. You should perform tests and inventory the network to determine the average data set size in your organization.
|
||||
|
||||
**Note**
|
||||
You can create a space-estimate file (Usmtsize.txt), by using the legacy **/p** command-line option to estimate the size of the store.
|
||||
|
||||
|
||||
|
||||
When trying to determine how much disk space you will need, consider the following issues:
|
||||
|
||||
- **E-mail** : If users deal with a large volume of e-mail or keep e-mail on their local computers instead of on a mail server, the e-mail can take up as much disk space as all other user files combined. Prior to migrating user data, make sure that users who store e-mail locally synchronize their inboxes with their mail server.
|
||||
|
||||
- **User documents**: Frequently, all of a user's documents fit into less than 50 MB of space, depending on the types of files involved. This estimate assumes typical office work, such as word-processing documents and spreadsheets. This estimate can vary substantially based on the types of documents that your organization uses. For example, an architectural firm that predominantly uses computer-aided design (CAD) files needs much more space than a law firm that primarily uses word-processing documents. You do not need to migrate the documents that users store on file servers through mechanisms such as Folder Redirection, as long as users will have access to these locations after the migration.
|
||||
|
||||
- **User system settings** Five megabytes is usually adequate space to save the registry settings. This requirement can fluctuate, however, based on the number of applications that have been installed. It is rare, however, for the user-specific portion of the registry to exceed 5 MB.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Common Migration Scenarios](usmt-common-migration-scenarios.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Estimate Migration Store Size (Windows 10)
|
||||
description: Estimate the disk space requirement for a migration so that you can use User State Migration Tool (USMT).
|
||||
ms.assetid: cfb9062b-7a2a-467a-a24e-0b31ce830093
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Estimate Migration Store Size
|
||||
|
||||
|
||||
The disk space requirements for a migration are dependent on the size of the migration store and the type of migration. You can estimate the amount of disk space needed for computers in your organization based on information about your organization's infrastructure. You can also calculate the disk space requirements using the ScanState tool.
|
||||
|
||||
## In This Topic
|
||||
|
||||
|
||||
- [Hard Disk Space Requirements](#bkmk-spacereqs). Describes the disk space requirements for the migration store and other considerations on the source and destination computers.
|
||||
|
||||
- [Calculate Disk Space Requirements Using the ScanState Tool](#bkmk-calcdiskspace). Describes how to use the ScanState tool to determine how big the migration store will be on a particular computer.
|
||||
|
||||
- [Estimate Migration Store Size](#bkmk-estmigstoresize). Describes how to estimate the average size of migration stores for the computers in your organization, based on your infrastructure.
|
||||
|
||||
## <a href="" id="bkmk-spacereqs"></a>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](usmt-choose-migration-store-type.md).
|
||||
|
||||
- **Source Computer.** The source computer needs enough available space for the following:
|
||||
|
||||
- [E250 megabytes (MB) minimum of hard disk space.](#bkmk-estmigstoresize) Space is needed to support the User State Migration Tool (USMT) 10.0 operations, for example, growth in the page file. Provided that every volume involved in the migration is formatted as NTFS, 250 MB should be enough space to ensure success for almost every hard-link migration, regardless of the size of the migration. The USMT tools will not create the migration store if 250 MB of disk space is not available.
|
||||
|
||||
- [Temporary space for USMT to run.](#bkmk-estmigstoresize) Additional disk space for the USMT tools to operate is required. This does not include the minimum 250 MB needed to create the migration store. The amount of temporary space required can be calculated using the ScanState tool.
|
||||
|
||||
- [Hard-link migration store.](#bkmk-estmigstoresize) It is not necessary to estimate the size of a hard-link migration store. The only case where the hard-link store can be quite large is when non-NTFS file systems exist on the system and contain data being migrated.
|
||||
|
||||
- [Destination computer.](#bkmk-estmigstoresize) The destination computer needs enough available space for the following:
|
||||
|
||||
- [Operating system.](#bkmk-estmigstoresize)
|
||||
|
||||
- [Applications.](#bkmk-estmigstoresize)
|
||||
|
||||
- [Data being migrated.](#bkmk-estmigstoresize) It is important to consider that in addition to the files being migrated, registry information will also require hard disk space for storage.
|
||||
|
||||
- [Temporary space for USMT to run.](#bkmk-estmigstoresize) Additional disk space for the USMT tools to operate is required. The amount of temporary space required can be calculated using the ScanState tool.
|
||||
|
||||
## <a href="" id="bkmk-calcdiskspace"></a>Calculate Disk Space Requirements using the ScanState Tool
|
||||
|
||||
|
||||
You can use the ScanState tool to calculate the disk space requirements for a particular compressed or uncompressed migration. It is not necessary to estimate the migration store size for a hard-link migration since this method does not create a separate migration store. The ScanState tool provides disk space requirements for the state of the computer at the time the tool is run. The state of the computer may change during day to day use so it is recommended that you use the calculations as an estimate when planning your migration.
|
||||
|
||||
**To run the ScanState tool on the source computer with USMT installed,**
|
||||
|
||||
1. Open a command prompt with administrator privileges.
|
||||
|
||||
2. Navigate to the USMT tools. For example, type
|
||||
|
||||
``` syntax
|
||||
cd /d "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\User State Migration Tool\<architecture>"
|
||||
```
|
||||
|
||||
Where *<architecture>* is x86 or amd64.
|
||||
|
||||
3. Run the **ScanState** tool to generate an XML report of the space requirements. At the command prompt, type
|
||||
|
||||
``` syntax
|
||||
ScanState.exe <StorePath> /p:<path to a file>
|
||||
```
|
||||
|
||||
Where *<StorePath>* is a path to a directory where the migration store will be saved and *<path to a file>* is the path and filename where the XML report for space requirements will be saved. For example,
|
||||
|
||||
``` syntax
|
||||
ScanState.exe c:\store /p:c:\spaceRequirements.xml
|
||||
```
|
||||
|
||||
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](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.
|
||||
|
||||
|
||||
|
||||
The space requirements report provides two elements, <**storeSize**> and <**temporarySpace**>. The <**temporarySpace**> value shows the disk space, in bytes, that USMT uses to operate during the migration—this does not include the minimum 250 MB needed to support USMT. The <**storeSize**> value shows the disk space, in bytes, required to host the migration store contents on both the source and destination computers. The following example shows a report generated using **/p:***<path to a file>*.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<PreMigration>
|
||||
<storeSize>
|
||||
<size clusterSize="4096">11010592768</size>
|
||||
</storeSize>
|
||||
<temporarySpace>
|
||||
<size>58189144</size>
|
||||
</temporarySpace>
|
||||
</PreMigration>
|
||||
```
|
||||
|
||||
Additionally, USMT performs a compliance check for a required minimum of 250 MB of available disk space and will not create a store if the compliance check fails.
|
||||
|
||||
## <a href="" id="bkmk-estmigstoresize"></a>Estimate Migration Store Size
|
||||
|
||||
|
||||
Determine how much space you will need to store the migrated data. You should base your calculations on the volume of e-mail, personal documents, and system settings for each user. The best way to estimate these is to survey several computers to arrive at an average for the size of the store that you will need.
|
||||
|
||||
The amount of space that is required in the store will vary, depending on the local storage strategies your organization uses. For example, one key element that determines the size of migration data sets is e-mail storage. If e-mail is stored centrally, data sets will be smaller. If e-mail is stored locally, such as offline-storage files, data sets will be larger. Mobile users will typically have larger data sets than workstation users. You should perform tests and inventory the network to determine the average data set size in your organization.
|
||||
|
||||
**Note**
|
||||
You can create a space-estimate file (Usmtsize.txt), by using the legacy **/p** command-line option to estimate the size of the store.
|
||||
|
||||
|
||||
|
||||
When trying to determine how much disk space you will need, consider the following issues:
|
||||
|
||||
- **E-mail** : If users deal with a large volume of e-mail or keep e-mail on their local computers instead of on a mail server, the e-mail can take up as much disk space as all other user files combined. Prior to migrating user data, make sure that users who store e-mail locally synchronize their inboxes with their mail server.
|
||||
|
||||
- **User documents**: Frequently, all of a user's documents fit into less than 50 MB of space, depending on the types of files involved. This estimate assumes typical office work, such as word-processing documents and spreadsheets. This estimate can vary substantially based on the types of documents that your organization uses. For example, an architectural firm that predominantly uses computer-aided design (CAD) files needs much more space than a law firm that primarily uses word-processing documents. You do not need to migrate the documents that users store on file servers through mechanisms such as Folder Redirection, as long as users will have access to these locations after the migration.
|
||||
|
||||
- **User system settings** Five megabytes is usually adequate space to save the registry settings. This requirement can fluctuate, however, based on the number of applications that have been installed. It is rare, however, for the user-specific portion of the registry to exceed 5 MB.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Common Migration Scenarios](usmt-common-migration-scenarios.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,62 +1,63 @@
|
||||
---
|
||||
title: Identify Applications Settings (Windows 10)
|
||||
description: Identify Applications Settings
|
||||
ms.assetid: eda68031-9b02-4a5b-a893-3786a6505381
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# 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](usmt-customize-xml-files.md).
|
||||
|
||||
## Applications
|
||||
|
||||
|
||||
First, create and prioritize a list of applications that to be migrated. It may be helpful to review the application lists and decide which applications will be redeployed and which applications will be retired. Often, the applications are prioritized based on a combination of how widely the application is used and how complex the application is.
|
||||
|
||||
Next, identify an application owner to be in charge of each application. This is necessary because the developers will not be experts on all of the applications in the organization. The application owner should have the most experience with an application. The application owner provides insight into how the organization installs, configures, and uses the application.
|
||||
|
||||
## Application Settings
|
||||
|
||||
|
||||
Next, determine and locate the application settings to be migrated. You can acquire much of the information that you need for this step when you are testing the new applications for compatibility with the new operating system.
|
||||
|
||||
After completing the list of applications to be migrated, review the list and work with each application owner on a list of settings to be migrated. For each setting, determine whether it needs to be migrated or if the default settings are adequate. Then, determine where the setting is located; for example, in the registry or in an .ini file. Next, consider the following questions to determine what needs to be done to migrate the setting successfully:
|
||||
|
||||
- Is the destination version of the application newer than the source version?
|
||||
|
||||
- Do these settings work with the new version?
|
||||
|
||||
- Do the settings need to be moved or altered?
|
||||
|
||||
- Can the first-run process force the application to appear as if it had run already? If so, does this work correctly, or does it break the application?
|
||||
|
||||
After answering these questions, create a custom .xml file to migrate settings. Work with the application owner to develop test cases and to determine the file types that need to be migrated for the application.
|
||||
|
||||
## Locating Where Settings Are Stored
|
||||
|
||||
|
||||
See [Migrate Application Settings](migrate-application-settings.md) and follow the directions.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Determine What to Migrate](usmt-determine-what-to-migrate.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Identify Applications Settings (Windows 10)
|
||||
description: Identify which applications and settings you want to migrate before using the User State Migration Tool (USMT).
|
||||
ms.assetid: eda68031-9b02-4a5b-a893-3786a6505381
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# 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](usmt-customize-xml-files.md).
|
||||
|
||||
## Applications
|
||||
|
||||
|
||||
First, create and prioritize a list of applications that to be migrated. It may be helpful to review the application lists and decide which applications will be redeployed and which applications will be retired. Often, the applications are prioritized based on a combination of how widely the application is used and how complex the application is.
|
||||
|
||||
Next, identify an application owner to be in charge of each application. This is necessary because the developers will not be experts on all of the applications in the organization. The application owner should have the most experience with an application. The application owner provides insight into how the organization installs, configures, and uses the application.
|
||||
|
||||
## Application Settings
|
||||
|
||||
|
||||
Next, determine and locate the application settings to be migrated. You can acquire much of the information that you need for this step when you are testing the new applications for compatibility with the new operating system.
|
||||
|
||||
After completing the list of applications to be migrated, review the list and work with each application owner on a list of settings to be migrated. For each setting, determine whether it needs to be migrated or if the default settings are adequate. Then, determine where the setting is located; for example, in the registry or in an .ini file. Next, consider the following questions to determine what needs to be done to migrate the setting successfully:
|
||||
|
||||
- Is the destination version of the application newer than the source version?
|
||||
|
||||
- Do these settings work with the new version?
|
||||
|
||||
- Do the settings need to be moved or altered?
|
||||
|
||||
- Can the first-run process force the application to appear as if it had run already? If so, does this work correctly, or does it break the application?
|
||||
|
||||
After answering these questions, create a custom .xml file to migrate settings. Work with the application owner to develop test cases and to determine the file types that need to be migrated for the application.
|
||||
|
||||
## Locating Where Settings Are Stored
|
||||
|
||||
|
||||
See [Migrate Application Settings](migrate-application-settings.md) and follow the directions.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Determine What to Migrate](usmt-determine-what-to-migrate.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,60 +1,61 @@
|
||||
---
|
||||
title: Identify Operating System Settings (Windows 10)
|
||||
description: Identify Operating System Settings
|
||||
ms.assetid: 1704ab18-1765-41fb-a27c-3aa3128fa242
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Identify Operating System Settings
|
||||
|
||||
|
||||
When planning for your migration, you should identify which operating system settings you want to migrate and to what extent you want to create a new standard environment on each of the computers. User State Migration Tool (USMT) 10.0 enables you to migrate select settings and keep the default values for all others. The operating system settings include the following:
|
||||
|
||||
- **Apperance.**
|
||||
|
||||
This includes items such as wallpaper, colors, sounds, and the location of the taskbar.
|
||||
|
||||
- **Action.**
|
||||
|
||||
This includes items such as the key-repeat rate, whether double-clicking a folder opens it in a new window or the same window, and whether you need to single-click or double-click an item to open it.
|
||||
|
||||
- **Internet.**
|
||||
|
||||
These are the settings that let you connect to the Internet and control how your browser operates. This includes items such as your home page URL, favorites, bookmarks, cookies, security settings, dial-up connections, and proxy settings.
|
||||
|
||||
- **Mail.**
|
||||
|
||||
This includes the information that you need to connect to your mail server, your signature file, views, mail rules, local mail, and contacts.
|
||||
|
||||
To help you decide which settings to migrate, you should consider any previous migration experiences as well as the results of any surveys and tests that you have conducted. You should also consider the number of help-desk calls related to operating-system settings that you have had in the past, and are able to handle in the future. Also decide how much of the new operating-system functionality you want to take advantage of.
|
||||
|
||||
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](usmt-how-to.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](usmt-determine-what-to-migrate.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Identify Operating System Settings (Windows 10)
|
||||
description: Identify which system settings you want to migrate, then use the User State Migration Tool (USMT) to select settings and keep the default values for all others.
|
||||
ms.assetid: 1704ab18-1765-41fb-a27c-3aa3128fa242
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Identify Operating System Settings
|
||||
|
||||
|
||||
When planning for your migration, you should identify which operating system settings you want to migrate and to what extent you want to create a new standard environment on each of the computers. User State Migration Tool (USMT) 10.0 enables you to migrate select settings and keep the default values for all others. The operating system settings include the following:
|
||||
|
||||
- **Apperance.**
|
||||
|
||||
This includes items such as wallpaper, colors, sounds, and the location of the taskbar.
|
||||
|
||||
- **Action.**
|
||||
|
||||
This includes items such as the key-repeat rate, whether double-clicking a folder opens it in a new window or the same window, and whether you need to single-click or double-click an item to open it.
|
||||
|
||||
- **Internet.**
|
||||
|
||||
These are the settings that let you connect to the Internet and control how your browser operates. This includes items such as your home page URL, favorites, bookmarks, cookies, security settings, dial-up connections, and proxy settings.
|
||||
|
||||
- **Mail.**
|
||||
|
||||
This includes the information that you need to connect to your mail server, your signature file, views, mail rules, local mail, and contacts.
|
||||
|
||||
To help you decide which settings to migrate, you should consider any previous migration experiences as well as the results of any surveys and tests that you have conducted. You should also consider the number of help-desk calls related to operating-system settings that you have had in the past, and are able to handle in the future. Also decide how much of the new operating-system functionality you want to take advantage of.
|
||||
|
||||
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](usmt-how-to.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](usmt-determine-what-to-migrate.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Include Files and Settings (Windows 10)
|
||||
description: Include Files and Settings
|
||||
description: Specify the migration .xml files you want, then use the User State Migration Tool (USMT) 10.0 to migrate the settings and components specified.
|
||||
ms.assetid: 9009c6a5-0612-4478-8742-abe5eb6cbac8
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,76 +1,77 @@
|
||||
---
|
||||
title: Migration Store Encryption (Windows 10)
|
||||
description: Migration Store Encryption
|
||||
ms.assetid: b28c2657-b986-4487-bd38-cb81500b831d
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Migration Store Encryption
|
||||
|
||||
|
||||
This topic discusses User State Migration Tool (USMT) 10.0 options for migration store encryption to protect the integrity of user data during a migration.
|
||||
|
||||
## USMT Encryption Options
|
||||
|
||||
|
||||
USMT enables support for stronger encryption algorithms, called Advanced Encryption Standard (AES), in several bit-level options. AES is a National Institute of Standards and Technology (NIST) specification for the encryption of electronic data.
|
||||
|
||||
The encryption algorithm you choose must be specified for both the **ScanState** and the **LoadState** commands, so that these commands can create or read the store during encryption and decryption. The new encryption algorithms can be specified on the **ScanState** and the **LoadState** command lines by using the **/encrypt**:*"encryptionstrength"* and the **/decrypt**:*"encryptionstrength"* command-line options. All of the encryption application programming interfaces (APIs) used by USMT are available in Windows 7, Windows 8, and Windows 10 operating systems. However, export restrictions might limit the set of algorithms that are available to computers in certain locales. You can use the Usmtutils.exe file to determine which encryption algorithms are available to the computers' locales before you begin the migration.
|
||||
|
||||
The following table describes the command-line encryption options in USMT.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Component</th>
|
||||
<th align="left">Option</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>ScanState</strong></p></td>
|
||||
<td align="left"><p><strong>/encrypt</strong><em><AES, AES_128, AES_192, AES_256, 3DES, 3DES_112></em></p></td>
|
||||
<td align="left"><p>This option and argument specify that the migration store is encrypted and which algorithm to use. When the algorithm argument is not provided, the <strong>ScanState</strong> tool employs the 3DES algorithm.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>LoadState</strong></p></td>
|
||||
<td align="left"><p><strong>/decrypt</strong><em><AES, AES_128, AES_192, AES_256, 3DES, 3DES_112></em></p></td>
|
||||
<td align="left"><p>This option and argument specify that the store must be decrypted and which algorithm to use. When the algorithm argument is not provided, the <strong>LoadState</strong> tool employs the 3DES algorithm.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
Some encryption algorithms may not be available on your systems. You can verify which algorithms are available by running the UsmtUtils command with the **/ec** option. For more information see [UsmtUtils Syntax](usmt-utilities.md)
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Migration Store Encryption (Windows 10)
|
||||
description: Learn how the User State Migration Tool (USMT) enables support for stronger encryption algorithms, called Advanced Encryption Standard (AES).
|
||||
ms.assetid: b28c2657-b986-4487-bd38-cb81500b831d
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Migration Store Encryption
|
||||
|
||||
|
||||
This topic discusses User State Migration Tool (USMT) 10.0 options for migration store encryption to protect the integrity of user data during a migration.
|
||||
|
||||
## USMT Encryption Options
|
||||
|
||||
|
||||
USMT enables support for stronger encryption algorithms, called Advanced Encryption Standard (AES), in several bit-level options. AES is a National Institute of Standards and Technology (NIST) specification for the encryption of electronic data.
|
||||
|
||||
The encryption algorithm you choose must be specified for both the **ScanState** and the **LoadState** commands, so that these commands can create or read the store during encryption and decryption. The new encryption algorithms can be specified on the **ScanState** and the **LoadState** command lines by using the **/encrypt**:*"encryptionstrength"* and the **/decrypt**:*"encryptionstrength"* command-line options. All of the encryption application programming interfaces (APIs) used by USMT are available in Windows 7, Windows 8, and Windows 10 operating systems. However, export restrictions might limit the set of algorithms that are available to computers in certain locales. You can use the Usmtutils.exe file to determine which encryption algorithms are available to the computers' locales before you begin the migration.
|
||||
|
||||
The following table describes the command-line encryption options in USMT.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Component</th>
|
||||
<th align="left">Option</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>ScanState</strong></p></td>
|
||||
<td align="left"><p><strong>/encrypt</strong><em><AES, AES_128, AES_192, AES_256, 3DES, 3DES_112></em></p></td>
|
||||
<td align="left"><p>This option and argument specify that the migration store is encrypted and which algorithm to use. When the algorithm argument is not provided, the <strong>ScanState</strong> tool employs the 3DES algorithm.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>LoadState</strong></p></td>
|
||||
<td align="left"><p><strong>/decrypt</strong><em><AES, AES_128, AES_192, AES_256, 3DES, 3DES_112></em></p></td>
|
||||
<td align="left"><p>This option and argument specify that the store must be decrypted and which algorithm to use. When the algorithm argument is not provided, the <strong>LoadState</strong> tool employs the 3DES algorithm.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
Some encryption algorithms may not be available on your systems. You can verify which algorithms are available by running the UsmtUtils command with the **/ec** option. For more information see [UsmtUtils Syntax](usmt-utilities.md)
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,161 +1,162 @@
|
||||
---
|
||||
title: USMT Requirements (Windows 10)
|
||||
description: USMT Requirements
|
||||
ms.assetid: 2b0cf3a3-9032-433f-9622-1f9df59d6806
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 05/03/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# USMT Requirements
|
||||
|
||||
|
||||
## In This Topic
|
||||
|
||||
|
||||
- [Supported Operating Systems](#bkmk-1)
|
||||
- [Windows PE](#windows-pe)
|
||||
- [Credentials](#credentials)
|
||||
- [Config.xml](#configxml)
|
||||
- [LoadState](#loadstate)
|
||||
- [Hard Disk Requirements](#bkmk-3)
|
||||
- [User Prerequisites](#bkmk-userprereqs)
|
||||
|
||||
## <a href="" id="bkmk-1"></a>Supported Operating Systems
|
||||
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 does not have any explicit RAM or CPU speed requirements for either the source or destination computers. If your computer complies with the system requirements of the operating system, it also complies with the requirements for USMT. You need an intermediate store location large enough to hold all of the migrated data and settings, and the same amount of hard disk space on the destination computer for the migrated files and settings.
|
||||
|
||||
The following table lists the operating systems supported in USMT.
|
||||
|
||||
<table>
|
||||
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating Systems</th>
|
||||
<th align="left">ScanState (source computer)</th>
|
||||
<th align="left">LoadState (destination computer)</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>32-bit versions of Windows 7</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>64-bit versions of Windows 7</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>32-bit versions of Windows 8</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>64-bit versions of Windows 8</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>32-bit versions of Windows 10</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>64-bit versions of Windows 10</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Note**
|
||||
You can migrate a 32-bit operating system to a 64-bit operating system. However, you cannot migrate a 64-bit operating system to a 32-bit operating system.
|
||||
|
||||
USMT does not support any of the Windows Server® operating systems, Windows 2000, Windows XP, or any of the starter editions for Windows Vista or Windows 7.
|
||||
|
||||
USMT for Windows 10 should not be used for migrating from Windows 7 to Windows 8.1. It is meant to migrate to Windows 10.
|
||||
For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](https://go.microsoft.com/fwlink/p/?LinkId=246564).
|
||||
|
||||
## Windows PE
|
||||
|
||||
- **Must use latest version of Window PE.** For example, to migrate to Windows 10, you'll need Windows PE 5.1. For more info, see [What's New in Windows PE](https://msdn.microsoft.com/library/windows/hardware/dn938350.aspx).
|
||||
|
||||
## Credentials
|
||||
|
||||
- **Run as administrator**
|
||||
When manually running the **ScanState** and **LoadState** tools on Windows 7, Windows 8 or Windows 10 you must run them from an elevated command prompt to ensure that all specified users are migrated. If you do not run USMT from an elevated prompt, only the user profile that is logged on will be included in the migration.
|
||||
|
||||
To open an elevated command prompt:
|
||||
|
||||
1. Click **Start**.
|
||||
2. Enter **cmd** in the search function.
|
||||
3. Depending on the OS you are using, **cmd** or **Command Prompt** is displayed.
|
||||
3. Right-click **cmd** or **Command Prompt**, and then click **Run as administrator**.
|
||||
4. If the current user is not already an administrator, you will be prompted to enter administrator credentials.
|
||||
|
||||
**Important**<BR>
|
||||
You must run USMT using an account with full administrative permissions, including the following privileges:
|
||||
|
||||
- SeBackupPrivilege (Back up files and directories)
|
||||
- SeDebugPrivilege (Debug programs)
|
||||
- SeRestorePrivilege (Restore files and directories)
|
||||
- SeSecurityPrivilege (Manage auditing and security log)
|
||||
- SeTakeOwnership Privilege (Take ownership of files or other objects)
|
||||
|
||||
|
||||
## Config.xml
|
||||
|
||||
- **Specify the /c option and <ErrorControl> settings in the Config.xml file.**<BR>
|
||||
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).
|
||||
|
||||
## LoadState
|
||||
|
||||
- **Install applications before running the LoadState command.**<BR>
|
||||
Install all applications on the destination computer before restoring the user state. This ensures that migrated settings are preserved.
|
||||
|
||||
## <a href="" id="bkmk-3"></a>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](usmt-estimate-migration-store-size.md).
|
||||
|
||||
## <a href="" id="bkmk-userprereqs"></a>User Prerequisites
|
||||
|
||||
|
||||
This documentation assumes that IT professionals using USMT understand command-line tools. The documentation also assumes that IT professionals using USMT to author MigXML rules understand the following:
|
||||
|
||||
- The navigation and hierarchy of the Windows registry.
|
||||
- The files and file types that applications use.
|
||||
- The methods to extract application and setting information manually from applications created by internal software-development groups and non-Microsoft software vendors.
|
||||
- XML-authoring basics.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)<BR>
|
||||
[Estimate Migration Store Size](usmt-estimate-migration-store-size.md)<BR>
|
||||
[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)<BR>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: USMT Requirements (Windows 10)
|
||||
description: While the User State Migration Tool (USMT) doesn't have many requirements, these tips and tricks can help smooth the migration process.
|
||||
ms.assetid: 2b0cf3a3-9032-433f-9622-1f9df59d6806
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 05/03/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# USMT Requirements
|
||||
|
||||
|
||||
## In This Topic
|
||||
|
||||
|
||||
- [Supported Operating Systems](#bkmk-1)
|
||||
- [Windows PE](#windows-pe)
|
||||
- [Credentials](#credentials)
|
||||
- [Config.xml](#configxml)
|
||||
- [LoadState](#loadstate)
|
||||
- [Hard Disk Requirements](#bkmk-3)
|
||||
- [User Prerequisites](#bkmk-userprereqs)
|
||||
|
||||
## <a href="" id="bkmk-1"></a>Supported Operating Systems
|
||||
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 does not have any explicit RAM or CPU speed requirements for either the source or destination computers. If your computer complies with the system requirements of the operating system, it also complies with the requirements for USMT. You need an intermediate store location large enough to hold all of the migrated data and settings, and the same amount of hard disk space on the destination computer for the migrated files and settings.
|
||||
|
||||
The following table lists the operating systems supported in USMT.
|
||||
|
||||
<table>
|
||||
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating Systems</th>
|
||||
<th align="left">ScanState (source computer)</th>
|
||||
<th align="left">LoadState (destination computer)</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>32-bit versions of Windows 7</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>64-bit versions of Windows 7</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>32-bit versions of Windows 8</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>64-bit versions of Windows 8</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>32-bit versions of Windows 10</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>64-bit versions of Windows 10</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
<td align="left"><p>X</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Note**
|
||||
You can migrate a 32-bit operating system to a 64-bit operating system. However, you cannot migrate a 64-bit operating system to a 32-bit operating system.
|
||||
|
||||
USMT does not support any of the Windows Server® operating systems, Windows 2000, Windows XP, or any of the starter editions for Windows Vista or Windows 7.
|
||||
|
||||
USMT for Windows 10 should not be used for migrating from Windows 7 to Windows 8.1. It is meant to migrate to Windows 10.
|
||||
For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](https://go.microsoft.com/fwlink/p/?LinkId=246564).
|
||||
|
||||
## Windows PE
|
||||
|
||||
- **Must use latest version of Window PE.** For example, to migrate to Windows 10, you'll need Windows PE 5.1. For more info, see [What's New in Windows PE](https://msdn.microsoft.com/library/windows/hardware/dn938350.aspx).
|
||||
|
||||
## Credentials
|
||||
|
||||
- **Run as administrator**
|
||||
When manually running the **ScanState** and **LoadState** tools on Windows 7, Windows 8 or Windows 10 you must run them from an elevated command prompt to ensure that all specified users are migrated. If you do not run USMT from an elevated prompt, only the user profile that is logged on will be included in the migration.
|
||||
|
||||
To open an elevated command prompt:
|
||||
|
||||
1. Click **Start**.
|
||||
2. Enter **cmd** in the search function.
|
||||
3. Depending on the OS you are using, **cmd** or **Command Prompt** is displayed.
|
||||
3. Right-click **cmd** or **Command Prompt**, and then click **Run as administrator**.
|
||||
4. If the current user is not already an administrator, you will be prompted to enter administrator credentials.
|
||||
|
||||
**Important**<BR>
|
||||
You must run USMT using an account with full administrative permissions, including the following privileges:
|
||||
|
||||
- SeBackupPrivilege (Back up files and directories)
|
||||
- SeDebugPrivilege (Debug programs)
|
||||
- SeRestorePrivilege (Restore files and directories)
|
||||
- SeSecurityPrivilege (Manage auditing and security log)
|
||||
- SeTakeOwnership Privilege (Take ownership of files or other objects)
|
||||
|
||||
|
||||
## Config.xml
|
||||
|
||||
- **Specify the /c option and <ErrorControl> settings in the Config.xml file.**<BR>
|
||||
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).
|
||||
|
||||
## LoadState
|
||||
|
||||
- **Install applications before running the LoadState command.**<BR>
|
||||
Install all applications on the destination computer before restoring the user state. This ensures that migrated settings are preserved.
|
||||
|
||||
## <a href="" id="bkmk-3"></a>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](usmt-estimate-migration-store-size.md).
|
||||
|
||||
## <a href="" id="bkmk-userprereqs"></a>User Prerequisites
|
||||
|
||||
|
||||
This documentation assumes that IT professionals using USMT understand command-line tools. The documentation also assumes that IT professionals using USMT to author MigXML rules understand the following:
|
||||
|
||||
- The navigation and hierarchy of the Windows registry.
|
||||
- The files and file types that applications use.
|
||||
- The methods to extract application and setting information manually from applications created by internal software-development groups and non-Microsoft software vendors.
|
||||
- XML-authoring basics.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)<BR>
|
||||
[Estimate Migration Store Size](usmt-estimate-migration-store-size.md)<BR>
|
||||
[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)<BR>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,128 +1,129 @@
|
||||
---
|
||||
title: Verify the Condition of a Compressed Migration Store (Windows 10)
|
||||
description: Verify the Condition of a Compressed Migration Store
|
||||
ms.assetid: 4a3fda96-5f7d-494a-955f-6b865ec9fcae
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Verify the Condition of a Compressed Migration Store
|
||||
|
||||
|
||||
When you migrate files and settings during a typical PC-refresh migration, the user state is usually stored in a compressed folder on the intermediate store. This compressed folder, also called the compressed migration store, is a single image file that contains:
|
||||
|
||||
- All of the files being migrated.
|
||||
|
||||
- The user’s settings.
|
||||
|
||||
- A catalog file that contains metadata for all files in the migration store.
|
||||
|
||||
When you run the **LoadState** command to load the data from these files to the destination computer, LoadState requires a valid catalog file in order to open the migration store. You can run the **UsmtUtils** command with the **/verify** option to determine whether the compressed migration store is intact, or whether it contains corrupted files or a corrupted catalog. You should run the **/verify** option on the migration store before you overwrite the original user-state files and settings.
|
||||
|
||||
When you use the **/verify** option, you can specify what type of information to report in the UsmtUtils log file. These report types are:
|
||||
|
||||
- **Catalog**: Displays the status of only the catalog file.
|
||||
|
||||
- **All**: Displays the status of all files, including the catalog file.
|
||||
|
||||
- **Failure only**: Displays only the files that are corrupted.
|
||||
|
||||
## In This Topic
|
||||
|
||||
|
||||
The following sections demonstrate how to run the **UsmtUtils** command with the **/verify** option, and how to specify the information to display in the UsmtUtils log file.
|
||||
|
||||
- [The UsmtUtils syntax for the /verify option](#bkmk-verifysyntax)
|
||||
|
||||
- [To verify that the migration store is intact](#bkmk-verifyintactstore)
|
||||
|
||||
- [To verify the status of only the catalog file](#bkmk-verifycatalog)
|
||||
|
||||
- [To verify the status of all files](#bkmk-verifyallfiles)
|
||||
|
||||
- [To verify the status of the files and return only the corrupted files](#bkmk-returncorrupted)
|
||||
|
||||
### <a href="" id="bkmk-verifysyntax"></a>The UsmtUtils Syntax for the /verify Option
|
||||
|
||||
To verify the condition of a compressed migration store, use the following UsmtUtils syntax:
|
||||
|
||||
cd /d<USMTpath>usmtutils /verify\[:<reportType>\] <filePath> \[/l:<logfile>\] \[/decrypt \[:<AlgID>\] {/key:<keystring> | /keyfile:<filename>}\]
|
||||
|
||||
Where the placeholders have the following values:
|
||||
|
||||
- *<USMTpath>* is the location where you have saved the USMT files and tools.
|
||||
|
||||
- *<reportType>* specifies whether to report on all files, corrupted files only, or the status of the catalog.
|
||||
|
||||
- *<filePath>* is the location of the compressed migration store.
|
||||
|
||||
- *<logfile>* is the location and name of the log file.
|
||||
|
||||
- *<AlgID>* is the cryptographic algorithm that was used to create the migration store on the **ScanState** command line.
|
||||
|
||||
- *<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.
|
||||
|
||||
### <a href="" id="bkmk-verifyintactstore"></a>To Verify that the Migration Store is Intact
|
||||
|
||||
To verify whether the migration store is intact or whether it contains corrupted files or a corrupted catalog, type:
|
||||
|
||||
``` syntax
|
||||
usmtutils /verify D:\MyMigrationStore\store.mig
|
||||
```
|
||||
|
||||
Because no report type is specified, UsmtUtils displays the default summary report.
|
||||
|
||||
### <a href="" id="bkmk-verifycatalog"></a>To Verify the Status of Only the Catalog File
|
||||
|
||||
To verify whether the catalog file is corrupted or intact, type:
|
||||
|
||||
``` syntax
|
||||
usmtutils /verify:catalog D:\MyMigrationStore\store.mig
|
||||
```
|
||||
|
||||
### <a href="" id="bkmk-verifyallfiles"></a>To Verify the Status of all Files
|
||||
|
||||
To verify whether there are any corrupted files in the compressed migration store, and to specify the name and location of the log file, type:
|
||||
|
||||
`usmtutils /verify:all D:\MyMigrationStore\store.mig /decrypt /l:D:\UsmtUtilsLog.txt`
|
||||
|
||||
In addition to verifying the status of all files, this example decrypts the files. Because no encryption algorithm is specified, UsmtUtils uses the default 3DES cryptographic algorithm.
|
||||
|
||||
### <a href="" id="bkmk-returncorrupted"></a>To Verify the Status of the Files and Return Only the Corrupted Files
|
||||
|
||||
In this example, the log file will only list the files that became corrupted during the ScanState process. This list will include the catalog file if it is also corrupted.
|
||||
|
||||
``` syntax
|
||||
usmtutils /verify:failureonly D:\MyMigrationStore\USMT\store.mig /decrypt:AES_192 /keyfile:D:\encryptionKey.txt
|
||||
```
|
||||
|
||||
This example also decrypts the files by specifying the cryptographic algorithm and the location of the file that contains the encryption key.
|
||||
|
||||
### Next Steps
|
||||
|
||||
If the **/verify** option indicates that there are corrupted files in the migration store, you can use the **/extract** option in the UsmtUtils tool to recover data from some corrupted stores. For more information, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[UsmtUtils Syntax](usmt-utilities.md)
|
||||
|
||||
[Return Codes](usmt-return-codes.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Verify the Condition of a Compressed Migration Store (Windows 10)
|
||||
description: Use these tips and tricks to verify the condition of a compressed migration store when using User State Migration Tool (USMT).
|
||||
ms.assetid: 4a3fda96-5f7d-494a-955f-6b865ec9fcae
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Verify the Condition of a Compressed Migration Store
|
||||
|
||||
|
||||
When you migrate files and settings during a typical PC-refresh migration, the user state is usually stored in a compressed folder on the intermediate store. This compressed folder, also called the compressed migration store, is a single image file that contains:
|
||||
|
||||
- All of the files being migrated.
|
||||
|
||||
- The user’s settings.
|
||||
|
||||
- A catalog file that contains metadata for all files in the migration store.
|
||||
|
||||
When you run the **LoadState** command to load the data from these files to the destination computer, LoadState requires a valid catalog file in order to open the migration store. You can run the **UsmtUtils** command with the **/verify** option to determine whether the compressed migration store is intact, or whether it contains corrupted files or a corrupted catalog. You should run the **/verify** option on the migration store before you overwrite the original user-state files and settings.
|
||||
|
||||
When you use the **/verify** option, you can specify what type of information to report in the UsmtUtils log file. These report types are:
|
||||
|
||||
- **Catalog**: Displays the status of only the catalog file.
|
||||
|
||||
- **All**: Displays the status of all files, including the catalog file.
|
||||
|
||||
- **Failure only**: Displays only the files that are corrupted.
|
||||
|
||||
## In This Topic
|
||||
|
||||
|
||||
The following sections demonstrate how to run the **UsmtUtils** command with the **/verify** option, and how to specify the information to display in the UsmtUtils log file.
|
||||
|
||||
- [The UsmtUtils syntax for the /verify option](#bkmk-verifysyntax)
|
||||
|
||||
- [To verify that the migration store is intact](#bkmk-verifyintactstore)
|
||||
|
||||
- [To verify the status of only the catalog file](#bkmk-verifycatalog)
|
||||
|
||||
- [To verify the status of all files](#bkmk-verifyallfiles)
|
||||
|
||||
- [To verify the status of the files and return only the corrupted files](#bkmk-returncorrupted)
|
||||
|
||||
### <a href="" id="bkmk-verifysyntax"></a>The UsmtUtils Syntax for the /verify Option
|
||||
|
||||
To verify the condition of a compressed migration store, use the following UsmtUtils syntax:
|
||||
|
||||
cd /d<USMTpath>usmtutils /verify\[:<reportType>\] <filePath> \[/l:<logfile>\] \[/decrypt \[:<AlgID>\] {/key:<keystring> | /keyfile:<filename>}\]
|
||||
|
||||
Where the placeholders have the following values:
|
||||
|
||||
- *<USMTpath>* is the location where you have saved the USMT files and tools.
|
||||
|
||||
- *<reportType>* specifies whether to report on all files, corrupted files only, or the status of the catalog.
|
||||
|
||||
- *<filePath>* is the location of the compressed migration store.
|
||||
|
||||
- *<logfile>* is the location and name of the log file.
|
||||
|
||||
- *<AlgID>* is the cryptographic algorithm that was used to create the migration store on the **ScanState** command line.
|
||||
|
||||
- *<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.
|
||||
|
||||
### <a href="" id="bkmk-verifyintactstore"></a>To Verify that the Migration Store is Intact
|
||||
|
||||
To verify whether the migration store is intact or whether it contains corrupted files or a corrupted catalog, type:
|
||||
|
||||
``` syntax
|
||||
usmtutils /verify D:\MyMigrationStore\store.mig
|
||||
```
|
||||
|
||||
Because no report type is specified, UsmtUtils displays the default summary report.
|
||||
|
||||
### <a href="" id="bkmk-verifycatalog"></a>To Verify the Status of Only the Catalog File
|
||||
|
||||
To verify whether the catalog file is corrupted or intact, type:
|
||||
|
||||
``` syntax
|
||||
usmtutils /verify:catalog D:\MyMigrationStore\store.mig
|
||||
```
|
||||
|
||||
### <a href="" id="bkmk-verifyallfiles"></a>To Verify the Status of all Files
|
||||
|
||||
To verify whether there are any corrupted files in the compressed migration store, and to specify the name and location of the log file, type:
|
||||
|
||||
`usmtutils /verify:all D:\MyMigrationStore\store.mig /decrypt /l:D:\UsmtUtilsLog.txt`
|
||||
|
||||
In addition to verifying the status of all files, this example decrypts the files. Because no encryption algorithm is specified, UsmtUtils uses the default 3DES cryptographic algorithm.
|
||||
|
||||
### <a href="" id="bkmk-returncorrupted"></a>To Verify the Status of the Files and Return Only the Corrupted Files
|
||||
|
||||
In this example, the log file will only list the files that became corrupted during the ScanState process. This list will include the catalog file if it is also corrupted.
|
||||
|
||||
``` syntax
|
||||
usmtutils /verify:failureonly D:\MyMigrationStore\USMT\store.mig /decrypt:AES_192 /keyfile:D:\encryptionKey.txt
|
||||
```
|
||||
|
||||
This example also decrypts the files by specifying the cryptographic algorithm and the location of the file that contains the encryption key.
|
||||
|
||||
### Next Steps
|
||||
|
||||
If the **/verify** option indicates that there are corrupted files in the migration store, you can use the **/extract** option in the UsmtUtils tool to recover data from some corrupted stores. For more information, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[UsmtUtils Syntax](usmt-utilities.md)
|
||||
|
||||
[Return Codes](usmt-return-codes.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user