Windows 10 Rollback via SCCM
The 30 Day Rollback option is available for all windows 10 users, but currently can not be automated using SCCM.
This should change, as this feature closely integrates with Microsofts testing strategy of using different branches which grow bigger in size as the rollout of a new build progresses.
When planing to integrate a similar scenario, in our case, we anticipate errors which have not been cought in testing of the previous branch and need to be able to quickly restore operations.
I am well aware that if all our applications were packaged this would not pose much of a problem but as you all know this is rarely the case.
Because of that a reinstall of the previous build (and local applications) would cause a massive loss of time (and money).
Since MS is pushing Enterprise Customers to become part of their testing chain and offers reasonable support times only with LTSB this feature - available even for home users - should be automated using SCCM.
Klaus Steinhauer
shared this idea
AdminBob Mac Neill
(Software Engineer, Microsoft Endpoint Configuration Manager)
responded
Thanks for all your suggestions and feedback, updating status to completed. The DISM commands listed in the previous admin response address this ask and I’ve verified all via task sequence with no issues.
SCCM 1902 fast Ring released today
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Update-1902-for-Configuration-Manager-current-branch-is-now/ba-p/376516
Docs: https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1902