locked
Help, My Capture Image Task Sequence Keeps Failing to Sysprep RRS feed

  • Question

  • I am using MDT to capture an image from a Windows 10 version 1903 Hyper-V vm and once I run litetouch.vbs from within the VM and it reboots, it fails with the errors in the attached screenshot ("Failed to run the action: Execute Sysprep").  I have tried creating a fresh VM and running the task sequence again but it still fails with the same error.  I have also tried creating a new capture image task sequence and it still fails.  I am running MDT version 6.3.8456 and I have updated my deployment share

    Deployment failure: ZTI ERROR - Unhandled error returned by LTISysprepAny help or advice would be appreciated.


    Johnnie Davis, Technology Specialist

    Monday, September 23, 2019 2:13 PM

Answers

  • So, after contacting Microsoft about this issue I found out there was a newer ISO available in the Microsoft VLSC site that was just updated in September.  I downloaded that ISO and setup a new reference image from it and the sysprep worked using that version.  Note: I found that in this version some of the usual apps added to the base image would prevent the image from sysprepping (Adobe Reader DC was one of those apps).  

    VLSC New Windows 10 1903 ISO


    Johnnie Davis, Technology Specialist


    • Edited by JohnnyKool Monday, October 7, 2019 1:36 PM
    • Marked as answer by JohnnyKool Monday, October 7, 2019 1:36 PM
    Monday, October 7, 2019 1:33 PM

All replies

  •  Check bdd.log as well C:\Windows\System32\Sysprep\Logs for more info, where does it failing.

    Tuesday, September 24, 2019 12:29 PM
  • Actually when I log back in to the VM, I get the message that Windows can not find script file "C:\MININT\Scripts\LiteTouch.wsf."  And in the Sysprep folder, the Logs folder is not present.

    Johnnie Davis, Technology Specialist

    Tuesday, September 24, 2019 12:41 PM

  • Johnnie Davis, Technology Specialist

    Tuesday, September 24, 2019 12:42 PM
  • In the Properties of your Sysprep/Capture TS, in the Task Sequence tab, just to test, disable the Mass Storage step and then try your process again.
    Tuesday, September 24, 2019 1:06 PM
  • In the Properties of your Sysprep/Capture TS, in the Task Sequence tab, just to test, disable the Mass Storage step and then try your process again.
    I tried that but that didn't work.  It still fails to execute the Sysprep step.

    Johnnie Davis, Technology Specialist

    Tuesday, September 24, 2019 6:03 PM
  • So I applied the workaround suggested in the article below, but Sysprep still fails in my capture image task sequence.  I also notice that the Unattend file shows Windows Professional Edition in the Product property.  Shouldn't it show Windows Enterprise?

    https://social.technet.microsoft.com/Forums/en-US/df7f8b10-da83-48cd-8eb6-607e37568bf0/windows-10-1903-sim-tool-in-adk-101183621-fails-to-generate-catalogs-correctly-for-x64?forum=win10itprosetup


    Johnnie Davis, Technology Specialist

    Wednesday, October 2, 2019 3:08 PM
  • So, after contacting Microsoft about this issue I found out there was a newer ISO available in the Microsoft VLSC site that was just updated in September.  I downloaded that ISO and setup a new reference image from it and the sysprep worked using that version.  Note: I found that in this version some of the usual apps added to the base image would prevent the image from sysprepping (Adobe Reader DC was one of those apps).  

    VLSC New Windows 10 1903 ISO


    Johnnie Davis, Technology Specialist


    • Edited by JohnnyKool Monday, October 7, 2019 1:36 PM
    • Marked as answer by JohnnyKool Monday, October 7, 2019 1:36 PM
    Monday, October 7, 2019 1:33 PM