USMT 4.0 Restore

[AaronBISSELL]

Well - I got the restore process to work with the help of the community here - but alas, it would seem the troubles continue to pile up. It's always something right?

 

The restore process begins, and fails - with these log entries

 

2014-07-07 08:51:39, Info [0x000000] LOADSTATE.EXE Version 6.3.9600.16384[gle=0x000000b7]

2014-07-07 08:51:39, Info [0x000000] USMT Started at 2014/07/07:08:51:39.795

2014-07-07 08:51:39, Info [0x000000] Command line: C:\_SMSTaskSequence\Packages\BH100001\amd64\loadstate.exe \\server\global\Public\USMT\2ec5311fed447e625cbf57c0b51659f0 /c /l:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstateprogress.log /i:C:\_SMSTaskSequence\Packages\BH100001\amd64\migdocs.xml /i:C:\_SMSTaskSequence\Packages\BH100001\amd64\migapp.xml

2014-07-07 08:51:39, Info [0x000000] Script file specified: C:\_SMSTaskSequence\Packages\BH100001\amd64\migdocs.xml[gle=0x000000cb]

2014-07-07 08:51:39, Info [0x000000] Script file specified: C:\_SMSTaskSequence\Packages\BH100001\amd64\migapp.xml[gle=0x000000cb]

2014-07-07 08:51:39, Info [0x000000] Starting the migration process[gle=0x00000006]

2014-07-07 08:51:40, Warning [0x080000] ELAM hive is missing (C:\WINDOWS\system32\config\elam). Ignoring load request.

2014-07-07 08:51:47, Info [0x000000] System information:

Computer name: 2VMCXV1

Machine SID: S-1-5-21-3464013732-403841507-2018575180

OS version: 6.1.7601.Service Pack 1

Language: en-US

Architecture: 64-bit

Drives:

C: Type: Fixed, Bus type: RAID, Hotplug: No

D: Type: CD/DVD

Z: Type: Remote

Users:

2VMCXV1\Guest, administrator: No, interactive: Yes, logged on: No, has profile: No

2VMCXV1\Administrator, administrator: Yes, interactive: Yes, logged on: No, has profile: No

2014-07-07 08:51:47, Info [0x000000] Processing the settings store[gle=0x00000006]

2014-07-07 08:51:53, Info [0x000000] Selecting migration units

[gle=0x00000006]

2014-07-07 08:51:53, Error [0x000000] The account 2VMCXV1\UpdatusUser is chosen for migration, but the target does not have account 2VMCXV1\UpdatusUser. See documentation on /lac, /lae, /ui, /ue and /uel options.

2014-07-07 08:51:53, Info [0x000000] Failed.[gle=0x00000006]

2014-07-07 08:51:53, Info [0x000000] Unable to create a local account because /lac was not specified[gle=0x00000006]

2014-07-07 08:51:53, Info [0x000000] USMT Completed at 2014/07/07:08:51:53.614[gle=0x00000006]

2014-07-07 08:51:53, Info [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------

2014-07-07 08:51:53, Info [0x000000] * USMT error code 14:

2014-07-07 08:51:53, Info [0x000000] +-----------------------------------------------------------------------------------------

2014-07-07 08:51:53, Info [0x000000] | Unable to create a local account because /lac was not specified

2014-07-07 08:51:53, Info [0x000000] +-----------------------------------------------------------------------------------------

It seems it was trying to migrate a profile and failing during the process? Here are the loadstate / scanstate commands in my .ini file.

ScanStateArgs=/v:5 /o /c /uel:90 /ue:*\* /ui:HOMECARE\*

LoadStateArgs=/v:5 /c /ue:%computername%\* /ui:HOMECARE\*

I thought that the scanstate would ignore local profiles with those commands? But even so, if they didn't - I thought that the loadstate commands would ignore the restore process on Local profiles? is there something I am missing in my syntax?

Thanks in advance!

 

[AmrelMahdy]

it seems that you are using local account "2VMCXV1\UpdatusUser" which doesnt exist locally on the machine you are restoring the data on

[AaronBISSELL]

Correct - but does that mean it's trying to restore that data from the backup? Or are you suggesting that is the user account that the restore process itself is using to restore the data?

 

In any event - could you suggest a possible solution that I could try?

 

Thanks!

[AaronBISSELL]

Definitely need advice from someone who understands USMT commands in task sequence .INI files better than I do

[anyweb]

when debugging stuff like this set your debug level to /v:13 like so

 

http://www.niallbrady.com/2012/01/25/troubleshooting-usmt/

 

that will give more output in the logs above,

 

in addition, you can simply add a /lac statement like in the following batch file below

@set USMT_WORKING_DIR=%~2%\USMTbits\amd64

"%~2\USMTbits\amd64\loadstate.exe" "%~1" /c /lac:Password123 /i:%~2\USMTbits\amd64\miguser.xml /i:%~2\USMTbits\amd64\migapp.xml /i:%~2\USMTbits\amd64\wallpaper.xml /i:%~2\USMTbits\amd64\printers.xml /nocompress /v:13 /l:%~2\Windows\CCM\logs\SMSTSLog\loadstate.log

the variables used above (%~1 and %~2 are as follows)

 

 

if you dont want to use a batch file then modify the statements in your task sequence to match the above (more or less) and you'll be ok, the restore and backup parts of the above are all in the CM12 BitLocker Frontend HTA code available for download here

 

http://www.windows-noob.com/forums/index.php?/topic/7294-the-cm12-bitlocker-frontend-hta/

 

why reinvent the wheel ;-)

[Peter van der Woude]

To add-on to Niall, if you really don't want any batch files or whatever to call USMT, this is what the different task sequence settings mean: http://www.petervanderwoude.nl/post/how-the-settings-in-configmgr-translate-to-the-command-line-in-usmt/