I am re-posting with approval this clarification on Volume Licensing Key 2.0 "KMS" servers. Microsoft has been very speedy in responding to concerns about how one might support the new activation scheme first being deployed in Vista. There are two good bits of licensing news contained below. The second bit of news is a EULA change.
From: Steve Straub <[log in to unmask]>
To: "[log in to unmask]" <[log in to unmask]>
CC: Michael Stark <[log in to unmask]>, "Michael Greene (EDSG)"
<[log in to unmask]>, Rod Gode <[log in to unmask]>
Date: Fri, 3 Nov 2006 09:07:07 -0800
Subject: RE: Re: [windows-hied]: Volume License Activation 2.0 - Select 6
versus Campus models?
KMS implementation for various agreements: You do not need to manage a different KMS for each licensing agreement you have. You could have one KMS for your entire institution.
We do understand that in the education space an institution may have many Volume Licensing agreements (in the corporate space we have many customers w many licensing agreements also). Today we do not ask you to take the Windows XP VLK from each of those agreements and only install that VLK on the number of machines covered in the agreement... you can take one VLK from one agreement and create a master or golden image to apply across the organization. You can think of the KMS in the same way (one KMS can cover multiple licensing agreements).
I also wanted to make people aware of a change in the EULA around transfer of License. The terms regarding license-to-device assignment of the retail product (including Home Basic, Home Premium, Business and Ultimate) now read as follows:
-You may uninstall the software and install it on another device for your use. You may not do so to share this license between devices.
>From info at http://windowsvistablog.com/blogs/windowsvista/archive/2006/11/02/news-revision-to-windows-vista-retail-licensing-terms.aspx. The original terms allowed 1 reassignment and was genuinely geared toward combating piracy; however, it's become clear to us that those original terms were perceived as adversely affecting an important group of customers: PC and hardware enthusiasts. We respect the time and expense you go to in customizing, building and rebuilding your hardware and we heard you that the previous terms were seen as an impediment to that.
[log in to unmask]
From: Michael Stark [mailto:[log in to unmask]]
Sent: Thursday, November 02, 2006 1:27 PM
To: Steve Straub; [log in to unmask]
Subject: RE: Re: [windows-hied]: Volume License Activation 2.0 - Select 6 versus Campus models?
I think I have done a first run through of the docs posted, and I can't see how one differentiates between different KMS license pools. If you enter a host KMS SRV record, how do you identify Select agreement from campus agreement SRV types? Or put another way, how do your clients auto detect that your KMS relates to the select 6 or Campus 3 license pool?
Why Might I care? We have about half select 6 per machine upgrades (most no S/A so they will only have access to Business, not enterprise), and and half Campus enrolled employees who need to be able to install and activate either business or enterprise.
The two pools of users are financed and managed in different fashions.
Most 2000 and XP systems at the moment are deployed not using any sort of unattended install/RIS type of deployment, but rather a boot CD and enter VLK at install time, or a ghost clone of that golden system. We only have a very Small WinPE usage at this point. In large this is my department internally, but I support licensing for all the Select 6 and Campus 3 users in two separate license groups.
I'm so glad our partner program/System builder Vista licenses will be out of this discussion until they optionally enroll in Select.
Mike Stark U.C. San Diego, Academic Computing Services
Manager, Microsupport & Software Distribution
Voice (858) 534-4060 Fax (858) 534-7018 AP&M 1220
internet: [log in to unmask]
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.