Issues with KMS setup

[neonetman]

Good mornign all,

 

Following a failure of one of our DC's, I'm having to set up a new KMS from scratch:-

 

* I've downloaded the Office 2019 Volume Activation Pack and installed that on the new server

* I've downloaded the VAMT tool from Windows ADK

* I've inserted our Windows 10 KMS key using slmgr.vbs /ipk on the DC

* I've scanned the domain for machines using VAMT

* NSlookup shows I have the correct DNS entries for volume licensing

* slmgr /dli all gives me current count of 2 and total requests of 3079 (suposedly all withing grace period)

* Trying to activate a client with using VAMT, or using slmgr /ato on the client gives me an error code of 0xC004F074 no KMS could be contacted

* The windows firewall on the server is currently switched off for testing

* Trying to telnet to {DC}:1688 gives a blank screen and no response

* Trying to telnet to {client}:1688 from the DC gives connection refused

 

I'm at a loss where to look next as I've tried everything I can think of, as well as trawling Google.

[RLR]

The one time I had KMS issues was a while back but I had to create a manual DNS entry to fix it: https://docs.microsoft.com/en-us/windows-server/get-started/common-troubleshooting-procedures-kms-dns

 

Will need to scroll down a bit but might be worth reading it all if you've not done so already.

[jthompson]

Have you considered using Active Directory-based activation rather than KMS? I think it's quite a bit simpler with the newer AD-based method. From what I remember, just add the Volume Activation Services role to a server, use the wizard to add the required KMS key(s) and that's it. Your keys will be stored in AD rather than on a KMS server. You might still need a KMS server for older products, but if you're Win10 and Office 2019, it should be fine without.

 

https://docs.microsoft.com/en-us/deployoffice/vlactivation/activate-office-by-using-active-directory

[tmoon-mint]

Have you considered using Active Directory-based activation rather than KMS? I think it's quite a bit simpler with the newer AD-based method. From what I remember, just add the Volume Activation Services role to a server, use the wizard to add the required KMS key(s) and that's it. Your keys will be stored in AD rather than on a KMS server. You might still need a KMS server for older products, but if you're Win10 and Office 2019, it should be fine without.

 

https://docs.microsoft.com/en-us/deployoffice/vlactivation/activate-office-by-using-active-directory

 

Windows 8.1 and Office 2016 also support active directory based activation soo all supported products should be okay.

[3s-gtech]

KMS used to actually be something I had to faff about with and manage until I moved to AD based activation. It’s just better.