Below, is an extract of the FAQ section for Virtualization and Volume Activation 2.0 whitepapers:
Q. Do virtual servers or virtual machines (VM) add to the KMS count?
A. No. Only physical computers are added to the KMS count.
Q. Can I KMS-activate virtual machines and guest operating systems?
A. Yes, but keep in mind that virtual machines are not added to the KMS count.
Q. Can I MAK-activate virtual machines and guest operating systems?
A. Yes. If MAK activation is used, it is subject to the same hardware tolerance restrictions as on physical machines. This means that if the host hardware changes, the virtual machine may require reactivation. MAK activation of virtual machines is also applied against the MAK activation limit, thus decreasing the activations remaining on the MAK.
Q. What is the guidance for deploying Windows volume editions in virtual machines?
A. When the virtual machine is created, it is recommended to run sysprep /generalize to reset activation and other system-specific information as the last step before storing or capturing the VM image. Optionally, if you do not want to generalize all computer settings, you can run slmgr /rearm to reset the product activation timers only. This can be done a maximum of 3 times.
It is important to run either sysprep /generalize or slmgr /rearm the system before storing an image. This prevents the activation timer from running down while the product is in storage.
Q. Does KMS for Windows 2003 run within a virtual machine?
A. No. KMS for Windows Server 2003 is not supported in a virtual machine. An updated version of KMS for Windows Server 2003 supporting KMS in a virtual machine will be released by Windows Server 2008 launch.
Q. Does Windows Server 2008 support KMS on a virtual machine?
A. Yes. KMS is supported in a virtual machine in Windows Server 2008.
Q. Can I run VAMT on a virtual machine?
A. Yes.
Recent Comments