none
MDT Error - Cannot deploy image RRS feed

  • Question

  • Hello, MDT Experts

    May I ask your help on how to fix this MDT error after completing ScanState part. I am going to upgrade Windows 10 enterprise client to Windows 10 LTSB by deploying a complete Windows 10 image.

    Expectation is that it should restart and apply Windows 10 image after backing up user data and settings.

    By the way, this is an isolated case, other deployments are okay.

    Error:

    ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument

    Below is a part of BDD logs.

    TargetOS is the current SystemDrive LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    Get the Boot Drive. LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    The current autorun setting is - 145 LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    Disabling Autorun LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    Find the boot drive (if any) [True] [10.0.14393.2999] [False] LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    New ZTIDisk : \\Client\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    DISKPART + Select Disk 0 LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    DISKPART + Select Partition 1 LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    DISKPART + Assign LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    DISKPART + Exit LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
    About to run command: cscript.exe //nologo "\\​Server\MDTShare$\Scripts\ztiRunCommandHidden.wsf" "DiskPart.exe /s C:\Users\MADORA~1\AppData\Local\Temp\rad1A944.tmp" LTIApply 6/19/2019 6:26:36 PM 0 (0x0000)
    About to run command: DiskPart.exe /s C:\Users\MADORA~1\AppData\Local\Temp\rad1A944.tmp ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
    Command has been started (process ID 8476) ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
    ZTI Heartbeat: command has been running for 0 minutes (process ID 8476) ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
      Console > Microsoft DiskPart version 6.1.7601 ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
      Console > Copyright (C) 1999-2008 Microsoft Corporation. ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
      Console > On computer: DRICH7-TP ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
      Console > Disk 0 is now the selected disk. ztiRunCommandHidden 6/19/2019 6:26:50 PM 0 (0x0000)
      Console > Partition 1 is now the selected partition. ztiRunCommandHidden 6/19/2019 6:26:50 PM 0 (0x0000)
      Console > There is no volume specified. ztiRunCommandHidden 6/19/2019 6:26:55 PM 0 (0x0000)
      Console > Please select a volume and try again. ztiRunCommandHidden 6/19/2019 6:26:55 PM 0 (0x0000)
    Return code from command = -2147024809 ztiRunCommandHidden 6/19/2019 6:26:55 PM 0 (0x0000)
    Command has returned: -2147024809 LTIApply 6/19/2019 6:26:55 PM 0 (0x0000)
    No boot drives found. None. LTIApply 6/19/2019 6:28:00 PM 0 (0x0000)
    Reverting autorun setting to - 145 LTIApply 6/19/2019 6:28:00 PM 0 (00000)
    Boot Drive not found, attempting recovery option (Win8+Sysprep scenario)... LTIApply 6/19/2019 6:28:00 PM 0 (0x0000)
    Found Recovery option: MBR 0 1 1 17 304    304 LTIApply 6/19/2019 6:28:02 PM 0 (0x0000)
    ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5) LTIApply 6/19/2019 6:28:02 PM 0 (0x0000)

    Any help on this will be much appreciated. Thank you in advance.

    Cheers,

    Michael

    Monday, July 1, 2019 8:31 AM

