Tag Archives: 12288

Key Management Service – Troubleshooting!

So, is the KMS working? I’ve popped together some things to run through to verify Things™. No glossy pictures – I’ve covered most of this in greater depth with pretty pictures in my previous KMS posts 🙂

  • Verify the KMS server record(s) is available via DNS.

The KMS servers must be registered in DNS so that the KMS clients can find them. Execute the following command:

nslookup -type=srv _vlmcs._tcp

…this will return all _vlmcs records. When setting up the KMS server, you will have the option to register it in DNS. Assuming it’s a Microsoft DNS and you have the appropriate permissions, it’s a no brainer! It’s also good for tracking down rogue KMS servers…

  • Check the Event logs on client and the server.

It’s a straight forward process, that should happen on every working system. The KMS client sends a request to the KMS server, found courtesy of the _VLMCS records in DNS. This generates an event ID 12288.

This is the KMS client talking to the KMS server.

The server should then respond, and in turn log an event ID 12290, detailing the machine name, licence type, activation threshold and the result. You’ll find this in the KMS log on the KMS server.

The client, should then report an event ID 12289. This is effectively a closure. Everything has worked as expected. Happy days.

  • The SLMGR.VBS tool.

The SLMGe.VBS came about with VISTA, and was probably the only good thing one could about the initial release of VISTA. SLMGR.VBS has a host, hah no pun intended >_<, of options to choose from. You can manually point the KMS client at a KMS server instead of using DNS discovery for example. You can also strip out VLKs and apply a MAK, or vice versa.

Typically, for troubleshooting, you’ll be querying the KMS client for information. The top two commands I’ve used thus far are:

  1. slmgr.vbs /dli
  2. slmgr.vbs /dlv

You can run these on both KMS client and KMS server.

Thanks for reading o/

Key Management Service – Interpretting the Event Logs

At first glance, you may think the event logs on the KMS client are simple, but they actually provide a wealth of information, if you know what to look for.

A successful client to host communication will result in two events being recorded on the KMS client:

  • 12288
  • 12289

Continue reading

Key Management Service – Is it Working?

Really quick post!

Following my setup of multiple KMS servers in my domain, I was desperate to know if things were working. A new KMS server will need a minimum of activations before you’ll see anything on a client. So how do you know if it is working?

It’s simple!

Continue reading

Key Management Service – Setting it up for Windows 10 and Office 2016.

I picked up another task, which aint too bad. A simple brief, provide Key Management Services (KMS) for Office 2016 and Windows 10.

In order to license Windows 10 and Office 2016 via a KMS, you must run it on Windows Server 2012. It will not work on anything less.

This was a sticking point for my organisation, as we currently host our KMS on Server 2008. This did complicate matters, as I would have two KMS servers. Generally speaking KMS boxes aren’t load balanced, if it is even possible (I don’t think it is).

Continue reading