Adding Office 2016 to KMS killed it

[Sheridan]

I've just added the Office 2016 KMS to our 2012 Server running KMS, which was sucessful - until the end when I close the dialogue box

 

Now the KMS service (software protection?) can't be stopped/started and KMS is completely unresponsive. I'm not able to reboot this server for a while as its in use and I suspect my KMS is now knackered.

 

There's so little in the way of diagnostics for kms, has anyone found a way to 'reset' it?

[Sheridan]

Moved it to a new server, and changed the DNS entry - now working again! Can't even uninstall the service on the old one so I've left it.

[3s-gtech]

I'm banging on about it at the moment, but have a look at Active Directory Activation. It has more UI tools (including adding keys and reporting) and doesn't have some of the more onerous parts of KMS. Plus, it works nicely alongside it, and doesn't take long to get running.

[Sheridan]

Ad activation is an option for when we run w10 clients, which brings so many nightmares that activation will be the least of them! [emoji3]