Tag Archives: Key Management Service

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 – Shutting Down the Old KMS

Just a couple of quick tips from my experience. I kept the original KMS server active, but offline in case I needed a fallback.

1: Disable the KMS service. Seriously, stop it. In fact, burn it with fire as it has a habit of restarting at the most inopportune of times πŸ˜›

2: Your old KMS server will still receive requests if it remains in DNS. This isn’t too bad, as when a client cannot get to the KMS server, it will try something else from DNS.

As stated in earlier blogs, use the nslookup ocmmand to find the _VLMCS entries. You *must* have your new KMS servers in DNS!

3: If you’re happy with hte new KMS sevrer(s), then you need to remove DNS publishing and from DNS itself.

This is a great step by article, and really helped me through this process.

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 – Licensing previous versions of Office

Okies, hit an interesting snag. I am getting very close to decommissioning my old KMS server. but I had a slight niggle on my new KMS boxes. Namely:

An activation request has been processed.

Why you no license?

Why you no license?

Continue reading

Key Management Service – The Volume Activation Management Tool GUI

Hi. As per previous posts, I’ve been tinkering with the Key Management Service (KMS). Today I will cover the Volume Activation Management Tool (VAMT).

This GUI is a very useful management tool, and I do recommend it (especially when people ask license type questions!).

It’s a very straight forward thing to set up, as long as you avoid the gotchas. Which I did not!

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