Office 2010 KMS Host Activation

I have a KMS host setup on Server 2012 R2.  I want to use this to activate Office 2010 clients.  I have VAMT installed.  Some of the workstations are showing up under License Status as "Licensed".  Others are showing up as "Out of box grace".  On the workstations that show "Out of box grace" the message "Product Activation Required" is appearing.  I had a virtual box setup from a couple of months ago and it eventually timed out after the 30 day threshold I assigned.  I obviously need to get this fixed in the next month so workstations don't lose their office license.

Some things I have tried:

1)  Running "cscript ospp.vbs /act" from and out of box grace workstation gives the error message "The software licensing service reported that the computer could not be activated.  The count reported by your Key Management Service (KMS) is insufficient.

2)  From the host running "cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864"

(summary of results)

Current count: 4
Total requests received: 42
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 12
Requests with License Status Initial grace period: 30

I have run other diagnostic commands as well but these seem to offer up the most information, at least to start with.  I thought I needed to get to at least a count of 5 but in VAMT it is showing 6 workstations with a License Status of "Licensed".  Could this be a DNS problem?

From a client I ran the command "nslookup -type=srv _vlmcs._tcp >%temp%\kms.txt" and the result was:

*** can't find _vlmcs._tcp: Non-existent domain
schwientekdIT DirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

schwientekdIT DirectorAuthor Commented:
It turned out to be a DNS issue.  I will leave the question here and explain my solution:

1.Open the DNS Microsoft Management Console (MMC).

2.Expand the DNS Zone to the Connection-specifc DNS Suffix for domain.

3.Right-click on the _tcp folder and select Other New Records.

4.Select Service Location (SRV) as the new record type.

5.Fill in the following information for the new record:
Service: _VLMCS
 (Note: This is not in the drop-down list, so you'll need to type it in. Be sure to include the underscore at the beginning.)
Protocol: _tcp
 (Note: Select this from the drop-down list.)
Port: 1688
Priority: 10
Host offering the service:

Workstations are now registering correctly.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.