DNS auto-discover: KMS name not available

Question

_{Monday, July 1, 2013 5:29 PM}

I installed and configured the Office 2013 KMS Host on Server 2012 however none of the client Office 2013 will find or activate themselves.  When doing a cscript ospp.vbs /dstatusall it says the "DNS auto-discover: KMS name not available".  I tried to manually set the KMS host via "slmgr.vbs /skms FDQN:PORT" but it still can't find or activate Office.

I am only using KMS for Office 2013.  What am i missing?

All replies (4)

_{Monday, July 1, 2013 9:33 PM ✅Answered}

Hi,

is your KMShost servicing any clients, for any products (e.g. Windows activation)?

maybe you haven't opened the Windows Firewall on the KMShost, so that's why clients can't contact the KMShost?

on the KMShost, check it with cscript slmgr.vbs /dli all
this will show you if the KMShost is receiving any client requests.
the KMShost should be listening on TCP port 1688, can you telnet to this port (from a client) - do you get refused?

Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

_{Friday, July 5, 2013 6:57 AM}

Hi LMNAmis,

Just checking to see how is everything going on?

Max Meng
TechNet Community Support

_{Wednesday, July 24, 2013 3:33 AM}

Hi,

I've marked the reply as answer as there has been no update for a couple of days. Please let us know if you would like further assistance.

Max Meng
TechNet Community Support

_{Friday, September 6, 2013 2:38 PM}

Unfortunately, you can´t use slmgr for Office 2013. Not run. 

I had this problem in few computers last week.

For while, I use this commands:

1. How to verify status of license?
   Execute  cscript "C:\Program Files\Microsoft Office\Office15\OSPP.VBS" /dstatus
2. How to configure KMS for Office 2013?
   Execute: cscript "C:\Program Files\Microsoft Office\Office15\OSPP.VBS" /sethst:sbr00as97.br.biz
3. How to activate the licence 2013?
   Execute: cscript "C:\Program Files\Microsoft Office\Office15\OSPP.VBS" /act

You will need administrative privileges.