Fix it now
Error 8568 is ERROR_DS_LOW_DSA_VERSION: the level cannot be raised because one or more domain controllers in scope are at a lower, incompatible functional level. Where 8565 is a promotion blocked by a level, 8568 is a level blocked by a controller. The fix is never to force the raise; it is to find the server and deal with it.
Get-ADDomain | Format-List Name,DomainMode
Get-ADForest | Format-List Name,ForestMode
Get-ADDomainController -Filter * | Sort-Object OperatingSystemVersion | Format-Table Name,OperatingSystem,OperatingSystemVersion,Site,IsGlobalCatalog -AutoSize
nltest /dclist:contoso.com
repadmin /replsummary
- Compare the two lists.
Get-ADDomainControllerreads the directory and includes servers that are switched off;nltest /dclist:shows what the domain currently advertises. A server in one list only is either dead metadata or an advertising problem. - For each server below the target level, either upgrade it or remove it.
Uninstall-ADDSDomainControlleracts on the server you run it on, so it goes on the machine being removed, not on a peer. - Push the change out and confirm every partner has seen it before you retry, because the raise reads the directory rather than the network.
- Retry the raise as a member of Enterprise Admins for the forest, and raise every domain that is behind before you attempt the forest at all.
The change is irreversible. Microsoft states that undoing a functional level change requires a forest recovery to an earlier point in time, so take a system state backup of two healthy controllers first.
If the level reads back correctly from a controller in another site, you are done. If the raise is still refused, the next section covers what else counts as a domain controller as far as this check is concerned.
Why it happens
The behaviour version stored on the domain and on the forest is a promise about every controller holding a copy of the partition. Raising it tells the directory it may use object classes, attributes and replication behaviours that older builds cannot interpret. If one controller could not read what the others write, replication would carry it objects it cannot store, so the directory checks first and refuses. Microsoft’s wording for 8568 is exactly that: the level cannot be raised because there exist one or more domain controllers at a lower incompatible functional level.
The detail that costs people the most time is that the check reads the directory, not the network. A server switched off two years ago but never removed still counts, because its NTDS Settings object still sits under its server object in the configuration partition. Powering a controller off is not the same as removing it, and the directory only knows about the second. This is, by a wide margin, the most common reason an administrator sees 8568 while being certain the offending machine is long gone.
Two neighbouring codes turn up during the same work and both are more specific than they look. 8569 is ERROR_DS_NO_BEHAVIOR_VERSION_IN_MIXEDDOMAIN: the forest level cannot be raised because one or more domains are still in mixed domain mode, and all domains must be in native mode first. 8567 is ERROR_DS_INCOMPATIBLE_VERSION: the operating system installed on this server is incompatible with the functional level of the domain or forest. Neither is a generic status to be read alongside an event; each names its own condition.
The precondition Microsoft states for the raise is short and worth quoting to yourself before you start: all domain controllers in the domain are running at least the version of Windows Server that you want to raise the domain functional level to, and you must be a member of Enterprise Admins or equivalent to raise the forest level. If either is untrue, the raise fails and there is nothing to override.
A live domain controller on an older operating system
You have this one if The sorted list shows a server below the target build, and it answers diagnostics normally.
- Establish what it does: operations master roles, global catalog status, and whether it serves DNS for its site.
- Move those functions to a controller you are keeping, and change any DHCP scope option or static setting naming its address.
- Demote it with
Uninstall-ADDSDomainControllerrun on the machine itself, then remove it from the domain. - Force replication and retry the raise.
Building a new controller and demoting the old one leaves you a machine to roll back to, which an in-place upgrade does not.
A domain controller that is dead but still in the directory
You have this one if The server named does not answer at all, and replication has been reporting failures against it for a long time.
- Confirm it will never rejoin the network. This step is not reversible.
- In Active Directory Users and Computers, with Advanced Features on, delete its computer object from the Domain Controllers organisational unit and confirm the permanently-offline prompt.
- Remove any surviving NTDS Settings and server object in Active Directory Sites and Services.
- Remove its records from DNS, then retry the raise.
A read-only controller, or one in a site you had forgotten
You have this one if Everything in the main data centre is current, and the blocker is a branch server nobody administers directly.
- List them explicitly:
Get-ADDomainController -Filter {IsReadOnly -eq $true} | Format-Table Name,OperatingSystem,Site - Decide whether that site still needs a local controller at all before you replace it with anything.
- Demote it from the branch server if you can reach it. If you cannot, delete its account from a writable controller and choose the option to reset the accounts it cached.
A domain that has not been raised
You have this one if Every domain looks fine when you check the one you are in, and the forest raise still fails – or 8569 appears rather than 8568.
- Enumerate every domain in the forest and read each one’s mode.
- Raise the domains that are behind, one at a time, dealing with their own down-level controllers first.
- Raise the forest only when the lowest domain level in the forest is at or above your target.
Full reference
The three codes, exactly as Microsoft states them
| Code | Name | Published meaning |
|---|---|---|
| 8568 | ERROR_DS_LOW_DSA_VERSION | The functional level of the domain or forest cannot be raised, because one or more domain controllers are at a lower incompatible functional level |
| 8569 | ERROR_DS_NO_BEHAVIOR_VERSION_IN_MIXEDDOMAIN | The forest functional level cannot be raised because one or more domains are still in mixed domain mode; all domains must be in native mode |
| 8567 | ERROR_DS_INCOMPATIBLE_VERSION | The operating system installed on this server is incompatible with the functional level of the domain or forest |
Two lists, and why they disagree
| Command | What it reads | What a discrepancy means |
|---|---|---|
Get-ADDomainController -Filter * |
The directory’s own list of controller objects | A server here but not advertising is switched off, or its metadata was never cleaned up |
nltest /dclist:<domain> |
What the domain currently advertises | A server here but not in the directory list points at a DNS or locator problem |
repadmin /replsummary |
Replication health per controller | Long-standing failures against a name nobody recognises usually identify the dead server for you |
Do not demote a controller that is the only global catalog in its site, the only DNS server its clients point at, or the current holder of an operations master role, until you have moved that function somewhere else. A functional level raise is never urgent enough to justify taking a site offline for it.
Order of work
- Back up the system state of two healthy controllers and confirm the backups restore.
- Build the list of controllers from the directory, not from memory or from a spreadsheet.
- Deal with the live down-level servers: move their roles, then upgrade or demote them.
- Deal with the dead ones: metadata cleanup, then Sites and Services, then DNS.
- Force replication and confirm every partner agrees on the remaining set of controllers.
- Raise each domain that is behind, then the forest, as an Enterprise Admin.
- Read the level back from a controller in a different site to confirm it replicated rather than just being written locally.
What raising the level does not do
- It does not change how member servers or workstations authenticate. Functional levels constrain domain controllers only.
- It does not upgrade anything. Every controller has to already be at the version you are raising to.
- It does not clean up after the controllers you removed. DNS records and Sites and Services objects still need attention.
- It is not reversible. There is no supported way back other than a forest recovery to an earlier point in time.
- It does not fix replication. If replication is broken, raising the level on one controller simply produces a forest that disagrees with itself.
When a licence is the actual fix
If the server pinning your level is physical hardware running a build that no longer receives updates, this stops being a configuration problem and becomes a licensing one: you need a domain controller you are entitled to run. Arco supplies Windows Server 2025 Standard. Before ordering, check what you already hold – a Standard licence carries the right to run two virtual machines plus one Hyper-V host, so a virtual replacement may be covered by a host licence you already have. And if the blocker turns out to be a controller that was decommissioned years ago and never cleaned out of the directory, the fix is metadata cleanup and it costs nothing.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
8568 |
ERROR_DS_LOW_DSA_VERSION, 0x2178: the level cannot be raised because one or more domain controllers are at a lower incompatible functional level | Microsoft Learn |
8569 |
ERROR_DS_NO_BEHAVIOR_VERSION_IN_MIXEDDOMAIN, 0x2179: the forest level cannot be raised while one or more domains are still in mixed domain mode | Microsoft Learn |
8567 |
ERROR_DS_INCOMPATIBLE_VERSION, 0x2177: the operating system installed on this server is incompatible with the functional level of the domain or forest | Microsoft Learn |
Confirm the fix worked
- The raise completes and
Get-ADDomainreports the new DomainMode. - After replication, the level reads the same from a controller in a different site.
Get-ADDomainController -Filter *no longer lists any server you removed.nltest /dclist:and the directory’s own list agree on the set of controllers.- Replication summarises clean across the estate and the domain controller diagnostics pass on two controllers.
Questions people ask about this
The server it names was decommissioned years ago. Why does it still count?
Because the check reads Active Directory rather than the network. Until its NTDS Settings object is removed from the configuration partition, the directory treats it as a member of the domain.
Can I raise the forest and leave one domain behind?
No. The forest level cannot exceed the lowest domain level in the forest, so every controller in every domain has to qualify first. If a domain is still in mixed mode you get 8569, which says so directly.
Is an in-place upgrade of the old controller good enough?
For the level check, yes – what matters is the version the controller reports. Whether an in-place upgrade is supported from your particular build is a separate question, and building a new controller alongside is often quicker and leaves you something to fall back to.
Does fixing 8568 always mean buying a server licence?
No. If the blocker is stale metadata, cleanup is free. If it is a virtual machine on a host with spare licensed capacity, no purchase is involved either. You only buy when you need a licensed instance you do not already hold.
Can I force the raise past a controller I do not care about?
No, and you would not want to. The check exists because the down-level controller would be sent objects it cannot store. Remove it properly instead.
