How to Activate Windows Server 2022: All Editions Explained

To activate Windows Server 2022, install a product key that matches the edition and channel you deployed. The server then contacts Microsoft, or your own activation service. A single machine with a retail key needs two commands, which we show below.

For fleets we have three more routes: KMS, Active Directory-based activation and AVMA for Hyper-V guests.

1. Retail or OEM key: two slmgr commands, or Settings, Activation.
2. Evaluation copy: convert the edition with DISM first, then enter the key.
3. KMS: the generic client key and a KMS host on the network.
4. Active Directory-based activation: domain-joined servers activate against the forest.
5. AVMA: virtual machines activate through a Datacenter host.

Not installed yet? Start with how to install Windows Server 2022.

This page goes through each route from a sysadmin’s point of view.

The right method depends on three things.

• The edition, Standard or Datacenter.
• The license channel: retail, OEM or volume.
• The machine itself, a physical host or a VM.

Windows Server 2022 editions and licensing

The system ships in three main editions, plus the smaller Essentials. Each key is tied to one edition and one license channel.

Check before activating, with either line below.

DISM /Online /Get-CurrentEdition
slmgr /dlv

A mismatch is the single most common reason activation fails with a perfectly valid key.

Standard covers a physical host plus two virtual machines per fully licensed server. Microsoft calls those two OSEs.

Datacenter removes the VM limit and adds more.

• Storage Spaces Direct
• Software-Defined Networking
• Shielded VMs
• Unlimited Storage Replica

Both editions are licensed per physical core. The minimum is 8 core licenses per processor and 16 per server, even on a smaller box.

Our breakdown of virtual machine limits in Windows Server 2022 Standard works through the stacking math.

Preparing for Windows Server 2022 activation

You need an administrator account, a key for the installed edition and a route to the activation service.

Correct system time and working DNS matter more than people think. Both break activation silently.

We’d run the detailed license view first. Its “Product Key Channel” line shows the type of install, and that decides every next step.

How to activate Windows Server 2022 with a product key

With a retail, OEM or MAK key, activation takes about two minutes. The server contacts Microsoft over the internet.

1. Right-click Start and choose the Admin entry of Terminal or Command Prompt.
2. Install the key with the first line below, using your own 25 characters.
3. Activate online with the second line.
4. Check the result with the third or the fourth line.

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
slmgr /dlv
slmgr /xpr

Settings and Server Manager reach the same result through a GUI.

Settings app on Desktop Experience

• Press Win+I and open Update & Security, then Activation.
• Click Change product key.
• Type the key and click Next, then Activate.

Server Manager

• Open Server Manager and select Local Server.
• Next to Product ID, click the “Not activated” link.
• Enter the key in the window that opens, and confirm.

Activation usually completes within seconds. Now and then it takes a few minutes while the licensing service syncs.

So we’d wait before running the activation line a second time.

Server Core: the SConfig activation menu

No Settings app on Server Core. No problem either.

On Windows Server 2022 SConfig opens by itself after sign-in, inside PowerShell. Closed it? Type SConfig and press Enter. Local administrator rights needed.

• Option 11, Windows activation.
• Then 3 to add a new product key.
• Then 2 to activate with the installed key.
• And 1 shows the current status.

One catch from Microsoft’s own SConfig notes: it doesn’t run in a remote PowerShell session. Signed in locally or over Remote Desktop, it works.

Windows Server 2022 activation from cmd on another server

Got a handful of servers and no wish to log on to each? slmgr takes a computer name, plus an account with admin rights there.

slmgr.vbs SRV02 CONTOSO\admin <password> /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr.vbs SRV02 CONTOSO\admin <password> /ato

Swap in your own server name, account and key. Dozens of machines? Then we’d move to VAMT, the Volume Activation Management Tool, which Microsoft points to for managing remote clients. The full option list lives in our slmgr commands guide.

Offline activation, which used to be phone activation

Isolated network? A retail or MAK key still works there. The phone line is gone, though. Microsoft moved telephone activation online, to the Product Activation portal at aka.ms/aoh, also reachable as visualsupport.microsoft.com. Calling the old number won’t finish it.

The sign-in only protects the portal. Microsoft says it doesn’t tie your account to the license.

Which edition the key has to match is settled in Windows Server 2022 Standard vs Datacenter, and the clean installation itself in how to install Windows Server 2022.

Activating licensed Windows Server 2022 Standard and Datacenter

Installed from full media, not a trial? Then the route depends on two things. The edition, and where the key came from.

Not sure which channel the server is on? One line answers it:

slmgr /dlv

Read the Description line. RETAIL, OEM or VOLUME_MAK there? That’s a key somebody typed in. VOLUME_KMSCLIENT? Then the server sits waiting for a KMS host, and a product key from a shop isn’t what it needs yet.

OEM servers usually arrive activated. That license stays with the hardware it shipped on, so we wouldn’t plan to move it to a new box.

Edition and key have to match. A Standard key on Datacenter fails, and so does the reverse. Check the edition name in Settings or in Server Manager before you paste anything.

Moving a working server from MAK to retail, or from KMS to a retail key? Same edition, same slmgr lines as above. No reinstall.

