Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
USMT hardlink migration fails on refresh scenario - XP SP3 x86 to Windows 7 x64

Unanswered USMT hardlink migration fails on refresh scenario - XP SP3 x86 to Windows 7 x64

  • Thursday, September 27, 2012 2:39 PM
     
     
    Sign In to Vote
    0

    Good afternoon,

                             I have set up an MDT 2012 server and have captured an image of Windows 7 Enterprise x64, in my customsettings.ini I have SkipUserData=NO and I select the USMT to use the local machine storeage.

    I run the script ltiapply.vbs from the deployment share and the USMT runs creates the directories and logs, when the image is then applied to the machine and it automatically logs on as the local administrator the USMT runs and the following error message is presented.

    During the deployment process, 9 errors and 1 warnings were reported.X

    _______________________________________________________________________________________________________________________________

    ZTI ERROR - Non-Zero return code from Loadstate, RC = 71

    Moving state store directory c:\statestore to %WINDIR%\StateStore so that it does not get deleted.

    ZTI ERROR - Non-zero return code by ZTIUserState, rc = 71

    Litetouch deployment failed, Return Code = -2147467259 0x80004005

    Failed to run the action: Restore User State.

    No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. (Error: 00000047; source: Windows)

    The execution of the group (state restore) has failed and the execution has been aborted. An action failed.

    Operation aborted (Error: 80004004; source: Windows)

    Failed to run the last action: Restore User State. Execution of task sequence failed.

    No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. (Error: 00000047; source: Windows)

    Task Sequence Engine Failed! Code: enExecutionFail

    Task sequence execution failed with error code 80004005

    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

    ______________________________________________________________________________________________________________________________

    Once the message appears the c:\userstate is deleted and c:\windows\StateStore is not created (and I have unchecked hidden folders and hide OS files).

    The c:\MININT\SMSOSD is also deleted so I have no logs. I have the smsts.log

    The machine has joined the domain OK and everything else is fine just the USMT fails :(

    Has anyone encountered this issue before? Any assistance would be appreciated.

    Thanks,

    Ryan

     

All Replies

  • Thursday, September 27, 2012 7:35 PM
     
     
    Sign In to Vote
    1
    Did you check c:\windows\temp\Deployment logs for the logs? They shouldn't just disappear
     
  • Friday, September 28, 2012 12:16 PM
     
     
    Sign In to Vote
    0

    Hi JoeZeppy,

                        I'll call you Zeppy if that's OK, I have found the logs and the USMT files in that location. From the USMT restore log I get

    2012-09-27 14:51:17, Error                 There was an error while calling CreateProfile. Error: 0x800700B7

    2012-09-27 14:51:17, Info                  [0x0803e5] Not unmapping HKCU; it is not mapped
    2012-09-27 14:51:17, Error                 [0x000000] Error 0 creating profile for user <mydomain>\<myusername> (source user <mydomain>\<myusername>)
    2012-09-27 14:51:17, Info                  [0x000000] Failed.[gle=0x00000006]
    2012-09-27 14:51:17, Info                  [0x000000]   A Windows Win32 API error occurred                                                            


    • Edited by Ryan Conlon Friday, September 28, 2012 12:29 PM
    •  
     
  • Friday, September 28, 2012 12:30 PM
     
     
    Sign In to Vote
    1

    Did not read from start, however with the error you just pasted - looks like ProfileList issue.

    Can you compare the list of folders/profiles in Documents and settings and compare it with the list in the registry? Under HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

    By default there should be systemprofile, localservice and networkservice + Local Admin and other user profiles - who ever logged in.

    Check this as well - http://blogs.technet.com/b/deploymentguys/archive/2010/03/28/usmt-failures-due-to-bad-profile-list-entries.aspx

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"


    • Edited by Vik Singh Friday, September 28, 2012 12:30 PM typo
    •  
     
  • Friday, September 28, 2012 12:52 PM
     
     
    Sign In to Vote
    0

    Hi there Vik,

                       Thanks for the input, I have found this resource online http://blogs.technet.com/b/configurationmgr/archive/2012/01/12/fix-configmgr-2007-osd-deployments-fail-with-error-0x800700b7-in-loadstate-log.aspx

    Looks like as I was the one logged on when I created my reference image (and the profile is still there) this causes an issue when USMT is running.

    I will re-do my base image and re-test.

    Thanks for the input peeps!