Tag Archives: adsiedit.msc

Find Domain Schema Version

Posted on by

Find Domain Schema Version KB ID 0000025 

Problem

You want to upgrade or find out your current Schema version, or check that an” adprep / forestprep” command has worked correctly.

Solution

Find Domain Schema Version: PowerShell

Use the following sytax
[box]

Get-ADObject (Get-ADRootDSE).schemaNamingContext -Property objectversion

[/box]

Post Server 2016 Find Domain Schema Version

The value is populated with Server 2016 again.

If you check the value above on a domain that has Windows 2012 domain controllers, you will see the value is ‘not set’.

If the entry is blank;

Instead navigate to this registry key;

[box][HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters[/box]

Locate the ‘Schema Version’ Note: the figure in brackets is the decimal value!

Find Domain Scheman Version For Windows Servers Before 2012 RTM

1. For Windows Server 2003 you will need to Install the Support Tools on your server. (2008, 2008 R2, and 2012 have the tools built in).

2. Press (Windows Key+R) > adsiedit.msc > {enter}

3. Right Click > CN=Schema,CN=Configuration,DC=domain,DC=com > Properties

<pNote: If you cannot see this you need to select “Connect To” then pick “Schema”.

4. On the Attribute Editor tab > Locate objectVersion.

 

What Are The Windows Server Schema Versions?

20: Windows 2000

30: Windows 2003 RTM, Windows 2003 SP1, and Windows 2003 SP2

31: Windows 2003 R2

44: Windows Server 2008 RTM

47: Windows Server 2008 R2 (and SBS 2011)

56: Windows Server 2012 RTM

69: Windows Server 2012 R2

87: Windows Server 2016 RTM

88: Windows Server 2019 RTM

88: Windows Server 2022

91: Windows Server 2025

Related Articles, References, Credits, or External Links

NA

Exchange Error during/post upgrade from Exchange 2003 ‘ Mailbox manager settings cannot be managed by the current version of Exchange Management Console’

Posted on by

KB ID 0000547 

Problem

I’ve already covered migration from 2003 here, I got an email today {Thanks Ashley :)} to say that when they tried to migrate the address policies from 2003 to 2010 using this command:

[box]Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} | Set-EmailAddressPolicy –IncludedRecipients AllRecipients[/box]

They got the following error;

Error on Exchange 2010

Set-EmailAddressPolicy : The recipient policy “Default Policy” with mailbox manager settings cannot be managed by the current version of Exchange Management Console. Please use a management console with the same version as the object.

Error on Exchange 2007

The recipient policy “Default Policy” with mailbox manager settings cannot be managed by the current version of Exchange Management Console. Please use a management console with the same version as the object.

Solution

This happens because In your Exchange 2003 environment, there is a Mailbox Manager Policy that’s been tied to the recipient update policy.

Option 1 (If you have access to the 2003 Exchange Management Console)

1. On your Exchange 2003 Server Launch the Exchange Management Console > Recipients > Recipients Polices > You may have more than one if so repeat this process with each one > right click > Change Property Pages > Make sure “Mailbox Manager Settings” is NOT TICKED. (If it is, Untick it and re-run the command above).

Option 2 (If you DO NOT have access to the 2003 Exchange Management Console)

1. From within ADSIEdit (Install the support tools if you can’t find it) > Configuration > CN=Configuration… > CN=Services… > CN=Microsoft Exchange… > CN={Your Exchange Org} > CN=Recipient Policies > Right click CN=Default Policy > Properties.

2. Locate the msExchPolicyOptionList attribute > Edit > Remove the entry that’s called ” 0xec 0x13 0x68 0x3b 0x89 0xce 0xba 0x42 0x94… (Mailbox Manager Settings)” > OK > Apply > OK.

Related Articles, References, Credits, or External Links

Special thanks to Ashley for the information. Exchange 2003 to 2010 Transition “Swing Migration”