There you go
http://nitindupare.blogspot.com/2012/08/uninstall-kms-host.html

http://kapothi.com/switch-windows-10-license-kms-mak/

I'm not even sure this will work but try the following commands and skip step 4.
After uninstalling the KMS license, maybe running cscript slmgr.vbs /ato all you need to activate your Windows 10 upgrade license.

Oh, wait, it's Friday afternoon.

Well this saga isn't over yet.

My old Windows 2008 R2 KMS server is still up and running, has KMS installed, but is NOT published in DNS - I've confirmed this.

But when I went to a computer and ran

cscript slmgr.vbs /ato

to force a re-registration, it still registered with the old server.

Now I've disabled the port (1688) on the old server. Now to see how the client PCs handle that.

@Chris said:

I am not 100% sure on this, but I believe you need the 5+ installs of Office 2016 for KMS to activate the clients.
You can cohost the Office 2013 KMS host and the Office 2016 KMS host on the same system. Its my understanding that the Office 2013 KMS host will only activate Office 2013 clients.

Good to know!
Thanks.

So far the KMS key isn't registering. 😞

OK that's just weird!

There was a contact us email address in VLSC. I wrote them, included my license key and business information. They wrote back today indicating that they would create my key and I would receive it in a separate email. Additionally it would be added to my VLSC account.

I actually received the email with the KMS key before this email, and sure enough, the KMS key is now in my VLSC account.

@NetworkNerd said:

How do they know you are using the one volume license for imaging and not re-using it over and over illegally?

They don't, but as that is generally how it is used, it's not a flag.

Correct, no cons once you get it working and surpass the minimum count.