none
Cloud Management Gateway Upgrade Task Sequence Status Messages? RRS feed

  • Question

  • Pretty simple question. Can anyone confirm if an upgrade task sequence should be sending status messages back through a CMG to the database? My first few tests over CMG complete an upgrade but never send a status message during the entire sequence.  And we should be getting some for each step.
    Friday, June 14, 2019 12:30 AM

All replies

  • Hi PaulWetter,

    Based on my experience, the CMG In-place Upgrade Task Sequence status messages will be sent back to the CMG. Please refer to:
    Upgrade Windows 10 over the Internet with In-Place Upgrade Task Sequences and ConfigMgr

    Please help check the smsts.log to see if there are any clues that prevent the status messages. 



    Hope it helps. Thanks for your time.

    Best regards,
    Simon Ren

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 14, 2019 8:07 AM
  • Hi,

    May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Thanks and regards,
    Simon 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 17, 2019 2:17 AM
  • Yes, the current state is, it’s the weekend and I haven’t had a chance to do additional troubleshooting, or look at the smsts log again. I will know more tomorrow. Thanks, Paul
    Monday, June 17, 2019 3:09 AM
  • Hello Paul,

    Thanks for your feedback. Look forward to your new message. Have a nice weekend!

    Thanks and regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 17, 2019 6:19 AM
  • So, it is definitely failing to send the status messages when I look at the smsts.log.  But, I don't know why or where to start the troubleshooting..  (Replaced my actual CMG url with generic)

    This series repeats throughout the smsts.log with the "Failed to send status message (80004005)" all along the way.

    <![LOG[End TS policy evaluation]LOG]!><time="11:12:13.594+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="policyutil.cpp:11341">
    <![LOG[Policy evaluation initiated]LOG]!><time="11:12:13.595+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="utils.cpp:4777">
    <![LOG[Sending success status message]LOG]!><time="11:12:13.603+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="tsmanager.cpp:1047">
    <![LOG[MP server https://MYCMG123.MYDOMAIN123.COM/CCM_Proxy_MutualAuth/72057594037927938. Ports 80,443. CRL=false.]LOG]!><time="11:12:13.606+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="utils.cpp:6873">
    <![LOG[Setting authenticator]LOG]!><time="11:12:13.606+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="utils.cpp:6895">
    <![LOG[Sending StatusMessage]LOG]!><time="11:12:13.634+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:4863">
    <![LOG[Setting the authenticator.]LOG]!><time="11:12:13.676+300" date="06-12-2019" component="TSManager" context="" type="0" thread="6060" file="libsmsmessaging.cpp:1527">
    <![LOG[Converting MutualAuth URL to ServerAuth: https://MYCMG123.MYDOMAIN123.COM/CCM_Proxy_ServerAuth/72057594037927938]LOG]!><time="11:12:13.676+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:9881">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: MYCMG123.MYDOMAIN123.COM:443  CCM_POST CCM_Proxy_ServerAuth/72057594037927938/ccm_system_AltAuth/request]LOG]!><time="11:12:13.677+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:9946">
    <![LOG[SSL - using authenticator in request.]LOG]!><time="11:12:13.677+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:10081">
    <![LOG[In SSL, but with no client cert]LOG]!><time="11:12:13.678+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:10102">
    <![LOG[In SSL, but with no media cert]LOG]!><time="11:12:13.678+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:10108">
    <![LOG[401 - Unsuccessful with anonymous access. Retrying with context credentials.]LOG]!><time="11:12:13.916+300" date="06-12-2019" component="TSManager" context="" type="0" thread="6060" file="libsmsmessaging.cpp:10309">
    <![LOG[Using thread token for request]LOG]!><time="11:12:13.916+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:10159">
    <![LOG[401 - Unsuccessful with context credentials. Retrying with supplied credentials.]LOG]!><time="11:12:13.964+300" date="06-12-2019" component="TSManager" context="" type="0" thread="6060" file="libsmsmessaging.cpp:10315">
    <![LOG[Network access account credentials are not supplied or invalid.]LOG]!><time="11:12:13.965+300" date="06-12-2019" component="TSManager" context="" type="1" thread="6060" file="libsmsmessaging.cpp:10211">
    <![LOG[pNext != NULL, HRESULT=80004005 (..\libsmsmessaging.cpp,2172)]LOG]!><time="11:12:13.965+300" date="06-12-2019" component="TSManager" context="" type="0" thread="6060" file="libsmsmessaging.cpp:2172">
    <![LOG[reply has no message header marker]LOG]!><time="11:12:13.966+300" date="06-12-2019" component="TSManager" context="" type="3" thread="6060" file="libsmsmessaging.cpp:2172">
    <![LOG[DoRequest (sReply, false), HRESULT=80004005 (..\libsmsmessaging.cpp,4888)]LOG]!><time="11:12:13.966+300" date="06-12-2019" component="TSManager" context="" type="0" thread="6060" file="libsmsmessaging.cpp:4888">
    <![LOG[Failed to send status message (80004005)]LOG]!><time="11:12:13.966+300" date="06-12-2019" component="TSManager" context="" type="3" thread="6060" file="libsmsmessaging.cpp:4892">
    <![LOG[smStatusMessage.Send(), HRESULT=80004005 (..\utils.cpp,6966)]LOG]!><time="11:12:13.967+300" date="06-12-2019" component="TSManager" context="" type="0" thread="6060" file="utils.cpp:6966">
    <![LOG[Error calling message lib Send(). Code 0x80004005]LOG]!><time="11:12:13.967+300" date="06-12-2019" component="TSManager" context="" type="2" thread="6060" file="utils.cpp:6966">
    <![LOG[Non fatal error 0x80004005 in sending task sequence execution status message to MP]LOG]!><time="11:12:13.967+300" date="06-12-2019" component="TSManager" context="" type="2" thread="6060" file="utils.cpp:6978">


    • Edited by PaulWetter Wednesday, June 19, 2019 1:45 PM
    Wednesday, June 19, 2019 1:43 PM
  • I had opened a support case with MSFT and I was told today that this is a bug with relaying status messages that was introduced in CB 1902.  I am told that this will be fixed in the next release (which I assume they are referring to 1906).  So, i guess the wait is on....
    Tuesday, June 25, 2019 7:19 PM