Hi, Have you installed a Windows Server 2008 R2 KMS key on the KMS host after installing KB968915? Please run slmgr –dlv on both your KMS host and the Windows Server 2008 R2 client and then paste the results here. Tim Quan

I have a Windows 2003 SP2 server running KMS. To this point, I have no problems activating Windows 2008 SP1/SP2 clients against the KMS service running on Windows 2003. I tried deploying a couple of Windows 2008 R2 server and running into problems doing the slmgr.vbs -ato. When I run the slmgr.vbs -skms <IP-of-KMS-Server>, it has no problem contacting the KMS server, I get: Key Management Service machine name set to <IP-of-KMS-Server> sucessful. I have already applied the update, 968915 as recommended but this doesn't seem to make a difference. I already have a current count of 10 (of Windows 2008 SP1/Sp2) when I run slmgr.vbs -dlv on the KMS host. Question then would be, is it starting to count from 0 again for Windows 2008 R2, until it reaches 5 before activating ? If not, then I am at a lost as to why it's not working...any help greatly appreciated. Thank you, Narish Persaud.

No, According to the documentation a combination of 5 Windows 2008/2008 R2 servers are required to activate, http://technet.microsoft.com/en-us/library/ff793434.aspx Are you receiving any specific errors? Did you remember to import a Server Group B product key from the VL site, http://technet.microsoft.com/en-us/library/ff793412.aspx -- Mike Burr

Hi Tim, I am not sure what you meant by Installing a Windows Server 2008 R2 KMS key on the host after installing KB968915. Can you please point me to a link or give me the steps to accomplish this task. Here is the output from slmgr.vbs for the 2003 KMS host and the 2008 R2 client that I'm trying to activate agains. Thanks, ***** 2003 SP2 KMS HOST **** --------------------------- Windows Script Host --------------------------- Software licensing service version: 6.0.6001.16550 Name: Windows(TM) Server 2003 KMS, Kms3 edition Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_B channel Activation ID: 56df4151-1f9f-41bf-acaa-xxxxxxxxxxx Application ID: 55c92734-d682-4d71-983e-xxxxxxxx Extended PID: 55041-00152-339-011149-03-1033-3790.0000-xxxxxxx Installation ID: 0045550649549234035029151906143585847786xxxxxxxxxxxx Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937 Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938 Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940 \ Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939 Partial Product Key: 6YDF9 License Status: Licensed Key Management Service is enabled on this machine Current count: 10 Listening on Port: 1688 DNS publishing disabled KMS priority: Normal --------------------------- OK --------------------------- ***** 2008 R2 client ***** --------------------------- Windows Script Host --------------------------- Software licensing service version: 6.1.7600.16385 Name: Windows Server(R), ServerStandard edition Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel Activation ID: 68531fb9-5511-4989-97be-xxxxxxx Application ID: 55c92734-d682-4d71-983e-xxxxxxxxxx Extended PID: 00477-00168-001-000042-03-1033-7600.0000-xxxxxxxxx Installation ID: 001723157923781842772094832152757784410860xxxxxxxxx Partial Product Key: R7VHC License Status: Initial grace period Time remaining: 31440 minute(s) (21 day(s)) Remaining Windows rearm count: 3 Trusted time: 8/13/2010 5:14:50 PM Please use slmgr.vbs /ato to activate and update KMS client information in order to update values. --------------------------- OK ---------------------------

Hi, Thank you for the reply. From the output on your KMS host, we can see “Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_B channel”. This means you are still using a Windows Server 2008 Server Group B key. Please understand that to activate Windows Server 2008 R2 clients, you must use a Windows Server 2008 R2 key. You cannot use the original key which can only activate Windows Vista/Server 2008 (non-R2). Therefore, you need to buy a Windows Server 2008 R2 KMS key now. After installing it, it should show “Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel”. http://www.microsoft.com/licensing/existing-customers/product-activation.aspx Tim Quan

Hi Tim I have a 2008 std KMS host, I'm trying to activate a 2008 R2 to it, with a 2008R2 kms key If I understood this correctly, I should activate my 2008 std with a 2008 R2 key. Did I get this right Because I've been trying to activate a 2008R2 server with a 2008 R2 key on a 1008 std kms host and it's not working for me. And yes I did update the KMS host to allow R2 activations

Please post a new thread to discuss your issue to reduce confustions.

Hi, has this issue been clarified somewhere else ? I think the question is perfectly clear and I dont understand why it couldnt be answered. Basically the question is: Do i need to reactivate the kms host in any way (after installing the hotfix) in order to be able to activate clients with the 2008 R2 OS. It is obvious, that I need a different key on the Client for R2. Regards,Jan

Ok, now I can answer the question myself. The key is to understand the difference between KMS host keys and MS client keys. A KMS host key needs to be activated on the kms Server (host). You need to use the 2008 R2 host key, even if the operating system on the kms server is 2008 without R2. On the clients (servers and clients that activate through kms) no key needs to be configured, unless you changed the original key to a MAK (or mistaken used the kms host key). You can revert to publicly available "generic" kms client keys on the client machines.