You might be looking into the possibility to convert the Windows Server Evaluation edition to the retail edition. We'll look at how to install a license key to transform Windows Server 2019 from the Evaluation version to the retail one.

Vladan Seget

Vladan Seget is as an independent consultant, professional blogger, vExpert 2009-2018, VCAP-DCA/DCD, VCP, and MCSA. He has been working for over 20 years as a system engineer.

Microsoft calls this license conversion. In some releases of Windows Server, you can also freely convert among OEM, volume-licensed, and retail versions with the same command and the appropriate key.

Cases in which you run an evaluation and then need to convert it to retail are numerous. Yes, this is really useful for environments created for a proof-of-concept (POC) purpose that then decide to go to production. In such cases, it's a great time-saver because you don't have to start from scratch.

Some features of Windows Server 2019 need the Datacenter edition instead of the Standard edition installed. You should know you can also convert the Standard to the Datacenter edition without reinstalling, and this post will show you how.

The possibility of converting a Microsoft OS isn't new, but previously, back in the day, this was not really possible.

Although in this post we'll focus only on converting licenses or editions, you might be looking also for upgrade options. There's support for some use cases but not others.

Supported and unsupported cases ^

There are situations when an upgrade won't work. Let's have a look.

If you think that upgrading between server versions is easy, it might be in some situations. You should not underestimate it. But you need to be aware of some considerations first.

Here are a couple of known facts about upgrading from a previous release of Windows Server (WS 2012 or WS 2016):

  • There's no support for upgrading from one language to another. You'll have to upgrade to the same language. You can then change the language UI only.
  • If you have a domain controller (DC), you'll need to run a Forestprep and Domainprep prior to the upgrade. You should follow the usual Microsoft checklist concerning DCs before the upgrade.
  • There's no support for converting the Core edition to Server with the UI, even though some sources have been saying Microsoft will finally implement this in WS 2019. They have not.
  • You can't downgrade from Standard back to Eval. There's no support for upgrading from a previous Windows Server installation to an evaluation copy. You can and should install evaluation versions as clean installs.
  • You can convert the evaluation version of Windows Server 2019 Standard to either Windows Server 2019 Standard (retail) or Datacenter (retail).

Upgrade Windows Server 2019 Evaluation to Full ^

If you have installed Windows Server 2019 StandardEvaluation or DatacenterEvaluation, you have essentially only 180 days to test any features of the new server platform version. This might be enough for some but not for others.

During this period, all features of Windows Server 2019 are fully working and available. However, after the trial period is over, the system starts to ask for activation and powers down every hour. This is quite annoying.

The Windows License expiration notice displays on regular basis.

This edition cannot be upgraded

This edition cannot be upgraded

First, check the version that's running with this command:

You'll see a message about the edition you currently have.

Get the current edition

Get the current edition

Now we can get the list of editions you can convert your current Eval edition to:

And you should get this output:

Get target editions

Get target editions

To upgrade to the edition you want, you can run a PowerShell command to perform the actual edition upgrade. You'll need, however, a valid serial number to do this.

Run this command:

So to upgrade from Eval to Standard, use this command:

From Eval to Datacenter, use this command:

You'll get a prompt to reboot the server during which the server will change its edition.

The server will run through the image-conversion process and then restart twice. After the server reboots, you'll need to reactivate it and enter the key again.

How to convert the Standard edition to Datacenter ^

This is basically the same process as above. The main difference is the system we're on is on Standard already, not Eval.

We'll be using PowerShell, even if apparently other ways exist. From an elevated command prompt, use this command:

You'll see a message about the edition you currently have.

Get the current edition Standard

Get the current edition Standard

Then simply run this command, which is the same as the one to go from Eval Standard to Datacenter:

You must enter a valid product key to continue with the upgrade process. It'll ask you to reboot.

It's worth noting that if you've used an evaluation edition to build a DC for your POC, you can't change the edition. You'll either need to build a new DC, demote the evaluation edition DC, or convert Eval to Standard (or Datacenter) and then promote it again for a DC.

You can also use this command to change your edition between other types, such as Datacenter or Essentials.

By simply running a few PowerShell commands, you can check the currently installed edition, see which version you can upgrade to, and also run the actual upgrade PowerShell command.

Win the monthly 4sysops member prize for IT pros


Users who have LIKED this post:

  • avatar
  • avatar
  1. Leos Marek 4 months ago

    Hello Vladan,

    Id say you can still use the KMS keys for upgrade/edition change the environment uses KMS activation.


  2. Mike Kanakos 4 months ago

    Hi vladan,


    You didn't mention but I think you can also extend the trial period of server o/s using the rearm switch of slmgr . 

    Patrick Gruenauer has a good write up on his site:



  3. Author
    Vladan Seget 4 months ago

    Mike, absolutely. Rearm is another option. Thanks for the mention.


  4. Daniel 4 months ago

    Sadly, Eval Standard (ServerStandardEvalCor) to ServerStandardCor doesn't seem to work as well... thank you for reimplement this bug from 2016 Microsoft... you lazy developers!


  5. Rob 4 months ago

    V helpful blog Vladan, thanks, merci, hvala.


  6. Sanan 2 months ago

    Hi Vladan,

    Thank you so much for the helpful article. Question, the product key has to be retail, or can we use an OEM key?



  7. Author
    Vladan Seget 2 months ago

    I'd say that OEM is attached to the hardware you're installing. So if you reinstalling to the hardware you've bought the WS with, you'll be fine. Perhaps a phone call to Microsoft is necessary (for activation) as it was the case back in the days with XP? 


  8. Marko Vukovic 1 week ago

    This does not work for MAK keys unfortunately. 


Leave a reply

Your email address will not be published. Required fields are marked *


© 4sysops 2006 - 2019


Please ask IT administration questions in the forums. Any other messages are welcome.


Log in with your credentials


Forgot your details?

Create Account