locked
Litetouch deployment failed, Return Code = -2147467259 0x80004005 RRS feed

  • Question

  • I'm sure I have probably overlooked something simple here, but for the past few days when I create a new Windows 7 image, sysprep it, capture with imagex, then upload it into MDT I keep getting this error when I deploy it to a system. Here is the smstslog file if it helps. Appreciate any suggestions.

    Expand a string: WinPEandFullOS TSManager 1/23/2010 1:15:07 AM 1272 (0x04F8)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 1/23/2010 1:15:07 AM 1272 (0x04F8)
    Process completed with exit code 1 TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    !--------------------------------------------------------------------------------------------! TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Failed to run the action: Install Operating System. 
    Incorrect function. (Error: 00000001; Source: Windows) TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Sending status message . . . TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Set a global environment variable _SMSTSLastActionRetCode=1 TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Clear local default environment TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Let the parent group (Install) decides whether to continue execution TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Incorrect function. (Error: 00000001; Source: Windows) TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Sending status message . . . TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,762) TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    **************************************************************************** TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Task sequence execution failed with error code 80004005 TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Cleaning Up. Removing Authenticator TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    Cleaning up task sequence folder TSManager 1/23/2010 1:15:10 AM 1272 (0x04F8)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,513) TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,513) TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Command line for extension .exe is "%1" %* TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Set command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Executing command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    ==========[ TsProgressUI started in process 1636 ]========== TsProgressUI 1/23/2010 1:15:11 AM 1512 (0x05E8)
    Command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister TsProgressUI 1/23/2010 1:15:11 AM 1512 (0x05E8)
    Unregistering COM classes TsProgressUI 1/23/2010 1:15:11 AM 1512 (0x05E8)
    Unregistering class objects TsProgressUI 1/23/2010 1:15:11 AM 1512 (0x05E8)
    Shutdown complete. TsProgressUI 1/23/2010 1:15:11 AM 1512 (0x05E8)
    Process completed with exit code 0 TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Successfully unregistered TS Progress UI. TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,654) TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Sending error status message TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Finalizing logging from process 1260 TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Finalizing logs to root of first available drive TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Successfully finalized logs to C:\SMSTSLog TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)
    Cleaning up task sequencing logging configuration. TSManager 1/23/2010 1:15:11 AM 1272 (0x04F8)

    Friday, January 22, 2010 5:54 PM

Answers

  • I remember there were some goofy flags in Vista when capturing the image that were different than XP.  I haven't captured in win7 yet.  Could this possibly be part of the issue?  Just throwing that out there...something like imagex /capture /flags "enterprise" ... ...??
    • Marked as answer by Jay9x Thursday, February 11, 2010 7:14 PM
    Friday, February 5, 2010 10:49 PM

