Troubleshooting User State Migration (4276311)

Connectivity:

• Make sure that "Simple file sharing" and any firewalls are turned off. This causes 50% of all failures.
• Use local accounts on the target systems to capture the profiles, not domain accounts. You can use the computer name in both the Host/IP and the domain fields. Use a local account that has administrative access to user profile data.

If this does not work then...

Capture the profile from the computer:

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

You can run the USMT local to the computer by installing either the x86 or x64 versions on the computer and then doing the following...

• Fire up a command prompt
• Change the working directory to USMT installation directory (should be C:\Program Files\USMT301 by default)
• Run the following command...

 "ScanState.exe /i:miguser.xml /i:migapp.xml /l:\ScanState.log /ue:*\* /ui:"

In the example below:
dir1 – path to scan state log (can be the current directory itself) | user1 – User name of the user profile that you wish to capture | dir2 – Path to store the captured user state file.

Please note that dir1 "scan_state_log_path" and dir2 "store_path" should be different.

For example:
"ScanState.exe /i:miguser.xml /i:migapp.xml /l:c:\dir1\ScanState.log /ue:*\* /ui:user1 c:\dir2”

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

We really only need ScanState.exe /i:miguser.xml /i:migapp.xml/l:\ScanState.log /ue:*\* /ui:

For loading, we use
For local users
LoadState.exe /i:migapp.xml /i:miguser.xml /lac /lae
 
For domain users
LoadState.exe /i:migapp.xml /i:miguser.xml