![]() The Reddit article states microsoft couldn't fix the issue but one of the poster's mentioned deactivating and reactivating the KMS host - something i don't want to do. So the issue is, running slmgr -ato on a windows 10 machine where the KMS is hosted on a patched Windows Server 2019, the Windows 10 machine reports the KMS server cannot be reached. I'd be interested to know if anyone has applied either the March 2022 or April 2022 update and are having the same issue. We found something on reddit which points to an update which is borking the KMS. ![]() Our other servers work as expected when we run slmgr -ato on them and find the KMS server without any issues. Looking into this, none of the machines on the domain are auto licensing themselves against the server when we run slmgr -ato yet our Office KMS works without any issues. We have been testing the roll out of our image (windows 10) and noticed it isn't licensing against the KMS server. ![]() Windows Server 2019 requires license activation after 180 days, otherwise the system will. We ran the latest round of updates over the easter holidays and our KMS server is on one of our Virtual DCs - this is Windows Server 2019 Server. At a command prompt, on the KMS server try typing: slmgr /ipk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |