[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2215
  • Last Modified:

kms server and server 2008 r2

Ok have run all the required commands etc for a kms server. It has activated 3 out of 3 servers.

It will not activate my windows 7 pro laptops (been on the system for neer on 30 days now)

If I run this command net stop slsvc i get the service is invalid (is this service installed on server 2008 R2 , the software licensing service that is, as i cannot see it in the services either)

This is what logs i get from the key management event viewer

An activation request has been processed.
Info:
0x0,25,TRLap-03.SCHOOLNET.LOCAL,37d4071f-639e-4a32-9ff4-7f65b02f8114,2010/09/19 22:41,0,5,0,b92e9980-b9d5-4821-9c94-140f632f6312

there are 40 laptops in total. I have tried to run this command from a client
slmgr.vbs /ato

But basically it says the count recorded from the key management server says there are not enough clients

Anyone got any ideas as to why they possibly are not activating?? they are all on mostly during the day.

Just for further info firewall not on.

I assumed i did not have to install windows 7 with a product key?? but it would pick it up from the kms server and activate the product is this correct?? or it did not ask me for a key when i installed win 7 at least anyway.
0
rmfb
Asked:
rmfb
  • 5
  • 3
1 Solution
 
kevinhsiehCommented:
KMS requires 5 servers to ask for keys and 25 clients to request keys before it will hand out keys for them.  I am surprised that your servers are activated if there are only 3. What kind of key are you using?

Here is the Technet chapter on activation.

http://technet.microsoft.com/en-us/library/ff793432.aspx
0
 
rmfbAuthor Commented:
using a kms b key for R2
0
 
kevinhsiehCommented:
Here's the TechNet troubleshooting guide. Also, were your laptops imaged? If they were, they may all have the same client computer ID and they won't add to the client count, so you won't hit your threshold of 25 clients.

http://technet.microsoft.com/en-us/library/ff793439.aspx

Here's a snippit from the TechNet article.

"Verify that the KMS activation threshold is met. Run Slmgr.vbs with the /dli command-line option on the KMS host to determine the host’s current count. Until the KMS host has a count of 25, Windows 7 client computers cannot be activated. Windows Server 2008 R2 KMS clients require a KMS count of 5 for activation. For more information about KMS requirements, see the Volume Activation Planning Guide. On the KMS client, look in the Application event log for event ID 12289. Check this event for the following:
Is the result code 0? Anything else is an error.
Is the KMS host name in the event correct?
Is the KMS port correct?
Is the KMS host accessible?
If the client is running a non-Microsoft firewall, does the outbound port need to be configured?
On the KMS host, look in the KMS event log for event ID 12290. Check this event for the following:

Did the KMS host log a request from the client computer? Verify that the name of the KMS client is listed. Verify that the client and KMS host can communicate. Did the client receive the response?
If no event is logged from the KMS client, the request did not reach the KMS host or the KMS host was unable to process it. Ensure that routers do not block traffic using TCP port 1688 (if the default port is used) and that stateful traffic to the KMS client is allowed."
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
rmfbAuthor Commented:
so far this morning there are 14 clients on the network all asking for activation and my client count is currently 4
0
 
rmfbAuthor Commented:
this is the clients response from the app log The client has processed an activation response from the key management service machine.
Info:
0x00000000, 0x04000000, 0, 0, 4, 120, 10080, 2010/09/20 08:58
0
 
kevinhsiehCommented:
Were your laptps imaged? You can try to run "slmgr /rearm" to reset the client computer ID (CMID) and other product-activation information. Otherwise, each client computer looks identical, and the KMS host does not count them as separate KMS clients.
0
 
rmfbAuthor Commented:
answer was a syprepping error /generalise all machines think they where the same to the activation server. Had to re-arm the OS then all started working
0
 
rmfbAuthor Commented:
yes exactly this had to rearm them. Image error did not generalise
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now