Fix it now
Microsoft publishes 8557 as “Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain.” The join was refused by a quota, not by a password or a network fault. Delegate rather than raise the number: accounts with delegated rights to create computer accounts are exempt.
Add-Computer -DomainName corp.example.com -OUPath "OU=Workstations,DC=corp,DC=example,DC=com" -Credential (Get-Credential) -Restart
- Delegate control on the organisational unit machines are built into, granting the right to create computer objects. Microsoft states that users with delegated permissions on containers to create and delete computer accounts are not restricted by the quota.
- Or pre-stage the object centrally and let the machine claim it, which takes the creation out of the joining account’s hands entirely.
- If you want to read or change the quota itself, Microsoft documents Adsiedit.msc and the ms-DS-MachineAccountQuota attribute on the domain head. The default allows an authenticated user to join ten machine accounts.
- Then reconcile the device count against your client access licences, because an estate that has grown into this ceiling has usually grown past what anyone last counted.
Raising the quota clears the error and is the wrong move. The quota is the only limit on how many computer accounts an ordinary account may create, and a computer account an attacker creates is one an attacker controls.
If the object appears in the OU you targeted, you are done. If not, the next section separates the quota from the three refusals that look like it.
Why it happens
ms-DS-MachineAccountQuota is an attribute on the head of the domain naming context. Microsoft’s own wording is that by default authenticated users are allowed to join ten machine accounts to the domain. It is not a pool you top up centrally; it is an allowance that applies to ordinary accounts, and error 8557 is the directory saying that this account has spent it.
The reason the default exists is that it lets an ordinary user join their own machine without a helpdesk ticket, while stopping a compromised account creating computer objects in bulk. Microsoft names two categories that are not restricted by the limitation: users in the Administrators or Domain Administrators groups, and users who have delegated permissions on containers in Active Directory to create and delete computer accounts. That second exemption is the whole fix, and it is why raising the number is unnecessary as well as unwise.
The related codes are different refusals wearing similar clothes. 1317, ERROR_NO_SUCH_USER, is published as “The specified account does not exist”, which is usually a typo or the wrong domain. 8305, ERROR_DS_OBJ_STRING_NAME_EXISTS, is “An attempt was made to add an object to the directory with a name that is already in use”. 2224, NERR_UserExists, is “The user account already exists” reported through the older network management layer. The last two turn up constantly when a machine is rebuilt under a name whose old object is still there.
A deployment account has spent its allowance
You have this one if The failure follows the account rather than the machine: a different administrator can join the same computer without trouble.
- Delegate the right to create computer objects to that account on the organisational units where machines land.
- Confirm the delegation took by joining one machine into that OU with the same account.
- Leave the quota alone. Delegated creation is exempt from it.
This is the fix Microsoft’s own guidance points at, and it is also better practice than either raising the quota or handing the deployment account Domain Admin.
The quota was set to zero and nobody delegated
You have this one if The attribute reads 0 and nobody can join anything except administrators.
- Leave the quota at zero. That part of the configuration is correct and deliberate.
- Delegate the right to create computer objects on each organisational unit where machines are meant to be created, or pre-stage every object centrally as part of the build.
- Record which accounts hold the delegation so the next person does not raise the quota to work around it.
The computer name is already taken
You have this one if Error 8305 or 2224 rather than 8557, on a machine being rebuilt under a name it has had before.
- Find the existing object and decide whether to reuse it, which keeps its memberships and security identifier, or remove it and start fresh.
- To reuse it, reset the account and join with an account that holds rights over that object.
- To remove it, disable it first, wait, and only then delete.
Stale objects from years of rebuilds
You have this one if The directory holds hundreds of computer objects whose last logon timestamps are months or years old, and nobody can say which are real.
- Find the inactive ones and disable rather than delete them.
- Move the disabled objects into a holding organisational unit and wait several weeks, so that seasonal and loan machines reappear.
- Delete only what is still untouched at the end of that window.
Deleting a computer object breaks that machine’s trust with the domain and destroys its security identifier, so anything granted to that computer has to be rebuilt. Disable, wait, then delete.
Full reference
The four codes
| Code | Symbolic name | Microsoft’s published text |
|---|---|---|
8557 |
ERROR_DS_MACHINE_ACCOUNT_QUOTA_EXCEEDED | Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased |
0x525 (1317) |
ERROR_NO_SUCH_USER | The specified account does not exist |
8305 |
ERROR_DS_OBJ_STRING_NAME_EXISTS | An attempt was made to add an object to the directory with a name that is already in use |
2224 |
NERR_UserExists | The user account already exists |
Who the quota does not apply to
Microsoft is explicit about the exemptions, and they are the difference between a five-minute fix and a security decision you will regret. Users in the Administrators or Domain Administrators groups are not restricted by the limitation. Neither are users who have delegated permissions on containers in Active Directory to create and delete computer accounts. Everything else about how the allowance is accounted for is detail; those two exemptions are what you act on.
Reading and changing the attribute
| Item | What it is |
|---|---|
ms-DS-MachineAccountQuota |
The attribute on the domain head. Default allows an authenticated user to join ten machine accounts |
| Adsiedit.msc | The tool Microsoft documents for viewing and changing the attribute |
| Delegate Control on an OU | The supported way to let an account create computer objects without the quota applying |
| Pre-staging | Creating the object centrally in advance, so the joining account never creates anything |
Setting the quota to a large number removes the only brake on how many computer accounts an ordinary account can create. Setting it to zero and delegating properly is the hardened configuration, and it is not more work once the delegation exists.
Pre-staging as a build step
Where machines are built by an imaging or provisioning system rather than by hand, pre-staging is usually cleaner than delegation. The object is created in the right organisational unit, with the right name, before the machine exists; the machine then claims it rather than creating anything. That also fixes the rebuild problem in passing, because the object the machine claims is the one that already carries its group memberships and its security identifier.
The half of this that is not technical
Hitting the machine account quota is a reliable sign that the estate has grown since anyone counted it. That matters because Windows Server access is licensed by client access licences: Microsoft’s own edition documentation gives the maximum number of users for Windows Server 2025 Standard, Datacenter and Datacenter: Azure Edition all as “based on CALs”. Nothing in the product will tell you whether you have enough. The join will succeed once you have delegated, and the obligation to be correctly licensed is separate from whether the technical block is gone.
Choosing between user and device licensing
The two models suit opposite patterns and the arithmetic usually settles it. Where several people share each machine – shift work, a shop floor, a ward, a classroom – licensing the device once regardless of who sits at it is the smaller number. Where each person uses several devices, licensing the person is. Estates rarely fit one model neatly, and mixing them across an organisation is normal rather than a compromise. What matters is that the count comes from your own headcount and device figures rather than from a rule of thumb.
When a licence is the actual fix
The technical block is removed by delegation and costs nothing, so do that first and do not let anyone sell you a way around it. The part that may cost money is separate: every user or device that accesses Windows Server needs a client access licence, and Microsoft’s own edition documentation gives the maximum number of users for Windows Server 2025 Standard and Datacenter alike as based on CALs. Running into the machine account quota is a good moment to reconcile the count, because it usually means the estate has grown since anyone did. Device CALs are the right shape where several people share each machine and user CALs where each person uses several devices; most organisations end up with some of both. Arco supplies both, will work out which model fits your ratio of people to devices, and will tell you if your existing agreement already covers what you have added.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
8557 |
ERROR_DS_MACHINE_ACCOUNT_QUOTA_EXCEEDED: the computer could not be joined because the account has exceeded the maximum number of computer accounts it may create in this domain | Microsoft Learn |
0x525 |
Windows error 1317, ERROR_NO_SUCH_USER: the specified account does not exist | Microsoft Learn |
8305 |
ERROR_DS_OBJ_STRING_NAME_EXISTS: an attempt was made to add an object to the directory with a name that is already in use | Microsoft Learn |
2224 |
NERR_UserExists: the user account already exists, reported through the network management layer | Microsoft Learn |
Confirm the fix worked
- The new computer object appears in the organisational unit you targeted.
- The same deployment account joins a second machine into that OU without the error returning.
- The ms-DS-MachineAccountQuota value is unchanged from what you intended it to be.
- A domain user signs in at the console of the newly joined machine.
- Your device and user counts reconcile against the client access licences you hold.
Questions people ask about this
Should I just raise the quota?
It clears the error and it is the wrong move. The quota is the only limit on how many computer accounts an ordinary account can create, and a computer account created by an attacker is one an attacker controls. Delegation achieves the same result for the people who should have it.
Does delegation really bypass the quota?
Yes. Microsoft states that users who have delegated permissions on containers in Active Directory to create and delete computer accounts are not restricted by the limitation, along with members of Administrators and Domain Administrators.
What is the default?
Microsoft’s wording is that authenticated users are allowed to join ten machine accounts to the domain by default. The attribute is ms-DS-MachineAccountQuota on the head of the domain, and Adsiedit.msc is the documented way to read or change it.
How many client access licences do I need?
One per user or one per device depending on the model you choose, and you can use both models across an estate. Microsoft’s edition documentation states only that the maximum number of users is based on CALs, so the count has to come from your own figures.
Why did I get 8305 instead?
Because an object with that name is already in the directory. That is a rebuild colliding with its own history rather than a quota problem, and the fix is to reuse the existing object or remove it deliberately.
