"BYOL" shows up on every Windows VPS page and rarely gets explained. Here is the whole thing, honestly: what the licence is, why the image starts as Evaluation, how to activate, how to switch editions without reinstalling, and which keys are actually allowed on a rented server.
Why the image is Evaluation
When you deploy a Windows plan, the machine boots Windows Server 2022 Standard (Desktop Experience) from a clean image — with the virtio drivers and guest agent already in place, so RDP and the console work out of the box. That image is the Evaluation edition.
Evaluation is a genuine, fully functional Windows Server — it just isn't licensed for production, and it runs on a timer. It exists so you can set the server up, test that your software runs, and decide it's the right box before you activate. It is not a way to run Windows for free: the countdown is real, and it's meant to end with you entering a key.
That split is what BYOL means. We supply the hardware and the image; the licence is yours to bring, and its cost is not in the plan price. A $11/mo Windows-Small is the price of the machine, not the Windows licence on it.
Activating with your own key
Log in over RDP as Administrator, open PowerShell as admin, and enter your key:
slmgr /ipk YOUR-WINDOWS-KEY
slmgr /ato
slmgr /ipk installs the product key; slmgr /ato activates against Microsoft's servers. To check the state at any time:
slmgr /dlv
That shows the edition, the licence status, and — on Evaluation — how much of the grace period is left.
Switching editions without reinstalling
If your key is for a different edition than the image (a Datacenter key, for instance), you don't reinstall — you convert the edition in place with DISM, then activate:
DISM /online /Set-Edition:ServerStandard /ProductKey:YOUR-KEY /AcceptEula
Swap ServerStandard for the target edition your key covers (e.g. ServerDatacenter). The server reboots into the new edition, and then slmgr /ato finishes activation. This matters because reinstalling would wipe your data; an edition switch keeps everything.
Which keys are actually allowed
This is the part that keeps people compliant, so read it plainly. Activation and licensing are two different things — a key can technically activate a copy of Windows without the licence terms permitting that use.
- You need hosting/mobility rights. A VPS is rented hardware you don't own. The licence has to permit running Windows Server on hardware that isn't yours — Microsoft's licensing has specific terms for this.
- OEM keys generally don't qualify. An OEM licence is bound to the physical machine it shipped with. Moving it to a VPS isn't what it's for.
- Volume/retail with the right terms, or a provider that offers SPLA-style licensing, is the usual path. If you're doing this for a business, check with whoever handles your Microsoft licensing.
We don't sell you the key and we don't police it — but we're not going to pretend any key that activates is fine, because that's how people end up out of compliance. Bring a licence that actually covers a hosted server.
After a reinstall
A reinstall from the dashboard gives you a fresh Evaluation image — same as day one. That means the previous activation is gone and you activate again with the same key:
slmgr /ipk YOUR-WINDOWS-KEY
slmgr /ato
So keep your key somewhere safe. You'll enter it after the first deploy and after any reinstall.
The short version
- The image is Windows Server 2022 Standard (Evaluation) — real Windows, on a timer, for setup and testing.
- Activate with your own key:
slmgr /ipkthenslmgr /ato. - Switch editions without reinstalling:
DISM /online /Set-Edition:… /ProductKey:… /AcceptEula. - Use a key with hosting rights — OEM keys don't count.
- Reinstall resets to Evaluation — reactivate.
That's BYOL with no asterisks. If you're comparing plans, the Windows VPS page has the four options, the Windows Server 2022 OS page covers the image, and if you want the payment side, see Windows VPS with Bitcoin or Monero. When you're ready to log in, connect over RDP.
Comments
No comments yet. Be the first.