How to Verify Active Directory Schema Version for Exchange Server SE, 2019 & 2016 (PowerShell & Reference Matrix)

Before deploying or upgrading Microsoft Exchange Server—whether applying a new Cumulative Update (CU) or upgrading to Exchange Server Subscription Edition (SE) or Exchange Server 2019—the first and most critical prerequisite is preparing Active Directory.

Running Setup.exe /PrepareSchema, Setup.exe /PrepareAD, and Setup.exe /PrepareAllDomains modifies directory classes, attributes, and security containers. If setup fails halfway through, or if domain controllers have not finished replicating schema changes across sites, running subsequent Exchange setup wizards will fail with blocking error messages.

In this updated enterprise reference, we provide the complete Active Directory Schema Version Matrix spanning Exchange Server SE, 2019, 2016, and legacy releases, explain how to inspect the three critical Active Directory naming contexts, and share an automated PowerShell script to validate schema readiness in seconds.


The Three Active Directory Schema Verification Points

To confirm that Active Directory has been completely and successfully prepared for an Exchange update, administrators must verify three distinct attributes across three Active Directory naming contexts:

  1. Schema Container (rangeUpper): Located in the Schema naming context on CN=ms-Exch-Schema-Version-Pt. This value updates during Setup.exe /PrepareSchema.
  2. Exchange Organization Container (objectVersion): Located in the Configuration naming context under CN=<OrganizationName>,CN=Microsoft Exchange,CN=Services. This value updates during Setup.exe /PrepareAD.
  3. Microsoft Exchange System Objects (MESO) Container (objectVersion): Located in each domain naming context under CN=Microsoft Exchange System Objects,DC=<Domain>. This value updates during Setup.exe /PrepareDomain or /PrepareAllDomains.
Active Directory Preparation & Schema Verification Flow 1. Schema Preparation Setup.exe /PrepareSchema • Executed on Schema Master DC • Requires: Schema Admins group Attribute to Inspect: rangeUpper CN=ms-Exch-Schema-Version-Pt SE / 2019: 15337 / 17000+ 2. Organization Prep Setup.exe /PrepareAD • Requires: Enterprise Admins group • Creates Microsoft Exchange container Attribute to Inspect: objectVersion (Configuration) CN=<Org>,CN=Microsoft Exchange SE / 2019 CU14: 16223 / 16230+ 3. Domain Prep Setup /PrepareAllDomains • Configures MESO container • Grants permissions across domains Attribute to Inspect: objectVersion (Domain) CN=Microsoft Exchange System Objects SE / 2019: 13236 / 13238 Replication Latency Rule: 1. Always wait for Active Directory replication to converge across all domain controllers before running server setup. 2. Use repadmin /syncall /AdeP on the Schema Master to force immediate forest-wide schema synchronization.

Active Directory Schema Version Reference Matrix

The following reference table maps each version of Microsoft Exchange Server to its corresponding rangeUpper, Forest objectVersion, and Domain objectVersion:

Exchange Server VersionSchema (rangeUpper)Forest (objectVersion)Domain (objectVersion)
Exchange Server SE RTM / CU117000 / 1700116230+13238
Exchange Server 2019 CU14 (2024 H1)153371622313236
Exchange Server 2019 CU13153371622313236
Exchange Server 2019 CU12153371622313236
Exchange Server 2019 CU11153351622313236
Exchange Server 2019 CU10153351622213236
Exchange Server 2019 CU9153351622113236
Exchange Server 2019 CU8153351622013236
Exchange Server 2019 RTM153321621313236
Exchange Server 2016 CU23153371622313236
Exchange Server 2016 CU22153351622313236
Exchange Server 2016 CU1153321613413236
Exchange Server 2016 RTM153171613413236
Exchange Server 2013 CU23153121544913236
Exchange Server 2010 SP3147341432213040
Exchange Server 2007 SP3146251122211221
Exchange Server 2003 SP2687069036936

Automated PowerShell Script: Verifying Schema Across AD Naming Contexts

Instead of manually navigating through adsiedit.msc, run this PowerShell script from any domain-joined workstation or server with the ActiveDirectory module:

POWERSHELL
# Script: Get-ExchangeSchemaVersion.ps1
# Description: Queries the 3 Active Directory naming contexts and outputs Exchange schema readiness

Import-Module ActiveDirectory -ErrorAction Stop

