0X00002113

AD DS Schema Mismatch 0x213: Fix DCPROMO Failures

EP
Erropedia Team
📅 August 6, 2026 📅 Updated Aug 6, 2026 👁 0 views Server & Cloud Intermediate
DCPROMO fails with 0x213 when installing a new DC into an existing forest. Schema version in source vs target is off. Here's the fix.

You're trying to promote a new Domain Controller into an existing forest, DCPROMO runs, gets through the early checks, then dies with ERROR_DS_INSTALL_SCHEMA_MISMATCH (0x00002113). This almost always happens when you're mixing OS versions. Classic scenario: you've got a Windows Server 2003 or 2008 forest, and you're trying to add a Windows Server 2008 R2 or 2012 DC. The new server's schema is newer than what the forest supports, and it refuses to proceed.

Here's what's happening under the hood. Every Windows Server version carries a schema version number. When DCPROMO runs, it contacts an existing DC to check the schema version. If the source DC's schema is older than what the new server expects (usually because adprep /forestprep wasn't run, or was run incorrectly), the install aborts. The error code 0x213 is your clue that this is a schema version mismatch, not a networking or DNS issue.

The fix is straightforward: run the schema updates with the right version of adprep from the installation media of the new server, not the old one. Sounds obvious, but I've seen people grab the wrong adprep from an old CD and wonder why nothing changes.

Fix: Step-by-Step

  1. Identify the current schema version. On the source DC (the one with the schema master role), open ADSI Edit, connect to the "Schema" partition, and locate CN=Schema,CN=Configuration,DC=domain,DC=com. Look at the objectVersion attribute. For Windows Server 2003 it's 30, 2008 is 44, 2008 R2 is 47, 2012 is 56. If your new server is 2008 R2 and the source has 44, that's your problem.
  2. Find the adprep folder on your new server's install media. It's in \sources\adprep on the DVD or ISO. Copy it to the schema master DC. You'll need to run it locally, not from the network share.
  3. Log on to the schema master with enterprise admin credentials. You also need to be in the Domain Admins group, and if the schema master isn't the PDC emulator (rare, but possible), make sure you have the required permissions there.
  4. Run adprep /forestprep first. Open a command prompt as administrator, navigate to the adprep folder, and run:
    adprep /forestprep
    It'll ask for confirmation, then run for a few minutes. Watch for exit code 0 and no errors.
  5. Then run adprep /domainprep. Same step, but this one updates the domain partitions. Run it on each domain that will host a DC, or at least the one you're promoting into. If you have multiple domains, do each one.
  6. For Server 2012 and later, also run adprep /rodcprep. If you're deploying read-only DCs, this is needed. If not, skip it — but it's harmless to run it anyway.
  7. Reboot the new server and try DCPROMO again. It should pass the schema check this time.

What to Check If It Still Fails

If you've run adprep and still get 0x213, here are the culprits I've seen in the field:

  • Wrong adprep version. You ran adprep from the old media, not the new one. Double-check the version in the folder name or properties. The adprep.exe version should match the OS you're installing.
  • Schema master not reachable. The new server couldn't contact the schema master during DCPROMO. Check DNS and firewall rules. Use nltest /dsgetdc:domain.com to verify discovery.
  • Replication lag. You ran adprep on the schema master, but the new DC is pulling from a different DC that hasn't replicated yet. Forcibly replicate with repadmin /replicate or repadmin /syncall from the schema master to the source DC.
  • You're trying to install a newer DC into an older forest without upgrading the forest functional level. This is less common, but if you're going from 2003 to 2012, you might need to raise the functional level to 2008 or higher first. Check your functional levels in Active Directory Domains and Trusts.
  • Schema version check bug in DCPROMO. Rare, but if everything looks correct and it still fails, run dcdiag /test:replications to ensure replication is healthy. Sometimes a stale lingering object causes DCPROMO to misread the schema version.

One more thing: if you're promoting a 2012 R2 DC into a 2008 R2 forest, the schema version should be 69 on the source after adprep. If it's not, something didn't apply. Don't just rerun adprep blindly — check the objectVersion again after each run. It should increment to the expected value.

Bottom line: this error is almost always a missed adprep step. Take the time to run it correctly, verify the schema version, and you'll be back in business. If you're still stuck after that, look at replication and functional level — those are the usual suspects.

Related Errors in Server & Cloud
0X000006E8 RPC_S_ADDRESS_ERROR (0X000006E8) - Quick Fix Guide 0X000009B1 Fix UPS error 0X000009B1 fast: NERR_UPSInvalidConfig Storage vMotion Data Transfer Interrupted – Fixes Container in VM Can't Reach Internet? Fix NAT and DNS
ERROR_DS_INSTALL_SCHEMA_MISMATCH 0x00002113 DCPROMO schema mismatch Active Directory schema version mismatch DCPROMO fails 0x213 schema upgrade Active Directory adprep /forestprep adprep /domainprep Windows Server 2008 R2 DCPROMO error 213 schema mismatch fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.