The standard port 1688 is allowed and also flawlessly working for the other activations. nslookup -type=srv _vlmcs._tcpĪlso shows the correct server as only SRV record.
Meanwhile reactivating Windows 10 or Office 2016 is still working on the exact same client.Ĭscript ospp.vbs /sethst: isn't fixing it.
No Key Management Service (KMS) could be contacted.Įrror 0xC004F042: The Software Licensing Service determined that the specified Key Management Service (KMS) cannot be used. But still the client won't activate and throw the following errors:Įrror 0xC004F074: The Software Licensing Service reported that the product could not be activated. Pro Plus 2010, 20, Windows Server 2008R2, 2012R2, 2016 Standard.Ģ019 Volume License Pack and restarting sppsvc I was also enable to successfully install the Office Pro Plus 2019 KMS Key. Since then everything was working.ĬSVLKs for the following products are installed and automated KMS activation is working for those: Windows 7 and 10 Enterprise, Office Thus, as far as I understand, the functional level of the KMS running server is limited to 2008R2, too, which could cause most of theĪbout half a year ago we reset the KMS service (uninstalled all CSVLKs, deleted SRV record, checked for other SRV records and reinstalledĮverything) as various KMS activations were unsuccessful. KMS service is running on a Windows Server 2012R2 Std which in return based on a 2008R2 domain controller. But unfortunately KMS activation isn't working. After some fiddling I managed installing the suite via ODT and the installation files based on our local fileserver.
I'm an IT administrator in a medium sized company (about ~500 clients) and just tried to deploy Office 2019 Professional Plus VL on a singleĬlient pc for test purposes.
0 kommentar(er)
