Exchange 2010 Upgrade on new 08 Child Domain?

My company is preparing to upgrade to Exchange 2010. Recently we have been meeting with consultants to prepare and think of the best plan for deployment and the smoothest upgrade.

Existing Environment:
Exchange 2003 (1 front-end and 1 back-end server) at one location
Active Directory 2003 - Multisite
Root Domain: company.net
Domain: corp.company.net
All Servers/Computers/Users (EVERYTHING) is currently on corp.company.net
When users logon to their computer or anything it is always the CORP domain.

Future Environment:
MIigrate everything to Exchange 2010 - 2mailbox servers 2Hub/CAS server in primary location (1mailbox/1HUB/CAS with DAG in DR site)

Our domain was previously migrated from an existing Novell domain.

The consultant recommended that we create a new child domain of company.net called "EXCH" or something similar that would be domain 2008.  He recommended that we install our Exchange 2010 configuration on the new EXCH.company.net domain and create a trust relationship between the two domains.  Another reason for creating a new domain would be that it is cleaner and does not currently have Exchange 2003 or old potential Novell corruption.

I was initilaly weary of creating a new child domain for Exchange as i am not sure what other repurcussions there would be? The Plan would be to eventually upgrade corp.company.net to 08 and upgrade our root domain to 08 as well.

I'd prefer to keep it all on the same corp.company.net domain for simplicity of management and administration. But - i wouldn't mind if it was installed on a cleaner new AD environment if it will not cause any more complexion or confusion. How would the relationship work between the two domains?

Is this a recommended Best Practice to do? What do you Experts think about this plan and what else could we do?


Thank you, Experts.
RavenIndAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

brotaCommented:
There is not need for another child domain.
IF you domain controllers meet the requirements for 2010. Then put it in the domain that the 2003 is. This will be your easisest migration.
If you make another child domain that is another pair of domain controllers you will need to manage.

I would run the Exchange Pre-Deployment Analyzer
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=88B304E7-9912-4CB0-8EAD-7479DAB1ABF2
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MidnightOneCommented:
Your consultant is an idiot; if he creates a new child domain EXCH.company.net, a transitive trust is automatically created. If they can't get that basic detail right - and anyone who's done a single Microsoft server exam should know it - I'd be wary of anything else he has to say.

When transitioning from Exchange 2003 -> 2010, the big things to look for from my experience is this:
You won't be able to add an Exchange 2007 system once 2010 is installed
There are some application compatibility issues with Exchange 2010 (e.g., Blackberry Enterprise server 4.x won't work

I used the Exchange 2010 deployment wizard and had few issues.
0
RavenIndAuthor Commented:
I believe his skills are sharp and he has a lot of experience with various Exchange 2010 deployments. His main concern was the 03 issues we might have to uncover when upgrading to Exchange 2010. He was thinking that there would be a lot to cleanup from the Novell configuration.

Would you recommend upgrading to 08 domain prior to Exchagne 2010? Or just doing it on our current AD 2003 environment?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

brotaCommented:
you only need 2003 sp2 for the domain controllers
I would run the Exchange BPA on your current enviorment to see if there are any issues before you start.
0
Neil RussellTechnical Development LeadCommented:
Sack your consultant! His plan is a waste of time, money and effort and as brota said, he is stating inacurate facts with regard to trusts.

Unless you STILL have novell running and are still using novell connectors for exchange in 2003 then there are no issues regarding Novell. If you migrated FROM Novell into Exchange and it runs now, why would he think it wont run in 2010?

There is a Phrase for this type of consultant...

Money Grabbing Idiot!
0
Neil RussellTechnical Development LeadCommented:
Sorry i only just reread that question...

How does creating a new child domain help? The exchange org belongs to the Forest right? Your exchange 2010 would still be a direct part of the exchange 2003 setup.

ONE Forest ONE Exchange Organization.
0
RavenIndAuthor Commented:
I thought it was an interesting idea indeed. I have read about some organizations that create domains like APPS.company.net to install Exchange and SharePoint but I could not find any MS documentation to back it up, or anything on line that said why. Is there any benefits to having your larger more complex apps on a different child domain than your users?
0
RavenIndAuthor Commented:
The consultant also said that it would take more hours to install Exchange in our current corp.company.net domain that by creating a separate 08 child domain. He said there would be some hours spent in Adsiedit cleaning some things. It would be quicker, in his opinion, to create a new fresh domain with 08 and have a clean environment.
0
MidnightOneCommented:
Ask him what, specifically, in AD needs cleaning up. If there's issues with the domain and ADSIedit is needed, those problems will still be there after adding a new domain, too.

Really, it sounds to me like he's ill-equipped to deal with the domain you have and seeks to increase your complexity for his benefit alone.
0
brotaCommented:
I can see a resource forest for Exchange but not a child domain because like everyone has said it is still in the same forest.
How many mailboxes?
If anything I would look into collapsing your domain into the root.
If there is major problems in the AD they could be in the root too. If there are major problems I would consider a new forest and do a cross forest migration.

0
RavenIndAuthor Commented:
I found some MS documentation on creating an Exchange 2010 resource forest. This might have been more what he was referring to: http://technet.microsoft.com/en-us/library/aa998031.aspx 

Does this make more sense possibly?
0
brotaCommented:
I dont see any reason why you would need it.You have a domain that can handle 2010
With a resource forest you need to create disabled user accounts in the domain.
The migration will be a cross forest migration. You may need 3rd party tools to support free busy during the migration since the interorg replication tool does not support free/busy between 2010 and 2003.
The interorg tool should work for public folder replication.

This method is usually done for merger migrations.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.