none
Refresh scenario missing after restart PC RRS feed

  • Question

  • Hello everybody.

    I have a problem with refresh scenario.

    I start LiteTouch.vbs from old OS. All steps executed succesfully. USMT works correctly.

    DynamicLogs shows me

    Property TaskSequenceID is now = 7X64V6.3.3 Wizard
    Found Task Sequence Item: //step[@type='BDD_InstallOS'] Wizard
    Found Task Sequence step of type //step[@type='BDD_InstallOS'] 
    Task Sequence contains a LTIApply.wsf step, and is not running within WinPE
    Property DeployTemplate is now = TASK SEQUENCE ELIZAROV Wizard
    DeploymentType = REFRESH

    As I understand, TS have to continue booting from c:\sources folder and TS have to continue properly,instead that:

    after restarting computer in WinPE, MDT offers again choose which TS I want to start. Previous Refresh scenario has failed in log I see the following

    BCD> .............           {d22e7e91-9ee7-46eb-89d7-c5859e4302f0} LTIApply
    BCD> device                  ramdisk=[C:]\sources\boot.wim,{ramdiskoptions} LTIApply
    BCD> path                    \windows\system32\boot\winload.exe LTIApply
    BCD> description             Microsoft Deployment WinPE LTIApply
    BCD> osdevice                ramdisk=[C:]\sources\boot.wim,{ramdiskoptions} LTIApply
    BCD> systemroot              \windows LTIApply
    BCD> detecthal               Yes LTIApply
    BCD> winpe                   Yes LTIApply
    BCDEdit returned ErrorLevel = 0 LTIApply


    BCDEdit returned ErrorLevel = 0 LTIApply
    Property BootPE is now = True LTIApply
    LTI Windows PE applied successfully LTIApply
    Event 41019 sent: LTI Windows PE applied successfully LTIApply
    LTIApply processing completed successfully. LTIApply
    Event 41001 sent: LTIApply processing completed successfully. LTIApply
    Property PHASE is now = PREINSTALL ZTINextPhase
    ZTINextPhase COMPLETED.  Return Value = 0 ZTINextPhase
    ZTINextPhase processing completed successfully. ZTINextPhase
    Event 41001 sent: ZTINextPhase processing completed successfully. ZTINextPhase
    Run Command: X:\windows\system32\bcdedit.exe /delete {d22e7e91-9ee7-46eb-89d7-c5859e4302f0} /cleanup LTICleanup
    BCD> The operation completed successfully.
    BCDEdit returned ErrorLevel = 0
    Removing BCDEdit
    Removing AutoAdminLogon registry entries LTICleanup
    VSSMaxSize not specified using 5% of volume. LTICleanup
    Logs contained 0 errors and 0 warnings. LTICleanup
    Checking mapped network drive. LTICleanup
    testing drive Z: mapped to \\192.168.1.1\DS$ LTICleanup
    Disconnecting drive Z: mapped to \\192.168.1.1\DS$ LTICleanup
    Cleaning up C:\MININT directory. LTICleanup
    Cleaning up TOOLS, SCRIPTS, and PACKAGES directories. LTICleanup
    Removing C:\MININT folder (final log entry) LTICleanup


    I can choose TS again, MDT creates new dynamiclogs folder where I see NEWCOMPUTER deployment type.

    It`s happening from all computers, phisical or virtual. I tried to recreated boot images,Update DS.

    Why Refresh scenario doesnt continue?

    Thank you for your answers.

    Thursday, May 12, 2016 10:19 AM

Answers

  • The problem was solved.

    I made mistake previously.While I tested some new features, I included file Unnattend.xml to extrafolder

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
                <Display>
                    <ColorDepth>16</ColorDepth>
                    <HorizontalResolution>1024</HorizontalResolution>
                    <RefreshRate>60</RefreshRate>
                    <VerticalResolution>768</VerticalResolution>
                </Display>
                <RunSynchronous>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>Lite Touch PE</Description>
                        <Order>2</Order>
                        <Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
                    </RunSynchronousCommand>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>LTICleanup</Description>
                        <Order>1</Order>
                        <Path>wscript.exe X:\Deploy\Scripts\LTICleanup.wsf</Path>
                    </RunSynchronousCommand>
                </RunSynchronous>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    This file execute LTICleanup scenario. 


    • Marked as answer by elizarov Friday, May 27, 2016 8:03 AM
    • Edited by elizarov Friday, May 27, 2016 8:06 AM errors
    Friday, May 27, 2016 8:03 AM

All replies

  • I found interestin infirmation in appropriate logs

    In DeploymentsLogs folder

    The task sequencer log is located at C:\Users\ALEXAN~1.ELI\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    Write all logging text to \\192.168.1.1\DS$\Logs\Dynamic\VIRTUALBOX ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    Validating connection to \\192.168.1.1\DS$\Logs\Dynamic\VIRTUALBOX ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    Mapping server share: \\192.168.1.1\DS$ ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    Already connected to server 192.168.1.1 as that is where this script is running from. ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    Property PHASE is now = PREINSTALL ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    ZTINextPhase COMPLETED.  Return Value = 0 ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    ZTINextPhase processing completed successfully. ZTINextPhase 5/12/2016 1:36:54 PM 0 (0x0000)
    Event 41001 sent: ZTINextPhase processing completed successfully. ZTINextPhase 5/12/2016 1:37:15 PM 0 (0x0000)
    Command completed, return code = -2147021886 LiteTouch 5/12/2016 1:37:15 PM 0 (0x0000)
    Property LTIDirty is now = FALSE LiteTouch 5/12/2016 1:37:15 PM 0 (0x0000)
    If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation. LiteTouch 5/12/2016 1:37:15 PM 0 (0x0000)
    Property OSDTargetDriveCache is now = DIRTY LiteTouch 5/12/2016 1:37:15 PM 0 (0x0000)
    LTI initiating task sequence-requested reboot. LiteTouch 5/12/2016 1:37:15 PM 0 (0x0000)
    Event 41017 sent: LTI initiating task sequence-requested reboot. LiteTouch 5/12/2016 1:37:36 PM 0 (0x0000)
    Property BootPE is now = LiteTouch 5/12/2016 1:37:36 PM 0 (0x0000)
    Microsoft Deployment Toolkit version: 6.2.5019.0 LTICleanup 5/12/2016 1:38:05 PM 0 (0x0000)
    Write all logging text to \\192.168.1.1\DS$\Logs\Dynamic\VIRTUALBOX LTICleanup 5/12/2016 1:38:05 PM 0 (0x0000)
    Validating connection to \\192.168.1.1\DS$\Logs\Dynamic\VIRTUALBOX LTICleanup 5/12/2016 1:38:05 PM 0 (0x0000)
    Mapping server share: \\10.57.6.211\DS$ LTICleanup 5/12/2016 1:38:05 PM 0 (0x0000)
    Mapped Network UNC Path Z:  = \\192.168.1.1\DS$ LTICleanup 5/12/2016 1:38:05 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\192.168.1.1\DS$ LTICleanup 5/12/2016 1:38:05 PM 0 (0x0000)
    Successfully established connection using supplied credentials. LTICleanup 5/12/2016 1:38:05 PM 0 (0x0000)
    Run Command: X:\windows\system32\bcdedit.exe /delete {d22e7e91-9ee7-46eb-89d7-c5859e4302f0} /cleanup LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    BCD> The operation completed successfully. LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    BCDEdit returned ErrorLevel = 0 LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    Removing BCDEdit LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    Removing AutoAdminLogon registry entries LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    VSSMaxSize not specified using 5% of volume. LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    Logs contained 0 errors and 0 warnings. LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    Checking mapped network drive. LTICleanup 5/12/2016 1:38:06 PM 0 (0x0000)
    testing drive Z: mapped to \\192.168.1.1\DS$ LTICleanup 5/12/2016 1:38:07 PM 0 (0x0000)
    Disconnecting drive Z: mapped to \\192.168.1.1\DS$ LTICleanup 5/12/2016 1:38:07 PM 0 (0x0000)
    Cleaning up C:\MININT directory. LTICleanup 5/12/2016 1:38:07 PM 0 (0x0000)
    Cleaning up TOOLS, SCRIPTS, and PACKAGES directories. LTICleanup 5/12/2016 1:38:07 PM 0 (0x0000)

    In SMSTS.log

    At the end of log

    Execution engine result code: 2 (Success=0, Failure=1, RebootInitiated=2) TSManager 5/12/2016 1:37:15 PM 2348 (0x092C)
    Process completed with exit code 2147945410 TSMBootstrap 5/12/2016 1:37:15 PM 2116 (0x0844)
    Exiting with return code 0x80070BC2 TSMBootstrap 5/12/2016 1:37:15 PM 2116 (0x0844)
    ==========[ TsProgressUI started in process 2588 ]========== TsProgressUI 5/12/2016 1:37:15 PM 2292 (0x08F4)
    Command line: "C:\MININT\Tools\X64\TSProgressUI.exe"  /Unregister TsProgressUI 5/12/2016 1:37:15 PM 2292 (0x08F4)
    Unregistering COM classes TsProgressUI 5/12/2016 1:37:15 PM 2292 (0x08F4)
    Unregistering class objects TsProgressUI 5/12/2016 1:37:15 PM 2292 (0x08F4)
    Shutdown complete. TsProgressUI 5/12/2016 1:37:15 PM 2292 (0x08F4)

    At the start of log

    ==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Command line: "C:\MININT\Tools\X64\TsmBootstrap.exe"  /env:SAStart TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Failed to find resource file TSRES.DLL for locale 1049 TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Succeeded loading resource DLL 'C:\MININT\Tools\X64\00000409\TSRES.DLL' TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Succeeded loading resource DLL 'C:\MININT\Tools\X64\TSRESNLC.DLL' TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Running Task Sequence in standalone. TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Loading the Environment Variables from "C:\MININT\Tools\X64\variables.dat". TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Loading task sequence file TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    Loading _SMSTSTaskSequence from C:\MININT\Tools\X64\TS.XML TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)
    User specified local data drive C: TSMBootstrap 5/12/2016 1:29:14 PM 2116 (0x0844)

     

    and many errors like these

    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566) TSManager 5/12/2016 1:29:14 PM 2348 (0x092C)

    Hope is says something interesting

    Thursday, May 12, 2016 10:57 AM
  • Sorry, I can't follow the text above, if you still need help, please copy the bdd.log and smsts.log file to a public site like onedrive and copy the link here.

    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, May 13, 2016 5:31 AM
    Moderator
  • Ofcouse,thank you.

    https://onedrive.live.com/redir?resid=15A3C09515F1E2F7!4929&authkey=!APWVCMlcXl0pqmQ&ithint=folder%2c

    Friday, May 13, 2016 8:05 AM
  • There is a mystery here that I don't understand. Something is corrupted.

    Sometime after the reboot, something restarted again, but all I see is the LTICleanup in the bdd.log file, which I don't understand.

    Got to find out *WHY* lticleanup.wsf is running after the reboot is initiated, is it after the reboot, or before?

    If you are still having problems, you might have to open a microsoft support case, as it will require some more intense debugging.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, May 13, 2016 8:17 PM
    Moderator
  • Do you have link to mdt connect portal?

    Tuesday, May 17, 2016 7:41 AM
  • Created feedback to microsoft connect.
    Tuesday, May 17, 2016 11:00 AM
  • The problem was solved.

    I made mistake previously.While I tested some new features, I included file Unnattend.xml to extrafolder

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
                <Display>
                    <ColorDepth>16</ColorDepth>
                    <HorizontalResolution>1024</HorizontalResolution>
                    <RefreshRate>60</RefreshRate>
                    <VerticalResolution>768</VerticalResolution>
                </Display>
                <RunSynchronous>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>Lite Touch PE</Description>
                        <Order>2</Order>
                        <Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
                    </RunSynchronousCommand>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>LTICleanup</Description>
                        <Order>1</Order>
                        <Path>wscript.exe X:\Deploy\Scripts\LTICleanup.wsf</Path>
                    </RunSynchronousCommand>
                </RunSynchronous>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    This file execute LTICleanup scenario. 


    • Marked as answer by elizarov Friday, May 27, 2016 8:03 AM
    • Edited by elizarov Friday, May 27, 2016 8:06 AM errors
    Friday, May 27, 2016 8:03 AM