`*
or
`/uel:0` | **(User exclude based on last logon)**
Migrates only the users that logged onto the source computer within the specified time period, based on the **Last Modified** date of the Ntuser.dat file on the source computer. The **/uel** option acts as an include rule. For example, the **/uel:30** option migrates users who logged on, or whose user account was modified, within the last 30 days from the date when the ScanState command is run. You can specify a number of days or you can specify a date. You cannot use this option with the **/all** option. USMT retrieves the last logon information from the local computer, so the computer does not need to be connected to the network when you run this option. In addition, if a domain user has logged onto another computer, that logon instance is not considered by USMT. **Note**
The **/uel** option is not valid in offline migrations.
Examples:- `/uel:0` migrates accounts that were logged on to the source computer when the **ScanState** command was run.
- `/uel:90` migrates users who have logged on, or whose accounts have been otherwise modified, within the last 90 days.
- `/uel:1` migrates users whose accounts have been modified within the last 24 hours.
- `/uel:2002/1/15` migrates users who have logged on or whose accounts have been modified since January 15, 2002.
For example:
`loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore /uel:0` |
-| `/ue`:*DomainName UserName*
or
`/ue`*"DomainName User Name"*
or
`/ue`:*ComputerName LocalUserName* | **(User exclude)**
Excludes the specified users from the migration. You can specify multiple **/ue** options but you cannot use the **/ue** option with the **/all** option. *DomainName* and *UserName* can contain the asterisk () wildcard character. When you specify a user name that contains spaces, you will need to surround it with quotation marks.
For example:
`loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore /ue:contoso\user1`
For more examples, see the descriptions of the **/uel**, **/ue**, and **/ui** options in this table. |
-| `/md:`*OldDomain*:*NewDomain*
or
`/md:`*LocalComputerName:NewDomain* | **(move domain)**
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* may contain the asterisk () wildcard character.
You can specify this option more than once. You may want to specify multiple **/md** options if you are consolidating users across multiple domains to a single domain. For example, you could specify the following to consolidate the users from the Corporate and FarNorth domains into the Fabrikam domain: `/md:corporate:fabrikam` and `/md:farnorth:fabrikam`.
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. **Note**
If you specify an *OldDomain* that did not exist on the source computer, the **LoadState** command will appear to complete successfully, without an error or warning. However, in this case, users will not be moved to *NewDomain* but will remain in their original domain. For example, if you misspell "contoso" and you specify "/md:contso:fabrikam", the users will remain in contoso on the destination computer.
For example:
`loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
` /progress:prog.log /l:load.log /md:contoso:fabrikam` |
-| `/mu:`*OldDomain OldUserName*:[*NewDomain*]*NewUserName*
or
`/mu:`*OldLocalUserName*:*NewDomain NewUserName* | Specifies a new user name for the specified user. If the store contains more than one user, you can specify multiple **/mu** options. You cannot use wildcard characters with this option.
For example:
`loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
`/progress:prog.log /l:load.log /mu:contoso\user1:fabrikam\user1` |
-| `/lac:`[*Password*] | **(local account create)**
Specifies that if a user account is a local (non-domain) account, and it does not exist on the destination computer, USMT will create the account on the destination computer but it will be disabled. To enable the account, you must also use the **/lae** option.
If the **/lac** option is not specified, any local user accounts that do not already exist on the destination computer will not be migrated.
*Password* is the password for the newly created account. An empty password is used by default. **Caution**
Use the *Password* variable with caution because it is provided in plain text and can be obtained by anyone with access to the computer that is running the **LoadState** command.
Also, if the computer has multiple users, all migrated users will have the same password.
For example:
`loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
For instructions, see [Migrate User Accounts](usmt-migrate-user-accounts.md). |
-| `/lae` | **(local account enable)**
Enables the account that was created with the **/lac** option. You must specify the **/lac** option with this option.
For example:
`loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
`/progress:prog.log /l:load.log /lac:password /lae`
For instructions, see [Migrate User Accounts](usmt-migrate-user-accounts.md). |
-
+| **/all** | Migrates all of the users on the computer.
USMT migrates all user accounts on the computer, unless you specifically exclude an account with the `/ue` or `/uel` options. For this reason, you don't need to specify this option on the command line. However, if you choose to use the `/all` option, you can't also use the `/ui`, `/ue` or `/uel` options. |
+| **/ui**:*DomainName UserName*
or
**/ui**:*"DomainName User Name"*
or
**/ui**:*ComputerName LocalUserName* | **(User include)**
Migrates the specified user. By default, all users are included in the migration. Therefore, this option is helpful only when used with the `/ue` option. You can specify multiple `/ui` options, but you can't use the `/ui` option with the `/all` option. *DomainName* and *UserName* can contain the asterisk () wildcard character. When you specify a user name that contains spaces, you'll need to surround it with quotations marks.
For example:- To include only User2 from the Corporate domain, type:
`/ue:* /ui:corporate\user2`
**Note**
If a user is specified for inclusion with the `/ui` option and also specified to be excluded with either the `/ue` or `/uel` options, the user will be included in the migration.
For more examples, see the descriptions of the `/uel`, `/ue`, and `/ui` options in this table. |
+| **/uel**:*``*
or
**/uel**:*``*
or
**/uel**:0 | **(User exclude based on last logon)**
Migrates only the users that logged onto the source computer within the specified time period, based on the **Last Modified** date of the Ntuser.dat file on the source computer. The `/uel` option acts as an include rule. For example, the `/uel:30` option migrates users who logged on, or whose user account was modified, within the last 30 days from the date when the `ScanState.exe` command is run. You can specify the number of days or you can specify a date. You can't use this option with the `/all` option. USMT retrieves the last sign-in information from the local computer, so the computer doesn't need to be connected to the network when you run this option. In addition, if a domain user has signed into another computer, that sign-in instance isn't considered by USMT. **Note**
The `/uel` option isn't valid in offline migrations.
Examples:- `/uel:0` migrates accounts that were logged on to the source computer when the `ScanState.exe` command was run.
- `/uel:90` migrates users who have logged on, or whose accounts have been otherwise modified, within the last 90 days.
- `/uel:1` migrates users whose accounts have been modified within the last 24 hours.
- `/uel:2002/1/15` migrates users who have logged on or whose accounts have been modified since January 15, 2002.
For example:
`loadstate.exe/i:migapp.xml /i:migdocs.xml \server\share\migration\mystore /uel:0` |
+| **/ue**:*DomainName\UserName*
or
**/ue** *"DomainName\User Name"*
or
**/ue**:*ComputerName\LocalUserName* | **(User exclude)**
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 you specify a user name that contains spaces, you'll need to surround it with quotation marks.
For example:
`loadstate.exe/i:migapp.xml /i:migdocs.xml \server\share\migration\mystore /ue:contoso\user1`
For more examples, see the descriptions of the `/uel`, `/ue`, and `/ui` options in this table. |
+| **/md**:*OldDomain*:*NewDomain*
or
**/md**:*LocalComputerName:NewDomain* | **(Move domain)**
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* may contain the asterisk () wildcard character.
You can specify this option more than once. You may want to specify multiple `/md` options if you're consolidating users across multiple domains to a single domain. For example, you could specify the following to consolidate the users from the Corporate and FarNorth domains into the Fabrikam domain: `/md:corporate:fabrikam` and `/md:farnorth:fabrikam`.
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. **Note**
If you specify an *OldDomain* that didn't exist on the source computer, the `LoadState.exe` command will appear to complete successfully, without an error or warning. However, in this case, users won't be moved to *NewDomain* but will remain in their original domain. For example, if you misspell **contoso** and you instead specify **/md:contso:fabrikam**, the users will remain in **contoso** on the destination computer.
For example:
`loadstate.exe /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
` /progress:prog.log /l:load.log /md:contoso:fabrikam` |
+| **/mu**:*OldDomain OldUserName*:[*NewDomain*]*NewUserName*
or
**/mu**:*OldLocalUserName*:*NewDomain NewUserName* | **(Move user)**
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.
For example:
`loadstate.exe /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
`/progress:prog.log /l:load.log /mu:contoso\user1:fabrikam\user1` |
+| **/lac**:[*Password*] | **(Local account create)**
Specifies that if a user account is a local (non-domain) account, and it doesn't exist on the destination computer, USMT will create the account on the destination computer but it will be disabled. To enable the account, you must also use the `/lae` option.
If the `/lac` option isn't specified, any local user accounts that don't already exist on the destination computer won't be migrated.
*Password* is the password for the newly created account. An empty password is used by default. **Caution**
Use the *Password* variable with caution because it's provided in plain text and can be obtained by anyone with access to the computer that is running the `LoadState.exe` command.
Also, if the computer has multiple users, all migrated users will have the same password.
For example:
`loadstate.exe /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
For instructions, see [Migrate user accounts](usmt-migrate-user-accounts.md). |
+| `/lae` | **(Local account enable)**
Enables the account that was created with the `/lac` option. You must specify the `/lac` option with this option.
For example:
`loadstate.exe /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore`
`/progress:prog.log /l:load.log /lac:password /lae`
For instructions, see [Migrate user accounts](usmt-migrate-user-accounts.md). |
### Examples for the /ui and /ue options
@@ -109,24 +107,24 @@ The following examples apply to both the **/ui** and **/ue** options. You can re
| Exclude all local users. | `/ue:%computername%` |
| Exclude users in all domains named User1, User2, and so on. | `/ue:\user` |
-### Using the Options Together
+### Using the options together
-You can use the **/uel**, **/ue** and **/ui** options together to migrate only the users that you want migrated.
+You can use the `/uel`, `/ue` and `/ui` options together to migrate only the users that you want migrated.
-**The /ui option has precedence over the /ue and /uel options.** If a user is specified to be included using the **/ui** option, and also specified to be excluded using either the **/ue** or **/uel** options, the user will be included in the migration. For example, if you specify `/ui:contoso\* /ue:contoso\user1`, then User1 will be migrated, because the **/ui** option takes precedence over the **/ue** option.
+**The /ui option has precedence over the /ue and /uel options.** If a user is included using the `/ui` option and also excluded using either the `/ue` or `/uel` options, the user will be included in the migration. For example, if you specify `/ui:contoso\* /ue:contoso\user1`, then User1 will be migrated, because the `/ui` option takes precedence over the `/ue` option.
-**The /uel option takes precedence over the /ue option.** If a user has logged on within the specified time period set by the **/uel** option, that user's profile will be migrated even if they are excluded by using the **/ue** option. For example, if you specify `/ue:contoso\user1 /uel:14`, the User1 will be migrated if they have logged on to the computer within the last 14 days.
+**The /uel option takes precedence over the /ue option.** If a user has logged on within the specified time period set by the `/uel` option, that user's profile will be migrated even if they're excluded by using the `/ue` option. For example, if you specify `/ue:contoso\user1 /uel:14`, the User1 will be migrated if they've logged on to the computer within the last 14 days.
| Behavior | Command |
|--- |--- |
| Include only User2 from the Fabrikam domain and exclude all other users. | `/ue:* /ui:fabrikam\user2` |
| Include only the local user named User1 and exclude all other users. | `/ue:* /ui:user1` |
-| Include only the domain users from Contoso, except Contoso\User1. | This behavior cannot be completed using a single command. Instead, to migrate this set of users, you will need to specify the following:- Using the **ScanState** command-line tool, type: `/ue:* /ui:contoso`
- Using the **LoadState** command-line tool, type: `/ue:contoso\user1`
|
+| Include only the domain users from Contoso, except Contoso\User1. | This behavior can't be completed using a single command. Instead, to migrate this set of users, you'll need to specify the following options:- Using the **ScanState** command-line tool, type: `/ue:* /ui:contoso`
- Using the **LoadState** command-line tool, type: `/ue:contoso\user1`
|
| Include only local (non-domain) users. | `/ue: /ui:%computername%*` |
-## Incompatible Command-Line Options
+## Incompatible command-line options
-The following table indicates which command-line options are not compatible with the **LoadState** command. If the table entry for a particular combination is blank, the options are compatible and you can use them together. The X symbol means that the options are not compatible. For example, you cannot use the **/nocompress** option with the **/encrypt** option.
+The following table indicates which command-line options aren't compatible with the `LoadState.exe` command. If the table entry for a particular combination is blank, the options are compatible, and you can use them together. The X symbol means that the options aren't compatible. For example, you can't use the `/nocompress` option with the `/encrypt` option.
| Command-Line Option | /keyfile | /nocompress | /genconfig | /all |
|--- |--- |--- |--- |--- |
@@ -155,8 +153,8 @@ The following table indicates which command-line options are not compatible with
| **/lac** | | | | |
> [!NOTE]
-> You must specify either the **/key** or **/keyfile** option with the **/encrypt** option.
+> You must specify either the `/key` or `/keyfile` option with the `/encrypt` option.
-## Related topics
+## Related articles
-[XML Elements Library](usmt-xml-elements-library.md)
+[XML elements library](usmt-xml-elements-library.md)
diff --git a/windows/deployment/usmt/usmt-log-files.md b/windows/deployment/usmt/usmt-log-files.md
index 57563d3932..80d06d0350 100644
--- a/windows/deployment/usmt/usmt-log-files.md
+++ b/windows/deployment/usmt/usmt-log-files.md
@@ -1,6 +1,6 @@
---
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.
+description: Learn how to use User State Migration Tool (USMT) 10.0 logs to monitor your migration and to troubleshoot errors and failed migrations.
ms.reviewer:
manager: aaroncz
ms.author: frankroj
@@ -11,98 +11,98 @@ ms.topic: article
ms.technology: itpro-deploy
---
-# Log Files
+# 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 topic 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) 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.
-[Log Command-Line Options](#bkmk-commandlineoptions)
+[Log command-line options](#log-command-line-options)
-[ScanState and LoadState Logs](#bkmk-scanloadstatelogs)
+[ScanState and LoadState logs](#scanstate-and-loadstate-logs)
-[Progress Log](#bkmk-progresslog)
+[Progress log](#progress-log)
-[List Files Log](#bkmk-listfileslog)
+[List files log](#list-files-log)
-[Diagnostic Log](#bkmk-diagnosticlog)
+[Diagnostic log](#diagnostic-log)
-## Log Command-Line Options
+## Log command-line options
The following table describes each command-line option related to logs, and it provides the log name and a description of what type of information each log contains.
|Command line Option|File Name|Description|
|--- |--- |--- |
-|**/l** *[Path]FileName*|Scanstate.log or LoadState.log|Specifies the path and file name of the ScanState.log or LoadState log.|
-|**/progress** *[Path]FileName*|Specifies the path and file name of the Progress log.|Provides information about the status of the migration, by percentage complete.|
-|**/v** *[VerbosityLevel]*|Not applicable|See the "Monitoring Options" section in [ScanState Syntax](usmt-scanstate-syntax.md).|
-|**/listfiles** *[Path]FileName*|Specifies the path and file name of the Listfiles log.|Provides a list of the files that were migrated.|
-|Set the environment variable MIG_ENABLE_DIAG to a path to an XML file.|USMTDiag.xml|The diagnostic log contains detailed system environment information, user environment information, and information about the migration units (migunits) being gathered and their contents.|
+|**/l**"*[Path]FileName*|`Scanstate.log` or `LoadState.log`|Specifies the path and file name of the **ScanState** log or **LoadState** log.|
+|**/progress**:*[Path]FileName*|Specifies the path and file name of the Progress log.|Provides information about the status of the migration, by percentage complete.|
+|**/v**:*[VerbosityLevel]*|Not applicable|See [Monitoring options](usmt-scanstate-syntax.md#monitoring-options) in [ScanState syntax](usmt-scanstate-syntax.md).|
+|**/listfiles**:*[Path]FileName*|Specifies the path and file name of the Listfiles log.|Provides a list of the files that were migrated.|
+|Set the environment variable **MIG_ENABLE_DIAG** to a path to an XML file.|`USMTDiag.xml`|The diagnostic log contains detailed system environment information, user environment information, and information about the migration units (migunits) being gathered and their contents.|
> [!NOTE]
> You cannot store any of the log files in *StorePath*. If you do, the log will be overwritten when USMT is run.
-## ScanState and LoadState Logs
+## ScanState and LoadState logs
-ScanState and LoadState logs are text files that are create when you run the ScanState and LoadState tools. You can use these logs to help monitor your migration. The content of the log depends on the command-line options that you use and the verbosity level that you specify. For more information about verbosity levels, see Monitoring Options in [ScanState Syntax](usmt-scanstate-syntax.md).
+ **ScanState** and **LoadState** logs are text files that are create when you run the **ScanState** and **LoadState** tools. You can use these logs to help monitor your migration. The content of the log depends on the command-line options that you use and the verbosity level that you specify. For more information about verbosity levels, see [Monitoring options](usmt-scanstate-syntax.md#monitoring-options) in [ScanState syntax](usmt-scanstate-syntax.md).
-## Progress Log
+## Progress log
-You can create a progress log using the **/progress** option. External tools, such as Microsoft System Center Operations Manager 2007, can parse the progress log to update your monitoring systems. The first three fields in each line are fixed as follows:
+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 2006.
-- **Local time:** Time, in the format of *hrs*:*minutes*:*seconds* (using a 24-hour clock). For example: 13:49:13.
+- **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:10.
The remaining fields are key/value pairs as indicated in the following table.
| Key | Value |
|-----|-------|
-| program | ScanState.exe or LoadState.exe. |
-| productVersion | The full product version number of USMT. |
-| 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 can be one of the following:- Initializing
- Scanning
- Collecting
- Saving
- Estimating
- Applying
|
-| detectedUser | - For the ScanState tool, these are the users USMT detected on the source computer that can be migrated.
- For the LoadState tool, these are the users USMT detected in the store that can be migrated.
|
-| includedInMigration | Defines whether the user profile/component is included for migration. Valid values are Yes or No. |
-| forUser | Specifies either of the following:- The user state being migrated.
- *This Computer*, meaning files and settings that are not associated with a user.
|
-| detectedComponent | Specifies a component detected by USMT.- For ScanState, this is a component or application that is installed on the source computer.
- For LoadState, this is a component or application that was detected in the store.
|
-| 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. |
-| 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 can be one of the following:- **UnableToCopy**: Unable to copy to store because the disk on which the store is located is full.
- **UnableToOpen**: Unable to open the file for migration because the file is opened in non-shared mode by another application or service.
- **UnableToCopyCatalog**: Unable to copy because the store is corrupted.
- **UnableToAccessDevice**: Unable to access the device.
- **UnableToApply**: Unable to apply the setting to the destination computer.
|
-| 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:- **Ignore**: Non-fatal error ignored and the migration continued because the **/c** option was specified on the command line.
- **Abort**: Stopped the migration because the **/c** option was not specified.
|
-| errorCode | The errorCode or return value. |
-| numberOfIgnoredErrors | The total number of non-fatal errors that USMT ignored. |
-| message | The message corresponding to the errorCode. |
+| **program** | `ScanState.exe` or `LoadState.exe`. |
+| **productVersion** | The full product version number of USMT. |
+| **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:- Initializing
- Scanning
- Collecting
- Saving
- Estimating
- Applying
|
+| **detectedUser** | - For the **ScanState** tool, this key are the users USMT detected on the source computer that can be migrated.
- For the **LoadState** tool, this key are the users USMT detected in the store that can be migrated.
|
+| **includedInMigration** | Defines whether the user profile/component is included for migration. Valid values are **Yes** or **No**. |
+| **forUser** | Specifies either of the following values:- The user state being migrated.
- *This Computer*, meaning files and settings that aren't associated with a user.
|
+| **detectedComponent** | Specifies a component detected by USMT.- For **ScanState**, this key is a component or application that is installed on the source computer.
- For **LoadState**, this key is a component or application that was detected in the store.
|
+| **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**. |
+| **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:- **UnableToCopy**: Unable to copy to store because the disk on which the store is located is full.
- **UnableToOpen**: Unable to open the file for migration because the file is opened in non-shared mode by another application or service.
- **UnableToCopyCatalog**: Unable to copy because the store is corrupted.
- **UnableToAccessDevice**: Unable to access the device.
- **UnableToApply**: Unable to apply the setting to the destination computer.
|
+| **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:- **Ignore**: Non-fatal error ignored and the migration continued because the **/c** option was specified on the command line.
- **Abort**: Stopped the migration because the **/c** option wasn't specified.
|
+| **errorCode** | The errorCode or return value. |
+| **numberOfIgnoredErrors** | The total number of non-fatal errors that USMT ignored. |
+| **message** | The message corresponding to the errorCode. |
-## List Files Log
+## List files log
-The List files log (Listfiles.txt) provides a list of the files that were migrated. This list can be used to troubleshoot XML issues or can be retained as a record of the files that were gathered into the migration store. The List Files log is only available for ScanState.exe.
+The List files log (`Listfiles.txt`) provides a list of the files that were migrated. This list can be used to troubleshoot XML issues or can be retained as a record of the files that were gathered into the migration store. The List Files log is only available for `ScanState.exe`.
-## Diagnostic Log
+## Diagnostic log
-You can obtain the diagnostic log by setting the environment variable MIG\_ENABLE\_DIAG to a path to an XML file.
+You can obtain the diagnostic log by setting the environment variable **MIG_ENABLE_DIAG** to a path to an XML file.
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 is 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 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 following examples describe common scenarios in which you can use the diagnostic log.
**Why is this file not migrating when I authored an "include" rule for it?**
-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:
+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 .
@@ -113,7 +113,7 @@ Let's imagine that we have the following directory structure and that we want th
2 File(s) 26 bytes
```
-The directory of **C:\\data\\New Folder** contains:
+The directory of `C:\data\New Folder` contains:
```console
01/21/2009 10:08 PM .
@@ -144,59 +144,59 @@ To migrate these files you author the following migration XML: