This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 65%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESF%3C/text%3E%3C/svg%3E)
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
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/
I have set a state message view item for my TS, the steps are all complete, I can see that it says Failed to start the CCM client.. I tried to reinstall the client on device, it doesn't work. I have attached the whole message below, can you please help to take a look? [76661-log1.txt][1] [1]: /answers/storage/temp/76661-log1.txt
Hey, I really suggest first to upgrade the SCCM to 2010 with latest hotfix. You might suffer from any SCCM client bug whatsoever. If you would call MS support for this, I am sure they would first suggest you to do the same.
OK, thanks for your suggestion, I will do this later.
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.