Exchange Server Active Directory Versions

Microsoft Exchange Server There are important preparations that need to be made before starting the installation. These preparations include: Active Directory expansion and preparation of the schema. After these processes are completed, it is important to verify what has been done.

Find Exchange Server Schema Version with PowerShell

Exchange Server Before performing the version upgrade for Scheduling We need to control our versions, this is important for our environment to work healthily.

Bu islemi ADSI as we can do via PowerShell We can also do it practically by running the script below.

###############################################################################
# Get Exchange AD Schema Version
###############################################################################
#Needs ActiveDirectory PowerShell Module

# Exchange Schema Version
$sc = (Get-ADRootDSE).SchemaNamingContext
$ob = "CN=ms-Exch-Schema-Version-Pt," + $sc
Write-Output "RangeUpper: $((Get-ADObject $ob -pr rangeUpper).rangeUpper)"

# Exchange Object Version (domain)
$dc = (Get-ADRootDSE).DefaultNamingContext
$ob = "CN=Microsoft Exchange System Objects," + $dc
Write-Output "ObjectVersion (Default): $((Get-ADObject $ob -pr objectVersion).objectVersion)"

# Exchange Object Version (forest)
$cc = (Get-ADRootDSE).ConfigurationNamingContext
$fl = "(objectClass=msExchOrganizationContainer)"
Write-Output "ObjectVersion (Configuration): $((Get-ADObject -LDAPFilter $fl -SearchBase $cc -pr objectVersion).objectVersion)"

When you run the script I shared RangeUpper, ObjectVersion (Default) and ObjectVersion (Configuration) You can see the versions.

This image has an empty Alt attribute. File name: image-10-1024x488.png
  • rangeUpper, In the context of schema naming ms-Exch-Schema-Version-Pt is found in the properties of the container.
  • objectVersion (Default)The objectVersion property is located in the properties of the Microsoft Exchange System Objects container in the default naming context.
  • objectVersion (Configuration), In the configuration naming context, under Services > Microsoft Exchange in the properties of the container objectVersion is a feature.

Finding Exchange Server Schema Versions Using ADSI

Above rangeUpper, objectVersion(Default) and objectVersion(Configuration) We have given information about where the objects are located, based on this information ADSI We can provide the necessary controls via.

ADSI Edit Windows Server on you Active Directory is a tool used to manage structures and Lightweight Directory Access Protocol (LDAP) directly via Active Directory provides access to objects.
  1. Open ADSI Edit:
    • From the start menu Run Open the (Run) dialog.
    • adsiedit.msc type and Enter by pressing ADSI EditStart .
  2. Creating Links:
    • In the ADSI Edit window, right-click Connect to Select the option.
    • Select a well known Naming Context in option Schema Select the context and OK Click the button.
  3. Schema Object Access and RangeUpper Control
    • Go to the Schema directory you linked to.
    • In the schema directory, CN=Schema,CN=Configuration,DC=yourdomain,DC=com by following a path like Schema reach the object.
    • You can check the rangeUpper section in the Properties section of the “CN=ms-Exch-Schema-Version-Pt” object in the Schema object.
  • Checking ObjectVersion(default) Values
    • In the ADSI Edit window, right-click Connect to Select the option.
    • Default Naming Context We connect with the option
    • Microsoft Exchange System Object We come to the object and open the Properties section
    • We can view the objectVersion(Default) value.
  • Finding ObjectVersion(Configuration)
    • In the ADSI Edit window, right-click Connect to Select the option.
    • Configuration We connect with the option
    • In the Services – Microsoft Exchange – OrganizationName step, we come to the Properties section.
    • We can view the version of objectVersion(Configuration).

Exchange Server 2019 Schema Versions

Exchange 2019 versionrangeUpperobjectVersion
(Default)
objectVersion
(Configuration)
Exchange 2019 CU14170031324316762
Exchange 2019 CU13170031324316761
Exchange 2019 CU12170031324316760
Exchange 2019 CU11 with KB5014260170031324316759
Exchange 2019 CU11170031324216759
Exchange 2019 CU10170031324116758
Exchange 2019 CU9170021324016757
Exchange 2019 CU8170021323916756
Exchange 2019 CU7170011323816755
Exchange 2019 CU6170011323716754
Exchange 2019 CU5170011323716754
Exchange 2019 CU4170011323716754
Exchange 2019 CU3170011323716754
Exchange 2019 CU2170011323716754
Exchange 2019 CU1170001323616752
Exchange 2019 RTM170001323616751
Exchange 2019 Preview153321323616213

Exchange Server 2016 Schema Versions

Exchange 2016 versionrangeUpperobjectVersion
(Default)
objectVersion
(Configuration)
Exchange 2016 CU23153341324316223
Exchange 2016 CU22 with KB5014260153341324316222
Exchange 2016 CU22153341324216222
Exchange 2016 CU21153341324116221
Exchange 2016 CU20153331324016220
Exchange 2016 CU19153331323916219
Exchange 2016 CU18153321323816218
Exchange 2016 CU17153321323716217
Exchange 2016 CU16153321323716217
Exchange 2016 CU15153321323716217
Exchange 2016 CU14153321323716217
Exchange 2016 CU13153321323716217
Exchange 2016 CU12153321323616215
Exchange 2016 CU11153321323616214
Exchange 2016 CU10153321323616213
Exchange 2016 CU9153321323616213
Exchange 2016 CU8153321323616213
Exchange 2016 CU7153321323616213
Exchange 2016 CU6153301323616213
Exchange 2016 CU5153261323616213
Exchange 2016 CU4153261323616213
Exchange 2016 CU3153261323616212
Exchange 2016 CU2153251323616212
Exchange 2016 CU1153231323616211
Exchange 2016 RTM153171323616210
Exchange 2016 Preview153171323616041

Comment