How to Convert Windows Server Evaluation to Standard or Datacenter (2019, 2022, 2025)
Convert Windows Server 2019, 2022, and 2025 Evaluation editions to Standard or Datacenter with the right GVLK keys, DISM /Set-Edition, and KMS activation.
This guide explains the correct and Microsoft-supported way to convert Windows Server Evaluation editions to Standard or Datacenter for Windows Server 2019, 2022, and 2025.
It is written for:
- Public cloud providers
- OpenStack / KVM environments
- SPLA / KMS-based licensing
- Automated VM provisioning workflows
No retail or MAK keys are required for the conversion step.
1. Why Evaluation Conversion Fails for Many Users
Common mistakes:
- Using retail or MAK keys on Evaluation editions
- Using a 2019 key on 2022/2025
- Attempting activation before edition conversion
- Mixing KMS client keys with DISM incorrectly
Important rule:
Evaluation then Full edition conversion must be done using the correct Generic Volume License Key (GVLK) for the OS version and edition.
2. Identify Your Windows Server Version
Run:
DISM /Online /Get-CurrentEdition
Or check build number:
winver
| Build | Windows Version |
|---|---|
| 17763 | Server 2019 |
| 20348 | Server 2022 |
| 26100+ | Server 2025 |
3. Supported Conversion Keys (GVLK)
These keys are public, Microsoft-documented, and intended for KMS/SPLA environments.
Windows Server 2019
| Edition | GVLK |
|---|---|
| Standard | N69G4-B89J2-4G8F4-WWYCC-J464C |
| Datacenter | WMDGN-G9PQG-XVVXX-R3X43-63DFG |
Windows Server 2022
| Edition | GVLK |
|---|---|
| Standard | VDYBN-27WPP-V4HQT-9VMD4-VMK7H |
| Datacenter | WX4NM-KYWYW-QJJR4-XV3QB-6VM33 |
Windows Server 2025
| Edition | GVLK |
|---|---|
| Standard | TVRH6-WHNXV-R9WG3-9XRFY-MY832 |
| Datacenter | D764K-2NDRG-47T6Q-P8T8W-YP6DF |
4. Convert Evaluation then Standard or Datacenter
Example: Convert to Standard
DISM /Online /Set-Edition:ServerStandard /ProductKey:<GVLK> /AcceptEula
Example: Convert to Datacenter
DISM /Online /Set-Edition:ServerDatacenter /ProductKey:<GVLK> /AcceptEula
Replace <GVLK> with the correct key from Section 3.
5. Reboot (Mandatory)
After DISM completes successfully:
shutdown /r /t 0
The edition change is finalized only after reboot.
6. Activate Using KMS (SPLA / Cloud Providers)
After reboot, point the server to your KMS host:
slmgr /skms kms.yourdomain.local
slmgr /ato
Activation will succeed once:
- KMS host is licensed
- Minimum activation threshold is met
7. Verify Status
DISM /Online /Get-CurrentEdition
slmgr /dlv
Expected output:
- Edition:
ServerStandardorServerDatacenter - License Status:
Licensed - Activation Channel:
VOLUME_KMSCLIENT
8. Automation Notes (OpenStack / Cloudbase-Init)
For cloud environments:
- Perform conversion once on the golden image
- Sysprep after conversion
- Use KMS activation at first boot via cloud-init or Cloudbase-Init
Never ship Evaluation images to production tenants.
9. Compliance Notes for Providers
- GVLK keys are not licenses
- Licensing is enforced via SPLA / CSP reporting
- This method is fully Microsoft-compliant
- Retail or MAK keys must not be used for tenant VMs
10. Common Errors and Causes
| Error | Cause |
|---|---|
0x8a010101 | Retail/KMS key used on Eval |
1605 | Wrong OS version key |
| Activation fails | KMS threshold not met |
| Edition unchanged | Reboot skipped |
Conclusion
Converting Windows Server Evaluation editions correctly requires:
- Matching OS version
- Correct GVLK
- DISM-based edition change
- KMS activation after reboot
This approach scales cleanly for public clouds, OpenStack, and SPLA environments and avoids licensing violations.