HYPER-V Automatic Virtual Machine Activation

Windows Server 2012 R2 introduce a feature called Automatic Virtual Machine Activation (AVMA). Until Windows Server 2008 R2 the only feature to activate Virtual Servers in HYPER-V Host was to login in Server and follow the steps to Activate with the License Key.

With Automatic Virtual Machine Activation (AVMA) this can change and activate Virtual Servers that are in HYPER-V Host without need the Licenses Keys that you have for different version of Windows. 

Now let's explain how can use this feature

What is Automatic Virtual Machine Activation (AVMA)

It's  a feature that first introduce in Windows Server 2012 R2 that can allow to activate Virtual Machines via HYPER-V Host. 

Requirements for Automatic Virtual Machine Activation (AVMA)

Before start to use Automatic Virtual Machine Activation (AVMA) must meet the following requirements

1.  Host must has Windows Server 2012 R2 or 2016 Datacenter Edition with HYPER-V Role installed
2. Integration Services must run in Virtual Machines and verify that Data Exchange Service running in Virtual Machine

Support Guest Operating Systems for Virtual Machine Activation (AVMA)

Automatic Virtual Machine Activation (AVMA) support specific Guest operating systems

These are

Windows Server 2012 R2 Datacenter Edition in HYPER-V Host 

• Windows Server 2012 R2 Datacenter ,Standard ,Essential Edition

Windows Server 2016 Datacenter Edition in HYPER-V Host 

• Windows Server 2012 R2 Datacenter ,Standard ,Essential Edition
• Windows Server 2016 Datacenter ,Standard ,Essential Edition

How can use Virtual Machine Activation (AVMA) in Guest Operating System

First of all let's take a look how works AVMA.

Automatic Virtual Machine Activation (AVMA) always run in Windows Server Datacenter edition with HYPER-V Role installed. 

Windows Server Datacenter Edition as Management OS in HYPER-V Host has a feature that monitoring all the Virtual Machines.

Integration Service include the Microsoft Hyper-v Activation Component Driver in Virtual Machine which implement all the parts from the Virtual Machine side.

The communication between Management OS and guest side implemented by Data Exchange Service which included in Integration Services.

As i wrote in the beginning is one of the requirements to verify that Data Exchange Service is enable.

Now let's go to activate one Virtual Server with Automatic Virtual Machine Activation (AVMA).

• Login in Virtual Server
• Open command prompt
• Type the following command 
  slmgr /ipk <AVMA_key>

AVMA keys are the following. Yes Microsoft has publish specific AVMA keys that can use it base on the OS Version.

Find it here or go in Technet Page of Microsoft Automatic Virtual Machine Activation for more details.

For Windows Server 2012 R2 Datacenter Edition

For Windows Server 2016 Datacenter Edition

• After run the command you will get the following message

• If you want to verify that the Virtual Server has activated you can search for Event ID 12310 in HYPER-V Host.
• Unfortunately the info of the Logs are very limited.

• If you would like to have more details like full qualified domain name, OS and Service Packs , Processors you can use the Hyper-V Script: Looking at KVP GuestIntrinsicExchangeItems .
• Find more details in Technet Page of Microsoft Automatic Virtual Machine Activation .

Migration Affect AVMA ?

What happened if you Migrate Virtual Server in another HYPER-V Host? 

If you decide to move a Virtual Server which has Activate with AVMA key the new HYPER-V Host must has Windows Server 2012 R2 or 2016 Datacenter Edition.

Unless Virtual Server will change into unlicensed state.

If you have lot of Virtual Servers it's an easy way to Activate it without need to search for License Key's depends of Windows OS.

Have a nice weekend !!

How many Virtual Servers do you have ? It is worth to use AVMA ? Let's discuss it in our commented system or find me in Google + and Facebook