none
MDT 2013 v8456 Image capture failed RRS feed

  • Question

  • Hello MDT Guru,

    I have just upgraded my MDT 2013 to version 8456 and when trying to capture the reference image, the sysprep failed with an error. "can't find litetouch.vbs" script.

    I seems like the sysprep process somehow strip off the driver of the NIC.  When I look at the NIC, it has the big RED X.

    My environment.

    Dell Optiplex 5050.

    MDT version 8456,

    ADK 1809

    WinPE 1809.

    I build an image from windows 10 1803, and upgrade it to 1809.  The computer was fully patches.

    I can still deploy Win 10 1803 with no problem.

    Thanks for your help.

    Tuesday, February 26, 2019 4:32 PM

Answers

  • No one knows how to resolve this issue?
    • Marked as answer by Brichardi Wednesday, February 27, 2019 3:55 PM
    Wednesday, February 27, 2019 2:46 PM
  • When making an image on a physical machine I would make sure to directly inject the boot critical drivers using pnputil or dpinst. If it still strips out the driver you may need to add the following under the generalize section of your unattended.xml file

            <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>

    But that will preserve all devices installed.

    • Marked as answer by Brichardi Tuesday, March 12, 2019 2:09 PM
    Wednesday, February 27, 2019 4:53 PM

All replies

  • No one knows how to resolve this issue?
    • Marked as answer by Brichardi Wednesday, February 27, 2019 3:55 PM
    Wednesday, February 27, 2019 2:46 PM
  • So you're trying to build and capture your OS from a physical machine? You should do this in a VM so as not to junk up your image with anything hardware specific in it. 

    It also works more smoothly if you have a deployment share specifically built for creating and capturing images. You can create a single task sequence that will make the image as well as capture it. By using a VM you can add a "pause" to your task sequence to give yourself a chance to make a checkpoint.

    I'd recommend buying the Deployment Fundamentals Volume 6 book which has detailed step by step instructions.


    Daniel Vega

    Wednesday, February 27, 2019 3:28 PM
  • Thanks for reply to my question, but your suggestion does not help resolve my issue.


     
    Wednesday, February 27, 2019 3:55 PM
  • When making an image on a physical machine I would make sure to directly inject the boot critical drivers using pnputil or dpinst. If it still strips out the driver you may need to add the following under the generalize section of your unattended.xml file

            <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>

    But that will preserve all devices installed.

    • Marked as answer by Brichardi Tuesday, March 12, 2019 2:09 PM
    Wednesday, February 27, 2019 4:53 PM
  • MDT 8456 is doing something with the NIC when a capture occurs. Using a capture sequence I keep getting No physical adapters present cannot deploy over wireless. When I check for the NIC its been removed from the image and the capture process fails.

    I am using a Hyper-V virtual machine and attempting to syspre and capture a 2008 r2 Standard image.

    I have had success capturing an 1809 VM the same way.

    Still researching this but I have never seen a capture sequence fail this way.

    Tuesday, March 5, 2019 3:19 AM