Automatic virtual machine activation

Microsoft Partner for VM activation license
Automatic virtual machine activation for windows server
Windows Server 2019, 2016 & 2012 R2 - Automatic virtual machine activation

Windows Server 2019, Windows Server 2016 & Windows Server 2012 R2 - Automatic virtual machine activation

Applies to: Windows Server 2019, Windows Server Semi-Annual Channel, Windows Server 2016, Windows Server 2012 R2

Automatic Virtual Machine Activation (AVMA) acts as a proof-of-purchase mechanism, helping to ensure that Windows products are used in accordance with the Product Use Rights and Microsoft Software License Terms.

AVMA lets you install virtual machines on a properly activated Windows server without having to manage product keys for each individual virtual machine, even in disconnected environments. AVMA binds the virtual machine activation to the licensed virtualization server and activates the virtual machine when it starts up. AVMA also provides real-time reporting on usage and historical data on the license state of the virtual machine. Reporting and tracking data is available on the virtualization server.

Practical applications

On virtualization servers that are activated using Volume Licensing or OEM licensing, AVMA offers several benefits.

Server datacenter managers can use AVMA to do the following:

    • Activate virtual machines in remote locations

    • Activate virtual machines with or without an internet connection

    • Track virtual machine usage and licenses from the virtualization server, without requiring any access rights on the virtualized systems

There are no product keys to manage and no stickers on the servers to read. The virtual machine is activated and continues to work even when it is migrated across an array of virtualization servers.

Service Provider License Agreement (SPLA) partners and other hosting providers do not have to share product keys with tenants or access a tenant's virtual machine to activate it. Virtual machine activation is transparent to the tenant when AVMA is used. Hosting providers can use the server logs to verify license compliance and to track client usage history.

System requirements

AVMA requires a Microsoft Virtualization Server running Windows Server 2019 Datacenter, Windows Server 2016 Datacenter, or Windows Server 2012 R2.

Here are the guests that the different version hosts can activate:

Note that these activate all editions (Datacenter, Standard, or Essentials).

This tool does not work with other Virtualization Server technologies.

How to implement AVMA

    1. On a Windows Server Datacenter virtualization server, install and configure the Microsoft Hyper-V Server role. For more information, see Install Hyper-V Server.

    2. Create a virtual machine and install a supported server operating system on it.

    3. Install the AVMA key in the virtual machine. From an elevated command prompt, run the following command:

    4. slmgr /ipk <AVMA_key>

The virtual machine will automatically activate the license against the virtualization server.

AVMA keys

The following AVMA keys can be used for Windows Server 2019.

The following AVMA keys can be used for Windows Server, versions 1909, 1903, and 1809.




AVMA key



The following AVMA keys can be used for Windows Server, version 1803 and 1709.




AVMA key



The following AVMA keys can be used for Windows Server 2016.

The following AVMA keys can be used for Windows Server 2012 R2.

Reporting and tracking

The registry (KVP) on the virtualization server provides real-time tracking data for the guest operating systems. Because the registry key moves with the virtual machine, you can get license information as well. By default the KVP returns information about the virtual machine, including the following:

    • Fully qualified domain name

    • Operating system and service packs installed

    • Processor architecture

    • IPv4 and IPv6 network addresses

    • RDP addresses

For more information about how to get this information, see Hyper-V Script: Looking at KVP GuestIntrinsicExchangeItems.

This page Original Source is Microsoft: