Home » Exchange Server 2016 (Page 2)

Category Archives: Exchange Server 2016


PrepareSchema Failed while upgrading Exchange Servers

/PrepareSchema Failed while upgrading Exchange Server 2013

Error : Setup needs to contact the Active Directory schema master, but this computer isn’t in the same Active Directory site as the schema master (Admin) exchange server 2013



Checked the Number of Domain Controllers



Checked the FSMO Roles pointed to Domain Controller



WorkAround :

1: Either this can be done adding the Registry “String Value” as DefaultSite” Or

2: Moving the FSMO roles to the Domain Controller Exchange server is pointed to


Here we will execute on 2nd work around


Moving the Schema Role to the Domain Controller Exchange Server is Connected to…

For checking you can either try from command or go to Network control panel (ncpa.cpl)

From Command prompt


Query for Domain in the environment

Command : netdom query dc (you will see list of Domain controllers)



Now do nslookup for the Domain Controller Exchange server is connected to



Post confirmation try pinging the server IP with switch -a

Switch -a while pinging will give the name and the ping status

Ping -a “Ipaddress”



Now Moving the FSMO Role (Schema ) to the Domain Controller Exchange Server is connected to…

For that you need to run the command



Ntdsutil.exe is a command-line tool that provides management facilities for Active Directory Domain Services (AD DS) and Active Directory Lightweight Directory Services (AD LDS). You can use the ntdsutil commands to perform database maintenance of AD DS, manage and control single master operations, and remove metadata left behind by domain controllers that were removed from the network without being properly uninstalled.


Note: This tool is intended for use by experienced administrators…..


Steps to move Schema Role from One Domain to another Domain

Open Command Prompt as “RunasAdministrator

Type ntdsutil

Mention Role as shown below




FSMO Maintenance : Connections




Now mention the Domain Controller to want to Move



This will Bind the Domain Controller to are trying to connect

This will connect with local user account, then you need to come out of the Connections

Quit -> Enter

Now Type the Role you are trying to move

This will prompt “Are you sure you want the role of Schema Master transferred to the server – Server Name”


Click YES



After moving you need to Quit from FSMO Maintenance
And Quit ntdsutil as shown below:



For Confirming either you can check querying list of fsmo using the command “netdom query fsmo”



Proceed Installing Exchange Server.

Post completion move the Role, back to Domain Controller which it is earlier pointed to…


Roll Back FSMO Role….



Below is the process for verifying in the adsiedit to check if the exchange server installed properly

Connect to ADSIEDIT

Right click and click connect to Schema under



Click Connect and “Select a well known Naming Context” -> dropdown select -> Schema Partition as shown below:



Now you will see the Schema with Domain Name -> Expand

Now go to the Attribute “CN=ms-Exch-Schema-Version-Pt” on the right side of the page

Right Click -> Properties



Under Attribute Editor -> Under Attribute Editor select range upper

Note: If you are getting Null Value then select Filter and click “Show only Attributes that have values” so that you can see the values with attributes.



Under the Attribute Editor select “Range Upper” the value for Exchange 2013 should show the value – 15312 as shown below:




Praveen Kumar

MCP, MCSA, MCTS, MCITP | Windows Server & Exchange Server

Publisher @ Techrid.com