All replies

  • Well the error is:

    There is no volume specified.
    Please select a volume and try again.

    If this is an isolated case, then I would ask if this computer has multiple drives. I don't know what your dispart script does so it's hard to guess beyond Disk 0 missing what it was expecting.


    Daniel Vega

    Monday, July 1, 2019 4:06 PM
  • Hello, Daniel

    Thank you for the quick response. Appreciated.

    Here is the disk management of the computer.

    Let me know any additional information you need that will resolve this issue.

    Thanks!

    Cheers,

    Michael

    Tuesday, July 2, 2019 12:49 AM
  • I was reading through it more carefully and think I pin pointed the issue. It's using Diskpart 6.1 then later is says "Boot Drive not found, attempting recovery option (Win8+Sysprep scenario)". It's also hard to tell what's really going on with out the full bdd.log

    If you are trying to backup data and then wipe the system to lay down a clean Windows 10 image, you'll need to do this as a 2 step process. You can create a task sequence that will use USMT to backup all the user data and settings. Then you can run a "new computer" scenario where the disk is wiped. Just make sure MDT isn't set to skip USERDATA and that your backup location is set correctly.

    Make sure your deployment server is running up to date versions of MDT and the ADK.

    I would recommend first testing on a computer where the data isn't critical. You don't want to accidentally lose irreplaceable data.


    Daniel Vega

    Tuesday, July 2, 2019 1:43 PM
  • Hello, Daneil

    Apology for late response. I really appreciate your help on this.

    I cannot post the whole BDD.log file as it's too large, this forum won't allow to upload.

    Hopefully, we can find out the reason why the target computer wont' continue to restart after backup of user data and settings. Expectation is it will restart to apply Windows PE and do the rest of Refresh process using a Windows 10 custom image to upgrade from Windows 7 to Win10.

    I noticed that the error only happens here (ztiRunCommandHidden.log)

    What is exactly the ztiRUnCommandHidden.wsf doing in the system in order to proceed?

    Is there anything in the client that would possibly prevent this process to continue?

    I really need to see what is causing to fail in this particular target computer. Others are successful with same SSD hard drives, OS and HDD partitioning.

    Sunday, July 7, 2019 1:45 AM
  • Put the log on OneDrive or any file sharing site of your choice and post the link to the log.

    Daniel Vega

    Monday, July 8, 2019 1:25 PM
  • Hello, Daniel

    Please find below link for the full BDD logs.

    Full BDD Log File

    Thank you.

    Cheers,

    Michael

    Tuesday, July 9, 2019 11:42 PM
  • I'm not entirely familiar with what you're doing as I've never used MDT without formatting, but your boot partition looks like it's partition 2, whereas your task is looking at partition 1 (Disks start at 0, but Partitions start at 1).
    Wednesday, July 10, 2019 12:00 AM
  • Hello, Benweston

    This is an UPGRADE scenario from Windows 7 to Windows 10. We do not format the hard drive as it is encrypted and we do not want to do encryption again as it takes very long time to complete. 

    This works in other laptops with same SSD and formatting/partitioning style.

    What I really want to know is what is in this particular laptop wherein it stops at applying Windows PE.

    I am expecting it to reboot to start deploying image.

    Although I can use PXE boot as option 2 to accomplish upgrade but my situation is that I should do it remotely. Clients are in different places and I just do remote upgrade.

    Task sequence is doing the following:

    1. Backup user's data and settings.

    2. Suspend encrypted drive.

    3. Deploy Windows 10 enterprise LTSB 2016 custom image.

    4. Restore user's data and settings.

    Bootstrap:

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=Y
    DeployRoot=\\MDTServer\MDTShare$

    SkipBDDWelcome=YES

    UserID=MDTUserAccount
    UserPassword=
    UserDomain=Domain

    CustomSettings.Ini

    [Settings]
    Priority=DeploymentType,Default
    Properties=MyCustomProperty

    [NEWCOMPUTER]
    DoNotFormatAndPartition=NO

    JoinDomain=xx.xx.xx.com
    DomainAdmin=xx
    DomainAdminPassword=
    DomainAdminDomain=xx

    [REFRESH]
    DoNotFormatAndPartition=YES

    [Default]
    DeployRoot=\\MDTSERVER\MDTShare$

    UserID=xx
    UserPassword=
    UserDomain=xx

    SLShare=\\LOGSSERVER\Logs$
    SLShareDynamicLogging=\\LOGSSERVER\Logs$

    SkipBDDWelcome=YES
    SkipWizard=NO
    SkipTaskSequence=NO

    SkipDomainMembership=NO

    SkipComputerBackup=YES
    SkipCapture=NO
    DoCapture=NO

    SkipUserData=NO
    UserDataLocation=%UDShare%\%UDDir%
    UDShare=\\MIGSERVER\MigData$
    UDDir=%OSDComputerName%
    USMTMigFiles001=MigApp.xml
    USMTMigFiles002=MigDocs.xml
    USMTMigFiles003=MigCustom.xml
    ScanStateArgs=/v:5 /o /c /vsc /all
    LoadStateArgs=/v:5 /c /all /lac /lae
    UserExit=UserExit.vbs
    OSDComputername=#GetOfflineComputername()#

    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipBitLocker=YES

    SkipTimeZone=YES
    TimeZoneName=XX

    SkipLocaleSelection=YES
    UserLocale=en-us
    KeyboardLocale=en-us
    UILanguage=en-us

    DoNotCreateExtraPartition=YES

    SkipSummary=NO
    SkipFinalSummary=NO

    EventService=http://MDTSERVER:9800

    HideShell=YES
    FinishAction=REBOOT

    Wednesday, July 10, 2019 12:36 AM
  • If you're doing an upgrade, make a new task sequence and use the Standard Client Upgrade Task Sequence template. Do not using any custom disk part scripts, it's an upgrade you shouldn't be doing anything to the disk. Also, for upgrades, do not boot to the MDT boot media. You need to run litetouch from within an active Windows installation so that it can properly upgrade the computer to the new OS.

    In your CustomSettings.ini you do not need to specify the formatting settings for New and Refresh, just use the Standard Client Task sequence template. If you boot to the MDT boot image, it will automatically use "NEW COMPUTER" and wipe/partition the disk as needed. If you run litetouch from within Windows, then it will automatically run a "REFRESH" scenario. 


    Daniel Vega

    Wednesday, July 10, 2019 1:25 PM
  • Ok, its intriguing that it's working on other laptops with exactly the same partition structure.

    As I say I'm not familiar with tasks that don't format, so I'm not sure exactly what the Diskpart is *supposed* to be doing in your sequence when it's not formatting and partitioning, but it seems like its looking for where the boot partition is. For whatever reason, on this laptop, it looks like its giving up having only looked at Partition 1, and either never looks at Partition 2 or can't see it.

    Have you compared the log file from a successful laptop at exactly the same point? It might yield clues.

    Wednesday, July 10, 2019 1:34 PM
  • Yes I did compare but still I cannot figure out. Anyway, I will just proceed to option 2, PXE boot.

    Thanks!

     
    Friday, July 12, 2019 1:03 PM
  • Ok but this CustomSettings.Ini suits my requirements. I'm just curious for a few laptop with this issue.

    What is in the client that is causing it to fail. Anyway, it seems I have no choice for now but to do the

    refresh via PXE. 

    Thanks for the help.

    Cheers,

    Michael


     
    Friday, July 12, 2019 1:12 PM
  • Hi, Michael!

    I have the same issue like you. Have you found a solution?


    Emil Valiev


    • Edited by Emil Valiev Monday, September 7, 2020 1:43 PM
    Monday, September 7, 2020 1:43 PM