As Microsoft promised late last year, the company has ported some of its volume-activation technology to Windows Server 2003.
Microsoft has made available for download 32- and 64-bit versions of its Key Management Service for Windows Server 2003 Service Pack (SP) 1 systems, as noted on the Windows Connected blog.
Windows Connected’s Josh Phillips is none too happy about one change introduced as part of the new KMS port.
“Microsoft has made a significant change that will affect many enterprise customers,” blogged Phillips. “This update will not activate machines if running inside a virtual machine. This bucks the growing industry trend of virtualization for all classes of servers. In an effort to reduce piracy they are again punishing the very customers it is designed to protect.”
I asked Microsoft to comment on its reasons for the change. Here’s the response, provided via e-mail, which I received late in the day on February 13:
“By design, Microsoft’s Key Management Service (KMS) for Windows Server2003 is not supported to run within a virtual machine. We recognize that our customers want to take advantage of virtualization; which iswhy Windows Vista client installations running within a virtual machine are able to activate using KMS for Windows Server 2003,” said Cori Hartje,Director of Microsoft’s Genuine Software Initiative.
KMS is one of the elements of Microsoft’s Volume Activation 2.0 technologies. Volume Activation is the business component of Microsoft’s anti-piracy initiative; its consumer-side complement is Windows Genuine Advantage (WGA). Under Volume Activation 2.0, enterprises running Windows Vista Business, Vista Enterprise and the Longhorn Server SKUs will be required to track product-license keys via two schemes: Multiple Activation Keys (MAK), which are aimed at smaller organizations and/or isolated machines; and on-premise volume license key-management service (KMS) for networked environments with 25 or more machines.
Microsoft, Windows Server 2003, License, Management