Please follow these methods below to have a check, and post the result here to share with us. Maybe you can provide more information to help me analyze the issue for me. Any idea is welcome! Thanks in advance for your help. I'm out of ideas now and asking the wise Microsoft-TechNet-Community for some guidance. Is O activation maybe simply not working with such old structures we're about to update but that's still taking time. Is it maybe just due to the R2 domain controller? Vin app VAMT tells that it could not activate the keys. The standard port is allowed and also flawlessly working for the other activations. Meanwhile reactivating Windows 10 or Office is still working on the exact same client.
But still the client won't activate and throw the following errors.
Thus, as far as I understand, the functional level of the KMS running server is limited to R2, too, which could cause most of the problems we currently face. 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.
