[ad_1]
It’s a question that’s come up a number of times: How can I take a device running Windows 11 Home, upgrade it to Windows 11 Education, and provision it via Windows Autopilot? I suppose we should start off with a more basic question: Why?
For devices that ship with Windows 11 Pro, they are all set to use Windows Autopilot. Maybe you want to change them over to Windows 11 Enterprise, but that can be done using subscription activation, or after the fact by pushing out a new product key; the SKU change is immediate due to the behavior of virtual SKUs (or virtual editions, if you prefer that term). You can’t go from Windows 11 Home to Windows 11 Enterprise directly because Windows 11 Home is not a qualifying OS per the Enterprise licensing terms, so you’d have to do it in two hops: Windows 11 Home to Pro using a retail product key (e.g. buy a key online or from a reseller, use a different key per device), then Pro to Enterprise via subscription activation. But for the pain and cost of it, it’s easier to just buy a device with Pro preinstalled.
But things are different in the case of Education: Windows 11 Home is a qualifying OS per the Education SKU license terms. So education customers can save money by buying a device with Home preinstalled, knowing that they are within their rights (assuming they have an appropriate Windows or Microsoft 365 subscription, e.g. Windows Education A3) to upgrade that device to the Education SKU. But how can they do that? The Home SKU is not a virtual edition, so you can’t just inject a new product key and have it instantly change. There are other options, e.g.:
- In-place upgrade from Windows 11 Home to Windows 11 Education using media. Easy enough to do, but takes a long time.
- Wipe-and-load with a new Windows 11 Education image. Not as easy to do as you have to worry about drivers, OS settings, etc.
- Entering a new Windows 11 Education product key in the Settings app. This is probably the easiest, since you can just use the generic key for the Education SKU (documented here), NW6C2-QMPVW-D7KKK-3GKT6-VCFB2.
If you want to try the “change product key option”, you can go into Settings (which you can launch from a Shift-F10 command prompt by running the “start ms-settings:” command) and search for “change product key” (or navigate to System -> About -> Product key and activation):
But what if you wanted to streamline and automate the process? Fortunately, the underlying “changepk.exe” utility that Settings uses has some undocumented switches to run it without any user input. A simple “changepk.exe /ProductKey NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 /NoUI” command will make the change. Weirdly, the automatic reboot fails (even though you will see an event log entry that says the reboot was initiated), so we can add the “/NoReboot” switch (also undocumented) and then initiate the reboot ourselves. If we integrate that into the Get-WindowsAutopilotInfoCommunity.ps1 script, we can do all of that as part of the device registration process. Starting off with Home:
After the reboot, we see that we are indeed now running Education. (It still needs to be activated, so you would either need to push out a MAK key to the device or set up a KMS server for the device to activate against.)
Can you use other product keys to go to other Windows editions? Sure, but make sure you are properly licensed for that.
The Get-WindowsAutopilotInfoCommunity script has been updated on the PowerShell Gallery to include this logic. (Thanks again to Andrew Taylor for quickly approving my PR and updating the PowerShell Gallery.)
[ad_2]
Source link
