USMT loadstate error 27, invalid path. Tried multiple paths...
-
Monday, January 30, 2012 10:07 PM
Hello all,
Our first lab in a workstation class is migrating user data using USMT. We mapped a network drive, generated an xml using scanstate and loaded a new OS to do a loadstate on it. I'm using a batch file on the new Win7 install that maps the network drive again and runs loadstate, but I keep getting error code 27, invalid store path. I tried copying the file to the c: drive first and loading it from there, but got the same error. The instructor suggest that I can't generate the log file in the same directory as the genmig.xml that I'm using for loadstate, but moving the logfile generation directory doesn't change the outcome. Can anyone point out my mistake?
The batch file I'm using follows:
========
net use x: \\server-d222\migrate /user:[user] [pass]
========
x:\amd64\loadstate x:\ /i:migdocs.xml /i:migapp.xml /lac /lae /l:c:\load.log
pause
- Edited by WhiteVandal Monday, January 30, 2012 10:08 PM
All Replies
-
Wednesday, February 22, 2012 2:59 PM We had a similar problem. We used scanstate to save the settings to a I:\ drive. The program made a USMT folder in which the mig file was copied. We then renamed the USMT folder to <username>. After the migration to Win7, we were unable to import the settings with loadstate using the command I:\<username>. The reason for this was that the USMT tool expects a USMT subfolder within the store location. So, after createing a USMT subfolder in the I:\<username> folder and moving the mig file in it, loadstate worked perfectly. Hopefully, this solves your problem too. Good luck.
- Proposed As Answer by Oliver Adams Sunday, March 24, 2013 1:53 AM
-
Sunday, March 24, 2013 1:53 AMOver 1 year after you posted that reply and you are still helping people. This had me really confused. Read your post problem solved, thank you very much!
