{"id":15958,"date":"2014-01-30T09:33:11","date_gmt":"2014-01-30T09:33:11","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=15958"},"modified":"2014-01-30T09:33:11","modified_gmt":"2014-01-30T09:33:11","slug":"kb2925727-unknown-device-vmbus-in-device-manager-in-virtual-machine-for-avma","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=15958","title":{"rendered":"KB2925727 – Unknown Device (VMBUS) In Device Manager In Virtual Machine For WS2012 R2 AVMA"},"content":{"rendered":"

Automatic Virtual Machine Activation (AVMA) is the one Hyper-V feature in the Datacenter edition of Windows Server that you won\u2019t find in the other versions (Standard or Hyper-V Server). This is a technical feature than enables a licensing feature. Hosts that are licensed with the Datacenter edition are entitled to host as many VM installations of Windows Server as you are able to get on to that licensed physical machine. The complication for larger or hosting companies is activating the installations: firewalls and NVGRE network virtualization (SND or software-defined networking) makes routing to Microsoft\u2019s clearing house or a KMS a little difficult. So Microsoft allows you to activate the host, and install AVMA keys<\/a> into the guest OS of your template virtual machines.<\/p>\n

Microsoft has published a KB article<\/a> that is related to a funny you might see in your virtual machines that is related to AVMA.  <\/p>\n

\n

Symptoms<\/u><\/strong><\/p>\n

On a Windows Server 2012 R2 Datacenter Hyper-V host, you may see 2 unknown device <\/strong>under Other Devices <\/b>in device manager of any virtual machine running operating systems earlier than Windows Server 2012 R2.
If you view the properties of these devices and check driver details, Hardware IDs or Compatible IDs, they will show the following: <\/p>\n