In short, the client gets stuck in Provisioning mode and fails in previous Windows and SCCM version. There’s also a known issue well documented by the SCCM product group : A Configuration Manager in-place upgrade task sequence doesn’t continue after a Windows 10 in-place upgrade rollback. The reason is pretty simple, some of the DISM commands were introduced in the latest Windows 10 builds. The only “catch” is that you need to be using Windows 10 1803+ and SCCM 1902+ to use those DISM commands.
They are basically saying that you need to use the provided DISM commands for that. The product group has confirmed this in this User Voice Item. There no built-in action in SCCM to do a Windows 10 rollback. So let’s begin with explaining how to do the Windows 10 rollback action using SCCM. The term Uninstall is important here because Microsoft tools are not using the Rollback term, it’s using the Uninstall term. If you have compatibility issues with some OS component or applications after a Windows 10 Feature update, you can uninstall the updates using either Configuration Service Provider (Intune) or DISM (SCCM/MEMCM) Rollback Windows 10 to a Previous Version After ten days, Windows deletes those old files to free up disk space. This is a change from the initial versions of Windows 10, which gave you 30 days to decide. In this blog post, I’ll describe everything you need to know if you need to do a Windows 10 Rollback using SCCM or Intune.īy default, Windows 10 gives you ten days to roll back major upgrades. However, there’s a couple of catch that I found when I was asked to do it.
The Windows 10 Rollback action can be initiated by SCCM or Microsoft Intune. A Windows 10 Rollback is wanted for example because the user runs into a problem after the Windows 10 Feature Update deployment.
During a Windows 10 Feature Update deployment, you may want to uninstall or rollback to the previous Windows 10 version.
0 kommentar(er)
