Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
For a Windows Server 2012 R2 virtual machine on an eligible, activated Hyper-V Datacenter host, use the AVMA key that matches the guest edition: Datacenter Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW, Standard DBGBW-NPF86-BJVTX-K3WKJ-MTB6V, or Essentials K2XGM-NMBT3-2R6Q8-WF2FK-P36R2. These are generic activation keys, not licenses. AVMA requires Microsoft Hyper-V, an activated eligible host, and the guest’s Data Exchange integration service.
Windows Server 2012 R2 AVMA keys
| Guest edition | AVMA key |
|---|---|
| Datacenter | Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW |
| Standard | DBGBW-NPF86-BJVTX-K3WKJ-MTB6V |
| Essentials | K2XGM-NMBT3-2R6Q8-WF2FK-P36R2 |
Choose the key for the edition installed in the guest; the keys are not interchangeable. Microsoft continues to list these keys in its current AVMA documentation.
What AVMA does—and what it does not
Automatic Virtual Machine Activation (AVMA) lets an eligible Windows Server guest activate through its Hyper-V host. The host and guest exchange activation information, so the guest does not need to contact Microsoft’s activation service. This makes AVMA useful in disconnected or isolated networks and avoids distributing a separate activation key to each eligible VM.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Activation is not the same as licensing. An AVMA key is a generic mechanism, not a purchased product key or proof that your organization has the required Windows Server rights. Licensing obligations still apply under the applicable terms. Likewise, activation does not establish that a legacy operating system is supported or eligible for security updates.
#1 Best Overall
Requirements and host compatibility
- Eligible Datacenter host: The Hyper-V host must run an eligible Windows Server Datacenter edition and itself be activated. Windows Server Standard hosts do not provide AVMA.
- Microsoft Hyper-V: AVMA is not supported on VMware, VirtualBox, KVM, or other virtualization platforms.
- Eligible guest: The guest must be a supported Windows Server version and edition for the host. The key list above is for Windows Server 2012 R2 guests specifically.
- Data Exchange enabled: The VM’s Data Exchange integration service—called Key-Value Pair Exchange (KVP) in older documentation—must be enabled. It is enabled by default on new VMs, but check imported, cloned, restored, or modified VMs.
- Every cluster node activated: Each Hyper-V host that may run the VM must meet the requirements and be activated. Activating only the initial node is not enough for dependable failover or migration.
For the original 2012 R2 AVMA model, Windows Server 2012 R2 Datacenter hosts activate Windows Server 2012 R2 guests; Windows Server 2016 Datacenter hosts can activate Windows Server 2016 and Windows Server 2012 R2 guests. Microsoft’s current compatibility table also lists Windows Server 2019, 2022, and 2025 Datacenter hosts as able to activate eligible Windows Server 2012 R2 guests. In all cases, host edition, activation, and Hyper-V requirements still apply.
Install the AVMA key
- Confirm the guest edition and verify the host prerequisites above.
- In the guest, open Command Prompt or PowerShell with administrative privileges.
- Run the command for the guest edition:
slmgr /ipk Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TWThat example is for a Datacenter guest. For Standard, run:
slmgr /ipk DBGBW-NPF86-BJVTX-K3WKJ-MTB6VFor Essentials, run:
slmgr /ipk K2XGM-NMBT3-2R6Q8-WF2FK-P36R2Windows should then activate the guest through the eligible host. AVMA can also be configured as part of an unattended installation. See Microsoft’s implementation instructions for details.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Verify activation
Check the guest’s activation state with the usual Windows licensing tools, and confirm that the host itself is activated. For a more useful diagnosis, review activation events on both sides:
Rank #3
- Host, Event ID 12310: AVMA request history.
- Guest, Event ID 12309: AVMA-related activation event.
Microsoft describes AVMA success and failure categories in its event and reporting documentation. A success event indicates activation; an Invalid Host event points to an unresponsive or unsupported host; Invalid Data indicates a communication or exchanged-data problem; and Activation Denied indicates the AVMA identifier did not match.
Troubleshoot common failures
| Symptom or event | Likely cause | What to check |
|---|---|---|
| Key rejected | Wrong key for the installed edition, or unsupported guest | Match Datacenter, Standard, or Essentials to the guest edition and confirm it is Windows Server 2012 R2. |
| No activation after key installation | Host is inactive or not eligible | Confirm an eligible Datacenter Hyper-V host is running and activated. |
| Invalid Host | Host is unavailable, unsupported, or not the required Hyper-V environment | Check host version, edition, activation, and that the VM is actually running on Hyper-V. |
| Invalid Data | Host-to-guest exchange failed or data is corrupt, encrypted, or mismatched | Enable Data Exchange/KVP and inspect the VM’s integration services. |
| Activation Denied | AVMA identifier does not match | Recheck the guest version, edition, and installed AVMA key. |
| Works on one cluster node but not another | A destination node is not activated or eligible | Check every host on which the VM can run. |
| Failure after changing from AVMA to another key type | Key transition or stale KVP data | Follow Microsoft’s warning about removing associated KVP data when replacing the AVMA key with a retail, OEM, or volume-licensing key. |
For an orderly check, start with the edition/key match, then confirm host Datacenter edition and activation, Hyper-V, Data Exchange, event logs, and—if applicable—every failover destination. Microsoft notes that KVP data is not secured and can be modified, so do not treat it as a secure licensing record.
Rank #4
- Mastering Active Directory: Design, deploy, and protect Active Directory Domain Services for Windows Server 2022, 3rd Edition
- ABIS BOOK
- Packt Publishing
Migration and disconnected environments
AVMA does not require internet access for guest activation, but the host still has to be activated and the licensing requirements still apply. A VM can move among eligible Hyper-V hosts; for a cluster or migration path, every possible destination must be properly activated. Moving the guest to VMware or another non-Hyper-V platform removes the AVMA activation mechanism.
AVMA versus KMS, MAK, retail, and OEM keys
AVMA is specifically for eligible Windows Server guests on Hyper-V Datacenter hosts. KMS uses a separate volume-activation service and client setup keys; a KMS key is not an AVMA key. Microsoft maintains a distinct KMS client setup key list.
MAK, retail, and OEM activation are also different methods. Do not substitute their keys for an AVMA key or assume an AVMA key is a retail product. If replacing an AVMA key with another key type, account for Microsoft’s KVP-data guidance.
Is AVMA still suitable for Windows Server 2012 R2?
The keys remain in Microsoft’s AVMA documentation, and current documentation lists supported newer Datacenter hosts that can activate eligible 2012 R2 guests. That is a statement about the activation mechanism, not a statement that Windows Server 2012 R2 is a currently supported operating system. Treat support, security updates, and any Extended Security Updates (ESU) entitlement as separate matters; Microsoft’s ESU guidance covers its own prerequisites.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
