![]() Update: I checked a few of my 2016 datacenter servers that use ADBA. ![]() Volume activation expiration: 258159 minute(s) (180 day(s))Īctivation Object name: Windows Server 2019 DataCtr/Std KMS ![]() The slmgr /dli all output shows the following Name: Windows(R), ServerDatacenter editionĭescription: Windows(R) Operating System, VOLUME_KMSCLIENT channel The 2019 server I activated is datacenter with desktop experience. I have not checked to see if this impacts 2016 in my environment. I have not tried it via KMS since I am trying to move to strictly ADBA. I ended up removing the 2019 key, installing volume activation tools on the 2019 server, installing the 2019 key into AD from the 2019 server, and then I could activate a 2019 server. Yesterday, I loaded the 2019 KMS key into AD from a 2016 server using volume activation tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |