# Convert Evaluation Edition to Full Windows Server: DISM Steps for 2025

Source: https://srvscripts.com/guides/windows-server-convert-evaluation-edition/
Updated: 2026-10-03
Publisher: srvScripts (https://srvscripts.com/)

You can convert evaluation edition installations of Windows Server 2016, 2019, 2022 and 2025 into fully licensed Standard or Datacenter editions with one DISM command, without reinstalling the server or losing roles, applications and data. The same command also moves a licensed Standard server to Datacenter. This guide covers checking the current edition, the conversion itself, which product key to use (retail, MAK or KMS client key), the domain controller limitation, and how to fix activation afterwards.

**Short answer:** From an elevated prompt, run `DISM /online /Get-CurrentEdition` (it shows, for example, `ServerStandardEval`) and `DISM /online /Get-TargetEditions`. Then run `DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula` with a key for the target edition, and restart when asked. Activate with `slmgr /ato` and confirm with `slmgr /dlv`. A domain controller cannot be converted: build a licensed DC and demote the evaluation one.

In short: From an elevated prompt, run DISM /online /Get-CurrentEdition (it shows, for example, ServerStandardEval) and DISM /online /Get-TargetEditions.

## Why convert instead of reinstalling

Evaluation media is the quickest way to get Windows Server running: no key is needed during setup, and the download is freely available from Microsoft’s Evaluation Center. Many servers that start as a test end up in production with roles, data and applications configured. Reinstalling at that point costs hours of work, so it makes sense to convert evaluation edition servers in place.

The evaluation period is 180 days. `slmgr /rearm` resets activation timers, but it does not turn the evaluation into a licensed product and it is not a licensing strategy for production. Converting also matters for upgrades: Microsoft does not support upgrading from or to an evaluation copy, so an evaluation server must be converted before a later in-place upgrade to a newer version.

## Which method to use

| Goal | Method | Restart | Notes |
| --- | --- | --- | --- |
| Evaluation to licensed Standard or Datacenter | DISM /online /Set-Edition | Yes | Not possible on a domain controller |
| Standard to Datacenter (licensed) | DISM /online /Set-Edition:ServerDatacenter | Yes | One-way; Datacenter cannot go back to Standard |
| Change licence channel (retail, MAK, KMS) on the same edition | slmgr /ipk then slmgr /ato | No (restart of the licensing service advised) | Edition stays the same |
| Evaluation domain controller | New licensed DC, move FSMO roles, demote the evaluation DC | n/a | Microsoft does not support converting an evaluation DC |
| Desktop Experience to Server Core, or the reverse | Clean install | n/a | No conversion between installation options |

## Prerequisites

- Windows Server 2016, 2019, 2022 or 2025 evaluation (or licensed Standard for an edition upgrade).

- A product key for the target edition and version. A Windows Server 2025 Standard key will not convert a 2022 evaluation.

- An elevated Command Prompt or PowerShell session with local administrator rights.

- A backup or VM checkpoint, and a maintenance window: the server restarts, sometimes twice.

- The server must not be a domain controller. Check with `Get-CimInstance Win32_ComputerSystem | Select-Object DomainRole`; values 4 and 5 mean backup and primary DC.

Conversion rules from Microsoft:

- Evaluation Standard can become Standard or Datacenter.

- Evaluation Datacenter can only become Datacenter.

- Since Windows Server 2016, an evaluation installed with Desktop Experience cannot become Server Core (and the reverse). Only the edition changes.

## Checklist for production servers

Before you convert evaluation edition servers that already run production workloads, run through this list:

- **Confirm the role.** DCs cannot be converted; failover cluster nodes should be converted one node at a time, with roles drained first.

- **Match version, edition and key.** Note the output of `/Get-CurrentEdition` and the version from `winver`, and check that the key is for exactly that version and the target edition.

- **Take a checkpoint or backup.** The conversion rarely fails, but a checkpoint turns a failure into a five-minute rollback.

- **Plan the restart.** Services on the server stop during the restart; move VMs off Hyper-V hosts or schedule the window.

- **Check activation reachability.** For KMS, confirm DNS and TCP 1688 from the server; for MAK or retail, confirm outbound internet access or plan phone activation.

- **Record licence ownership.** Note which licence or agreement covers the server, so audits do not rely on memory.

## Step 1: check the current edition

```
DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
slmgr /dlv
```

Typical output:

| Edition ID | Meaning |
| --- | --- |
| ServerStandardEval | Windows Server Standard Evaluation |
| ServerDatacenterEval | Windows Server Datacenter Evaluation |
| ServerStandard | Windows Server Standard (licensed) |
| ServerDatacenter | Windows Server Datacenter (licensed) |

`/Get-TargetEditions` lists what this installation can become, for example `ServerStandard` and `ServerDatacenter`. `slmgr /dlv` shows “EVAL” in the description and the remaining time on an evaluation. `slmgr /xpr` prints the expiry date in a dialog.

## Step 2: choose the product key

The key must match the target edition and Windows Server version. You have three options:

- **Retail or OEM key**, from a boxed licence or your hardware vendor. Microsoft’s own conversion example uses a retail key.

- **MAK** (Multiple Activation Key) from the Microsoft 365 admin center or your volume licensing portal. It activates online against Microsoft.

- **KMS client setup key (GVLK)**, used when a KMS host or Active Directory-based activation exists in your network. Microsoft publishes these keys on its KMS client activation keys page; they are not secret and do not activate anything by themselves.

| Version and edition | KMS client setup key (GVLK) |
| --- | --- |
| Windows Server 2025 Standard | TVRH6-WHNXV-R9WG3-9XRFY-MY832 |
| Windows Server 2025 Datacenter | D764K-2NDRG-47T6Q-P8T8W-YP6DF |
| Windows Server 2022 Standard | VDYBN-27WPP-V4HQT-9VMD4-VMK7H |
| Windows Server 2022 Datacenter | WX4NM-KYWYW-QJJR4-XV3QB-6VM33 |

Always check the current list on Microsoft’s page (linked below) before use. Some product keys, such as certain CSP perpetual keys, are rejected by DISM during the conversion with “The specified product key could not be validated”. Hardware vendors document a two-step workaround: convert evaluation edition installs with the GVLK for the target edition first, then replace it with your real key using `slmgr /ipk` after the restart.

## Step 3: convert evaluation edition to Standard or Datacenter

- Optionally save the licence terms for your records:

```
DISM /online /Set-Edition:ServerStandard /GetEula:C:\Temp\license.rtf
```

- Run the conversion (Standard example):

```
DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
```

For Datacenter, use `/Set-Edition:ServerDatacenter` with a Datacenter key.

- Wait. The progress bar can pause for several minutes; do not interrupt it or close the window.

- When DISM asks to restart, type Y. The server applies the new edition during the restart and may restart once more.

- Sign in and confirm the new edition with `DISM /online /Get-CurrentEdition`.

When you convert evaluation edition servers this way, roles, features, applications, data and domain membership are kept. The server name and IP configuration do not change.

## What changes after the conversion

- The edition ID changes (for example from `ServerStandardEval` to `ServerStandard`) and the evaluation timer is removed once the server activates.

- The build number, installed updates, roles, features and drivers stay the same. Windows Update continues as before; no feature update is involved.

- After a Standard to Datacenter change, Datacenter-only features such as Storage Spaces Direct and Storage Replica without limits become available to install.

- Nothing changes in Active Directory: the computer account, group memberships and GPOs that apply to the server are unaffected.

Once you convert evaluation edition servers, update your inventory or CMDB so the edition and licence type are recorded correctly.

## Step 4: activate

How activation happens depends on the key you used:

```
REM Retail or MAK key: activate online
slmgr /ato
REM GVLK with a KMS host found through DNS: activate against KMS
slmgr /ato
REM GVLK with a specific KMS host
slmgr /skms kms01.contoso.com:1688
slmgr /ato
REM Replace the GVLK used for conversion with your real key
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
REM Check the result
slmgr /dlv
```

`slmgr /ipk` silently replaces any installed key; Microsoft recommends restarting the server or the Software Protection service afterwards. On Windows Server 2025 with Desktop Experience you can also check the status in **Settings » System » Activation**.

## Server Core and remote conversion

The DISM commands are identical on Server Core. Sign in at the console or through `sconfig` option 15 (exit to PowerShell), run the same commands, and answer the restart prompt. For several servers, add `/NoRestart` and control the restart yourself through PowerShell remoting:

```
$servers = 'APP01','APP02','APP03'
Invoke-Command -ComputerName $servers -ScriptBlock {
  DISM /online /Set-Edition:ServerStandard /ProductKey:TVRH6-WHNXV-R9WG3-9XRFY-MY832 /AcceptEula /NoRestart /Quiet
  "$env:COMPUTERNAME exit code: $LASTEXITCODE"
}
Restart-Computer -ComputerName $servers -Wait -For PowerShell -Force
```

Exit code **3010** means the operation succeeded and a restart is required. Afterwards, run `Invoke-Command -ComputerName $servers { DISM /online /Get-CurrentEdition }` to confirm each server changed. The example uses the Windows Server 2025 Standard GVLK and therefore expects a KMS host or Active Directory-based activation; replace it with your MAK or retail key where that applies.

## Activate with KMS or Active Directory-based activation

If you converted with a GVLK, the server needs something to activate against:

- **KMS host:** a server with the **Volume Activation Services** role (`Install-WindowsFeature VolumeActivation -IncludeManagementTools`) and a KMS host key (CSVLK) that covers Windows Server 2025. It publishes an `_vlmcs._tcp` SRV record in DNS and listens on TCP 1688. KMS activates Windows Server clients only once at least five KMS clients have contacted it.

- **Active Directory-based activation:** the activation object lives in the forest, so domain-joined servers with a GVLK activate automatically with no KMS count threshold. Set it up once with the Volume Activation Tools or `slmgr /ad-activation-online <CSVLK>`; `slmgr /ao-list` shows the activation objects the server can see.

An existing KMS host whose key only covers older Windows Server versions cannot activate Windows Server 2025 until you install a newer CSVLK on it.

## Convert Standard to Datacenter

A licensed Standard server can move up to Datacenter in place, for example when a Hyper-V host needs to run more than two Windows Server VMs:

```
DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
```

This is one-way: there is no supported path from Datacenter back to Standard short of reinstalling. The Datacenter: Azure Edition is not a target for this conversion on regular servers; it has its own installation and hosting requirements.

## Evaluation domain controllers

Microsoft states that you cannot convert an Active Directory domain controller from an evaluation to a retail version. If an evaluation server was promoted to a DC, you have two routes:

### Route A: replace the DC (recommended)

- Install a licensed Windows Server (or convert a non-DC evaluation server first), join it to the domain and promote it to a DC with DNS and global catalog.

- Move the FSMO roles: `Move-ADDirectoryServerOperationMasterRole -Identity DC02 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster`.

- Point clients and DHCP scopes to the new DC for DNS.

- Demote the evaluation DC with `Uninstall-ADDSDomainController` and remove the AD DS role.

### Route B: demote, convert, re-promote

If you have at least one other DC, you can demote the evaluation DC to a member server, convert evaluation edition to the licensed edition with DISM, and promote it again. Move its FSMO roles and DNS clients to the other DC first. With a single DC this route is not available; use Route A.

## Licensing notes

- The evaluation is intended for testing and lasts 180 days. Do not run production workloads on it beyond that; convert evaluation edition servers as soon as they become production systems.

- Standard and Datacenter are licensed per physical core, with minimums per processor and per server, plus Client Access Licences (CALs) for users or devices. Standard covers two operating system environments (VMs) per fully licensed host; Datacenter covers unlimited VMs on that host.

- Converting the edition does not grant a licence. The key you enter must come from a licence you own, from your volume licensing agreement, or from your hosting provider.

- Windows Server 2025 can also be licensed pay-as-you-go through Azure Arc, which is billed through Azure rather than a product key.

## Verify it works

```
DISM /online /Get-CurrentEdition
slmgr /dli
slmgr /xpr
Get-CimInstance SoftwareLicensingProduct -Filter "PartialProductKey IS NOT NULL AND Name LIKE 'Windows%'" |
  Select-Object Name, Description, LicenseStatus
```

`LicenseStatus` **1** means licensed. The description should no longer contain “EVAL”, and `slmgr /xpr` should say the machine is permanently activated (retail or MAK) or show a KMS renewal date about 180 days ahead.

## Troubleshooting

| Error or symptom | Cause | Fix |
| --- | --- | --- |
| DISM refuses to run on the server | It is a domain controller | Replace or demote the DC first (see above) |
| “The specified product key could not be validated” | Key for another edition or version, or a key type DISM rejects | Check the key matches the target edition; convert with the GVLK, then slmgr /ipk the real key |
| Target edition missing from /Get-TargetEditions | Evaluation Datacenter cannot become Standard | Use a Datacenter key, or reinstall with Standard |
| 0xC004F074 after slmgr /ato | No KMS host could be contacted | Check nslookup -type=srv _vlmcs._tcp.contoso.com, TCP 1688, or set slmgr /skms |
| 0x8007232B | DNS name does not exist: no KMS SRV record | Publish the KMS record or use slmgr /skms; or install a MAK |
| 0xC004F050 | Invalid product key | Re-enter the key; check version and edition |
| 0xC004C003 | Key blocked by the activation server | Obtain a valid key from your licensing portal |
| Still shows EVAL after restart | Conversion did not finish | Run DISM again; check C:\Windows\Logs\DISM\dism.log |

## Roll back or undo

There is no supported way to return from Standard or Datacenter to the evaluation edition, or from Datacenter to Standard. If a conversion fails part-way or you picked the wrong edition, restore the VM checkpoint or backup taken before you started. When you only installed the wrong key, you can remove it with `slmgr /upk` and install the correct one with `slmgr /ipk`; this changes the licence channel, not the edition.

## Convert evaluation edition at a glance

**Official documentation:** [Convert Windows Server evaluation, edition and license types](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-conversion-options), [KMS client activation and product keys](https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys), [Slmgr.vbs options for volume activation](https://learn.microsoft.com/en-us/windows-server/get-started/activation-slmgr-vbs-options).

**Related guides:** [In-place upgrade to Windows Server 2025](/guides/windows-server-2025-in-place-upgrade/) · [Transfer FSMO Roles with PowerShell and ntdsutil: Safe Steps](/guides/transfer-fsmo-roles-powershell/) · [Install and promote a Windows Server 2025 domain controller step by step](/guides/windows-server-2025-domain-controller/).

## Frequently asked questions

### Can I convert Windows Server evaluation to a full version without reinstalling?

Yes. Run DISM /online /Set-Edition with the target edition (ServerStandard or ServerDatacenter), a product key for that edition and /AcceptEula, then restart. Roles, applications and data are kept.

### Can I convert an evaluation domain controller?

No. Microsoft does not support converting an evaluation DC. Promote a licensed DC, move the FSMO roles, and demote the evaluation DC, or demote it, convert it and promote it again if another DC exists.

### Can I use a KMS client key (GVLK) to convert the evaluation edition?

Yes, the GVLK for the target edition is commonly used for the conversion, and hardware vendors document it as a workaround when other keys are rejected. After the restart, activate against your KMS host or install your MAK or retail key with slmgr /ipk.

### Can Evaluation Datacenter become Standard?

No. Evaluation Datacenter can only be converted to licensed Datacenter. Evaluation Standard can become either Standard or Datacenter.

### How do I check whether Windows Server is an evaluation?

Run DISM /online /Get-CurrentEdition and look for an edition ID ending in Eval, or run slmgr /dlv and look for EVAL in the description and a time-based expiration.