Active Directory-Based Activation (ADBA): Setup Guide

Active Directory-Based Activation (ADBA) lets domain-joined computers activate Windows and Office using information stored in Active Directory. There is no separate activation server to maintain and no minimum number of devices. For many organizations, ADBA is the simplest way to manage volume activation.

How ADBA Works

An administrator adds an activation object to Active Directory using a KMS host key (CSVLK). When a domain-joined computer with a Generic Volume License Key starts up, it reads the activation object from Active Directory and activates automatically. Activation lasts 180 days and is renewed whenever the computer is in contact with the domain.

ADBA vs KMS

Many organizations run ADBA for domain members and keep KMS for devices that are not joined to the domain.

Requirements

• Active Directory schema at a level that supports ADBA (Windows Server 2012 or later)
• Clients running supported versions of Windows and Office volume editions
• Enterprise Admin rights to create the activation object
• A valid CSVLK from your volume licensing agreement

Step-by-Step Setup

1. On a domain-joined Windows Server, open Server Manager → Add roles and features and install the Volume Activation Services role.
2. Launch Volume Activation Tools from the Tools menu.
3. Select Active Directory-Based Activation as the activation type.
4. Enter your CSVLK and give the activation object a descriptive name, such as “Windows 11 Enterprise”.
5. Activate the object online or by phone.
6. Repeat for additional products, such as Office LTSC, using the appropriate CSVLK and the Office volume license pack.

Activation objects replicate across domain controllers like other directory data.

Planning Before You Start

Before creating activation objects, list every product and version you plan to activate, such as Windows 11 Enterprise, Windows Server and Office LTSC. Each product family needs its own CSVLK. Confirm which keys you own in your volume licensing portal, and decide where devices outside the domain will activate. Documenting this plan makes audits easier and avoids accidentally activating editions you are not licensed for.

Security Considerations

Treat CSVLKs as sensitive credentials. Store them in a secure vault, limit access to a small group of administrators and never paste them into tickets or chat messages.

Configuring Clients

Volume-licensed installations of Windows and Office already contain a GVLK, so no extra configuration is usually needed. Simply join the computer to the domain and restart it. To confirm activation, run:

slmgr /dlv

The output should mention activation through Active Directory and display the name of the activation object.

Managing Activation Objects

• View objects with Volume Activation Tools or in ADSI Edit under the Activation Objects container in the configuration partition.
• Delete outdated objects when you retire product versions.
• Restrict who can modify objects to Enterprise Admins only.

Troubleshooting

• Clients not activating: confirm they are domain-joined and have a GVLK installed rather than a retail or MAK key.
• Office not activating: make sure you added an Office activation object using the Office volume license pack.
• Remote workers: devices must contact the domain at least once every 180 days, for example over VPN.

Frequently Asked Questions

Can ADBA and KMS run at the same time?

Yes. Domain members use ADBA first, while other devices can still use a KMS host.

Does ADBA work with Microsoft Entra ID-only devices?

No. ADBA requires on-premises Active Directory. Cloud-only devices typically use subscription activation.

Is there a limit on the number of devices?

ADBA itself has no technical limit, but you must stay within the licenses you purchased.

Conclusion

ADBA is a lightweight way to activate Windows and Office across a domain without running a KMS server or worrying about thresholds. Create activation objects once, and domain-joined computers activate themselves.