Desktop watermark still says Evaluation? Different job. Our guide to converting Windows Server 2022 evaluation to Standard covers the edition change, the reboots and the conversion paths.

Edition IDs for other releases sit in our page on activating Windows Server via DISM.

KMS activation for Windows Server 2022

Key Management Service lets clients activate against a host on your own network. Microsoft isn’t contacted by each client.

Setting up the KMS host

• Install the Volume Activation Services role with the line below.
• Open Volume Activation Tools, choose Key Management Service and enter your CSVLK.
• Let the wizard publish the _vlmcs._tcp SRV record in DNS, or create it manually.
• Open inbound TCP 1688 in Windows Firewall.

Install-WindowsFeature -Name VolumeActivation -IncludeManagementTools

Pointing clients at it

Volume-licensed media already contains the GVLK. A server coming from MAK or retail needs the generic key first.

It’s in Microsoft’s KMS client activation keys list.

slmgr /ipk <GVLK>
slmgr /skms kms01.contoso.local:1688
slmgr /ato

The second line is optional, for when DNS discovery fails.

These keys are public and do nothing by themselves. Without a KMS host on your network, a GVLK leaves the server unactivated.

That’s exactly why “free” Server keys posted online never work at home.

Active Directory-based activation for Windows Server 2022

ADBA stores an activation object in the domain. Domain-joined servers then activate at startup, with no KMS host to find and no five-request threshold.

We’d use it when every server is domain-joined and the AD schema is at the Windows Server 2012 level or newer.

Workgroup machines and DMZ hosts still need KMS, MAK or retail keys.

• Install the Volume Activation Services role on any domain member. A domain controller works too.
• In Volume Activation Tools, choose Active Directory-Based Activation.
• Enter the CSVLK and give the activation object a name.
• Restart a test server and check the detailed license view. It should report activation through Active Directory.

ADBA rarely needs tuning after that. Clients revalidate against AD every 180 days.

Adding a server to the domain is all it takes to license it. So it tends to replace KMS in AD-only shops.

Activating Windows Server 2022 guests with AVMA

Automatic Virtual Machine Activation lets guests activate against an activated Datacenter Hyper-V host. The VM needs no internet and no KMS.

A Datacenter host on this release or on 2025 activates guests of any edition.

Install the AVMA key in the guest and keep the Data Exchange integration service on. It then activates at boot.

The old version of this page listed AVMA keys for the 2016 and 2019 releases. Those don’t activate 2022 guests.

The current list lives in Microsoft’s AVMA documentation.

• In a failover cluster, every node has to be activated. Otherwise guests lose activation after a live migration.
• AVMA works only on Hyper-V. Other hypervisors, such as VMware or Proxmox, need regular keys or KMS.
• Requests are logged as Event ID 12310 on the host and 12309 in the guest’s Application log.

AVMA covers activation, not licensing. You still need enough Datacenter core licenses for the host. We’d see AVMA as a way to skip typing keys into every guest.

Windows Server 2022 activation errors

Most activation failures come from four causes.

• A key for a different edition or channel.
• A volume install looking for a KMS host that doesn’t exist.
• No route to Microsoft’s servers.
• A wrong system clock.

The error code tells you which one. So we’d read it before reinstalling anything.

The order that saves the most time: check the edition, the channel, DNS and the clock, and then retry activation.

If a key bought from HypestKey doesn’t activate after those checks, write to support@hypestkey.com. We help you fix it or send a replacement.

Checking Windows Server 2022 activation status

Check on the server with the detailed license view or the expiry view. PowerShell can query many servers at once.

Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select-Object Name, LicenseStatus

That line lists every licensed product and its status, where 1 stands for licensed. Want a different way to read it? Settings, slmgr and more sit in how to check Windows activation status.

• Document the key and method each server uses, because auditors ask for it.
• OEM keys stay with the server they came with.
• Retail licenses can move after you remove them from the old hardware.
• Volume licenses can be reassigned, though not more often than every 90 days. Permanent hardware failure is the exception.
• Remember the CALs. Activation covers the server, while each user or device that connects still needs a Windows Server CAL.
• Remote Desktop users need RDS CALs. Our page on managing CAL licenses in Windows Server 2022 explains both.
• After a move to different hardware, a KMS or AVMA guest typically reactivates by itself. A retail-activated server may ask for the activation line again.

For the KMS route we keep the generic client keys of every edition in Windows Server KMS keys. The client access licenses that come next are compared in RDS CAL Per User vs Per Device, and we explain the base CALs in managing CAL licenses in Windows Server 2022.

Quick answers

Common Windows Server 2022 activation mistakes

• Entering a Standard key on a Datacenter install.
• Typing a retail key into an evaluation copy before converting it.
• Expecting a public GVLK to activate a server with no KMS host.
• Running the activation line again and again while the service is still syncing.
• Using AVMA keys from an older version on 2022 guests.
• Leaving one cluster node unactivated.
• Ignoring the clock and DNS when the error mentions KMS.
• Trying to convert an evaluation domain controller.
• Treating activation as the whole license and forgetting CALs.

Terms used on this page