User State Migration (USMT) Troubleshooting

If you are having difficulty capturing user states from the K2000 here are a few things to look at.


Make sure that "Simple file sharing" and any firewalls are turned off. This causes 50% of all failures.

Use local accounts to capture the profiles NOT DOMAIN accounts and NOT Roaming Profiles. You can use the computer name in both the Host/IP field and the domain. Use an administrator account for the user login info.

Note: We do not make any changes to the workings of Microsoft's tool. We just run it remotely.

If this does not work then...

Manually capture the profile from the computer:

You can run USMT locally on the computer by copying either the x86 or amd64 versions on the computer.

Grab USMT from your main system you used to create KBE from, go to the following path “C:\Program Files\Windows AIK\Tools\USMT”.
Copy “x86” directory or “amd64” directory, depending on the architecture, to the system on which you wish to run the scan (example: "C:\USMT\x86\").

and then doing the following...

  • Fire up a command prompt
  • Change to the working directory where you copied USMT to (example: "C:\USMT\x86\")
  • Run the following command...

ScanState.exe /i:miguser.xml /i:migapp.xml /l:<scan_state_log_path>\ScanState.log /ue:*\* /ui:<user_name> <store_path>
there is a space between user_name and store_path

Where scan_state_log_path = path to scan state log (can be the current directory itself).
user_name = User name of the user profile that you wish to capture.
store_path = Path to store the captured user state file.
Please note that “scan_state_log_path” and “store_path” should be different.

For example:

ScanState.exe /i:miguser.xml /i:migapp.xml /l:C:\USMT\x86\ScanState.log /ue:*\* /ui:user1 C:\USMT\x86\users\user1
there is a space between user_name and store_path

If everything succeeds, you should get a non-empty .MIG file in the store_path directory.

To view the errors, explore the scanstate.log file in the path you defined (example: "C:\USMT\x86\").

We really only need ScanState.exe /i:miguser.xml /i:migapp.xml/l:<scan_state_log_path>\ScanState.log /ue:*\* /ui:<user_name> <store_path>

For loading, we use
For local users

LoadState.exe <user_state_store_path> /i:migapp.xml /i:miguser.xml /lac /lae

For domain users

LoadState.exe <user_state_store_path> /i:migapp.xml /i:miguser.xml

Last update: 2009-10-26 11:35
Modifications to reflect USMT 4.0: 2010-04-26 - Ted R. Staub
Author: AJ Paisley, Chris Grim
0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Answer this question or Comment on this question for clarity