Solved

Exchange 2003 migration for 2 AD Domains

Posted on 2004-03-24
5
623 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
  • 3
  • 2
5 Comments
 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
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
Comment Utility
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
Comment Utility
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
Comment Utility
Thanks alot!!
0
 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
You're welcome

:)
0

Featured Post

Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users do...so should you!

Join & Write a Comment

Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
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.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…

762 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

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now