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.
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.
AVMA only requires a virtualization server running Windows Server 2012 R2 Datacenter. The guest virtual machine operating system must be Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, or Windows Server 2012 R2 Essentials.
How to implement AVMA
1. On a Windows Server 2012 R2 Datacenter virtualization server, install and configure the Microsoft Hyper-V Server role.
2. Create a virtual machine and install a supported server operating system on it.
3. Install the AVMA key in the virtual machine.
a. From an elevated command prompt, run the following command:
slmgr /ipk <AVMA_key>
The virtual machine will automatically activate the license against the virtualization server.
NOTE: You can also employ the AVMA keys in any unattended setup file.
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 an IPv6 network addresses
· RDP addresses
NOTE: KVP data is not secured. It can be modified and is not monitored for changes.
IMPORTANT: KVP data should be removed if the AVMA key is replaced with another product key (retail, OEM, or volume licensing key).
Historical data about AVMA requests is available in a log file on the virtualization server (EventID 12310).
Since the AVMA activation process is transparent, error messages are not displayed. However, the following events are captured in a log file on the virtual machines (EventID 12309).
The virtual machine was activated.
The virtualization server is unresponsive. This can happen when the server is not running a supported version of Windows.
This usually results from a failure in communication between the virtualization server and the virtual machine, often caused by corruption, encryption, or data mismatch.
The virtualization server could not activate the guest operating system because the AVMA ID did not match.