KB
Windows Server

Changing Win Server Edition

3 min read693 words12 code blocks

At a glance#

  • Purpose: Upgrade a Windows Server installation in place from a lower edition to Standard or Datacenter.
  • Applies to: Windows Server 2012, 2012 R2, 2016, 2019 and later.
  • Risk: Medium — requires a reboot and cannot be reversed.
  • Time: About 30 minutes including reboot.

Overview#

Windows Server supports edition upgrades in place using DISM, without reinstalling. This is commonly needed when a server was built from an Evaluation ISO and the 180-day trial is expiring, or when a workload outgrows the edition it was installed with.

The keys listed below are Microsoft's public KMS client setup keys. They do not activate the server on their own — they tell Windows which edition to become. Activation happens afterwards against your KMS host or by entering a MAK/retail key.

Warning: Edition upgrades are one-way. You can go Standard → Datacenter, but never back. Downgrading requires a full reinstall. Confirm the target edition is correct, and check licensing entitlement, before proceeding.

Before you start#

  • Local Administrator rights.
  • A VM snapshot or full backup.
  • A scheduled maintenance window — the server reboots.
  • Confirmation from whoever handles licensing that the target edition is covered.
Note: An Evaluation edition cannot be converted directly to Datacenter in every version. Some paths require going to Standard first. If the conversion is refused, check the supported upgrade paths for that specific Windows Server release.

Procedure#

1. Check the current edition#

Open an elevated Command Prompt or PowerShell (right-click → Run as administrator):

powershell
DISM /online /Get-CurrentEdition

Output looks like:

text
Current edition is:
Current Edition : ServerStandardEval

An Eval suffix means this is an evaluation installation.

2. List the available target editions#

powershell
DISM /online /Get-TargetEditions

This shows only the editions this installation can legitimately be upgraded to. If your intended target is not listed, the path is not supported and a reinstall will be required.

3. Apply the edition change#

Use the key matching your Windows Server version and target edition:

Windows Server 2019 — Standard

powershell
DISM /Online /Set-Edition:ServerStandard /ProductKey:N69G4-B89J2-4G8F4-WWYCC-J464C /AcceptEula

Windows Server 2016 — Standard

powershell
DISM /Online /Set-Edition:ServerStandard /ProductKey:WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY /AcceptEula

Windows Server 2012 R2 — Standard

powershell
DISM /Online /Set-Edition:ServerStandard /ProductKey:D2N9P-3P6X9-2R39C-7RTCD-MDVJX /AcceptEula

Windows Server 2012 — Standard

powershell
DISM /Online /Set-Edition:ServerStandard /ProductKey:XC9B7-NBPP2-83J2H-RHMBY-92BT4 /AcceptEula

For Datacenter, substitute ServerDatacenter for ServerStandard and use the corresponding Datacenter KMS client key from Microsoft's published list.

The command takes several minutes. It will ask you to restart when it completes.

4. Reboot#

powershell
Restart-Computer -Force

The server may restart more than once and will sit at "Configuring Windows features" for a while. Do not power it off during this stage.

5. Activate#

The edition change does not activate Windows. After the reboot:

powershell
# Confirm licensing state
slmgr /dlv

# Activate against KMS
slmgr /ato

To apply a MAK or retail key instead:

powershell
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato

Verification#

powershell
DISM /online /Get-CurrentEdition

The Eval suffix should be gone and the edition should read ServerStandard or ServerDatacenter.

Confirm the licensing status:

powershell
slmgr /xpr

This should report that the machine is permanently activated, or give a KMS activation expiry date. Also check that services and applications came back correctly after the reboot.

Troubleshooting#

SymptomCause and fix
Error: 1168 — Element not foundThe target edition is not a supported upgrade path. Check Get-TargetEditions output.
The specified product key is invalidKey does not match this Windows Server version. Each release has its own key.
Command refuses to run on an Eval editionSome Evaluation editions must go to Standard first, then Datacenter.
Stuck at "Configuring Windows features"Normal, and can take 20+ minutes. Leave it. Only intervene after an hour.
Activation fails after the changeKMS host unreachable or not licensed for this edition. Check with slmgr /dlv and confirm DNS resolves the KMS SRV record.
Domain controller will not upgradeEdition upgrade is unsupported on a DC in some versions. Demote, upgrade, then promote again.