Any suggestions? Export (0) Print
Expand All

Log Files

You can use the ScanState and LoadState logs, as well as the progress log to help monitor your migration. To view the applicable command-line options, see Monitoring options.

You cannot store any of the log files in StorePath. If you do, the log will be written over when USMT is run.

Scanstate and Loadstate logs

Scanstate and Loadstate logs are both text files that are created when you run each of the tools. Although these logs are targeted mostly at developers, you can use these logs to help monitor the migration. To enable the verbose output, you should specify a verbosity level using the /v option. These logs will provide no valuable information if you do not specify a verbosity level. If the log already exists, the tools append the existing log. The content of the log depends on the command-line options that you use and the verbosity level that you specify.

Progress log

You can create a progress log using the /progress option. External tools, such as Microsoft Operations Manager (MOM), can parse the progress log to update your monitoring systems. The first 3 fields in each line are fixed. The fixed fields are:

  • Date: Date is in the format of dayshortNameOfTheMonthyear. For example: 08 Jun 2006.
  • Local time: Time is in hrs:minutes:seconds (24-hour clock). For example: 13:49:13.
  • Migration time: How long USMT was run in hrs:minutes:seconds. For example: 00:00:10.

The rest of the fields are key/value pairs as indicated in the following table.


Key Value


ScanState.exe or LoadState.exe.


The full product build version of USMT.


The name of the computer on which USMT was run.


The full command by which USMT was run.


Defines that a new phase in the migration is starting. Can be one of Initializing, Scanning, Collecting, Saving, Estimating, or Applying.


  • For ScanState, these are the users that USMT has detected on the computer that can be migrated.
  • For LoadState, these are the users that USMT has detected in the store that can be migrated.


Defines whether the user profile/component is included for migration (Yes or No).


Specifies either of the following:

  • The user state being migrated.
  • “This Computer” meaning the files and settings that are user independent.


Specifies a component detected by USMT

  • For ScanState, this is a component or application that is installed on the computer.
  • For LoadState, this is a component or application that was detected in the store.


Total size of the files and settings to migrate in megabytes (MB).


Total percentage of the migration that has been completed by either ScanState or LoadState.


Specifies which user ScanState is collecting files and setting for.


Time estimate in minutes for the migration to complete.


Type of non-fatal error occurred. 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: The store is corrupted.
  • UnableToAccessDevice: Unable to access the device.
  • UnableToApply: Unable to apply file the setting to the destination computer.


The name of the file or setting that caused the non-fatal error


Action taken by USMT for the non-fatal error. The values are:

  • Ignore: USMT ignored and continued with rest of the migration because /c was specified on the command line.
  • Abort: Stopped the migration because /c was not specified.


The errorCode or return value.


The total number of non-fatal errors that USMT ignored.


The message corresponding to the errorCode.

Community Additions

© 2015 Microsoft