# Read objectVersion and rangeUpper before mapping AD and Exchange schema levels > Use Find the Current Active Directory Schema Version to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/read-objectversion-rangeupper-map-ad-exchange-schema-levels/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:15:04+00:00 - Modified: 2026-08-27T12:56:25+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: IT, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Find the Current Active Directory Schema Version to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Find the Current Active Directory Schema Version ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Read objectVersion and rangeUpper before mapping AD and Exchange schema levels. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Find the Current Active Directory Schema Version](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/find-active-directory-schema) from Microsoft supports the following bounded statements: - The Active Directory schema level is the objectVersion value on CN=Schema,CN=Configuration in the forest, which Microsoft maps to Windows Server versions in its objectVersion table. The research record locates this support at Finding the schema version; Mapping the objectVersion attribute. - The Exchange schema level is the rangeUpper value on CN=ms-Exch-Schema-Version-Pt, which Microsoft directs readers to map with the Exchange 2016 or Exchange 2019 version tables. The research record locates this support at Find the current Exchange Schema version; Mapping the rangeUpper attribute. Only the traced statements above are asserted as source facts. Apply the review to forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles after confirming that the source and deployed context match. ## What the source does not establish These lookups discover and map current values; they do not authorize, execute, or validate a schema extension or an Exchange upgrade. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision. ## Applicability questions - For source statement 1 at Finding the schema version; Mapping the objectVersion attribute, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Find the current Exchange Schema version; Mapping the rangeUpper attribute, which observable configuration, record, or test can confirm applicability here? - What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope? - Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy? - What result would disprove the working assumption and return the issue to the owner? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation. An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before and after the test, and store only sanitized operational evidence. ## Verification and evidence Keep the source locations Finding the schema version; Mapping the objectVersion attribute; Find the current Exchange Schema version; Mapping the rangeUpper attribute adjacent to the sanitized artifacts used for comparison. Prefer directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, with enough identity and timing data for an independent recheck. Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed. ## Official references - [Find the Current Active Directory Schema Version](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/find-active-directory-schema) — Microsoft ## Primary reference - Name: Find the Current Active Directory Schema Version - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/find-active-directory-schema - Source publication date: 2025-07-08 ## Citation and use Preferred citation: “Read objectVersion and rangeUpper before mapping AD and Exchange schema levels,” DSE Security, https://update.dsesecurity.com/updates/read-objectversion-rangeupper-map-ad-exchange-schema-levels/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.