windows server 2019 kms activation not working

I tried the /dlv switch, which will display detailed license information. Knowing that the slmgr command is my friend for license activation, I continued with different options. This confirms our Active Directory is correctly configured to activate Windows KMS Clients The results show that we have two Activation Objects: one for Server 2012 R2, and our newly created KMS AD Activation (** LAB) which is our Windows Server 2016 license. The /ao-list switch displays all activation objects in Active Directory. I went to one of my problem servers, opened a command prompt, and checked my output from the slmgr /ao-list command. Of course, the first question was “What changed over the weekend?” And as usual the answer was “nothing.” This time, nothing really had been changed, and we had to figure out what was going on. I went to the customer to discuss what had happened. Hey! That’s not right! I went back to the physical machine and it was fine. I came back into the office on Monday, and all the virtual machines I had built the week prior showed that they weren’t activated. Truthfully, the set up and configuration were super easy, so that part was simple and straight forward. Haha! Just kidding! Nothing is ever that easy. We built a physical server running Windows 2016 Standard, and the machine activated properly. At this point everything was great, and everyone was happy. We started by building four virtual machines, two Windows 2016 Standard and two Windows 2016 Datacenter. We pretty much followed the blog post step by step. We installed our KMS key and gave it a name of 'KMS AD Activation ( ** LAB)'. We installed the role on a Windows Server 2012 R2 Domain Controller and chose Active Directory Based Activation as our volume activation method. The domain controllers in our test environment were all running Windows Server 2012 R2, so we did not need to prep our forest. We began our deployment by following the instructions in this excellent blog post by Charity Shelbourne, Active Directory-Based Activation vs. We took this opportunity to also migrate their activation methodology from a KMS Server to Active Directory Based Activation.Īs proper procedure for making all changes, we started our migration in the customer’s test environment. I recently helped a customer with deploying Windows Server 2016 in their environment. Hello everyone! My name is Mike Kammer, and I have been a Platforms PFE with Microsoft for just over two years now. This article was originally published as a TechNet blog on March 26, 2018.

Windows server 2019 kms activation not working