none
Reference Image fails - False: Verify File: LiteTouchPE_x64.iso RRS feed

  • Question

  • Hello everybody,

    I'm trying to create a Reference image for some Surface Laptop 2s.  I'm getting an error that I've haven't had before on other platforms.    Basically, consistently, in BDD.log, I see a line stating:  FAILURE (5610): False: Verify File: \\xxxxxx$\Boot\LiteTouchPE_x64wim.  This comes right after " Setting Boot drive to D "

    When the laptop loads after failing, in File Explorer,  I have a C: drive labeled "Windows",  and a D: drive labeled (Boot).  I'm wondering if this might be the problem.  

    Can anybody chime-in and help me understand this issue?

    Many thanks,

    Adrian

    excerpt from BDD.log

    <![LOG[  Console > Microsoft DiskPart version 10.0.18362.1]LOG]!><time="14:21:52.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[  Console > Copyright (C) Microsoft Corporation.]LOG]!><time="14:21:52.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[  Console > On computer: OCA-77T158KJMAV]LOG]!><time="14:21:52.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[  Console > Disk 0 is now the selected disk.]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[  Console > Partition 1 is now the selected partition.]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[  Console > DiskPart successfully assigned the drive letter or mount point.]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[  Console > Leaving DiskPart...]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[Return code from command = 0]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[Command has returned: 0]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDiskPartition : \\OCA-77T158KJMAV\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\OCA-77T158KJMAV\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Found bootable drive (No Boot File Test) [ D: ]: \\OCA-77T158KJMAV\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Reverting autorun setting to - 145]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Setting Boot drive to: D:]LOG]!><time="14:21:53.000+000" date="07-15-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5610 ): False: Verify File: \\OCA-WDS-PXE\Deploymentshare$\Boot\LiteTouchPE_x64.wim]LOG]!><time="14:21:56.000+000" date="07-15-2019" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Unable to create WebService class]LOG]!><time="14:21:59.000+000" date="07-15-2019" component="LTIApply" context="" type="2" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="14:21:59.000+000" date="07-15-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="14:21:59.000+000" date="07-15-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="14:21:59.000+000" date="07-15-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <


    anr

    Monday, July 15, 2019 10:18 PM

All replies

  • Just wondering, have you tried to run diskpart and clean the drive, then running it through again?
    Tuesday, July 16, 2019 12:32 PM
  • I didn't - but will try.

    anr

    Tuesday, July 16, 2019 3:08 PM
  • Hello Andrain,

    It looks from the error code that You haven't updated or generated the wim file by updating deployment share.

    Second Make Sure the Operating system which you've added in DS is pointing correctly to the TaskSequence. 

    Tuesday, July 16, 2019 3:17 PM
  • You don't need to make a reference image specific for a Surface. Build your reference image in a VM. Anything that would be Surface specific can be deployed during the task sequence that deploys to the client.

    You can make nested task sequences. First make a task sequence that just does stuff for that type of hardware.

    Then when you nest it, you can use a variable to restrict it to just that make or model it applies to.


    Daniel Vega

    Tuesday, July 16, 2019 6:01 PM
  • What a nested task sequence looks like.

    Add -> General -> Run Task Sequence


    Daniel Vega

    Tuesday, July 16, 2019 6:03 PM
  • Hey Dan,

         That is a neat concept. Other than drivers being model-specific, what are some examples of when a nested TS would be handy? Most of my images are exactly the same for all models, other than drivers for the models.

    Tuesday, July 16, 2019 6:12 PM
  • Hey Dan,

         That is a neat concept. Other than drivers being model-specific, what are some examples of when a nested TS would be handy? Most of my images are exactly the same for all models, other than drivers for the models.

    I also have nested task sequences for software packages based on certain configs. How it helps is that I have multiple task sequences that use similar software configurations. Instead of having to edit multiple task sequences, I just edit the nested task sequence and the change happens for multiple TS.

    It depends on how fluid someone wants to make their deployment. Using nest task sequences made it much easier for me to make updates and not worry about updating one TS forgetting to update another.


    Daniel Vega

    Tuesday, July 16, 2019 6:56 PM