SCCM - In-Place Upgrade Task Sequence - Stuck on "In Progress" state in console

Question

Hello!
I'm requesting help in troubleshooting an In-Place Upgrade Win10 1809->1909 using SCCM Task Sequence in a enterprise.

Problem:
The Task Sequence completes successfully (the machine gets upgraded to build 1909), but in SCCM Console the deploy still show as In Progress with the message "The task sequence execution engine performed a system reboot initiated by an action"

Situation:
The workstations have Win10 1809 and need to be upgraded to 1909 build.
I'm using a simple Task Sequence to apply the Upgrade package.
As the world situation, my users are at home using VPN, so after the reboots the machine losts conectivity to the Site.
SCCM 2010 - Site version: 5.0.9040.1000 - Console version: 5.2010.1093.1900 - Client version: 5.00.9040.1015
The Primary Site has CMG configured.

Objective: Be able to check the successfully deployments in console

Steps that I took to troubleshoot:

• Checking the setupact.log - No issues found;
• Checking the SMSTS.LOG - Here I see no issues regarding the Windows Upgrade and the TS completes successfully. But after the TS the machine tries to reach the Management Point and the connection fails (of course, it has not internal network conectivity);

Wich kind of settings should I be aware?

Thank you!

Answer 1

I am facing the exact same issue with exact same SMSTS log entries, CMG etc.

I am updating a combination of 1709 and 1809 to 1909, so likely the version jump may not be the issue we are facing, but rather the state reporting to the MP.

We see in the logs that is tries 5 or 6 times within 90 seconds, then permanently gives up with the non-fatal 0x80072ee7

How do we force a state message that shows the successful completion of the TS after the initial message send fails?

Answer 2

I have a client running into this same error - we think the deployment started while on VPN, and then completed on CMG.

The sequence gets to step 16 of 32 or so and doesn't report back it's status with a very similar error to what you show:

The sequence continues to completion offline without reporting status to the MP - all our devices are still showing only on step 16 "in-progress", while the local client log shows fully complete. The client immediately connected the CMG post task sequence, and is a health device.

Hard to continue the deployment when the reporting is show incomplete.