none
capture fail Code = 2147467259

    Question

  • MDT 2013 in place. Used for deployment of Windows 7 Entr only, for multiple models.

    Capture is used 3-4 times per year. Using VM.

    I got a urgent request for capturing a physical laptop. W7 OS is installed from Volume license. Few tweaks applied.

    When capture get the error (see screamshot). Checked web - tons of posts for the error. 99% during deployment.

    Found one about capture of Server 2012. And the guy resolved the error found in logs.

    In my case the log is clean. May be I have to check something else?

    To be sure of the server part I just captured clean VM. Works fine.

    Any suggestion please.

     


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Tuesday, May 15, 2018 7:19 PM

All replies

  • Did you check all potential log locations? It might have been moved to the C:\WINDOWS\Temp\DeploymentLogs folder? Based on the summary, the error seems to be occuring during the Apply Windows PE stage and the root cause appears to be (my French is a bit rusty) an incorrect argument. So yeah, locating the log file is crucial to narrow your issue down...

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Tuesday, May 15, 2018 9:17 PM
  • Hi Anton,

    here is a Depl Log files from the path you advised...

    https://1drv.ms/f/s!Av7GxVRWTkZlgUuhYNi4KoTcww0c

    I checked the bdd and see: For more information consult the task sequencer log ... \\SMSTS.LOG

    Unfortunately, I don't have it in my Depl log folder...

    May be other logs will help you to help me :)

    Thanks!


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Wednesday, May 16, 2018 1:13 PM
  • digged in a bit more and found smsts.lob in %userprofile% appdata local temp

    so I uploaded it to other logs...

    now will take a look, may be will find something before your input...

    Thx.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis



    • Edited by pob579 Wednesday, May 16, 2018 2:15 PM
    Wednesday, May 16, 2018 1:56 PM
  • After quickly going through the log files and the corresponding script files, I can't identify the underlying issue:

    The LTIApply script is able to identify your boot drive via this code block:

    Else 
    				oLogging.CreateEntry "Boot Drive not found, attempting recovery option (Win8+Sysprep scenario)...", LogTypeInfo
    
    				aDiskArray = Empty
    				on error resume next
    				aDiskArray = oUtility.BDDUtility.HiddenPartitionsToDrives
    				on error goto 0 
    
    				For each sCmd in aDiskArray
    					If ubound(split(sCmd,vbTab)) >= 7 then
    						If trim(split(sCmd,vbTab)(3)) = "1" then
    							oLogging.CreateEntry "Found Recovery option: " & sCmd, LogTypeInfo
    							sBootDrive = left(split(sCmd,vbTab)(7),2)
    							Exit for
    						End if
    					End if
    				Next
    
    				TestAndFail not isEmpty(sBootDrive), 5609, "Boot Drive was not found."
    			End if 


    The next bit is where MDT will query your Boot folder and try to identify which LitetouchPE.wim file it should use:

    ' Determine which architecture of PE we should install
    
    sDir = oEnvironment.Item("DeployRoot") & "\Boot\LiteTouchPE_" & sArchitecture & ".wim"
    TestAndFail oFSO.FileExists( sDir ), 5610, "Verify File: " & sDir 

    Assuming the corresponding LiteTouchPE_X64.wim is present in the Boot folder, I would need to do some more digging.

    I would also recommend upgrading MDT 2013 (6.2.5019.0) to a never release (Update 2 at the very least).


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Wednesday, May 16, 2018 2:20 PM
  • if upgrade is straightforward I can do it... but I prefer to make it after solving the issue.

    Please provide the link to upgrade instructions.

    For now I see that the very first error in smsts.log is related to Language.

    Don't know where... In boot image or on local pc.

    tsres.dll for locale 1036....   1036 is French-France.

    Yes, I deploy French OS. We are using French Canada (that has subsets).

    But the capture works for VM. Can I make a conclusion that the problem is in given PC ?

    Just in case I will do one more capture of VM to prove that no probs with boot image.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Wednesday, May 16, 2018 5:38 PM
  • Well, I am assuming your VMs are BIOS-based and you are trying to capture a system running a GPT (UEFI) partition layout as evident in your BDD.log:

    Property IsUEFI is now = True

    If memory serves me right, UEFI support in MDT 2013 was somewhat limited. We could take a look at your LTIApply.wsf script (I do not have an MDT 2013 installation here, so I have nothing to compare latest LTIApply script to, but I do believe that this script changed over the years), but from my point of view, the most evident way would be to upgrade to at least MDT 2013 Update 2, or, even better, straight to MDT 8450.

    Johan Arwidmark wrote a nice step by step guide, which you could follow.

    So yeah, these are the only two options I can think of...


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Wednesday, May 16, 2018 8:15 PM
  • Thanks Anton!

    Will take a closer look to the upgrade...


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thursday, May 17, 2018 11:03 AM
  • Anton,

    please take a look at LTIAplly...

    may be we can solve the problem before I will go to upgrade option...

    https://1drv.ms/f/s!Av7GxVRWTkZlgVjNFGl75eciDvOi

    Thx.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thursday, May 17, 2018 11:50 AM
  • I went through the code, but unfortunately, there isn't anything that jumps out. Then again, there are many moving parts involved - LTIApply makes calls into four different scripts: ZTIBCDUtility.vbs, ZTIConfigFile.vbs, ZTIDiskUtility.vbs and most importantly ZTIUtility.vbs. If I were in your shoes, I would make a backup of your current deployment share, perform a test upgrade and try again. If it still does not work, you can always go back to your original setup and if it does, then you can get on with your day...

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, May 17, 2018 8:27 PM
  • instead of upgrading configured MDT 2013 that serves W7 deployment (don't actually need W10) and have a chance to break what is work,

    I am going to install new 2016 server with 8450. Finally, I need to capture W7 physical machine.

    So, clean installation will show if my current server has an issue with capturing THIS physical machine. 

    The good point is that I don't need any selection profiles. The machine has all drivers and etc.

    Will let know. Hope that 8450 supports W7.

    Anton, I understand that errors in smsts.log not pointed you to the right direction, you suspect that there are outdated scripts that may cause the prob. Correct?

    Let me see 8450 live.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Friday, May 18, 2018 1:41 PM