Fix it now
Active Directory-based activation contacts no KMS host and opens no port: the client reads an activation object out of the forest. When it fails, the two things to establish are whether an activation object exists that covers this edition, and whether the client is actually running a generic volume licence key.
slmgr /ao-list
slmgr /dli
slmgr /ato
slmgr /dlv
- Read the
slmgr /ao-listoutput. It displays all activation objects available to the local computer, and an empty result is your answer. - Read the Description field from
slmgr /dli. It must say VOLUME_KMSCLIENT. RETAIL means the machine was installed from media that left a retail channel key, and directory-based activation will never work until that is corrected. - If the channel is wrong, install the generic volume licence key for the installed edition with
slmgr /ipk <GVLK>and try again. Microsoft publishes the key list. - If no activation object exists, create one from a domain controller: sign in with Domain Administrator and Enterprise Administrator credentials, add the Volume Activation Services role, and run the Volume Activation Tools wizard – or use
slmgr /ad-activation-online <KMS host key> <object name>. - Confirm with
slmgr /dlvthat the licence status reads Licensed and the activation method is the directory rather than a host.
Creating the object writes forest-wide. Local administrator rights are not enough on their own: the account needs read and write access to the activation object container in the root domain, which Enterprise Admins has.
If that fixed it you can stop here. If not, the next section covers how a client finds a licence in the directory and the failure Microsoft documents that nobody expects.
Why it happens
Active Directory-based activation stores a signed activation object in the forest, and any domain-joined computer running a generic volume licence key can read it. There is no service record to publish, no port to open and no activation count to reach, which is the practical difference from the Key Management Service: one machine works exactly as well as five hundred. Microsoft documents it for Windows 11, Windows 10, Windows Server 2022, 2019 and 2016, and for Microsoft Office.
The object is created from a KMS host key issued under your volume agreement, and that key decides which product group it can license. Once published, clients that are domain members and stay in periodic contact with a domain controller remain activated for up to 180 days since that last contact, attempting to reactivate before then. Microsoft states the default reactivation interval as every seven days.
None of the four codes in this record has a published meaning on learn.microsoft.com or support.microsoft.com. 0xC004F304, 0xC004F305, 0xC004F306 and 0xC004F313 are all described here by where they appear rather than by a vendor definition, and the confident readings in earlier versions of this article were unsourced. Run slui.exe 0x2a followed by the code on the failing client to get Microsoft’s own wording for your build.
There is one documented failure for this mechanism and it is not one people guess: servers installed from MSDN media rather than volume licensing media end up on a RETAIL channel key instead of VOLUME_KMSCLIENT. If your failing machines are virtual and your physical ones are fine, check the media before anything else.
The client is not running a generic volume licence key
You have this one if slmgr /dli reports a RETAIL or OEM channel, slmgr /ato returns Product Not Found, and Event ID 8198 appears with 0x8007007B.
- Confirm the channel in the Description field of
slmgr /dli. VOLUME_KMSCLIENT is what you need. - Install the generic volume licence key for the installed edition:
slmgr /ipk <GVLK>. Microsoft publishes the current list. - Run
slmgr /ato, then confirm withslmgr /dlv. - Replace the deployment media. MSDN ISOs install a retail channel key and will keep producing this.
Generic volume licence keys are public and identical on every machine of an edition. The entitlement lives in your agreement, not in the key, and they cannot be used with retail editions.
No activation object was ever published
You have this one if slmgr /ao-list is empty on every client you test, and the Volume Activation Tools wizard shows nothing configured.
- Sign in to a domain controller with Domain Administrator and Enterprise Administrator credentials.
- Launch Server Manager and add the Volume Activation Services role.
- Open the Volume Activation Tools, select the Active Directory-Based Activation option, enter your KMS host key and optionally a display name.
- Activate the key online or by phone, then select Commit and Close.
- On a client, run
slmgr /ao-list, confirm the object appears, then runslmgr /ato.
slmgr /ad-activation-online <Product Key> <Activation Object name> does the same job from a command line. Local administrator access is not required, but read and write access to the activation object container in the root domain is.
The published object does not cover this client’s edition
You have this one if slmgr /ao-list shows objects, but their descriptions name a different product family from the edition on the failing machine.
- Compare the descriptions from
slmgr /ao-listwith the editionslmgr /dlireports on the client. - Obtain the host key that covers the client editions you deploy and publish a second object from it.
- An extra object does not disturb the existing one; clients match whichever covers them.
- Retry
slmgr /atoon an affected client.
Host keys are issued per product generation. A key that predates the Windows release on your desktops will not license them however the object is configured.
The forest schema has not been updated
You have this one if The wizard refuses to create the object, or the activation object container does not exist in the forest at all.
- Microsoft’s requirement is that the forest schema is updated with
adprep.exeon a supported server operating system. - Run the schema update from supported Windows Server installation media, then let it replicate fully before publishing anything.
- Retry the Volume Activation Tools wizard afterwards.
- Note that older domain controllers can still activate clients once the schema has been updated.
The client cannot read the forest, or is not in it
You have this one if The object is visible from a domain controller but not from the failing client, which is in another site or was recently joined.
- Confirm the machine is domain-joined with a working secure channel:
Test-ComputerSecureChannel. - Check that replication has reached the client’s local domain controllers with
repadmin /replsummary. - Refresh policy and retry:
gpupdate /force, thenslmgr /ato. - A device that is Microsoft Entra joined only, with no on-premises domain membership, cannot use this method at all. Use KMS or MAK there.
Full reference
The commands, and what Microsoft says they do
| Command | Documented behaviour |
|---|---|
slmgr /ao-list |
Displays all activation objects available to the local computer |
slmgr /ad-activation-online <key> [<name>] |
Collects Active Directory data and starts forest activation. Needs read and write access to the activation object container in the root domain |
slmgr /ad-activation-get-IID <key> |
Starts forest activation in phone mode and outputs the installation ID |
slmgr /ad-activation-apply-cid <key> <CID> [<name>] |
Completes activation using the confirmation ID from the activation telephone call |
slmgr /del-ao <AO_DN or AO_RDN> |
Deletes the specified activation object from the forest |
slmgr /dli |
Displays licence information, including the Description field that names the channel |
slmgr /ipk <GVLK> |
Installs the generic volume licence key for the installed edition |
The activation object name is limited to 40 Unicode characters. Give it something you will recognise in a year, because the name is what you will type into slmgr /del-ao when you eventually retire it.
The configuration procedure, as documented
- Use an account with Domain Administrator and Enterprise Administrator credentials to sign in to a domain controller.
- Launch Server Manager.
- Add the Volume Activation Services role.
- Select the Volume Activation Tools.
- Select the Active Directory-Based Activation option.
- Enter the organisation’s KMS host key and optionally specify a display name.
- Activate the host key by phone or online.
- Select Commit, then Close.
How long an activated client stays activated
Clients activated this way maintain their activated state for up to 180 days since the last contact with the domain. They attempt to reactivate periodically before then and at the end of that period, and the default reactivation event occurs every seven days. That is a wide margin, which is exactly why a broken publication can go unnoticed for months and then produce a wave of failures across a site within days of each other.
The failure Microsoft documents that nobody expects
| Symptom | Reading |
|---|---|
| Virtual machines fail while physical servers activate | Different deployment media, not a directory problem |
| Event ID 8198 in the Application log with 0x8007007B | The documented signature of the wrong channel key |
slmgr /ato returns Product Not Found |
Same cause: a retail channel key where a GVLK is needed |
slmgr /dli Description says RETAIL |
MSDN or retail media. Install the GVLK and activate again |
slmgr /dli Description says VOLUME_KMSCLIENT |
The channel is right; look at the object and at replication |
Choosing between this and a KMS host
- Directory-based activation has no activation count threshold, no service record to publish and no port to open. That is its main advantage at small scale.
- It only works for forest-joined machines running a supported operating system. Anything outside the forest needs KMS or MAK.
- A KMS host serves machines that are not domain members, which is why many organisations run both for a period.
- Windows and Office are separate product families with separate host keys. Publish one activation object per family.
Where the codes leave you
Because none of the four codes here carries a published meaning, the diagnosis has to come from the two questions at the top of this article: is there an object that covers this edition, and is this client running a GVLK. slmgr /ao-list answers the first and the Description field from slmgr /dli answers the second. Between them they resolve the large majority of these reports without anyone needing to know what 0xC004F304 is supposed to say.
When a licence is the actual fix
Directory-based activation is built on a KMS host key, and a host key is only issued against a volume licence agreement. If the estate has no agreement behind it, or the agreement covers an older Windows generation than the machines you are deploying, no amount of directory work produces an object that can license those clients – the entitlement is genuinely missing. We supply Windows 11 Enterprise volume licences and the host keys that go with them, and can check which host key generation covers the client editions in your estate before you commit. That is the step most organisations skip when they upgrade desktops but not the agreement underneath them.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F304 |
Reported by a client that queried the directory and did not obtain an activation it could use. No published meaning; read the machine’s own text with slui.exe 0x2a | not published by the vendor |
0xC004F305 |
Reported in the same volume activation family. No published meaning | not published by the vendor |
0xC004F306 |
Reported in the same volume activation family. No published meaning | not published by the vendor |
0xC004F313 |
Reported in the same volume activation family. No published meaning | not published by the vendor |
Confirm the fix worked
slmgr /ao-liston an affected client lists the activation object you expect.slmgr /dlireports a Description of VOLUME_KMSCLIENT rather than RETAIL or OEM.slmgr /dlvreports a licence status of Licensed.- Reboot the client and confirm activation persists with no manual intervention.
- Test a machine in a different site, to confirm the object has replicated across the forest.
Questions people ask about this
Does this replace a KMS host?
For forest-joined machines running a supported operating system, it can. There is no count threshold and no port to open. Most organisations run both for a period, because machines outside the forest still need KMS or MAK.
Do I need to buy anything to fix this?
Only if you have no volume agreement, or your host key predates the editions you are deploying. If both are current, this is a publishing, media or replication problem and costs nothing.
Can one object license both Windows and Office?
No. They are separate product families with separate host keys. Publish one activation object per family.
Why do my virtual machines fail while the physical servers activate?
Check the media. Microsoft documents exactly this pattern: an MSDN ISO installs a RETAIL channel key rather than VOLUME_KMSCLIENT, which produces Product Not Found from slmgr /ato and Event ID 8198 with 0x8007007B. Install the correct KMS client setup key and activate again.
How long can a client go without contacting a domain controller?
Up to 180 days since the last contact. Clients attempt to reactivate periodically before then, with a default reactivation event every seven days.
