• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2594
  • Last Modified:

Exchange 2010 SP3 install error

I am receiving an error when upgrading to SP3. Seems its not able to contact the Schema Master since the Exchange server is on the Child Domain and the Schema Master account is on Root Domain and stating to run setup with the /prepareAD parameter which i have never done.

Here's the error:
Setup needs to contact the Active Directory schema master but this computer is not in the same Active Directory site as the schema master.

Setup needs to contact the Active Directory schema master but this computer is not in the same Active Directory domain as the schema master.

Setup encountered a problem while validating the stat of Active Directory Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain and site, and wait for replication to complete.
0
CiscoAzn
Asked:
CiscoAzn
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
You either need to move the schema master or run the prep from the command line on the schema master itself.

http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx

Once you have run prep on the schema master, wait for replication, then try again.

Simon.
0
 
CiscoAznAuthor Commented:
I need to know what is the ramification of moving the Schema Master from the Root Domain to the Child Domain?
0
 
Simon Butler (Sembee)ConsultantCommented:
Personally I would run prep on the schema master where it is now, rather than moving it.

Simon.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now