none
MDT 8443 Erratic Deployments with good summary have errors in log RRS feed

  • Question

  • Hello,

    I'm using MDT version 8443 to deploy Windows 1709 UEFI based images.  I have to use USB and/or OEM staged deployments to deploy these images.  Question is.... I'm getting erratic results with these deployments. Example: Good summary at the end, but logs have errors and/or Mininit or Deploy folder left behind.  Sometimes just the deploy folder, sometimes just the mininit folder, sometimes clean.  Any way to stop the errors and clean up the folders?  I at least want to be getting a consistent behavior.

    End of smsts.log.

    <![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="14:24:32.241+240" date="03-19-2018" component="TSManager" context="" type="2" thread="8636" file="utils.cpp:830">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="14:24:32.243+240" date="03-19-2018" component="TSManager" context="" type="2" thread="8636" file="utils.cpp:861">
    <![LOG[End program: ]LOG]!><time="14:24:32.243+240" date="03-19-2018" component="TSManager" context="" type="1" thread="8636" file="tsmanager.cpp:1055">
    <![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="14:24:32.243+240" date="03-19-2018" component="TSManager" context="" type="3" thread="8636" file="tsmanager.cpp:1059">
    <![LOG[Sending error status message]LOG]!><time="14:24:32.243+240" date="03-19-2018" component="TSManager" context="" type="1" thread="8636" file="tsmanager.cpp:1060">
    <![LOG[In non SMS staqndalone mode.Ignoring SendStatusMessage request]LOG]!><time="14:24:32.244+240" date="03-19-2018" component="TSManager" context="" type="1" thread="8636" file="tsmanager.cpp:1832">
    <![LOG[LOGGING: Setting log directory to "C:\Users\ADMINI~1\AppData\Local\Temp\".]LOG]!><time="14:24:32.247+240" date="03-19-2018" component="TSManager" context="" type="1" thread="8636" file="tslogging.cpp:2180">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="14:24:32.264+240" date="03-19-2018" component="TSMBootstrap" context="" type="1" thread="8584" file="commandline.cpp:1124">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="14:24:32.264+240" date="03-19-2018" component="TSMBootstrap" context="" type="1" thread="8584" file="tsmbootstrap.cpp:1270">
    <![LOG[Used smsts.ini to set logging settings.]LOG]!><time="14:24:32.485+240" date="03-19-2018" component="TsProgressUI" context="" type="1" thread="6128" file="tslogging.cpp:1457">
    <![LOG[==========[ TsProgressUI started in process 5464 ]==========]LOG]!><time="14:24:32.487+240" date="03-19-2018" component="TsProgressUI" context="" type="1" thread="6128" file="winmain.cpp:330">
    <![LOG[Unregistering COM classes]LOG]!><time="14:24:32.487+240" date="03-19-2018" component="TsProgressUI" context="" type="1" thread="6128" file="winmain.cpp:204">
    <![LOG[Shutdown complete.]LOG]!><time="14:24:32.488+240" date="03-19-2018" component="TsProgressUI" context="" type="1" thread="6128" file="winmain.cpp:512">

    Thanks

    Tuesday, March 20, 2018 9:54 PM

All replies

  • There is simply not enough information here - could you pull BDD.log from a failed OSD and post it to a public hosting site?

    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, March 22, 2018 9:10 AM