Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,436 questions
2 kms key host 2016-2019
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 13%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Mario
20
Reputation points
In my infrastructure I have 2 "central" ADs where the FSMO roles are distributed, and I also have 5 more sites with their own AD in their own vlan. All the ADs see each other and I have a replication process between them. Hub-Spoke. all ADs are global catalog
In a central AD, the volume activation services role with kms is operational and I understand that a host key based on 2016 was used to register. This has been the case for several years, there is a 2016 exchange, 2016 servers and WS activated 10 this way.
Currently we obtained another key host that is 2019, we want to configure it in a new AD2019 that would be added (same domain) where the volume activation serices role would be and see if the 2019 servers are activated in it.
What we don't want is for them to miss the activation of the current exchange, because we all know what happens if emails in a company stop working :)
I don't have much experience with coexistence within 2 kms. And if the key hosts are compatible or one steps on the other, for example, the 2019 key host activates both 2016 and 2019. How can I know that? What can I obtain from the licensing portal as additional information?
I just know that we have both types of MAK and KMS licensing.
Thanks!