All replies

  • Try booting up with your Generic_X86/64 iso and applying the image file manually, it could be any number of things, if it works there the you'll know your partitions/image are fine so its something in the configs of your TS and how its set to apply the image file.



    -Dustin
    Friday, January 22, 2010 6:46 PM
  • Can you please post the contents of your LTIApply.log file?

    Quick question, did you import Windows 7 setup files with any of your imported Win7 OS images?

    -Brian
    Friday, January 22, 2010 6:51 PM
  • Yes, I have imported Win7 setup files from a Win7 Enterprise DVD. Also I have another Windows 7 image working perfect (I actually created this image from the working one when I made it, the only difference between them is a software package I added)

    Is there a place in the TS that references the Setup files from the Win7 Ent DVD I imported? Maybe if so I could just change that possibly? Also where do I find the LTIApply.log? Sorry I'm still rather new to some of this.

    Thanks, Jay


    Saturday, January 23, 2010 12:01 AM
  • c:\minint\smsosd\osdlogs si the default log directory, copy the logs out *before* you hit finish on the error window for the MDT.

    -D

    -Dustin
    Saturday, January 23, 2010 12:19 AM
  • okay I got it, here it is.

    Microsoft Deployment Toolkit version: 5.0.1641.0 LTIApply 1/23/2010 8:27:12 AM 0 (0x0000)
    The task sequencer log is located at X:\Windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. LTIApply 1/23/2010 8:27:12 AM 0 (0x0000)
    Open Control File: OperatingSystems LTIApply 1/23/2010 8:27:12 AM 0 (0x0000)
    ------  Applying Windows image using Setup.exe ------ LTIApply 1/23/2010 8:27:13 AM 0 (0x0000)
    LTI applying image \\SCOM\Deploy$\Operating Systems\S10EW7ELL\S10EW7ELL.WIM using SETUP.EXE LTIApply 1/23/2010 8:27:13 AM 0 (0x0000)
    ERROR - Unable to find SETUP, needed to install the image \\SCOM\Deploy$\Operating Systems\S10EW7ELL\S10EW7ELL.WIM LTIApply 1/23/2010 8:27:13 AM 0 (0x0000)
    ZTI ERROR - Non-zero return code by LTIApply, rc = 1 LTIApply 1/23/2010 8:27:13 AM 0 (0x0000)


    I even reimported Win 7 Enterprise setup files back into MDT and I still get this. Strange eh?

    Jay

    Saturday, January 23, 2010 12:38 AM
  • Ok, I placed the source files in the folder with the new image and I got this from the LTIapply.log now. Did a google search, but only thing I came up with for rc = 31 is some update in vista causing a bug, but nothing in Win 7.



    Microsoft Deployment Toolkit version: 5.0.1641.0 LTIApply 1/23/2010 9:15:29 AM 0 (0x0000)
    The task sequencer log is located at X:\Windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. LTIApply 1/23/2010 9:15:29 AM 0 (0x0000)
    Open Control File: OperatingSystems LTIApply 1/23/2010 9:15:29 AM 0 (0x0000)
    ------  Applying Windows image using Setup.exe ------ LTIApply 1/23/2010 9:15:29 AM 0 (0x0000)
    LTI applying image \\SCOM\Deploy$\Operating Systems\S10EW7ELL1\S10EW7ELL.WIM using SETUP.EXE LTIApply 1/23/2010 9:15:30 AM 0 (0x0000)
    Cleaning off old operating system LTIApply 1/23/2010 9:15:30 AM 0 (0x0000)
    Skipping C:\Drivers LTIApply 1/23/2010 9:15:30 AM 0 (0x0000)
    Skipping C:\MININT LTIApply 1/23/2010 9:15:30 AM 0 (0x0000)
    Skipping C:\_SMSTaskSequence LTIApply 1/23/2010 9:15:30 AM 0 (0x0000)
    Installing image from \\SCOM\Deploy$\Operating Systems\S10EW7ELL1\S10EW7ELL.WIM using command: "\\SCOM\Deploy$\Operating Systems\S10EW7ELL1\Sources\setup.exe" /noreboot /unattend:C:\MININT\unattend.xml /m:"\\SCOM\Deploy$\$OEM$" LTIApply 1/23/2010 9:15:30 AM 0 (0x0000)
    About to run command: "\\SCOM\Deploy$\Operating Systems\S10EW7ELL1\Sources\setup.exe" /noreboot /unattend:C:\MININT\unattend.xml /m:"\\SCOM\Deploy$\$OEM$" LTIApply 1/23/2010 9:15:30 AM 0 (0x0000)
    Return code from command = 31 LTIApply 1/23/2010 9:18:49 AM 0 (0x0000)
    Setup failed applying image \\SCOM\Deploy$\Operating Systems\S10EW7ELL1\S10EW7ELL.WIM, rc = 31 LTIApply 1/23/2010 9:18:49 AM 0 (0x0000)
    ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 1/23/2010 9:18:49 AM 0 (0x0000)

    Saturday, January 23, 2010 1:34 AM
  • Do you have any vars in your customsettings.ini setting the deployment type? like refresh/upgrade/newcomputer etc?   it looks like its running the wrong command for a sysprepped image 
    -Dustin
    Saturday, January 23, 2010 3:14 AM
  • It read as this;

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=Y
    SkipAppsOnUpgrade=YES
    SkipCapture=YES
    SkipAdminPassword=YES
    SkipProductKey=YES


    I haven't changed anything in it. The wierd thing is I can deploy Windows 7 fine to the same computers with an image I made a couple weeks ago. I used this same image to make the new image and it keeps kicking me out. I've recreated the image twice now, but still get the same error.


    Monday, January 25, 2010 2:55 PM
  • As a quick test, boot to your generic_pe and apply your new image manually, make sure to format your drive first with diskpart or it can cause issues. 
    This will verify your image is ok, and your command line is executing incorrectly (if it works, your command line is incorrect - image is fine)

    you may just need to re-import your image/set your deployment type. it see's your image as an unattended install instead of a sysprepped image.

    diskpart
    sel disk 0
    sel part 1
    format quick
    exit

    net use * \\servername\distribution$\captures /user:dom\user

    imagex /apply z:\imagefolder\imagename.wim 1 c:

    -Dustin
    Monday, January 25, 2010 3:27 PM
  • Hi Dustin,

    That appears to work ok. The image seems to be fine after I did that.


    So how do I set the deployment type. I've did the same for this image as any other I've created, can't figure out why it isn't set like the others.

    Jay

    Tuesday, January 26, 2010 3:04 PM
  • Try re-importing your image into the MDT first, its seeing it as a default windows install instead of a sysprepped one.

    also , add :

    DeploymentType=NEWCOMPUTER to your customsettings.ini [default] section

    -D

    -Dustin
    Tuesday, January 26, 2010 4:04 PM
  • Okay, I'm just completely baffled now. I've completely recreated a new image from scratch by installing a fresh copy of Win 7 Enterprise. Captured this image, inserted it into MDT and placed the line in the post above in my customsettings.ini. Still get exact same error. Not sure what I got going on. Never had this issue before..it's almost like something has gone wrong with my MDT server, but all my old images work fine, including other Win7 images I've previously created before this started happening.

    Jay

    Wednesday, January 27, 2010 7:51 PM
  • One thing I just thought about, not sure if it matters. When I capture the image, I am capturing it from d: because c: is labeled as BDEDrive, but it's empty. Would this affect how MDT applies the image to a computer?

    Jay

    Wednesday, January 27, 2010 8:21 PM
  • There is actually a var to disable the BDE DRive, i saw it earlier today in a post on here but can't find it again. May want to double check the .chm (help doc) or documentation and turn that off. 

    Your image applied fine manually so its not at fault from what i can tell :)

    Edit: found it -

     DoNotCreateExtraPartition = YES

    -D

    -Dustin
    Wednesday, January 27, 2010 9:04 PM
  • Strange I put that var in my customsettings.ini and it still creates the BDE Drive when I boot PXE to image the system. Almost like it isn't reading my customsettings.ini to pull the settings.


    Thursday, January 28, 2010 2:44 PM
  • Well I've found out it is reading my customsettings.ini because I could change other things and saw them being affected. (Took out Time Zone, Bit Locker, etc) I reimported my Windows 7 Enterprise source files into MDT. I'm getting a bit further but I error out with an error that says "windows could not display the images available for installation"

    then I click ok and it look at my logs and here's what they say.

    LTIApply.log

    Microsoft Deployment Toolkit version: 5.0.1641.0 LTIApply 1/28/2010 10:30:38 AM 0 (0x0000)
    The task sequencer log is located at X:\Windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. LTIApply 1/28/2010 10:30:38 AM 0 (0x0000)
    Open Control File: OperatingSystems LTIApply 1/28/2010 10:30:38 AM 0 (0x0000)
    ------  Applying Windows image using Setup.exe ------ LTIApply 1/28/2010 10:30:38 AM 0 (0x0000)
    LTI applying image \\SCOM\Deploy$\Operating Systems\ELLIS\S10EELLIS.WIM using SETUP.EXE LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    Found a matching SETUP in \\SCOM\Deploy$\Operating Systems\Win7 x86\Sources LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    Cleaning off old operating system LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    Skipping C:\Drivers LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    Skipping C:\MININT LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    Skipping C:\_SMSTaskSequence LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    Installing image from \\SCOM\Deploy$\Operating Systems\ELLIS\S10EELLIS.WIM using command: "\\SCOM\Deploy$\Operating Systems\Win7 x86\Sources\setup.exe" /noreboot /unattend:C:\MININT\unattend.xml /m:"\\SCOM\Deploy$\$OEM$" LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    About to run command: "\\SCOM\Deploy$\Operating Systems\Win7 x86\Sources\setup.exe" /noreboot /unattend:C:\MININT\unattend.xml /m:"\\SCOM\Deploy$\$OEM$" LTIApply 1/28/2010 10:30:39 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 6 minutes (process ID 1156) LTIApply 1/28/2010 10:36:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 12 minutes (process ID 1156) LTIApply 1/28/2010 10:42:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 18 minutes (process ID 1156) LTIApply 1/28/2010 10:48:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 24 minutes (process ID 1156) LTIApply 1/28/2010 10:54:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 30 minutes (process ID 1156) LTIApply 1/28/2010 11:00:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 36 minutes (process ID 1156) LTIApply 1/28/2010 11:06:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 42 minutes (process ID 1156) LTIApply 1/28/2010 11:12:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 48 minutes (process ID 1156) LTIApply 1/28/2010 11:18:00 AM 0 (0x0000)
    Return code from command = 31 LTIApply 1/28/2010 11:21:41 AM 0 (0x0000)
    Setup failed applying image \\SCOM\Deploy$\Operating Systems\ELLIS\S10EELLIS.WIM, rc = 31 LTIApply 1/28/2010 11:21:41 AM 0 (0x0000)
    ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 1/28/2010 11:21:41 AM 0 (0x0000)





    Thursday, January 28, 2010 7:45 PM
  • smsts.log 

    Set command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 1/28/2010 10:30:34 AM 548 (0x0224)
    Start executing the command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 1/28/2010 10:30:34 AM 548 (0x0224)
    !--------------------------------------------------------------------------------------------! TSManager 1/28/2010 10:30:34 AM 548 (0x0224)
    Expand a string: WinPEandFullOS TSManager 1/28/2010 10:30:34 AM 548 (0x0224)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 1/28/2010 10:30:34 AM 548 (0x0224)
    Process completed with exit code 31 TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    !--------------------------------------------------------------------------------------------! TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Failed to run the action: Install Operating System. 
    A device attached to the system is not functioning. (Error: 0000001F; Source: Windows) TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Sending status message . . . TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Set a global environment variable _SMSTSLastActionRetCode=31 TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Clear local default environment TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Let the parent group (Install) decides whether to continue execution TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    A device attached to the system is not functioning. (Error: 0000001F; Source: Windows) TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Sending status message . . . TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,762) TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    **************************************************************************** TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Task sequence execution failed with error code 80004005 TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Cleaning Up. Removing Authenticator TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    Cleaning up task sequence folder TSManager 1/28/2010 11:21:41 AM 548 (0x0224)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,513) TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Command line for extension .exe is "%1" %* TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Set command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Executing command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    ==========[ TsProgressUI started in process 1736 ]========== TsProgressUI 1/28/2010 11:21:42 AM 1224 (0x04C8)
    Command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister TsProgressUI 1/28/2010 11:21:42 AM 1224 (0x04C8)
    Unregistering COM classes TsProgressUI 1/28/2010 11:21:42 AM 1224 (0x04C8)
    Unregistering class objects TsProgressUI 1/28/2010 11:21:42 AM 1224 (0x04C8)
    Shutdown complete. TsProgressUI 1/28/2010 11:21:42 AM 1224 (0x04C8)
    Process completed with exit code 0 TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Successfully unregistered TS Progress UI. TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,654) TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Sending error status message TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Finalizing logging from process 480 TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Finalizing logs to root of first available drive TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Successfully finalized logs to C:\SMSTSLog TSManager 1/28/2010 11:21:42 AM 548 (0x0224)
    Cleaning up task sequencing logging configuration. TSManager 1/28/2010 11:21:42 AM 548 (0x0224)

    Thursday, January 28, 2010 7:45 PM
  • When you imported your image - which option did you select ? (Custom image / full set of source files / WDS Image?)

    This isn't the 'recommended way' to test this but, go to your distribution share \control\operatingsystems.xml

    find your image's entry, and change  <IncludesSetup>True</IncludesSetup>  to false, save, and test again

    -D
    -Dustin
    Thursday, January 28, 2010 8:41 PM
  • When I reimported the image I am having issues with I selected "custom image". When I reimported Windows 7 Enterprise source files I selected "full set of surce files".

    I checked that xml file and it already has <IncludesSetup>False</IncludesSetup> instead of true.  My working images also have this same settings. I captured the image file with the following command.

    imagex /capture d: h:\imagename.wim "imagename"

    I found this post, and tried it but I didn't have a pid.txt in my boot image, but it sounds exactly like the problem I'm having.




    Jay
    • Proposed as answer by Joe The Tim Tuesday, December 20, 2011 12:03 PM
    Thursday, January 28, 2010 9:15 PM
  • yea i'm trying to pinpoint why its running setup.exe instead of imagex.exe /apply , it doesnt make sense ><
    -Dustin
    Thursday, January 28, 2010 10:08 PM
  • Yeah, this is the craziest problem by far I've ever had. I made another image using the same CD I used to make the working image I have now without even modifying it, so essentially it's the same exact copy. I captured it from drive c: just like the working one. Then imported it into MDT and setup a TS, and same errors. Says it's looking for Setup.exe and it's a custom image. Seems like something isn't talking with MDT to tell it it's not an install image. At this point I'm kinda lost, if you happen to think of anything else I appreciate the advise. Thanks so much for all the suggestions so far Dustin, it has been much much appreciated. :)

    Jay

    Monday, February 1, 2010 8:59 PM
  • I remember there were some goofy flags in Vista when capturing the image that were different than XP.  I haven't captured in win7 yet.  Could this possibly be part of the issue?  Just throwing that out there...something like imagex /capture /flags "enterprise" ... ...??
    • Marked as answer by Jay9x Thursday, February 11, 2010 7:14 PM
    Friday, February 5, 2010 10:49 PM
  • Hmm..I'll give that a try. Thanks
    Saturday, February 6, 2010 1:14 AM
  • Has anyone found an answer to this problem???
    Thursday, February 11, 2010 3:02 PM
  • I finally captured using the following command and it is working now. Still not sure why it's sensitive to this now when before I never had to do it. But I don't really care, it's working now. :)  I used the command below when capturing with imagex. It still runs the setup instead of applying the image directly, but it does work and installs the image just as I had it

    imagex /flags Enterprise /capture c: h:\imagename.wim "imagename"

    H is a network drive I mapped to so I could store the image.

    Thanks for that suggestions Sqwidd, much appreciated.

    Jay

    Thursday, February 11, 2010 7:14 PM
  • I think the issue has to to with the Build. The original os build number is different from the captured os build number and I can't seem to find how to recify this. Any Suggestion?
    Tuesday, March 16, 2010 8:11 PM
  • Did you try the /flags command with your Win 7 version? That fixed it for me. I know sometimes if I reimported the original install.wim file from the Win 7 dvd, that it would make it work again as well. Not sure why that ever had anything to do with it, but sometimes when I upload a new image to MDT it will not work, so I'll delete the current install.wim file I have in MDT and redo it and it seems to almost work everytime.

    Jay

    Tuesday, March 16, 2010 9:49 PM
  • From the LTIApply.wsf:

       Elseif Left(sOSBuild, 1) < "6" then

        iRetVal = ApplyImage

       Else

        iRetVal = ApplySetup

       End if

     '//  Function: ApplyImage()
     '//
     '//  Input: None
     '//
     '//  Return: Success - 0
     '//  Failure - non-zero
     '//
     '//  Purpose: Apply the specified Windows XP image to the machine.  (We
     '//             always use Setup to install Vista images.)

    It looks like you always need setup files for Vista and Win7 custom images.

     

     From MDT2010 documentation:

    If you attempt to import a custom image that does not have an Edition ID, the wizard fails with an error similar to the following:

    Setup failed applying image F:\Deploy\Operating Systems\W2K8R2RTM\W2K8R2RTM.wim, rc = 31

    ZTI ERROR – Non-zero return code by LTIApply, rc = 31.

    To resolve this issue, add an Edition ID to the image by running the following command (where edition_id is the appropriate SKU ID as defined in the original factory image or in the Windows AIK, wim_file is the name of the WIM file, new_image_name is the new image name, and new_image_description is the new description for the image):

    imagex /flags <edition_id> /info <wim_file> 1 <new_image_name> <new_image_description>

    Friday, March 19, 2010 2:16 PM
  • Hello Serge

    what .wim file do you mean I have to add the flag to I am using MDT 2010 update 1 and I only have LiteTouchPE_x64.wim, is it that i have to add it to
    could you please tell me more excact how to

    Sorry for being that stupid.
    regards jan sejer 


    Jan Sejer
    • Proposed as answer by Mike Lambourne Wednesday, November 28, 2012 11:31 AM
    • Unproposed as answer by Mike Lambourne Wednesday, November 28, 2012 11:31 AM
    Friday, March 25, 2011 10:39 AM
  • Sorry - haven't got the hang of forums....

    I just thought I'd add my tuppence worth - had the same error, it turned out that the images local admin account was disabled. That's the only thing I changed....it may help someone.....

    Wednesday, November 28, 2012 11:41 AM
  • I having a very similar issues. I created my MDT share with a custom patched WIM. I deployed this OS to a workstation for further patching, captured and all went well. I imported the OS into my deployment share, changed the OS used for my TS and BOOM. I get a SLEW of error messages 8 total. When I change the image back to the first custom one it works every time.

    When you captured the image manually using Imagex and then imported it it worked and you were able to setup a TS to deploy?

    Thanks,

    Alex

    Friday, December 6, 2013 4:54 PM
  • I had kind of the same problem, I'd captured an image and wanted to deploy it to another system. When the process was almost finished I got the same error codes. Later that day I remembered that I had not checked the bios settings of the new pc.

    Solution in my case:

    - Changing the SATA mode in BIOS to: IDE, because the original image was captured using this setting in the bios.

    I hope this helps for some of you guys,

    Regards,

    Daemien

    Thursday, January 23, 2014 1:53 PM
  • I had the same problem after uploading the image file twice but noticed the size of the .wim file was a lot smaller than expected.

    I booted the machine which was captured and retrieved the .wim file from it and uploaded it to the WDS server and imported it that way.

    This worked fine after that, hope this helps

    Friday, February 7, 2014 9:27 AM