USMT Fail on replace scenario

I run my client replace task sequence on a Win 7 machine with 2 Partitions. I then run my client task sequence on a windows 8 machine with only one partition. My USMT restore however fail with the following error in SMSTS and loadstate logs:

Not enough storage is available to complete this operation. (Error: 8007000E; Source: Windows)]LOG]!><time="10:42:40.009-120" date="06-25-2014" component="TSManager" context="" type="3" thread="1712" file="instruction.cxx:895">

I have more than enough space on the target machine.

In the loadstate.log I notice the following:

[gle=0x00000006]
2014-06-25 10:42:39, Error                 [0x000000] The account DST09671\Maverick is chosen for migration, but the target does not have account DST10295\Maverick. See documentation on /lac, /lae, /ui, /ue and /uel options.[gle=0x00000006]
2014-06-25 10:42:39, Info                  [0x000000] Failed.[gle=0x00000006]
2014-06-25 10:42:39, Info                  [0x000000]   Unable to create a local account because /lac was not specified[gle=0x00000006]
2014-06-25 10:42:39, Info                  [0x000000] USMT Completed at 2014/06/25:10:42:39.728[gle=0x00000057]
2014-06-25 10:42:39, Info                  [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------
2014-06-25 10:42:39, Info                  [0x000000] * USMT error code 14:
2014-06-25 10:42:39, Info                  [0x000000] +-----------------------------------------------------------------------------------------
2014-06-25 10:42:39, Info                  [0x000000] | Unable to create a local account because /lac was not specified
2014-06-25 10:42:39, Info                  [0x000000] +-----------------------------------------------------------------------------------------

June 25th, 2014 5:22am

Don't pay too much attention to the error in the task sequence itself. As you can see in the loadstate.log, that's your real problem. Also, the error explains itself already.

Error 14 means USMT_ERROR_USE_LAC - Unable to create a local account because /lac was not specified.

It looks like you are migrating a local user without allowing USMT to create one, if it doesn't exist. So, do as mentioned in the error message and use /lac and retry.

Free Windows Admin Tool Kit Click here and download it now
June 25th, 2014 5:31am

Don't pay too much attention to the error in the task sequence itself. As you can see in the loadstate.log, that's your real problem. Also, the error explains itself already.

Error 14 means USMT_ERROR_USE_LAC - Unable to create a local account because /lac was not specified.

It looks like you are migrating a local user without allowing USMT to create one, if it doesn't exist. So, do as mentioned in the error message and use /lac and

June 25th, 2014 5:33am

That's a good question. I haven't tried it via the gui, yet, but I would think that checking the box Restore local computer user profiles in the Restore User and Files Settings step would be sufficient.
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2014 5:38am

I would like to NOT capture and restore local account and some other admin account. How about if I do this in my Client replace task sequence:

June 25th, 2014 5:44am

Should be possible, but the variable that you should be using then is OSDMigrateAdditionalCaptureOptions.
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2014 5:48am

Thank you Peter. I have changed the variable and will test.
June 25th, 2014 5:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics