Windows Server evaluation licence on a VPS: limits, expiry and activating your own key

Short answer: the Windows Server evaluation is the full Standard or Datacenter edition with a time limit: Microsoft gives it 180 days, and it must be activated online within the first 10. slmgr /dlv shows the time left, and before it runs out you convert the server in place to a licensed edition with DISM /online /Set-Edition and your own product key. After expiry Windows keeps running but shuts itself down at intervals.

This is the licence your server starts with when Windows Server 2022 or 2019 is installed from a hosting provider’s template without a licence in the price, which is how a Windows VPS at VMHeaven is set up. It is not a trap and not a trial in the consumer sense. It is a documented Microsoft mechanism with clear limits. Below is everything you need to know about it: how long it lasts, how to check, what happens at the end, and how to move to your own licence without reinstalling.

What is the Windows Server evaluation edition?

Microsoft publishes evaluation versions of Windows Server 2022 and 2019 on its Evaluation Center. The page for each version states the terms plainly: the evaluation ISO covers the Standard and Datacenter editions, the evaluation expires after 180 days, and it has to be activated over the internet within the first 10 days, or the server starts shutting itself down.

• It is the real edition. The evaluation ISO carries the full Standard and Datacenter editions, and turning one into a licensed edition later happens in place, without a reinstall. What you set up during the evaluation is what you keep.
• It names itself. The edition ID ends in Eval, for example ServerDatacenterEval or ServerStandardEval. That suffix decides which licensed editions you can convert to later.
• Two clocks, not one. First the 10-day window to activate the evaluation online. Once that has happened, the 180 days.

How do I see how many days are left?

Open PowerShell or a command prompt as Administrator. These commands only read; they change nothing.

slmgr /dlv                          # detailed licence information
slmgr /xpr                          # just the expiry date
DISM /online /Get-CurrentEdition    # the edition ID: ...Eval means evaluation

# slmgr answers in a pop-up window; to get the text in the console instead:
cscript //nologo C:\Windows\System32\slmgr.vbs /dlv

In the slmgr /dlv output, three lines matter:

• Description contains TIMEBASED_EVAL on an evaluation.
• License Status should say Licensed. A grace period instead means the evaluation has not been activated online yet, which is common on a freshly deployed server. Run slmgr /ato now, because that is the 10-day clock.
• Remaining Windows rearm count is how many times this installation can still be rearmed.

If you prefer a number to a dialog box, ask the licensing service directly. GracePeriodRemaining is in minutes, so dividing by 1440 gives days:

Get-CimInstance SoftwareLicensingProduct -Filter "PartialProductKey IS NOT NULL AND ApplicationID='55c92734-d682-4d71-983e-d6ec3f16059f'" |
  Select-Object Name, Description, LicenseStatus,
    @{n='DaysLeft'; e={[math]::Round($_.GracePeriodRemaining / 1440, 1)}}

LicenseStatus 1 means licensed (for an evaluation: activated and counting down the 180 days). 2 is the initial grace period before activation. A status of 0 or 5 (unlicensed, notification), or zero days left, means the licence has run out. Microsoft’s slmgr reference documents every option used here.

What happens when the evaluation expires?

Windows does not delete anything and does not lock you out. It starts shutting itself down. The Windows Licensing Monitoring Service (WLMS) writes the reason into the Application event log in plain words: The license period for this installation of Windows has expired. The operating system will shut down every hour.

Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='WLMS'} -MaxEvents 5 |
  Format-List TimeCreated, Message

In practice that means RDP sessions cut off mid-work, services that stop without a clean shutdown and scheduled tasks that never run. The server is still yours and still boots, and the shutdowns stop once it runs a licensed, activated edition. So the conversion below works after expiry too; you just have less than an hour per attempt.

The simplest way not to get there by surprise: run slmgr /xpr once after activating, and put the date it prints in your calendar, a couple of weeks early.

Can I extend the evaluation?

