Perform Windows 10 Edition Upgrade Using SCCM

In this article, we will demonstrate how to perform a Windows 10 edition upgrade using SCCM. The Edition Upgrade Policy in SCCM can be used to perform Windows 10 edition upgrades. For example, you can easily upgrade Windows 10 Pro to Windows 10 Enterprise.

There are several methods for changing the product key on a Windows 10 PC. If you want to change the product key on a single machine, go to Windows 10 Settings. Another simple method is to run the slui.exe 3 command, which displays a window in which you can enter the product key.

If you only have a few computers, the solutions listed above are adequate. If you want to change or upgrade the Windows 10 edition for many computers, you can use SCCM.

In this post, we will use the latest Configuration Manager version to upgrade the edition of Windows 10 devices to a new edition. By using a valid key, I will be upgrading Windows 10 Pro to Windows 10 Enterprise.

Prerequisites for Windows 10 Edition Upgrade

Before you use SCCM to change Windows 10 editions, take a look at some prerequisites.

• Ensure you have a valid product key for the new version of Windows. This product key can be either a multiple activation key (MAK), or a generic volume licensing key (GVLK).
• You must have the Configuration Manager Full Administrator security role to upgrade Windows 10 editions using SCCM.
• The devices must run the Configuration Manager client software.

Supported Windows 10 Edition Upgrade paths

To change a Windows 10 edition, you must know the supported upgrade paths.

• Windows 10 Pro to Windows 10 Enterprise
• From Windows 10 Home to Windows 10 Education
• From Windows 10 Mobile to Windows 10 Mobile Enterprise

Create Windows 10 Edition Upgrade Policy in SCCM

You can create a policy for the Windows 10 edition upgrade in SCCM using the following steps:

• Launch the SCCM console.
• Go to Assets and Compliance > Compliance Settings.
• Right-click the Windows 10 Edition Upgrade node.
• Click Create Edition Upgrade Policy.

On the General page of the Create Edition Upgrade Policy Wizard, specify the following information:

• Name – Specify a name for the edition upgrade policy
• Description – Enter a description.
• Specify the type of edition upgrade that you want to create – Select Edition Upgrade for devices managed with the Configuration Manager client.
• SKU to upgrade device to – From the drop-down list, select the target edition of Windows 10 desktop. In my case it is Windows 10 Enterprise.
• License information: If you have a product key with you select Product Key option else select License file. Enter a valid product key for the target Windows 10 desktop edition.

Note – Once you enter the key, you cannot change or modify the key later. Therefore, you must enter the correct product key here.

Click Next.

On the Summary page, click Next.

Finally, on the completion page, click Close.

Deploy Edition Upgrade policy for Windows 10

We will now deploy the edition upgrade policy that we just created in the above step.

• In the SCCM console, go to Assets and Compliance > Compliance Settings > Windows 10 Edition Upgrade node.
• Right-click the Windows 10 edition upgrade policy you want to deploy and click Deploy.

Click Browse and choose the device collection to which you want to deploy the policy.

Select the schedule by which the client evaluates the policy. Click OK.

Once the client evaluates the targeted policy, it applies the upgrade. If you want to speed up the things, here is a bonus tip.

On the Windows 10 client computer, open Configuration Manager properties. Click Configurations tab and select the Windows 10 edition upgrade baseline and click Evaluate.

Check the Last Evaluation time date and time. Click OK.

Monitor the Windows 10 Edition Upgrade Policy Deployment

After you deploy the policy, you can monitor this deployment from the Deployments node of the Monitoring workspace.

If you have entered a valid key, I don’t see any issues with this deployment. But if you see the below errors, it indicates an unsuccessful deployment.

• Not applicable for this device
• Data type conversion failed

In addition to that, on the client computer open DcmWmiProvider.log. If the upgrade is successful, you should find similar lines in your log file.

Initializing the OS Edition Upgrade Provider. OsEditionUpgradeProvider
>>>>>>Starting GetAllInstances in OsEditionUpgradeProvider<<<<<<
>>>>>>Starting GetSingletonInstance in OsEditionUpgradeProvider<<<<<<
>>>>>>Starting PopulateInstanceForEditionUpgradeClass in OsEditionUpgradeProvider<<<<<<
>>>>>>Finished PopulateInstanceForEditionUpgradeClass in OsEditionUpgradeProvider<<<<<< 
>>>>>>Finished GetSingletonInstance in OsEditionUpgradeProvider<<<<<<
>>>>>>Finished GetAllInstances in OsEditionUpgradeProvider<<<<<< 
>>>>>>Starting PutInstanceAsync in OsEditionUpgradeProvider<<<<<<
Already upgraded, existing edition = 4 and target edition = 4