Joshua312

Well, I finally got things working...my two main issues were that the central site had SP2 Config Mgr. Client but the distribution points had not been updated. After updating those, I had to include the following in my scanstate. /ui:*.* /ue:Administrator /ue:*\* You could also do %computername%\* if you have accounts which have a \ in them which need to be migrated. I did not want any local accounts to be migrated.

I did a bit more digging today and was looking through the Config Mgr. It looks like our primary site had the latest SCCM client installed, however the secondary sites never had their packages updated with the latest SP2 client, so they were installing SP1 which was in their package folder. I've updated the sites this evening and am hoping this will fix the issue, I know SP2 is needed for USMT 4 to work, so if all my other items are in order - I'm hoping to report back with success!

Right now I am using a different method which seemed to work without errors on the screen, however data was still not restored. http://sccm.haas.se/?p=272 Error is IsUSMTPreLonghorn failed (0x80070002) UserStateMigrationAction: GetUSMTBinaryFailed (0x80070003) Failed to initialize Failed to run the action Restore User State. The system cannot find the file specified. Right now I am trying the capture with the USMT package point to the USMT root and then with the restore USMT package pointed directly to x86 to see if it is having issues deciphering what to execute. I can see all the USMT files (x86 and x64) being downloaded right before trying to execute the restore function, so I am wondering if it is looking in the USMT root and not seeing the file it needs. I cannot find a loadstate log on the PC when going into F8. I can only see the smts logs.

I will run it again at work tomorrow and reply back. I've been trying a few different methods trying to get this to work and the furthest I've gotten so far is just not having the data restore back into the directories. I've also tried using this method instead: http://blogs.technet.com/b/configurationmgr/archive/2010/06/30/how-to-use-usmt-4-hardlinking-in-a-configuration-manager-2007-task-sequence.aspx So I could use it also for W7 to W7 rebuilds but I get an immediate error on my first task sequence when I try to restart into the full Windows OS, it gives me an error code that translates to the operation is not allowed. Does anyone mind sharing their XML so I can compare to what I have setup to see where I may be going wrong.

Has it ever been determined why user data is not being restored but instead still sitting in the USMTOffline folder? I receive a task sequence error when it attempts to restore, when I login I can see all the data in the folder but it is not restored. My USMT 4 package points to the USMT root folder with the x86 and x64 subfolders within. I have it set so advertisement data is downloaded to the DP.