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:
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?
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?
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!
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).
Following on from my previous blog here, I had jumped through the Microsoft hoops to get my nice shiny gold padlock and green bar.
However all was not delivered as expected!
Ever since I started tinkering with SSL and HTTPS, I have had an unnatural hankering to move over into Extended Validation. It sounded simple enough, as per these Microsoft articles here, here and here.