Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1114
  • Last Modified:

Problems with Exchange 2007 SP1 installation in a child domain of a forest

We are in the middle of trying to install the Exchange 2007 SP1 in our organization.  Our topology is:

Parent.com  -- Nothing really sits here other than 2 DCs.
ChildDom.Parent.Com -- All of our users, computers, and existing exchange organization sits here.

I've run the following on DC1.parent.com:
 setup /prepareschema
 setup /prepareAD

When I now attempt to run the setup /prepareAD from my ChildDom.Parent.Com I get a messaage saying:

Setup needs to contact the Active Directory schema master but this computer is not in the same Active Directory domain as the schema master (DC=Parent,DC=com).
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.3&id=2376fec1-b9ce-44db-beb6-cb9ac4788988

I am sure I am missing something here -- What do I need to do in order to get my ChildDom.Parent.Com domain ready for the installation of SP1?
0
qsnow
Asked:
qsnow
  • 8
  • 3
  • 3
  • +1
1 Solution
 
mass2612Commented:
Hi,

What happens if you try to run setup /PrepareAllDomains from the parent domain? If that suceeds just try running the Exchange setup in the child domain.
0
 
qsnowAuthor Commented:
Just tried that and then forced a replication... Same error:

Setup needs to contact the Active Directory schema master but this computer is not in the same active directory domain as the schema master (DC=parent,Dc=com)
0
 
mass2612Commented:
Can you verify that the schema is updated using ADSI Edit > Schema of DC in Root domain > CN=ms-Exch-Schema-Version-Pt > RangeUpper =10637?

0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
qsnowAuthor Commented:
On my parent/root..  I do have a RangeUpper = 10637
0
 
qsnowAuthor Commented:
Checking that value on my Child - it is at 4197
0
 
qsnowAuthor Commented:
Opps, sorry. I was looking at the wrong RangeUpper on the Child... Looking at ADSI schema pointing to a child controller - it also shows 10637.
0
 
mass2612Commented:
Sorry this one's got me stumped. Anyone have any more ideas. I've not tried SP1 yet.
0
 
SembeeCommented:
There are schema changes in SP1, so you will have to run the prep.
Have you verified that the schema master is available? Install the Windows Support Tools and then run

netdom query fsmo

That will show you which servers hold the roles. Verify that they are all available.

Simon.
0
 
qsnowAuthor Commented:
V:\>netdom query fsmo
Schema owner                Holt-RDC1.HoltCompanies.com

Domain role owner           South-RDC1.Primary.com

PDC role                           North-dc2.ChildDom.Primary.com

RID pool manager            South-dc1.ChildDom.Primary.com

Infrastructure owner        South-dc2.ChildDom.Primary.com

The command completed successfully.

FYI:  North DCs are in a North site in AD, South DCs are in a South site in AD.  I'm running all the exchange installations for SP1 in the South site.
0
 
SembeeCommented:
Can you access this machine:

Holt-RDC1.HoltCompanies.com

The other machines are not really a concern.

Simon.
0
 
qsnowAuthor Commented:
yes.  I have no connectivity issues.  I can ping the machine, RDP into the machine, replicate to/from the machine.
0
 
SembeeCommented:
Can you not run prep from that machine instead?

Simon.
0
 
qsnowAuthor Commented:
From RDC1?  Over the course of my trials and tribulations here, I've done the following things on RDC/root (All said completed):

setup /PrepareSchema
setup /PrepareAD

setup /PrepareAllDomains

setup /prepareDomain:ChildDom
0
 
qsnowAuthor Commented:
Okay, looks like a stupid issue on my part.  What threw me off from finding it was the frist response on the RangeUpper verification.  10637 is the RTM version.  When you do the AD Schema extension for SP1, that rangeUpper should be 11116.  I was thinking that my schema got modified correctly since I saw the 10637 as proposed.

End result, it looks like the setup.exe for exchange that was being run was being pathed from the RTM extraction that I had on the server(s).
0
 
Vee_ModCommented:
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 8
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now