Windows 7 & KMS
So we had a Windows 2003 server happily serving KMS to both Windows 7 and Windows 2008 R2 servers with no problems.
Server died, we rebuilt it with a new name as a 2008r2 server, found that 2008r2 can't issue windows 7 kms ? So we rebuilt it again with Windows 2003 and KMS 1.2.
I can do the slmgr /ipk <win7kmskey> and get a successfully added key.
But if i then do a slmgr /dlv all , all the keys say unlicensed and none of them appear to be my key, and no clients can authenticate against this kms. I know i need to start the 25 count again but i'm not even getting 'not enough clients' error i'm getting cant connect to kms error after doing a /skms <fqdn> and /ato.
Here is my /dvi all output :
C:\WINDOWS\system32>cscrip
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Name: Windows(TM) Server 2003 KMS, KmsW2k3Prs edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms1 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_B channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_C channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms2 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_A channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_C channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms1 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_W7 channel
Partial Product Key: RQYF8
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms2 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_A channel
This license is not in use.
License Status: Unlicensed
Server died, we rebuilt it with a new name as a 2008r2 server, found that 2008r2 can't issue windows 7 kms ? So we rebuilt it again with Windows 2003 and KMS 1.2.
I can do the slmgr /ipk <win7kmskey> and get a successfully added key.
But if i then do a slmgr /dlv all , all the keys say unlicensed and none of them appear to be my key, and no clients can authenticate against this kms. I know i need to start the 25 count again but i'm not even getting 'not enough clients' error i'm getting cant connect to kms error after doing a /skms <fqdn> and /ato.
Here is my /dvi all output :
C:\WINDOWS\system32>cscrip
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Name: Windows(TM) Server 2003 KMS, KmsW2k3Prs edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms1 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_B channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_C channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms2 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_A channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_C channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel
This license is not in use.
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms1 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_W7 channel
Partial Product Key: RQYF8
License Status: Unlicensed
Name: Windows(TM) Server 2003 KMS, W7R2-Kms2 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_A channel
This license is not in use.
License Status: Unlicensed
ASKER
If you look at my printout it shows status 'unlicensed' clients wont register even manually.
-To clarify, you ran slmgr /ipk on the *KMS HOST*, correct?
-And the output from slmgr /dlv above is from a Windows 7 client?
-And the output from slmgr /dlv above is from a Windows 7 client?
ASKER
I ran the /ipk and /ato both on the KMS Server (A windows 2003 32 bit box with KMS 1.2 installed).
-When you ran SLMGR /IPK, did it generate any errors? Is there anything in the Application Log around that time, from KMS?
-KMS 1.2 requires SP2 for Server 2003 to be installed. Is SP2 installed on your host?
-I know I mentioned it before, but is Windows Firewall disabled? If not, you will need to create a rule allowing KMS through the firewall:
¿Go to Control Panel and open Windows Firewall.
¿Click the Allow A Program Through Windows Firewall link.
¿Click the Change Settings button.
¿Select the Key Management Service option
¿Click OK.
*Note that when you enable the firewall on a KMS host, the default TCP communications port number is 1688. *
-Finally, KMS relies on DNS SRV records and the host needs to be configured with appropriate permissions. If the SRV record is not created/updated, KMS clients will not be able to locate the host. Here is the Deployment Guide for KMS if you have not already seen it:
http://download.microsoft.com/download/2/9/7/297AC437-018B-4F42-AB8E-EA91FD996029/Volume_Activation_Planning_Guide_Windows7.docx
"The KMS host must be configured so that it has the credentials needed to create and update SRV, A (Internet Protocol version 4, or IPv4), and AAAA (Internet Protocol version 6, or IPv6) RRs on the DNS servers, or the records need to be created manually. The recommended solution for giving the KMS host the needed credentials is to create a security group in AD DS, and then add all KMS hosts to that group. In a DNS server that is running Microsoft software, ensure that this security group is given full control over the _VLMCS._TCP record on each DNS domain that will contain the KMS SRV RRs."
-KMS 1.2 requires SP2 for Server 2003 to be installed. Is SP2 installed on your host?
-I know I mentioned it before, but is Windows Firewall disabled? If not, you will need to create a rule allowing KMS through the firewall:
¿Go to Control Panel and open Windows Firewall.
¿Click the Allow A Program Through Windows Firewall link.
¿Click the Change Settings button.
¿Select the Key Management Service option
¿Click OK.
*Note that when you enable the firewall on a KMS host, the default TCP communications port number is 1688. *
-Finally, KMS relies on DNS SRV records and the host needs to be configured with appropriate permissions. If the SRV record is not created/updated, KMS clients will not be able to locate the host. Here is the Deployment Guide for KMS if you have not already seen it:
http://download.microsoft.com/download/2/9/7/297AC437-018B-4F42-AB8E-EA91FD996029/Volume_Activation_Planning_Guide_Windows7.docx
"The KMS host must be configured so that it has the credentials needed to create and update SRV, A (Internet Protocol version 4, or IPv4), and AAAA (Internet Protocol version 6, or IPv6) RRs on the DNS servers, or the records need to be created manually. The recommended solution for giving the KMS host the needed credentials is to create a security group in AD DS, and then add all KMS hosts to that group. In a DNS server that is running Microsoft software, ensure that this security group is given full control over the _VLMCS._TCP record on each DNS domain that will contain the KMS SRV RRs."
ASKER
/ipk succedded iwth no errors at all.
It is 2003 R2 32 bit
Windows firewall is turned completely off.
The DNS SRV record exists, everything seems to be as it should except i can't /ato on the server to activate the licenses.
I get : "Activating Windows(TM) Server 2003 KMS, W7R2-Kms1 edition (<key>) Error: 0xC004C008 The activation server determined that the specified product key could not be used."
It is 2003 R2 32 bit
Windows firewall is turned completely off.
The DNS SRV record exists, everything seems to be as it should except i can't /ato on the server to activate the licenses.
I get : "Activating Windows(TM) Server 2003 KMS, W7R2-Kms1 edition (<key>) Error: 0xC004C008 The activation server determined that the specified product key could not be used."
Best bet is to call Microsoft's Product Activation Call Center. Either the key you are using is not actually a KMS host key (this happens alot, actually) or Microsoft believes you've already used that key on more than 6 different servers. They should be able to verify the key for you and/or reset it to continue using.
http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx
U.S. Microsoft Activation Center
(888) 352 7140
http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx
U.S. Microsoft Activation Center
(888) 352 7140
ASKER
I feared getting this answer. I have never, ever, talked to a more incompetant bunch then the Microsoft Activation Center. It is one thing to oursource, it is quite another to take the rejects that no other company will outsource to.
I called them 4 times today thinking the same thing, the first 3 CSR's had never even heard of KMS and despite my attempts to teach them they transfered me around to tech support, back into the menu system, and flat out disconnected me. The fourth guy knew what KMS was, said he'd send me a new key i'd have in 10 minutes. Sure enough 10 minutes later I got a key .. the same key i'd been trying to use from my Enterprise agreement !!
I don't know if I can stomach another call to them unless you know some trick to getting someone who has ever worked with KMS even once ?
I called them 4 times today thinking the same thing, the first 3 CSR's had never even heard of KMS and despite my attempts to teach them they transfered me around to tech support, back into the menu system, and flat out disconnected me. The fourth guy knew what KMS was, said he'd send me a new key i'd have in 10 minutes. Sure enough 10 minutes later I got a key .. the same key i'd been trying to use from my Enterprise agreement !!
I don't know if I can stomach another call to them unless you know some trick to getting someone who has ever worked with KMS even once ?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Also, I believe it usually takes a few hours for KMS clients to re-register. How long has it been since the host has been up?