1. The model of 'the object which managed by Active Directory and the one's attributes' can be extended as necessary. The model is called Active Directory Schema. Active Directory Schema has also been updated as OS is upgraded. The list is below. Active Directory Schema Versions.
2. Normally schema update done for applications like Exchange and SCCM, schema update also done for operating systems, Active Directory to support the new operating system and same time OS with new release, Windows Server 2003 and Windows Server 2003 R2 have the different schema versions, you have to update the schema before updating the new release version of OS (Windows Server 2003 R2) in.
3. Validate schema version via PowerShell: Get-ADObject (Get-ADRootDSE).schemaNamingContext -Property objectVersion. In this screenshot, I have ObjectVersion equal to 69, denoting the schema has been extended for AD on Windows Server 2012 R2. Validate schema version via Registry Editor: Click Start and search for; regedit.
4. The Active Directory schema changes that are described in this topic might not apply to all editions of an Exchange 2019 version. To verify that Active Directory has been successfully prepared, see the Exchange Active Directory versions section in Prepare Active Directory and domains for Exchange 2019.

• 5Determine the AD Schema Version on a Windows Client or Server

The official Active Directory (AD) schema versions are:

Validate schema version via PowerShell: Get-ADObject (Get-ADRootDSE).schemaNamingContext -Property objectVersion. In this screenshot, I have ObjectVersion equal to 69, denoting the schema has been extended for AD on Windows Server 2012 R2. Validate schema version via Registry Editor: Click Start and search for; regedit. AD Schema Versions Below is a list of OS versions and related schema versions. Find out the current schema version by inspecting the objectVersion property of CN=Schema,CN=Configuration, For example, to find out the current schema version, use a tool like ADSIEDIT or dsquery, e.g.

Samba supports the following Active Directory schema versions:

* Experimental support. To report problems, click https://bugzilla.samba.org.

To upgrade the schema version on a running Samba installation to 2012_R2, use this command:

Note: This tool only works from 2008 R2. In order to upgrade from earlier versions, the ldf files must be manually sourced from the Windows adprep tool and run with the --ldf-file= option.

To determine the Active Directory (AD) schema version on a Samba domain controller (DC):

dsquery

To determine the Active Directory (AD) schema version from the Windows command line:

PowerShell

Active Directory Schema Version For Windows 7

To determine the Active Directory (AD) schema version from the Windows PowerShell:

You can query Active Directory to determine the schema version as shown below. Replace “dc=domainname” with your information:

dsquery * cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr objectVersion

The PowerShell version below does not require any customization:

Active Directory Schema Version 87

Get-ADObject (get-adrootdse).schemaNamingContext -Property objectVersion

The table below shows Active Directory schema versions.

Active Directory Schema Version Exchange 2016