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

Continue reading

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