And how are the Windows Server operating systems of those virtual machines going to activate against a centrally deployed KMS server with which they cannot communicate? Tenants, be they internal or external, must be isolated from the hosting infrastructure and each other. Lots of non-IT staff (I don’t mean the receptionist, but delegated IT outside of central infrastructure management) will be deploying virtual machines for themselves. In fact, it will work pretty well for a flat network where all virtual machines are in the same network or Active Directory as the hosting infrastructure where the KMS will likely reside.īut think about a true cloud for a moment, with its multi-tenancy, self-service, and broad network access. Initially it sounds like KMS activation is the perfect approach to use in a large-scale virtualization environment. This is more scalable and removes the dependency for machines to have Internet access. New machines are directed to the KMS instead of the Microsoft online service to activate. Key Management Service : A Key Management Service (KMS) installed, activated using a special KMS key, and advertised on the network.I hope this isn’t what you plan for a network with dozens, hundreds, or even thousands of virtual machines. This method is intended for rare occasions. Offline : If your activation fails or the machine is offline then you can call the Microsoft clearing house to perform the activation over the phone.This is okay for a few installations, but it’s not scalable. Online : Your machine connects directly to a Microsoft service on the Internet and activates.There are three ways to do an activation:
These are very real designs that must be implemented by large enterprises and hosting companies that are building multi-tenant clouds.Īnyone who has legally deployed Windows (hopefully that is all of you) since the days of Windows XP has had to activate their product key. There might be many Active Directory forests that have no external trusts.
Those networks could be isolated using either VLANs or Hyper-V Network Virtualization ( HNV).
Imagine a Hyper-V installation that is large or complex. Why Automatic Virtual Machine Activation Is Required Today I will discuss how you can use a new feature in Windows Server 2012 R2 Hyper-V called Automatic Virtual Machine Activation ( AVMA) to automatically activate the guest OS installations of Hyper-V virtual machines.
0 kommentar(er)
