![]() ![]() Hosting companies might want to add this one to their customer knowledgebase. AVMA is only supported on virtual machines running Windows Server 2012 R2 or later versions of operating systems.Īccording to Microsoft the unknown devices are “harmless and can be ignored”. These Virtual Devices (VDev) are provided for Automatic Virtual Machine Activation (AVMA) to communicate with the host. If you view the properties of these devices and check driver details, Hardware IDs or Compatible IDs, they will show the following: On a Windows Server 2012 R2 Datacenter Hyper-V host, you may see 2 unknown device under Other Devices in device manager of any virtual machine running operating systems earlier than Windows Server 2012 R2. Microsoft has published a KB article that is related to a funny you might see in your virtual machines that is related to AVMA. So Microsoft allows you to activate the host, and install AVMA keys into the guest OS of your template virtual machines. 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’s clearing house or a KMS a little difficult. 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. This is a technical feature than enables a licensing feature. ![]() Automatic Virtual Machine Activation (AVMA) is the one Hyper-V feature in the Datacenter edition of Windows Server that you won’t find in the other versions (Standard or Hyper-V Server). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |