D
DaveBryan37
The problem with KMS issues is that searches get flooded results from people having the normal problems(needing updates, DNS discovery, etc.)
I have a 2012R2 KMS server that works fine with all other clients(achieved minimums) and has updates KB3173424 & KB3172614(sppsvc version is 6.3.9600.19101). It has the correct Windows Srv 2016 DataCtr/Std KMS key installed from the MVLS site. Only the 2016 clients come back with "No KMS could be contacted", but if you look in the logs of the KMS server you can see it was contacted by that client and processed the request(EventID 12290 - Activation processed - "0xC004F042") It is communicating for sure, but we are getting a version mismatch according to the page below. All updates have been applied on both client and server. I have tried the /skms, /ipk, /ato,, etc switches on the clients with the correct parameters even though they are communicating, but always same error. The clients are using the standard KMS keys, and I have a feeling they would work with our CSVLK key, but I have always read that is a bad fix to have all of your clients using that key. We are not to ADBA yet because we still have Win7 and 2008R2 clients.
So I have client to server communication 100%, updates KB3172614 & KB3173424 installed/rebooted, and ourcorporate Windows Srv 2016 DataCtr/Std KMS key installed/activated. What am I missing?
Windows Server 2016 Volume Activation Tips
Appendix A: KMS Client Setup Keys
Activation Error Codes for Volume Activation
https://technet.microsoft.com/library/jj612867.aspx
Thanks,
Dave
Continue reading...
I have a 2012R2 KMS server that works fine with all other clients(achieved minimums) and has updates KB3173424 & KB3172614(sppsvc version is 6.3.9600.19101). It has the correct Windows Srv 2016 DataCtr/Std KMS key installed from the MVLS site. Only the 2016 clients come back with "No KMS could be contacted", but if you look in the logs of the KMS server you can see it was contacted by that client and processed the request(EventID 12290 - Activation processed - "0xC004F042") It is communicating for sure, but we are getting a version mismatch according to the page below. All updates have been applied on both client and server. I have tried the /skms, /ipk, /ato,, etc switches on the clients with the correct parameters even though they are communicating, but always same error. The clients are using the standard KMS keys, and I have a feeling they would work with our CSVLK key, but I have always read that is a bad fix to have all of your clients using that key. We are not to ADBA yet because we still have Win7 and 2008R2 clients.
So I have client to server communication 100%, updates KB3172614 & KB3173424 installed/rebooted, and ourcorporate Windows Srv 2016 DataCtr/Std KMS key installed/activated. What am I missing?
Windows Server 2016 Volume Activation Tips
Appendix A: KMS Client Setup Keys
Activation Error Codes for Volume Activation
https://technet.microsoft.com/library/jj612867.aspx
Thanks,
Dave
Continue reading...