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

How to change Windows 10 Professional version/edition to Enterprise? > This is explained in my previous post here. The manual process explained in the previous post is suitable for thousands of machines. Rather we can use SCCM Current Branch 1511 default compliance settings policy can be used to automate the Windows 10 version change process. Follow the following path in SCCM CB console “\Assets and Compliance\Overview\Compliance Settings\Windows 10 Edition Upgrade“. Right click on Windows 10 Edition Upgrade node and click on “Create Edition Upgrade Policy“.


On “Create Edition Upgrade Policy” Wizard, you need to specify the name of the SCCM compliance policy for Windows 10 edition upgrade “Windows 10 Pro to Ent“. Specify the target version of Windows 10 edition you wanted to upgrade. In the scenario, I choose to upgrade my Windows 10 Professional edition to Enterprise edition (SKU Upgrade Device to Windows 10 Enterprise).


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


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


Give ample to 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 CI Name = “Windows 10 pro to Ent” and targeted to User collection Test Users.


More compliance status can be viewed SCCM CB Asset Message pop as shown in the following picture :- Settings performed on the Windows 10 MDM client device – Edition Upgrade Identifier, Edition and Product Key.


About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: ConfigMgr (SCCM), SCCM 2016


  1. Brian says:


    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?



    • Anoop says:

      Hi 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.


  2. Alan Dooley says:

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

Leave a Comment and Contact Anoop