If you have continue on error, or any bad logic in your conditions, or even if the machine rolls back and then runs the rollback steps, it is true that the Task Sequence can finish successfully without upgrading your OS.
Remember the TS does not have a detection method like an application. If the TS Finishes successfully, then that's what it will return. If you want it to fail if the machine didn't upgrade, then you need to check your logic, add error handling or add a step at the end that check for the build verison, and if not your expected version, it would exit with a non-0 exit code.
SCCM In-place upgrade: TS installed, but the OS not upgrade to new one
I'm using SCCM 1906 to in-place upgrade Windows 10 1809 to 2004, the different devices have different results. Some device upgraded successful, but some not. TS installed successful on issue device, but the OS version is not updated. I have done some research, but cannot find the cause, can anyone help here? Much appreciate. Reference: https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager [76278-smsts.log][1] [76267-setuperr.log][2] [1]: /api/attachments/76278-smsts.log?platform=QnA [2]: /api/attachments/76267-setuperr.log?platform=QnA
2 answers
Sort by: Newest
-
Gary Blok 1,736 Reputation points
2021-03-11T23:37:08.123+00:00 -
Pavel yannara Mirochnitchenko 11,986 Reputation points MVP
2021-03-10T13:17:27.693+00:00 Doesn't make any since for me, heh. I would first suggest you to build a state message view item of that TS, look its results and understand what went wrong and what step it has failed. This view also reveals IPU errors starting with 0x19xxxx codes.
https://www.prajwaldesai.com/monitor-sccm-task-sequence-progress/