Windows 10 Subscription Activation Not "stepping-up"

%3CLINGO-SUB%20id%3D%22lingo-sub-671957%22%20slang%3D%22en-US%22%3EWindows%2010%20Subscription%20Activation%20Not%20%22stepping-up%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-671957%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20recently%20decided%20to%20make%20the%20switch%20from%20KMS%20to%20Subscription%20activation%20for%20our%20E3%20users.%20I've%20been%20able%20to%20successfully%20test%20this%20in%20a%20few%20different%20situations%20when%20I've%20run%20into%20a%20roadblock.%20Due%20to%20our%20size%2C%20we%20will%20face%20a%20struggle%20forcing%20everyone%20to%20change%20to%20their%20Azure%20AD%20creds%20(name%40domain.com)%2C%20so%20we%20intended%20to%20run%20the%20script%20Microsoft%20recommends%20for%20manual%20activation.%20To%20do%20this%20via%20SCCM%2C%20however%2C%20we%20wanted%20to%20set%20a%20configuration%20baseline%20to%20remediate%20any%20machines%20that%20do%20not%20make%20the%20switch%20by%20using%20powershell.%20We%20wrote%20a%20script%20that%20successfully%20activates%20the%20underlying%20pro%20license%2C%20but%20now%20these%20machines%20are%20not%20making%20the%20%22step-up%22%20to%20enterprise.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20attempted%20to%20run%20the%20script%20MS%20suggests%20on%20each%20of%20these%20machines%20since%2C%20but%20to%20no%20avail.%20I%20have%20also%20made%20GPO%20changes%20and%20registry%20changes%20suggested%20on%20other%20posts%20but%20that%20also%20did%20not%20work.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20opened%20a%20ticket%20with%20MS%20but%20they%20have%2C%20so%20far%2C%20only%20suggested%20changes%20that%20I%20have%20already%20made.%20Does%20anyone%20have%20any%20sort%20of%20experience%20with%20making%20this%20change%20to%20subscription%20in%20an%20enterprise%20environment%3F%20How%20does%20the%20%22step-up%22%20to%20enterprise%20occur%3F%20I'm%20struggling%20to%20find%20any%20sort%20of%20information%20to%20aid%20me%20in%20troubleshooting%20where%20that%20piece%20may%20be%20failing.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-671957%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Epat.oneil%40tideworks.com%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

We recently decided to make the switch from KMS to Subscription activation for our E3 users. I've been able to successfully test this in a few different situations when I've run into a roadblock. Due to our size, we will face a struggle forcing everyone to change to their Azure AD creds (name@domain.com), so we intended to run the script Microsoft recommends for manual activation. To do this via SCCM, however, we wanted to set a configuration baseline to remediate any machines that do not make the switch by using powershell. We wrote a script that successfully activates the underlying pro license, but now these machines are not making the "step-up" to enterprise. 

I attempted to run the script MS suggests on each of these machines since, but to no avail. I have also made GPO changes and registry changes suggested on other posts but that also did not work. 

 

I opened a ticket with MS but they have, so far, only suggested changes that I have already made. Does anyone have any sort of experience with making this change to subscription in an enterprise environment? How does the "step-up" to enterprise occur? I'm struggling to find any sort of information to aid me in troubleshooting where that piece may be failing. 

0 Replies