I was very proud to be invited by the Windows Server Management Team to show and explain Project Honolulu during Microsoft Ignite in Orlando, FL. I was on the Server Management booth from Monday to Wednesday and it was amazing. There was so much interest in this new solution. So many questions and good ideas….
Hyper-V: Automatic Virtual Machine Activation (AVMA)
One very cool feature that is there since the release of Windows Server 2012 R2, which I have seen so far but very rarely used by customers
I hope you all know the activation methods KMS und MAK…
But now what if i run Hyper-V hosts and run VMs operating in fully independent subnets, domains, etc.? In these areas, my KMS does not work and i also usually do not have access to the VMs, so that i could enter any MAK key.
Thats when you should use AVMA. The only Thing you need is a Hyper-V host running an activated version of Windows Server 2012 R2 Datacenter.
VMs on this host running Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard or Windows Server 2012 R2 Essentials, will now be equipped with one of the following keys:
- Datacenter – Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
- Standard – DBGBW-NPF86-BJVTX-K3WKJ-MTB6V
- Essentials – K2XGM-NMBT3-2R6Q8-WF2FK-P36R2
The key can be integrated into your templates or provided by unattend.xml. Alternatively the customer can enter the key itself.
That’s it … now my VMs are activated by the activated Hyper-V host. I need no connection to KMS, no admin rights, etc …
IMPORTANT: This form of activation only works for Windows Server 2012 R2 !!!