none
MDT LiteTouch stops midproccess, resulting in State Restore not completing Windows 10 RRS feed

  • Question

  • I'm having a very frustrating & intermittent issue when building my Windows 10 reference image.  Sometimes it will work, other times it won't.  During the state restore, the LiteTouch will just stop; no errors, no popups, just nothing will happen.  For example, this morning I started the process (without building a WIM), and it installed properly.  I then restarted the process to build a WIM, and it didn't complete.  Nothing was changed in the process, and I have built several other images successfully in the past.

    When I looked at the change log, I saw the following oddities:

    The LiteTouch process hangs at 1:08:27pm during the "Copying \\RefPCHostname\FallCreators$\Tools\X64\CcmCore.dll to C:\MININT\Tools\X64\CcmCore.dll"  I waited 15 minutes to see if it would do anything.  It didn't.

    Than I manually ran  LTIBootStrap.vbs, which did something and then the vbs file disappeared.  I waited another 2 minutes, and at 1:27:37, then manually ran the Litetouch.wsf, which restarted and completed the state restore process. 

    It used to be a fully automated process; I can't figure out why it stops, and how to prevent it from  stopping in future builds.  Any suggestions would be more than welcome

    I'm trying to post the actual log file, but having difficulties attaching it or posting the xml content

    • Edited by Dan NC Wednesday, December 20, 2017 7:45 PM
    Wednesday, December 20, 2017 7:37 PM

All replies

  • Weird. You could always upload your log files to a public hosting site and I - or one of the MVPs visiting this forum - could then take a look.

    You could also try updating your MDT installation to build 8450 released last night which had been extensively validated with Windows / ADK 1709: https://blogs.technet.microsoft.com/msdeployment/2017/12/21/mdt-8450-now-available/


    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, December 21, 2017 7:18 AM
  • I tried uploading the log to my google drive.  Assuming it worked as expected, it should be located here: https://tinyURL.com/y8dct95r
    Thursday, December 21, 2017 1:33 PM
  • Here is the log following the reboot.  now even manually running those scripts isn't having it complete the TS

    LTI initiating task sequence-requested reboot. LiteTouch 2/9/2018 3:23:46 PM 0 (0x0000)
    Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS LiteTouch 2/9/2018 3:26:12 PM 0 (0x0000)
    Property start is now = LiteTouch 2/9/2018 3:26:12 PM 0 (0x0000)
    Microsoft Deployment Toolkit version: 6.3.8450.1000 LiteTouch 2/9/2018 3:26:12 PM 0 (0x0000)
    ZTIUtility!GetAllFixedDrives (False) LiteTouch 2/9/2018 3:26:12 PM 0 (0x0000)
    New ZTIDisk : \\MININT-L31DDSE\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2/9/2018 3:26:12 PM 0 (0x0000)
    New ZTIDiskPartition : \\MININT-L31DDSE\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-L31DDSE\root\cimv2:Win32_LogicalDisk.DeviceID="C:" LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    New ZTIDisk : \\MININT-L31DDSE\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    New ZTIDisk : \\MININT-L31DDSE\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    ZTIUtility!GetAllFixedDrives =   C: LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    Found existing task sequence state information in C:\_SMSTaskSequence, will continue LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    Property LTIDirtyOS is now = FALSE LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    Creating startup folder item to run LiteTouch.wsf once the shell is loaded. LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created. LiteTouch 2/9/2018 3:26:13 PM 0 (0x0000)
    Microsoft Deployment Toolkit version: 6.3.8450.1000 LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    ZTIUtility!GetAllFixedDrives (False) LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    New ZTIDisk : \\MININT-L31DDSE\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    New ZTIDiskPartition : \\MININT-L31DDSE\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-L31DDSE\root\cimv2:Win32_LogicalDisk.DeviceID="C:" LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    New ZTIDisk : \\MININT-L31DDSE\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    New ZTIDisk : \\MININT-L31DDSE\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    ZTIUtility!GetAllFixedDrives =   C: LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Found existing task sequence state information in C:\_SMSTaskSequence, will continue LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Not running within WinPE. LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    DeploymentMethod = UNC LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Validating connection to \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Mapping server share: \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Mapped Network UNC Path Z:  = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Successfully established connection using supplied credentials. LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    DeployRoot = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Property DeployDrive is now = Z: LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    DeployDrive = Z: LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Phase = STATERESTORE LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Validating connection to \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Mapping server share: \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Successfully established connection using supplied credentials. LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Property DeployDrive is now = Z: LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    DeployDrive = Z: LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Validating connection to \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Mapping server share: \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Successfully established connection using supplied credentials. LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    DeploymentType = NEWCOMPUTER LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    ResourceRoot = \\hostmachine\FallCreators$ LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    Property ResourceDrive is now = Z: LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    ResourceDrive = Z: LiteTouch 2/9/2018 3:27:33 PM 0 (0x0000)
    SMS Task Sequencer found at \\hostmachine\FallCreators$\Tools\X64, copying to C:\MININT\Tools\X64 LiteTouch 2/9/2018 3:27:34 PM 0 (0x0000)
    Copying \\hostmachine\FallCreators$\Tools\X64\CcmCore.dll to C:\MININT\Tools\X64\CcmCore.dll LiteTouch 2/9/2018 3:27:34 PM 0 (0x0000)

    at this point it just hangs...... no error message, no warning, nothing further.  a reboot than gives another error message that the process failed to run the TS.  any suggestions?
    • Edited by Dan NC Friday, February 9, 2018 9:26 PM
    Friday, February 9, 2018 9:25 PM