Hi, I have some questions regarding KMS activation. We have purchased Windows Server 2008 R2 and Windows 7 Professional volume licenses, and got a confirmation like this: Quantity # Product ############################################ # Windows Server 2008 R2 # n # Product key aaa-...-aaa (MAK) # # Product key bbb-...-bbb (KMS) ############################################ # Windows 7 Professional # m # Product key ccc-...-ccc (MAK) # # Product key ddd-...-ddd (KMS) ############################################ I would like to use one of those Windows Servers to be the KMS host for the m Windows 7 machines. What keys do I use where? Initially I have thought: the bbb KMS key for one of the Windows Servers, and the ddd KMS key for all of the Windows 7 desktops. After reading several websites, I am not so sure about that any more. My current info is, that those KMS keys (bbb *and* ddd) are keys, which turn the machine into a KMS host. So bbb would turn Windows Server 2008 into a KMS host, and ddd would turn a Windows 7 machine into a KMS host. The Win2k8 could then active almost any Windows OS, while the Windows 7 KMS host could only activate other Windows 7 machines. Instead of using the ddd key for Windows 7, I would have to use a special product key, which turns the machine into a KMS client (i.e. FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 as posted in [1]) Is that correct, or am I totally wrong? If I am correct, how does the Windows Server 2008 KMS host know, that it should activate no more than m Windows 7 machines? Thank you and best regards Damian [1] http://technet.microsoft.com/en-us/library/ff793421.aspx

Hello Damluk, You need to use the bbb keys to make a Windows Server 2008\R2 machine a KMS host. It will activate Windows 7, Windows VIsta, Windows Server 2008 and Windows Server 2008 R2 KMS hosts. The KMS host does not maintain a list of activated machines, it is used for activation, not for compliance. If you are using Volume license media, the installations defaults to the correct keys to make the machines KMS clients. Those keys are generic and posted on TechNet and are specific per installed edition. http://technet.microsoft.com/en-us/library/ff793421.aspx Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Okay so i have the same situation, i have keys for Server 2008r2, CAL keys for Server 2008r2 and then RDS keys, and then Office 2010 keys, all are similar as in they have KMS and MAK numbers. I'm just struggling to understand the concept behind how these work. I somehow need to make the primary Server 2008 r2 Server a KMS Host with my new keys? and by typing in this command line string slmgr /ipk <setup key>. My server will switch from a client to a host, and by doing this, when i try to activate computers on my network, the server will step up and take care of this instead of running out to the windows update site? So do we use the MAK key on the client machines then ? how do i go abuot getting Office 2010 activated on the RDS Server?

1. Install W2K8 with DNS (MAK license) 2. KMS - configure DNS according to http://technet.microsoft.com/en-us/library/ff793405.aspx 3. Install clients, register them at the KMS and activate them using slmgr function in two steps, the first slmgr command points to KMS server (on port 1688): slmgr -skms FQDN_OF_KMS_SERVER:1688 and the second is activation slmgr -ato

I've read that Office 2010 is different with this licensing, something like server 2008 cannot activate the office licenses and only a windows 7 machine can. Is there any truth to this? And/Or would the installation of Office be similar? How do i install my RDS licenses for the machine to use as i have 13 thin clients that connect to the server. All licensing is Per Device. Is it the same slmgr function? and once i type in the appropriate key, i can pull up my RDS License manager and it will show the purcahsed keys?

Hello gutzmaj, To use KMS to activate Office 2010, you need a Windows 7, a Windows Server 2008 R2 or a Windows Server 2003 to be your KMS host machine. Windows Server 2008 cannot be a KMS host for Office 2010.Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Hello Gutmaj, RDS is not handled by SLMGR, I would start a separate thread for questions about those licenses,Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

The KMS host does not maintain a list of activated machines, it is used for activation, not for compliance. Hi Darrell, thank you for your answer! Do I understand correctly, that the resulting Windows Server 2008 R2 KMS host, activated by bbb, would itself activate an unlimited number of Windows 7 machines, and it is the administrator's responsibility to not overuse licenses? Moreover, neither do I need the ccc nor the ddd keys? Best regards Damian

The KMS host does not maintain a list of activated machines, it is used for activation, not for compliance. Hi Darrell, thank you for your answer! Do I understand correctly, that the resulting Windows Server 2008 R2 KMS host, activated by bbb, would itself activate an unlimited number of Windows 7 machines, then? Moreover, neither do I need the ccc nor the ddd keys? Best regards Damian

Hello Damian, Yes you understand it correct.Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Thank you, Darrell!