Skip to content
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB

How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB

Written By Anoop C Nair
Last Updated August 9, 2024
Posted In SCCM
SHARE

Let’s discuss how to change or upgrade the Windows 10 edition using SCCM’s current branch CB. How can we change the Windows 10 Professional version/edition to Enterprise?

This is explained in my previous post here. The manual process described in the last post is suitable for thousands of machines. Instead, we can use the SCCM Current Branch 1511 default compliance settings policy to automate the Windows 10 version change process.

Follow the following path in the SCCM CB console: “\Assets and Compliance\Overview\Compliance Settings\Windows 10 Edition Upgrade“. Right-click on the Windows 10 Edition Upgrade node and click “Create Edition Upgrade Policy“.

On the “Create Edition Upgrade Policy” Wizard, you need to specify the name of the SCCM compliance policy for the Windows 10 edition upgrade “Windows 10 Pro to Ent“.

Patch My PC
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB - Fig.1
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB – Fig.1

How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB

Specify the target version of the Windows 10 edition you want to upgrade to I upgraded my Windows 10 Professional edition to Enterprise edition (SKU Upgrade Device to Windows 10 Enterprise) in this scenario.

How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB - Fig.2
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB – Fig.2

The above is the only configuration page in this SCCM CB compliance policy for the Windows edition upgrade. Once the policy is created, you need to deploy this policy device or user collection.

How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB - Fig.3
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB – Fig.3

Once a deployment is created and targeted to user/device collections, the SCCM CB console view will look like this: Remember to set the Deployment action to “Remediate” rather than “Monitor.”

How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB - Fig.4
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB – Fig.4

Give ample time to Intune MDM / SCCM full client to evaluate compliance policy for Windows 10 edition upgrade. You can check the status of the compliance policy from “\Monitoring\Overview\Deployments\Windows 10 Pro to Ent Status to Test Users“. You can see the CI Name = “Windows 10 pro to Ent”, targeted to user collection test users.

How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB - Fig.5
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB – Fig.5

The SCCM CB Asset Message pop shows more compliance status, as shown in the following picture: Settings performed on the Windows 10 MDM client device: Edition Upgrade Identifier, Edition, and Product Key.

Settings Name
Edition Upgrade Identifier
Edition
Product Key
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB – Table 1
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB - Fig.6
How to Change or Upgrade Windows 10 Edition Using SCCM Current Branch CB – Fig.6

Resources

SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)

SCCM Video Tutorials For IT Pros – HTMD Blog #2 (howtomanagedevices.com)

We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

Written by

Anoop C Nair is Workplace Technology solution architect with 25+ years of experience in global enterprise organizations such as JP Morgan, Capgemini, etc. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for consecutive 11+ years! He also conducts Intune and modern workplace tech training for enterprise organizations. He is Blogger, Speaker, and Founder of HTMD Community and HTMD Conference. His main focus is on Device Management technologies like Intune, Windows, Cloud PC. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security.

Discussion · 12 comments

  1. Anoop,

    As always, great post. Can you show that the license key and Windows version did change on your target system? We successfully applied this to a test collection and the configuration shows compliant. However, the license key and Windows version still shows Pro. Any pointers?

    Thanks.

    Brian

    1. StaffHi Brian ! – This feature works only with MDM channel. Was your Windows 10 machine was MDM client or SCCM 1511 client? If it’s SCCM 1511 client then this is expected behavior.

      KR/Anoop

  2. So are you saying this can only be used if you are using Intune and that it does not work for full client? Thanks

    1. StaffHello Henrik!- Thank you. The document says – “In the Deploy Windows 10 Edition Upgrade dialog box, choose the collection to which you want to deploy the policy and the schedule by which the policy will be evaluated, and then click OK. For PCs that are managed with the Configuration Manager client, you must deploy the policy to a device collection. For PCs that are enrolled with Intune, you can deploy the policy to a

      user or device collection

      . “

      1. The document says under Deploy the policy “3. Choose the DEVICE collection to which you want to deploy the policy.”

  3. Hello Anoop, This is a great post. I deployed this in my infrastructure, the issue I am facing is that os sku is updating but os caption is not. What can be done regarding this. Thanks

  4. Where this key got written in Client machine?
    Any registry path?

    Reason
    When we run Winver > we see professional
    When we run slmgr/dlv >> we see enterprise.

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read