Can anybody shed some light on why this would be talking to my old KMS server and not my ADBA server? It is my understanding that since I installed an ADBA server it should be checking there first, and like I said above I can verify that it is working because my Windows 10 systems are activating fine. So I ran the /dhistorykms switch and it looks to be trying to activate on the KMS server instead of the ADBA server so it fails because I don't have any Office 2016 KMS keys on it. So through the course of trouble shooting the problem I found the ospp.vbs script and tried to force an activation with the /act switch, which fails.
The KMS key I got from the VLSC added perfectly and shows as available. I've installed the KMS key on the ADBA server as well as the 2016 volume license pack. My problem is I can't seem to get my Office Standard 2016 Volume licenses to activate. So I installed server 2019 and setup ADBA and it is licensing my Windows 10 system beautifully. I have setup up an Active Directory Based Activation server (ADBA.) I also have a Key Management Server (KMS) The KMS server has been in place for years with no problems but it's time to move to a newer server as it's 2008R2 and I need to start activating Windows 10 and Office 2016 licenses.