The Settings trick that fixes one PC becomes a week of desk visits at fifty. Organisations change editions the way they do everything else — with licensing first, a target state, and tooling that pushes it. This page is the honest map of the fleet routes, so you stop scaling a manual trick and start planning a rollout.
Everything in this batch's single-PC pages still applies — supported paths, genuine keys, activation as a separate step. What changes at fleet scale is the delivery mechanism and the licence bookkeeping. Nobody should type keys at fifty desks. Here are the routes real IT departments use, in the order they usually consider them.
👆 Four fleet routes, one principle — the edition follows the licence system, not a person with a key list walking the floor.
Fleet work starts on paper, not on a PC. Count the machines, record each one's current edition (a discovery tool or a script running DISM /Online /Get-CurrentEdition across the fleet does this in minutes), and match the count against what your volume agreement or subscription actually covers. The gap between 'PCs we have' and 'Enterprise rights we hold' is the purchase conversation, and it must happen before the rollout, not during an audit after it. Simultaneously, list the machines on unsupported paths — Home PCs and LTSC boxes — because they will not convert in place no matter what you push at them.
If the organisation holds Enterprise E3 or E5 per-user licences, the lightest rollout exists: assign the licences to users, and when those users sign in to a qualifying Pro PC with their work account, Windows steps the PC up to Enterprise and activates it against the subscription — no key typed anywhere. It is also self-correcting in reverse: move the licence away, and after its grace period the PC reverts to its underlying edition. For subscription shops this is not a project; it is a licence assignment.
For KMS and MAK estates, the edition change itself is delivered as configuration: MDM policies and provisioning packages can carry an edition upgrade to enrolled devices, and the humble scripted route — the same DISM /Online /Set-Edition command from this batch, deployed through your existing software distribution — covers the rest. Whichever carrier you choose, the pattern is identical: pilot on five machines, verify edition and activation, then widen in rings. Keys live in the licence portal and the deployment system, never in a spreadsheet emailed around the team.
PCs that are being refreshed anyway should not be converted at all — they should be imaged directly as Enterprise from your deployment system, landing on the right edition with the GVLK already in the image. That is the deeper point of the fleet route: at scale, activation stops being a per-PC event. Your KMS host or Active Directory activation vouches for every domain PC automatically, MAK covers the strays that never touch the network, and the helpdesk's edition questions shrink to the genuinely odd machines. Build the backbone first; the edition changes then become the easiest rollout you run all year.
Start with the single-PC process in the video to understand the mechanics — then scale it with the routes on this page.
▶️ Watch Full VideoNot by hand. Subscription shops assign Enterprise E3 or E5 licences and PCs upgrade themselves when licensed users sign in. Volume shops push the edition change through MDM policies, provisioning packages or scripted DISM commands in rings, and new machines are imaged as Enterprise directly. Activation runs through a KMS host or Active Directory, so no keys are typed at desks.
No. Fleet PCs carry the published KMS client setup key (GVLK), which is identical for everyone and holds no rights, and activate against the organisation's KMS host. Alternatively they activate through Active Directory or through users' Enterprise subscriptions. The only typed-key route, MAK, is reserved for machines that never reach the office network.
Three things: an inventory of current editions across the fleet, confirmation that your agreement or subscription covers every PC you plan to convert, and a list of machines on unsupported in-place paths — Home editions and LTSC — which need a different plan such as imaging. Pilot on a handful of machines and verify both edition and activation before widening.