Upgrade Windows to the latest version with Configuration Manager
Applies to: Configuration Manager (current branch)
This article provides the steps in Configuration Manager to upgrade the OS on a computer. You can choose from different deployment methods, such as stand-alone media or Software Center. The in-place upgrade scenario has the following features:
Upgrades the OS to Windows 10, or Windows Server 2016 and later
Keeps the applications, settings, and user data on the computer
Has no external dependencies, such as the Windows ADK
Is faster and more resilient than traditional OS deployments
The Windows 10 in-place upgrade task sequence supports deployment to internet-based clients managed through the cloud management gateway. This ability allows remote users to more easily upgrade to Windows 10 without needing to connect to the intranet. For more information, see Deploy Windows 10 in-place upgrade via CMG.
Only create OS upgrade packages to upgrade to the following OS versions:
- Windows 10
- Windows Server 2016
- Windows Server 2019
Devices must run one of the following OS versions to target an OS upgrade task sequence:
- Windows 7
- Windows 8.1
- An earlier version of Windows 10. For example, you can upgrade Windows 10, version 1809 to Windows 10, version 1903.
For more information, see Windows 10 upgrade paths.
- Windows Server 2012
- Windows Server 2012 R2
- An earlier version of Windows Server 2016
- An earlier version of Windows Server 2019
Task sequence requirements and limitations
Review the following requirements and limitations for the task sequence to upgrade an OS to make sure it meets your needs:
Only add task sequence steps that are related to the core task of upgrading the OS. These steps primarily include installing packages, applications, or updates. Also use steps that run command lines, PowerShell, or set dynamic variables.
Review drivers and applications that are installed on computers. Before you deploy the upgrade task sequence, make sure the drivers are compatible with Windows 10.
The following tasks aren't compatible with the in-place upgrade. They require you to use traditional OS deployments:
Changing the computer's domain membership, or updating the local Administrators group.
Implementing a fundamental change on the computer, such as:
- Changing disk partitions
- Changing the system architecture from x86 to x64
- Implementing UEFI. (For more information on a possible option, see Convert from BIOS to UEFI during an in-place upgrade.)
- Modifying the base OS language
You have custom requirements including using a custom base image, using third-party disk encryption, or require WinPE offline operations.
The only prerequisite for the upgrade scenario is to have a distribution point available. Distribute the OS upgrade package and any other packages that you include in the task sequence. For more information, see Install or modify a distribution point.
Prepare the OS upgrade package
The Windows 10 upgrade package contains the source files necessary to upgrade the OS on the destination computer. The upgrade package must be the same edition, architecture, and language as the clients that you upgrade. For more information, see Manage OS upgrade packages.
Create a task sequence to upgrade the OS
Use the steps in Create a task sequence to upgrade an OS to automate the upgrade of the OS.
To create a task sequence to upgrade an OS to Windows 10, you typically use the steps in Create a task sequence to upgrade an OS. The task sequence includes the Upgrade OS step, as well as additional recommended steps and groups to handle the end-to-end upgrade process.
You can create a custom task sequence and add the Upgrade OS step. This step is the only one required to upgrade the OS to Windows 10. If you choose this method, to complete the upgrade, also add the Restart Computer step after the Upgrade OS step. Be sure to use the The currently installed default operating system setting to restart the computer into the installed OS and not Windows PE.
To deploy the OS, use one of the following deployment methods:
When you use stand-alone media, you must include a boot image in the task sequence. This configuration makes the task sequence available in the Task Sequence Media Wizard.
To monitor the task sequence deployment to upgrade the OS, see Monitor OS deployments.