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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |