mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 13:57:22 +00:00
USMT Refresh 5
This commit is contained in:
Frank Rojas
parent
7f44584cab
commit
f71fc6c551
@ -94,7 +94,7 @@ By default, all users are migrated. The only way to specify which users to inclu
|
||||
| **/ue**:*DomainName\UserName* <br/>or <br/>**/ue** *"DomainName\User Name"* <br/>or <br/>**/ue**:*ComputerName\LocalUserName* | **(User exclude)** <br/><br/>Excludes the specified users from the migration. You can specify multiple `/ue` options but you can't use the `/ue` option with the `/all` option. *DomainName* and *UserName* can contain the asterisk (`*`) wildcard character. When a user name that contains spaces is specified, it needs to be surround with quotation marks (`"`). <br/><br/>For example: <br/>`LoadState.exe /i:MigApp.xml /i:MigDocs.xml \server\share\migration\mystore /ue:contoso\user1` <br/>For more examples, see the descriptions of the `/uel`, `/ue`, and `/ui` options in this table. |
|
||||
| **/md**:*OldDomain*:*NewDomain* <br/>or <br/>**/md**:*LocalComputerName:NewDomain* | **(Move domain)** <br/><br/>Specifies a new domain for the user. Use this option to change the domain for users on a computer or to migrate a local user to a domain account. *OldDomain* might contain the asterisk () wildcard character. <br/><br/>This option can be specified more than once. If consolidating users across multiple domains to a single domain, multiple `/md` options might need to be specified. For example, to consolidate the users from the Corporate and FarNorth domains into the Fabrikam domain, specify the following settings: `/md:corporate:fabrikam` and `/md:farnorth:fabrikam`. <br/><br/>If there are conflicts between two `/md` commands, the first rule that you specify is applied. For example, if you specify the `/md:corporate:fabrikam` and `/md:corporate:farnorth` commands, then Corporate users would be mapped to the Fabrikam domain. <div class="alert"> **Note** <br/>If you specify an *OldDomain* that didn't exist on the source computer, the `LoadState.exe` command appears to complete successfully, without an error or warning. However, in this case, users aren't moved to *NewDomain* but instead remain in their original domain. For example, if you misspell **contoso** and you instead specify **/md:contso:fabrikam**, the users remain in **contoso** on the destination computer.</div> <br/> For example: <br/>`LoadState.exe /i:MigApp.xml /i:MigDocs.xml \server\share\migration\mystore` <br/>` /progress:Progress.log /l:LoadState.log /md:contoso:fabrikam` |
|
||||
| **/mu**:*OldDomain OldUserName*:[*NewDomain*]*NewUserName* <br/>or <br/>**/mu**:*OldLocalUserName*:*NewDomain NewUserName* | **(Move user)** <br/><br/>Specifies a new user name for the specified user. If the store contains more than one user, you can specify multiple `/mu` options. You can't use wildcard characters with this option. <br/><br/>For example: <br/>`LoadState.exe /i:MigApp.xml /i:MigDocs.xml \server\share\migration\mystore` <br/>`/progress:Progress.log /l:LoadState.log /mu:contoso\user1:fabrikam\user1` |
|
||||
| **/lac**:[*Password*] | **(Local account create)** <br/><br/>If a user account is:<ul><li>A local (non-domain) account</li><li>It doesn't exist on the destination computer</li></ul>this setting specifies to create the account on the destination computer. However, the account is disabled. To enable the account, you must also use the `/lae` option. <br/><br/>If the `/lac` option isn't specified, any local user accounts that don't already exist on the destination computer aren't migrated. <br/><br/>*Password* is the password for the newly created account. An empty password is used by default. <div class="alert"> **Caution** <br/>Use the *Password* variable with caution. The *Password* variable is provided in plain text and anyone with access to the computer that is running the `LoadState.exe` command can obtain the password. <br/>Also, if the computer has multiple users, all migrated users have the same password.</div> <br/>For example: <br/>`LoadState.exe /i:MigApp.xml /i:MigDocs.xml \server\share\migration\mystore` <br/><br/>For instructions, see [Migrate user accounts](usmt-migrate-user-accounts.md). |
|
||||
| **/lac**:[*Password*] | **(Local account create)** <br/><br/>If a user account is:<ul><li>A local (non-domain) account</li><li>An account that doesn't exist on the destination computer</li></ul>this setting specifies to create the account on the destination computer. However, the account is disabled. To enable the account, you must also use the `/lae` option. <br/><br/>If the `/lac` option isn't specified, any local user accounts that don't already exist on the destination computer aren't migrated. <br/><br/>*Password* is the password for the newly created account. An empty password is used by default. <div class="alert"> **Caution** <br/>Use the *Password* variable with caution. The *Password* variable is provided in plain text and anyone with access to the computer that is running the `LoadState.exe` command can obtain the password. <br/>Also, if the computer has multiple users, all migrated users have the same password.</div> <br/>For example: <br/>`LoadState.exe /i:MigApp.xml /i:MigDocs.xml \server\share\migration\mystore` <br/><br/>For instructions, see [Migrate user accounts](usmt-migrate-user-accounts.md). |
|
||||
| `/lae` | **(Local account enable)** <br/><br/>Enables the account that was created with the `/lac` option. You must specify the `/lac` option with this option. <br/><br/>For example: <br/>`LoadState.exe /i:MigApp.xml /i:MigDocs.xml \server\share\migration\mystore` <br/>`/progress:Progress.log /l:LoadState.log /lac:password /lae` <br/><br/>For instructions, see [Migrate user accounts](usmt-migrate-user-accounts.md). |
|
||||
|
||||
### Examples for the /ui and /ue options
|
||||
|
||||
@ -1,28 +1,21 @@
|
||||
---
|
||||
title: Log Files (Windows 10)
|
||||
description: Learn how to use User State Migration Tool (USMT) 10.0 logs to monitor your migration and to troubleshoot errors and failed migrations.
|
||||
title: USMT Log Files
|
||||
description: Learn how to use User State Migration Tool (USMT) logs to monitor your migration and to troubleshoot errors and failed migrations.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/01/2022
|
||||
ms.date: 12/22/2023
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# USMT log files
|
||||
|
||||
You can use User State Migration Tool (USMT) 10.0 logs to monitor your migration and to troubleshoot errors and failed migrations. This article describes the available command-line options to enable USMT logs, and new XML elements that configure which types of errors are fatal and should halt the migration, which types are non-fatal and should be skipped so that the migration can continue.
|
||||
You can use User State Migration Tool (USMT) logs to monitor your migration and to troubleshoot errors and failed migrations. This article describes the available command-line options to enable USMT logs. It also describes new XML elements that can be used to configure:
|
||||
|
||||
[Log command-line options](#log-command-line-options)
|
||||
|
||||
[ScanState and LoadState logs](#scanstate-and-loadstate-logs)
|
||||
|
||||
[Progress log](#progress-log)
|
||||
|
||||
[List files log](#list-files-log)
|
||||
|
||||
[Diagnostic log](#diagnostic-log)
|
||||
- Which types of errors are fatal and should halt the migration.
|
||||
- Which types are non-fatal and should be skipped so that the migration can continue.
|
||||
|
||||
## Log command-line options
|
||||
|
||||
@ -47,11 +40,11 @@ The following table describes each command-line option related to logs, and it p
|
||||
|
||||
You can create a progress log using the `/progress` option. External tools, such as Microsoft System Center Operations Manager, can parse the progress log to update your monitoring systems. The first three fields in each line are fixed as follows:
|
||||
|
||||
- **Date:** Date, in the format of *day* *shortNameOfTheMonth* *year*. For example: 08 Jun 2006.
|
||||
- **Date:** Date, in the format of *day* *shortNameOfTheMonth* *year*. For example: 08 Jun 2023.
|
||||
|
||||
- **Local time:** Time, in the format of *hrs*:*minutes*:*seconds* (using a 24-hour clock). For example: 13:49:13.
|
||||
|
||||
- **Migration time:** Duration of time that USMT was run, in the format of *hrs:minutes:seconds*. For example: 00:00:10.
|
||||
- **Migration time:** Duration of time that USMT was run, in the format of *hrs:minutes:seconds*. For example: 00:00:20.
|
||||
|
||||
The remaining fields are key/value pairs as indicated in the following table.
|
||||
|
||||
@ -62,15 +55,15 @@ The remaining fields are key/value pairs as indicated in the following table.
|
||||
| *computerName* | The name of the source or destination computer on which USMT was run. |
|
||||
| *commandLine* | The full command used to run USMT. |
|
||||
| *PHASE* | Reports that a new phase in the migration is starting. This key can be one of the following values:<ul><li>Initializing</li><li>Scanning</li><li>Collecting</li><li>Saving</li><li>Estimating</li><li>Applying</li></ul> |
|
||||
| *detectedUser* | <ul><li>For the **ScanState** tool, this key are the users USMT detected on the source computer that can be migrated.</li><li>For the **LoadState** tool, this key are the users USMT detected in the store that can be migrated.</li></ul> |
|
||||
| *detectedUser* | <ul><li>For the **ScanState** tool, this key is the users USMT detected on the source computer that can be migrated.</li><li>For the **LoadState** tool, this key is the users USMT detected in the store that can be migrated.</li></ul> |
|
||||
| *includedInMigration* | Defines whether the user profile/component is included for migration. Valid values are **Yes** or **No**. |
|
||||
| *forUser* | Specifies either of the following values:<ul><li>The user state being migrated.</li><li>*This Computer*, meaning files and settings that aren't associated with a user.</li></ul> |
|
||||
| *detectedComponent* | Specifies a component detected by USMT.<ul><li>For *ScanState*, this key is a component or application that is installed on the source computer.</li><li>For **LoadState**, this key is a component or application that was detected in the store.</li></ul> |
|
||||
| *totalSizeInMBToTransfer* | Total size of the files and settings to migrate in megabytes (MB). |
|
||||
| *totalPercentageCompleted* | Total percentage of the migration that has been completed by either **ScanState** or **LoadState**. |
|
||||
| *totalPercentageCompleted* | Total percentage of the migration that is completed by either **ScanState** or **LoadState**. |
|
||||
| *collectingUser* | Specifies which user **ScanState** is collecting files and settings for. |
|
||||
| *totalMinutesRemaining* | Time estimate, in minutes, for the migration to complete. |
|
||||
| *error* | Type of non-fatal error that occurred. This key can be one of the following values:<ul><li>**UnableToCopy**: Unable to copy to store because the disk on which the store is located is full.</li><li>**UnableToOpen**: Unable to open the file for migration because the file is opened in non-shared mode by another application or service.</li><li>**UnableToCopyCatalog**: Unable to copy because the store is corrupted.</li><li>**UnableToAccessDevice**: Unable to access the device.</li><li>**UnableToApply**: Unable to apply the setting to the destination computer.</li></ul> |
|
||||
| *error* | Type of non-fatal error that occurred. This key can be one of the following values:<ul><li>**UnableToCopy**: Unable to copy to store because the disk on which the store is located is full.</li><li>**UnableToOpen**: Unable to open the file for migration because another application or service has the file open in non-shared mode.</li><li>**UnableToCopyCatalog**: Unable to copy because the store is corrupted.</li><li>**UnableToAccessDevice**: Unable to access the device.</li><li>**UnableToApply**: Unable to apply the setting to the destination computer.</li></ul> |
|
||||
| *objectName* | The name of the file or setting that caused the non-fatal error. |
|
||||
| *action* | Action taken by USMT for the non-fatal error. The values are:<ul><li>**Ignore**: Non-fatal error ignored and the migration continued because the **/c** option was specified on the command line.</li><li>**Abort**: Stopped the migration because the **/c** option wasn't specified.</li></ul> |
|
||||
| *errorCode* | The errorCode or return value. |
|
||||
@ -87,15 +80,15 @@ You can obtain the diagnostic log by setting the environment variable **MIG_ENAB
|
||||
|
||||
The diagnostic log contains:
|
||||
|
||||
- Detailed system environment information
|
||||
- Detailed system environment information.
|
||||
|
||||
- Detailed user environment information
|
||||
- Detailed user environment information.
|
||||
|
||||
- Information about the migration units (migunits) being gathered and their contents
|
||||
- Information about the migration units (migunits) being gathered and their contents.
|
||||
|
||||
## Using the Diagnostic Log
|
||||
|
||||
The diagnostic log is essentially a report of all the migration units (migunits) included in the migration. A migunit is a collection of data that is identified by the component it's associated with in the XML files. The migration store is made up of all the migunits in the migration. The diagnostic log can be used to verify which migunits were included in the migration and can be used for troubleshooting while authoring migration XML files.
|
||||
The diagnostic log is essentially a report of all the migration units (migunits) included in the migration. A migunit is a collection of data. In the XML files, the component identifies the migunit that the migunit is associated with. The migration store is made up of all the migunits in the migration. The diagnostic log can be used to verify which migunits were included in the migration and can be used for troubleshooting while authoring migration XML files.
|
||||
|
||||
The following examples describe common scenarios in which you can use the diagnostic log.
|
||||
|
||||
@ -103,21 +96,21 @@ The following examples describe common scenarios in which you can use the diagno
|
||||
|
||||
Let's imagine that we have the following directory structure and that we want the **data** directory to be included in the migration along with the **New Text Document.txt** file in the **New Folder**. The directory of `C:\data` contains:
|
||||
|
||||
```console
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
01/21/2009 10:08 PM <DIR> ..
|
||||
01/21/2009 10:08 PM <DIR> New Folder
|
||||
01/21/2009 09:19 PM 13 test (1).txt
|
||||
01/21/2009 09:19 PM 13 test.txt
|
||||
```cmd
|
||||
12/21/2023 01:08 PM <DIR> .
|
||||
12/21/2023 01:08 PM <DIR> ..
|
||||
12/21/2023 01:08 PM <DIR> New Folder
|
||||
12/21/2023 01:19 PM 13 test (1).txt
|
||||
12/21/2023 01:19 PM 13 test.txt
|
||||
2 File(s) 26 bytes
|
||||
```
|
||||
|
||||
The directory of `C:\data\New Folder` contains:
|
||||
|
||||
```console
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
01/21/2009 10:08 PM <DIR> ..
|
||||
01/21/2009 10:08 PM 0 New Text Document.txt
|
||||
```cmd
|
||||
12/21/2023 01:08 PM <DIR> .
|
||||
12/21/2023 01:08 PM <DIR> ..
|
||||
12/21/2023 01:08 PM 0 New Text Document.txt
|
||||
1 File(s) 0 bytes
|
||||
```
|
||||
|
||||
@ -143,22 +136,22 @@ To migrate these files you author the following migration XML:
|
||||
</migration>
|
||||
```
|
||||
|
||||
However, upon testing the migration you notice that the **New Text Document.txt** file isn't included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable **MIG_ENABLE_DIAG** set such that the diagnostic log is generated. Upon searching the diagnostic log for the component **DATA1**, the following XML section is discovered:
|
||||
However, upon testing the migration you notice that the **New Text Document.txt** file isn't included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable **MIG_ENABLE_DIAG** set such that the diagnostic log is generated. Searching the diagnostic log for the component **DATA1** reveals the following XML section:
|
||||
|
||||
```xml
|
||||
<MigUnitList>
|
||||
<MigUnit Name="<System>\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true">
|
||||
<Patterns Type="Include">
|
||||
<Pattern Type="File" Path="C:\data [*]"/>
|
||||
</Patterns>
|
||||
</MigUnit>
|
||||
<MigUnit Name="<System>\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true">
|
||||
<Patterns Type="Include">
|
||||
<Pattern Type="File" Path="C:\data [*]"/>
|
||||
</Patterns>
|
||||
</MigUnit>
|
||||
</MigUnitList>
|
||||
<Perform Name="Gather" User="System">
|
||||
<MigUnit Name="<System>\DATA1 (CMXEAgent)">
|
||||
<Operation Name="Store" Type="File" Path="C:\data" SimObj="false" Success="true"/>
|
||||
<Operation Name="Store" Type="File" Path="C:\data [test (1).txt]" SimObj="false" Success="true"/>
|
||||
<Operation Name="Store" Type="File" Path="C:\data [test.txt]" SimObj="false" Success="true"/>
|
||||
</MigUnit>
|
||||
<MigUnit Name="<System>\DATA1 (CMXEAgent)">
|
||||
<Operation Name="Store" Type="File" Path="C:\data" SimObj="false" Success="true"/>
|
||||
<Operation Name="Store" Type="File" Path="C:\data [test (1).txt]" SimObj="false" Success="true"/>
|
||||
<Operation Name="Store" Type="File" Path="C:\data [test.txt]" SimObj="false" Success="true"/>
|
||||
</MigUnit>
|
||||
</Perform>
|
||||
```
|
||||
|
||||
@ -197,23 +190,23 @@ This diagnostic log confirms that the modified **<pattern>** value enables
|
||||
|
||||
In this scenario, you have the following directory structure and you want all files in the **Data** directory to migrate, except for text files. The `C:\Data` folder contains:
|
||||
|
||||
```console
|
||||
```cmd
|
||||
Directory of C:\Data
|
||||
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
01/21/2009 10:08 PM <DIR> ..
|
||||
01/21/2009 10:08 PM <DIR> New Folder
|
||||
01/21/2009 09:19 PM 13 test (1).txt
|
||||
01/21/2009 09:19 PM 13 test.txt
|
||||
12/21/2023 01:08 PM <DIR> .
|
||||
12/21/2023 01:08 PM <DIR> ..
|
||||
12/21/2023 01:08 PM <DIR> New Folder
|
||||
12/21/2023 01:19 PM 13 test (1).txt
|
||||
12/21/2023 01:19 PM 13 test.txt
|
||||
2 File(s) 26 bytes
|
||||
```
|
||||
|
||||
The `C:\Data\New Folder\` contains:
|
||||
|
||||
```console
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
01/21/2009 10:08 PM <DIR> ..
|
||||
01/21/2009 10:08 PM 0 New Text Document.txt
|
||||
```cmd
|
||||
12/21/2023 01:08 PM <DIR> .
|
||||
12/21/2023 01:08 PM <DIR> ..
|
||||
12/21/2023 01:08 PM 0 New Text Document.txt
|
||||
1 File(s) 0 bytes
|
||||
```
|
||||
|
||||
@ -245,7 +238,7 @@ You author the following migration XML:
|
||||
</component>
|
||||
```
|
||||
|
||||
However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable **MIG_ENABLE_DIAG** set so that the diagnostic log is generated. Upon searching the diagnostic log for the component **DATA1**, the following XML section is discovered:
|
||||
However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable **MIG_ENABLE_DIAG** set so that the diagnostic log is generated. Searching the diagnostic log for the component **DATA1** reveals the following XML section:
|
||||
|
||||
```xml
|
||||
<MigUnitList>
|
||||
@ -327,9 +320,6 @@ Your revised migration XML script excludes the files from migrating, as confirme
|
||||
|
||||
## Related articles
|
||||
|
||||
[XML elements library](usmt-xml-elements-library.md)
|
||||
|
||||
[ScanState syntax](usmt-scanstate-syntax.md)
|
||||
|
||||
[LoadState syntax](usmt-loadstate-syntax.md)
|
||||
|
||||
- [XML elements library](usmt-xml-elements-library.md).
|
||||
- [ScanState syntax](usmt-scanstate-syntax.md).
|
||||
- [LoadState syntax](usmt-loadstate-syntax.md).
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Migrate EFS Files and Certificates (Windows 10)
|
||||
title: Migrate EFS Files and Certificates
|
||||
description: Learn how to migrate Encrypting File System (EFS) certificates. Also, learn where to find information about how to identify file types, files, and folders.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/01/2022
|
||||
ms.date: 12/22/2023
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
@ -16,7 +16,7 @@ This article describes how to migrate Encrypting File System (EFS) certificates.
|
||||
|
||||
## To migrate EFS files and certificates
|
||||
|
||||
Encrypting File System (EFS) certificates will be migrated automatically. However, by default, the User State Migration Tool (USMT) 10.0 fails if an encrypted file is found unless you specify an `/efs` option. Therefore when a device has EFS encrypted files, you must specify the `/efs` option with any one of the following parameters:
|
||||
Encrypting File System (EFS) certificates are migrated automatically. However, by default, the User State Migration Tool (USMT) fails if an encrypted file is found unless you specify an `/efs` option. Therefore when a device has EFS encrypted files, you must specify the `/efs` option with any one of the following parameters:
|
||||
|
||||
- `abort`
|
||||
- `skip`
|
||||
@ -24,12 +24,13 @@ Encrypting File System (EFS) certificates will be migrated automatically. Howeve
|
||||
- `copyraw`
|
||||
- `hardlink`
|
||||
|
||||
when running the `ScanState.exe` command to migrate the encrypted files. Then, when you run the `LoadState.exe` command on the destination computer, the encrypted file and the EFS certificate will be automatically migrated.
|
||||
when running the `ScanState.exe` command to migrate the encrypted files. Then, when you run the `LoadState.exe` command on the destination computer, the encrypted file and the EFS certificate are automatically migrated.
|
||||
|
||||
> [!NOTE]
|
||||
> The `/efs` options are not used with the `LoadState.exe` command.
|
||||
>
|
||||
> The `/efs` options aren't used with the `LoadState.exe` command.
|
||||
|
||||
Before using the **ScanState** tool for a migration that includes encrypted files and EFS certificates, you must ensure that all files in an encrypted folder are encrypted as well or remove the encryption attribute from folders that contain unencrypted files. If the encryption attribute has been removed from a file but not from the parent folder, the file will be encrypted during the migration using the credentials of the account used to run the **LoadState** tool.
|
||||
Before using the **ScanState** tool for a migration that includes encrypted files and EFS certificates, you must ensure that all files in an encrypted folder are encrypted as well or remove the encryption attribute from folders that contain unencrypted files. If the encryption attribute is removed from a file but not from the parent folder, the file is encrypted during the migration using the credentials of the account used to run the **LoadState** tool.
|
||||
|
||||
You can run the [Cipher.exe](/windows-server/administration/windows-commands/cipher) tool at a Windows command prompt to review and change encryption settings on files and folders. For example, to remove encryption from a folder, at a command prompt enter:
|
||||
|
||||
@ -41,6 +42,5 @@ where *<Path>* is the full path of the topmost parent directory where the
|
||||
|
||||
## Related articles
|
||||
|
||||
[What does USMT migrate?](usmt-what-does-usmt-migrate.md)
|
||||
|
||||
[Identify file types, files, and folders](usmt-identify-file-types-files-and-folders.md)
|
||||
- [What does USMT migrate?](usmt-what-does-usmt-migrate.md).
|
||||
- [Identify file types, files, and folders](usmt-identify-file-types-files-and-folders.md).
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Migration Store Encryption (Windows 10)
|
||||
title: Migration Store Encryption
|
||||
description: Learn how the User State Migration Tool (USMT) enables support for stronger encryption algorithms, called Advanced Encryption Standard (AES).
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
@ -12,13 +12,13 @@ ms.technology: itpro-deploy
|
||||
|
||||
# Migration store encryption
|
||||
|
||||
This article discusses User State Migration Tool (USMT) 10.0 options for migration store encryption to protect the integrity of user data during a migration.
|
||||
This article discusses User State Migration Tool (USMT) 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.exe` and the `LoadState.exe` 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.exe` and the `LoadState.exe` 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 encryption algorithm you choose must be specified for both the `ScanState.exe` and the `LoadState.exe` 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.exe` and the `LoadState.exe` command lines by using the `/encrypt`:*encryption_strength* and the `/decrypt`:*encryption_strength* command-line options. All of the encryption application programming interfaces (APIs) used by USMT are available in currently supported versions of Windows. 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.
|
||||
|
||||
@ -28,8 +28,9 @@ The following table describes the command-line encryption options in USMT.
|
||||
|*LoadState*|**/decrypt**<*AES, AES_128, AES_192, AES_256, 3DES, 3DES_112*>|This option and argument specify that the store must be decrypted and which algorithm to use. When the algorithm argument isn't provided, the **LoadState** tool employs the **3DES** algorithm.|
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Some encryption algorithms may not be available on your systems. You can verify which algorithms are available by running the `UsmtUtils.exe` command with the `/ec` option. For more information, see [UsmtUtils syntax](usmt-utilities.md).
|
||||
|
||||
## Related articles
|
||||
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
- [Plan your migration](usmt-plan-your-migration.md).
|
||||
|
||||
@ -1,28 +1,28 @@
|
||||
---
|
||||
title: Plan Your Migration (Windows 10)
|
||||
title: Plan Your Migration
|
||||
description: Learn how to your plan your migration carefully so your migration can proceed smoothly and so that you reduce the risk of migration failure.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/01/2022
|
||||
ms.date: 12/22/2023
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Plan your migration
|
||||
|
||||
Before you use the User State Migration Tool (USMT) 10.0 to perform your migration, we recommend that you plan your migration carefully. Planning can help your migration proceed smoothly and can reduce the risk of migration failure.
|
||||
Before you use the User State Migration Tool (USMT) to perform your migration, we recommend that you plan your migration carefully. Planning can help your migration proceed smoothly and can reduce the risk of migration failure.
|
||||
|
||||
In migration planning, both organizations and individuals must first identify what to migrate, including user settings, applications and application settings, and personal data files and folders. Identifying the applications to migrate is especially important so that you can avoid capturing data about applications that may be phased out.
|
||||
In migration planning, both organizations and individuals must first identify what to migrate, including user settings, applications and application settings, and personal data files and folders. Identifying the applications to migrate is especially important so that you can avoid capturing data about applications that might be phased out.
|
||||
|
||||
One of the most important requirements for migrating settings and data is restoring only the information that the destination computer requires. Although the data that you capture on the source computer may be more comprehensive than the restoration data for backup purposes, restoring data or settings for applications that you won't install on the destination system is redundant. Restoring data or settings for applications that aren't installed can also introduce instability in a newly deployed computer.
|
||||
One of the most important requirements for migrating settings and data is restoring only the information that the destination computer requires. Although the data that you capture on the source computer might be more comprehensive than the restoration data for backup purposes, restoring data or settings for applications that aren't installed on the destination system is redundant. Restoring data or settings for applications that aren't installed can also introduce instability in a newly deployed computer.
|
||||
|
||||
## In this section
|
||||
|
||||
| Link | Description |
|
||||
|--- |--- |
|
||||
|[Common migration scenarios](usmt-common-migration-scenarios.md)|Determine whether you'll perform a refresh migration or a replace migration.|
|
||||
|[Common migration scenarios](usmt-common-migration-scenarios.md)|Determine whether to perform a refresh migration or a replace migration.|
|
||||
|[What does USMT migrate?](usmt-what-does-usmt-migrate.md)|Learn which applications, user data, and operating system components USMT migrates.|
|
||||
|[Choose a migration store type](usmt-choose-migration-store-type.md)|Choose an uncompressed, compressed, or hard-link migration store.|
|
||||
|[Determine what to migrate](usmt-determine-what-to-migrate.md)|Identify user accounts, application settings, operating system settings, and files that you want to migrate inside your organization.|
|
||||
@ -30,4 +30,4 @@ One of the most important requirements for migrating settings and data is restor
|
||||
|
||||
## Related articles
|
||||
|
||||
[USMT XML reference](usmt-xml-reference.md)
|
||||
- [USMT XML reference](usmt-xml-reference.md).
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: User State Migration Toolkit (USMT) Reference (Windows 10)
|
||||
title: User State Migration Toolkit (USMT) Reference
|
||||
description: Use this User State Migration Toolkit (USMT) article to learn details about USMT, like operating system, hardware, and software requirements, and user prerequisites.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/01/2022
|
||||
ms.date: 12/22/2023
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
@ -26,8 +26,6 @@ ms.technology: itpro-deploy
|
||||
|
||||
## Related articles
|
||||
|
||||
[User State Migration Tool (USMT) overview topics](usmt-topics.md)
|
||||
|
||||
[User State Migration Tool (USMT) how-to topics](usmt-how-to.md)
|
||||
|
||||
[User State Migration Tool (USMT) troubleshooting](usmt-troubleshooting.md)
|
||||
- [User State Migration Tool (USMT) overview articles](usmt-topics.md).
|
||||
- [User State Migration Tool (USMT) how-to articles](usmt-how-to.md).
|
||||
- [User State Migration Tool (USMT) troubleshooting](usmt-troubleshooting.md).
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: USMT Requirements (Windows 10)
|
||||
title: USMT Requirements
|
||||
description: While the User State Migration Tool (USMT) doesn't have many requirements, these tips and tricks can help smooth the migration process.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
@ -14,45 +14,51 @@ ms.technology: itpro-deploy
|
||||
|
||||
## Supported operating systems
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 doesn't 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 User State Migration Tool (USMT) doesn't 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. The same amount of hard disk space is also needed on the destination computer for the migrated files and settings.
|
||||
|
||||
The following table lists the operating systems supported in USMT.
|
||||
|
||||
|Operating Systems|ScanState (source computer)|LoadState (destination computer)|
|
||||
| Operating Systems | ScanState<br>(Source Device)| LoadState<br>(Destination Device)|
|
||||
|--- |--- |--- |
|
||||
|32-bit versions of Windows 7|✔️|✔️|
|
||||
|64-bit versions of Windows 7|✔️|✔️|
|
||||
|32-bit versions of Windows 8|✔️|✔️|
|
||||
|64-bit versions of Windows 8|✔️|✔️|
|
||||
|32-bit versions of Windows 10|✔️|✔️|
|
||||
|64-bit versions of Windows 10|✔️|✔️|
|
||||
|Windows 7|✔️|❌|
|
||||
|Windows 8|✔️|❌|
|
||||
|Windows 10|✔️|✔️|
|
||||
|Windows 11|✔️|✔️|
|
||||
|
||||
> [!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.
|
||||
>
|
||||
> - You can migrate a 32-bit operating system to a 64-bit operating system. However, you can't migrate a 64-bit operating system to a 32-bit operating system.
|
||||
>
|
||||
> - It's supported to gather data from a source device using **ScanState** for a version of Windows that is out of support, but it's not supported to restore data to a destination device using **LoadState** to a version of Windows that is out of support.
|
||||
|
||||
## Unsupported scenarios
|
||||
|
||||
- USMT doesn't support any of the Windows Server® operating systems.
|
||||
- USMT for Windows 10 shouldn't be used for migrating between previous versions of Windows. USMT for Windows 10 is only meant to migrate to Windows 10 or between Windows 10 versions. For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) overview](/previous-versions/windows/hh825227(v=win.10)).
|
||||
- USMT shouldn't be used for migrating between previous versions of Windows. USMT is only meant to:
|
||||
- Migrate to a currently supported version of Windows
|
||||
- Migrate between currently supported versions of Windows, assuming the version of Windows being migrated to is newer or the same as the previous version of Windows being migrated from.
|
||||
|
||||
For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) overview](/previous-versions/windows/hh825227(v=win.10)).
|
||||
|
||||
## Windows PE
|
||||
|
||||
- **Must use latest version of Windows 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](/windows-hardware/manufacture/desktop/whats-new-in-windows-pe-s14).
|
||||
- **Must use latest version of Windows PE.** For more info, see [What's New in Windows PE](/windows-hardware/manufacture/desktop/whats-new-in-windows-pe-s14).
|
||||
|
||||
## 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 don't run USMT from an elevated prompt, only the user profile that is logged on will be included in the migration.
|
||||
When manually running the **ScanState** and **LoadState** tools, you must run them from an elevated command prompt to ensure that all specified users are migrated. If you don't run USMT from an elevated prompt, only the user profile that is logged on is included in the migration.
|
||||
|
||||
To open an elevated command prompt:
|
||||
|
||||
1. Select **Start**.
|
||||
2. Enter `cmd` in the search function.
|
||||
3. Depending on the OS you're using, **cmd** or **Command Prompt** is displayed.
|
||||
4. Right-click **cmd** or **Command Prompt**, and then select **Run as administrator**.
|
||||
5. If the current user isn't already an administrator, you'll be prompted to enter administrator credentials.
|
||||
1. Enter `cmd` in the search function.
|
||||
1. **cmd** or **Command Prompt** is displayed.
|
||||
1. Right-click **cmd** or **Command Prompt**, and then select **Run as administrator**.
|
||||
1. If the current user isn't already an administrator, it prompts to enter administrator credentials.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> You must run USMT using an account with full administrative permissions, including the following privileges:
|
||||
>
|
||||
> - SeBackupPrivilege (Back up files and directories)
|
||||
@ -65,7 +71,7 @@ To open an elevated command prompt:
|
||||
|
||||
### Specify the `/c` option and <ErrorControl> settings in the `Config.xml` file
|
||||
|
||||
USMT will fail if it can't 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 didn't migrate, but the migration won't 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#errorcontrol), [Log files](usmt-log-files.md), and [XML elements library](usmt-xml-elements-library.md).
|
||||
USMT fails if it can't migrate a file or setting, unless the `/c` option is specified. When you specify the `/c` option, USMT logs an error each time it encounters a file that is in use that didn't migrate, but the migration isn't 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#errorcontrol), [Log files](usmt-log-files.md), and [XML elements library](usmt-xml-elements-library.md).
|
||||
|
||||
## LoadState
|
||||
|
||||
@ -88,6 +94,6 @@ This documentation assumes that IT professionals using USMT understand command-l
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Plan your migration](usmt-plan-your-migration.md)
|
||||
- [Estimate migration store size](usmt-estimate-migration-store-size.md)
|
||||
- [User State Migration Tool (USMT) overview topics](usmt-topics.md)
|
||||
- [Plan your migration](usmt-plan-your-migration.md).
|
||||
- [Estimate migration store size](usmt-estimate-migration-store-size.md).
|
||||
- [User State Migration Tool (USMT) overview articles](usmt-topics.md).
|
||||
|
||||
@ -1,18 +1,18 @@
|
||||
---
|
||||
title: User State Migration Tool (USMT) Overview Topics (Windows 10)
|
||||
title: User State Migration Tool (USMT) Overview Articles
|
||||
description: Learn about User State Migration Tool (USMT) overview articles that describe USMT as a highly customizable user-profile migration experience for IT professionals.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/01/2022
|
||||
ms.date: 12/22/2023
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# User State Migration Tool (USMT) overview topics
|
||||
# User State Migration Tool (USMT) overview articles
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 provides a highly customizable user-profile migration experience for IT professionals. USMT includes three command-line tools: `ScanState.exe`, `LoadState.exe`, and `UsmtUtils.exe`. USMT also includes a set of three modifiable .xml files: `MigApp.xml`, `MigDocs.xml`, and `MigUser.xml`. Additionally, you can create custom .xml files to support your migration needs. You can also create a `Config.xml` file to specify files or settings to exclude from the migration.
|
||||
The User State Migration Tool (USMT) provides a highly customizable user-profile migration experience for IT professionals. USMT includes three command-line tools: `ScanState.exe`, `LoadState.exe`, and `UsmtUtils.exe`. USMT also includes a set of three modifiable .xml files: `MigApp.xml`, `MigDocs.xml`, and `MigUser.xml`. Additionally, you can create custom .xml files to support your migration needs. You can also create a `Config.xml` file to specify files or settings to exclude from the migration.
|
||||
|
||||
## In this section
|
||||
|
||||
@ -24,6 +24,6 @@ The User State Migration Tool (USMT) 10.0 provides a highly customizable user-pr
|
||||
|
||||
## Related articles
|
||||
|
||||
- [User State Migration Tool (USMT) how-to topics](usmt-how-to.md)
|
||||
- [User State Migration Tool (USMT) troubleshooting](usmt-troubleshooting.md)
|
||||
- [User State Migration Toolkit (USMT) reference](usmt-reference.md)
|
||||
- [User State Migration Tool (USMT) how-to articles](usmt-how-to.md).
|
||||
- [User State Migration Tool (USMT) troubleshooting](usmt-troubleshooting.md).
|
||||
- [User State Migration Toolkit (USMT) reference](usmt-reference.md).
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user