Exchange 2003 migration for 2 AD Domains

We have an AD domain set up with an empty root and two child domains - London and New York. Each child domain has its own site in our Exchange 5.5 org. We are planning to migrate to Exchange 2003 and consolidate both sites into one. The user accounts will stay in their respective AD domains, but the Exch2003 Server will serve them all from the New York domain.
I am not sure how the single Exchange 2003 server is going to handle managing two seperate AD domains in one Exchange site, or if this is even possible. Has anyone been through this particular scenario, and is there anything special I need to do during the migration?
Thanks
chrisherbertAsked:
Who is Participating?
 
David WilhoitConnect With a Mentor Senior Consultant, ExchangeCommented:
you can put the EXchange server in any of the domains, but of course, putting it in the root no longer makes it "empty" :)

the root domain must have the enterprise level RUS. there will also be a domain level RUS for that root, so don't remove it, both will be created when you do your forestprep and domainprep. In London, you'll need to run domainprep to create the RUS, or you can create it manually, whichever suits you./

D
0
 
David WilhoitSenior Consultant, ExchangeCommented:
yea, it will work. The child domains have a default 2-way transitive trust, if I'm not mistaken. to do the migration,each 5.5 site will have an ADC, with a PFCA and a User CA. Each domain, including the root, will need a Recipient Update Service (RUS), so that the users can be mail-enabled. OWA will work fine, if you set the default domain to "\" in IIS. Use an enterprise account with Schema admin rights to do your forestprep, domainprep and first E2K3 server install. That's about it, as long as you haven't monkied with the perms in AD, everything should go well. Is AD in native mode now, at least 2000 native mode?

D
0
 
chrisherbertAuthor Commented:
Thanks for the response. We will be fully AD (Win2003) by the time I do the migration - London is a little behind at the moment but that is being dealt with now.
Why does the root domain need the Recipient Update Service? There are no accounts in that domain - it is strictly an empty root. Are you saying that I should put the Exchange Server in that domain? I was planning to have it in the New York domain...
0
 
chrisherbertAuthor Commented:
Thanks alot!!
0
 
David WilhoitSenior Consultant, ExchangeCommented:
You're welcome

:)
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.

All Courses

From novice to tech pro — start learning today.