Configuring ADBA

To configure ADBA in an organization's activation server (running Windows Server 2016), complete the following steps:

  1. The system administrator needs to install the ADBA role service on a domain controller, as shown in Figure 5.12, including the KMS host key (see Figure 5.13):
Figure 5.13: Configuring ADBA in Windows Server 2016
Figure 5.14: Installing the KMS host key
  1. The system administrator needs to activate the KMS host key with Microsoft-hosted activation services using the Volume Activation Management Tool (VAMT).
  2. Once the domain member computers that are running Windows 10 (excluding Home edition) are powered up, the licensing service on such computers automatically queries the AD for licensing information.
  3. Actually, the client computer queries Active Directory Domain Services (ADDS) for activation information.
  4. If the licensing service on the client computers finds a valid activation object on a domain controller, the activation takes place silently without any user intervention.
  5. If the licensing service on the client computers does not find a valid activation object on a domain controller, the client computers look for a KMS host in order to attempt activation.
ADBA simplifies the volume activation process by activating clients that are running Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019. It requires extending the AD schema by running adprep.exe.