Technically, a limited number of times. slmgr /rearm, followed by a restart, resets the activation timers. Microsoft’s slmgr documentation describes it in one line and adds that sysprep /generalize calls the same rearm. A server deployed from a generalized image may therefore have used some of its rearms before you ever logged in. The number that counts is the Remaining Windows rearm count in slmgr /dlv on your own machine, not a figure from a forum.

slmgr /dlv          # check "Remaining Windows rearm count" first
slmgr /rearm
Restart-Computer

Keep in mind what it is for. The evaluation exists so you can evaluate Windows Server, and rearming exists for test and imaging scenarios. For a server you depend on, the clean answer is a licence. The terms that apply to your installation are linked from winver (“Microsoft Software License Terms”).

How do I convert the evaluation to Standard or Datacenter with my key?

Microsoft documents an in-place conversion in Convert Windows Server editions and license types. No reinstall, and your data, roles and settings stay. There are rules about which edition can become which, and they are the part people get wrong:

• A Standard evaluation with Desktop Experience can become retail Standard or Datacenter. Server Core evaluations have their own exceptions, which is one more reason to trust Get-TargetEditions over any list.
• A Datacenter evaluation can only become retail Datacenter, not Standard.
• A Desktop Experience evaluation cannot become a Server Core edition.
• An Active Directory domain controller running an evaluation cannot be converted at all. Microsoft’s route is a new domain controller on a licensed server, then moving the roles over.

1. 1Open the console and take a backup

   The conversion restarts the server, sometimes more than once, and RDP drops each time. Keep the VNC console from the panel open in another tab so you can watch it, and take a backup first.

2. 2Check the current edition and the allowed targets

   DISM /online /Get-CurrentEdition     # e.g. ServerDatacenterEval
   DISM /online /Get-TargetEditions     # e.g. ServerDatacenter

   Only editions in the second list are possible. If the one your key is for is not there, an in-place conversion cannot reach it.

3. 3Read the licence terms (optional, but it is your licence)

   DISM /online /Set-Edition:ServerDatacenter /GetEula:C:\license.rtf

4. 4Convert with your key

   DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

   Replace ServerDatacenter with the target from step 2 and the X groups with your retail key. Let DISM finish and restart when it asks. It can take a while, and the server may reboot more than once while it applies the change.

5. 5Activate and verify

   slmgr /ato                          # activate online
   slmgr /dlv                          # License Status: Licensed, no TIMEBASED_EVAL
   DISM /online /Get-CurrentEdition    # no Eval suffix any more

What about volume licence (MAK) keys?

Microsoft’s documented order is: convert the evaluation to the retail edition first, then switch the licence type with slmgr /ipk and your volume (MAK) or OEM key, and activate with slmgr /ato. If you are unsure which key to use for the conversion step, ask whoever issued your licence before you start.

Which licence may I use on a rented server?

Whether a key may run on hardware you rent from a hosting company is a question of Microsoft’s licence terms, not of whether DISM accepts it. A key that activates is not, on its own, proof that its licence covers this use. One documented example: Microsoft’s Flexible Virtualization Benefit lets customers with subscription licences or licences with active Software Assurance deploy them on an “Authorized Outsourcer’s” servers, shared or dedicated. It excludes the “Listed Providers” Microsoft names at aka.ms/listedproviders.

Other licence types have their own terms, and we cannot tell you which ones apply to your key. Ask the reseller or Microsoft partner who sold it. Our support can tell you exactly what the server runs and help with the technical side of the switch.

Do you need Windows at all?

If Windows is there only because a guide assumed it, check first. Web servers, bots, VPNs, game servers and most automation run on Linux, which needs no licence at all. Windows earns its place when you need a desktop, Windows-only software or Microsoft’s server roles. Our comparison of RDP and a Linux VPS walks through that decision.

If you do keep Windows, the next jobs are the same either way: securing the RDP server, moving RDP off port 3389 and, if the server needs one, running a VPN without cutting off RDP.

Frequently asked