![]() ![]() ![]() It is not a GPO issue, since his server, as well as mine, and our 2012 R2 servers in this environment are all under the same OU and are getting the same policies. Additionally, a colleague of mine deployed a 2019 server a few weeks ago, and that one is working fine (he used a different deployment method than I did). We still have the occasional 2012 R2 deployment, and those servers activate as soon as they are on the network. This is only the issue with these two servers. They will activate every time I do that, but they never, ever do it on their own. I have to manually run this command: slmgr /ato These two systems will never, ever reactivate on their own. However, the way KMS works is that systems should automatically attempt to reactivate every seven days. I can run the command to manually activate them, and they will activate. The current issue is that the two 2019 Standard VMs I have deployed in our development environment will not automatically activate. We have published SRV records in DNS to handle activation. We have two KMS hosts handling Windows/Microsoft licensing for pretty much the entire fleet. Most of them are 2012 R2, with a few stragglers running Server 20 R2. ![]() Our current footprint is about ~500 Windows Servers. I am working on onboarding Windows Server 2019 for my company. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |