Solved

Exchange 2003 migration for 2 AD Domains

Posted on 2004-03-24
5
666 Views
Last Modified: 2012-05-04
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
0
Comment
Question by:chrisherbert
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 24

Expert Comment

by:David Wilhoit
ID: 10673926
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
 

Author Comment

by:chrisherbert
ID: 10676991
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
 
LVL 24

Accepted Solution

by:
David Wilhoit earned 500 total points
ID: 10677213
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
 

Author Comment

by:chrisherbert
ID: 10677238
Thanks alot!!
0
 
LVL 24

Expert Comment

by:David Wilhoit
ID: 10677262
You're welcome

:)
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This video discusses moving either the default database or any database to a new volume.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question