# 1. Query RootDSE for Forest & Domain Naming Contexts
$RootDSE = Get-ADRootDSE
$SchemaNC = $RootDSE.schemaNamingContext
$ConfigNC = $RootDSE.configurationNamingContext
$DomainNC = $RootDSE.defaultNamingContext

Write-Host "`n=== ACTIVE DIRECTORY EXCHANGE SCHEMA AUDIT ===" -ForegroundColor Cyan
Write-Host "Domain Controller Contacted: $($RootDSE.dnsHostName)" -ForegroundColor Gray

# 2. Query Schema Container (rangeUpper)
$SchemaObj = Get-ADObject -Identity "CN=ms-Exch-Schema-Version-Pt,$SchemaNC" -Properties rangeUpper
$RangeUpper = $SchemaObj.rangeUpper

# 3. Query Exchange Organization Container in Configuration NC
$OrgContainer = Get-ADObject -Filter 'objectClass -eq "msExchOrganizationContainer"' -SearchBase "CN=Microsoft Exchange,CN=Services,$ConfigNC" -Properties objectVersion
$ForestObjectVersion = $OrgContainer.objectVersion
$OrgName = $OrgContainer.Name

# 4. Query Microsoft Exchange System Objects (MESO) Container in Domain NC
$MesoObj = Get-ADObject -Identity "CN=Microsoft Exchange System Objects,$DomainNC" -Properties objectVersion
$DomainObjectVersion = $MesoObj.objectVersion

# Output Formatted Report
$Report = [PSCustomObject]@{
    "Exchange Organization"   = $OrgName
    "Schema (rangeUpper)"     = $RangeUpper
    "Forest (objectVersion)"  = $ForestObjectVersion
    "Domain (objectVersion)"  = $DomainObjectVersion
}

$Report | Format-List

# Interpret the results
$Status = switch ($RangeUpper) {
    {$_ -ge 17000} { "Exchange Server Subscription Edition (SE) Ready" }
    {$_ -ge 15337} { "Exchange Server 2019 / 2016 Latest CU Ready (CU12-CU14 / CU23)" }
    {$_ -ge 15332} { "Exchange Server 2019 / 2016 Early CU (RTM-CU2)" }
    {$_ -ge 15312} { "Exchange Server 2013 CU23" }
    {$_ -ge 14734} { "Exchange Server 2010 SP3" }
    Default        { "Legacy or Incomplete Schema Preparation" }
}

Write-Host "Detected Level: $Status" -ForegroundColor Green

Verifying Replication Across All Domain Controllers

After running /PrepareSchema, ensure that the new rangeUpper value has fully replicated to all domain controllers in all Active Directory sites before proceeding with /PrepareAD or installing Exchange servers:

POWERSHELL
# Script: Check-SchemaReplicationAllDCs.ps1
# Description: Verifies rangeUpper consistency across all DCs in the forest

$DCs = Get-ADDomainController -Filter *

$ReplicationAudit = foreach ($dc in $DCs) {
    try {
        $val = (Get-ADObject -Server $dc.HostName -Identity "CN=ms-Exch-Schema-Version-Pt,$SchemaNC" -Properties rangeUpper).rangeUpper
        [PSCustomObject]@{
            DomainController = $dc.HostName
            Site             = $dc.Site
            RangeUpper       = $val
            ReplicationState = ($val -ge 15337 ? "Synchronized" : "Pending Replication")
        }
    } catch {
        [PSCustomObject]@{
            DomainController = $dc.HostName
            Site             = $dc.Site
            RangeUpper       = "Unreachable"
            ReplicationState = "Failed"
        }
    }
}

$ReplicationAudit | Format-Table -AutoSize

Summary Checklist for Exchange Administrators

  1. Schema Master Placement: Always execute Setup.exe /PrepareSchema on a member server in the same Active Directory site as the Schema Master FSMO role holder.
  2. Replication Convergence: Verify that rangeUpper matches across all domain controllers before proceeding to /PrepareAD.
  3. Domain Preparation: Confirm that the Microsoft Exchange System Objects container (MESO) exists in all domains hosting Exchange recipients, not just the root domain.
  4. Stale Objects: If preparing for an in-place upgrade to Exchange Server SE, audit and clean up stale legacy Exchange objects using our Exchange SE Active Directory Pre-Upgrade Runbook.