Avatar of Justin Owens
Justin OwensFlag for United States of America

asked on 

Request for Advice - AD/Exchange Migration

Scenario:

CompanyA:
AD 2003 Native
Exchange 2007

CompanyB:
AD 2008 Mixed
Exchange 2003

CompanyA acquires CompanyB.

CompanyA's desire:
Single forest with two child domains (CompanyA.parentco.corp and CompanyB.parentco.corp).
Single Exchange organization to host email boxes for CompanyA and CompanyB users.  The users would need to default to their respective external domain addresses (companyA.com for CompanyA.partentco.corp and companyB.com for CompanyB.parentco.corp) but have the ability to have the other external domain addresses added as needed on a case by case basis.

AD is to be 2008 and Exchange is to be 2010.

CompanyA desires for CompanyA.parentco.corp to host its users and computers and CompanyB.parentco.corp to host its users and computer.

Questions:
What is the easiest way to make this happen?  What is the safest way to make this happen?  New hardware is a given and will be purchased, but not until a plan is in place and approved.

Much obliged.

DrUltima
Active DirectoryExchangeIT Administration

Avatar of undefined
Last Comment
Leon Fester
Avatar of setasoujiro
setasoujiro
Flag of Belgium image

the easiest , best way would be to upgrade both of the domains to 2008 seperately, then when all is well, create a trust between the domains
Avatar of Justin Owens
Justin Owens
Flag of United States of America image

ASKER

Not an option.  CompanyA wants a single forest with child domains, not two forests in a Trust.

DrUltima
Avatar of setasoujiro
setasoujiro
Flag of Belgium image

then it will make things a lot harder.
i think you're best of setting up a new domain for comp B after A is upgraded and ready to accept cchils
Avatar of Justin Owens
Justin Owens
Flag of United States of America image

ASKER

You misunderstand... I may not be clear in my requirements.  I am sorry.

Root of forest is not to contain any users other than builtin and service accounts.  All user accounts must remain in the child domain.  The way I see it is three new domains (root of forest and two children), importing users into their respective child domains.  What I am unclear about is the best placement for Exchange.  Will it work on the root to service both child domains, or must there be two Exchange instances in each of the child domains (and if so, how to mitigate having both public domains available to both child ad domains)?

DrUltima
Avatar of Justin Owens
Justin Owens
Flag of United States of America image

ASKER

This is where I really wish could can just tell AD "Make yourself a child of this parent".
Avatar of setasoujiro
setasoujiro
Flag of Belgium image

no it will work in the root domain.
and also in one of the childs if trusts are all in order
SOLUTION
Avatar of Leon Fester
Leon Fester
Flag of South Africa image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
SOLUTION
Avatar of Leon Fester
Leon Fester
Flag of South Africa image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of Justin Owens
Justin Owens
Flag of United States of America image

ASKER

I am already familiar with ADMT, thanks.  Also, the third link is not applicable, as it is for Exchange 2003, not 2010.

DrUltima
Avatar of Leon Fester
Leon Fester
Flag of South Africa image

CompanyB is still using Exchange 2K3, hence the recommendation of that page.
If it's not needed then don't refer to it.

Was just trying to be helpful.
Avatar of Justin Owens
Justin Owens
Flag of United States of America image

ASKER

And I appreciate that.  The current plan is to retire both current Exchange organizations (2003 and 2007) and install a new one.  One possible path is this:

http://technet.microsoft.com/en-us/library/aa998031.aspx

Although, it would be multiple forests.  Still in planning stages, so the requirement to all be in one forest may be able to be mitigated.  One thought I have is this, though.  If you can have your Exchange 2010 Organization in a different forest, why can you not have it in the same forest but a different domain.  Anyone have experience with that scenario?

DrUltima
ASKER CERTIFIED SOLUTION
Avatar of Justin Owens
Justin Owens
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
Avatar of Leon Fester
Leon Fester
Flag of South Africa image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Exchange
Exchange

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo