Solved

KMS is not functioning properly

Posted on 2013-11-20
3
297 Views
Last Modified: 2013-12-06
KMS(Key Management Service) is installed on one of Domain Controller but is is not functioning and clientmachines are showing windows need to update.
0
Comment
Question by:sanjayambre
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 17

Expert Comment

by:Learnctx
ID: 39664706
You have the KMS SRV records setup? Under the forward lookup in DNS for your domain this record should exist. _VLMCS._tcp.yourchild.yourrootdomain.internal.

DNS > Server > Forward Lookup Zones > yourchild.yourrootdomain.internal > _tcp

If it exists check the settings. You want to have it set to use port 1688 and point to the FQDN of your KMS server. Priority and all of that can be set to 0.

If it does not exist, create a new SRV record. Right click _tcp > choose other new records > service location (SRV).

Service: _VLMCS
Protocol: _tcp
Weight: 0
Priority: 0
Port: 1688
Host offering: yourkmsservername.yourchild.yourrootdomain.internal. << you want to terminate the FQDN with a period especially if you're servicing multiple domains.

In my case my KMS records all point back to a KMS server in the child domain of the forest.
0
 

Author Comment

by:sanjayambre
ID: 39671640
Checked & SRV settings are correct. we tried to update license on affected machines by running command "slmgr.vbs /ato" but geeting error.

Error is attached for the reference.
KMS-Error.jpg
0
 
LVL 17

Accepted Solution

by:
Learnctx earned 275 total points
ID: 39671888
It looks like you have not activated enough clients with theKMS. Try running the following command:

Slmgr.vbs /dli

If the count is not higher than 5 you need to activate more hosts.

If the count is higher than 5, then try re-arming your end points, restarting them and then reactivating them.

Step 1: Re-arm by using command "slmgr.vbs -rearm"
Step 2: Reboot
Step 3: Activate "slmgr.vbs -ato"

If the count is higher than 5 make sure to check the key management service event log in eventvwr for any errors.

If you have Office bundled there is a good blog post here from Microsoft if you have not correctly sysprep'd the machines.

https://blogs.technet.com/b/odsupport/archive/2010/06/14/troubleshooting.aspx.
0

Featured Post

Independent Software Vendors: 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!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article outlines the process to identify and resolve account lockout in an Active Directory environment.
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question