Best way to upgrade to Exchange 2013 and change domain name

Ok first here is our systems background:
-Active Directory with server 2012 DCs running in server 2003 domain and forest functional levels because we have a flat domain name with no TLD. We are also running Exchange 2003

We are wanting to upgrade Exchange 2003 and change domain name to include a TLD as required by windows server starting with 2008 r2. What is the simplest way of doing these 2 things?

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.

Simon Butler (Sembee)ConsultantCommented:
Simple? There is no such thing for this scenario.
Changing the domain name isn't supported with later versions of Exchange, and under Exchange 2003 it usually meant that Exchange didn't work correctly.
Therefore the only option I would consider is a new Forest and domain and migrate all resources across to it. Options to do that vary, depending on the number of users either manual or third party software.
That will also allow you to do the migration in a controlled manner, using trusts etc to ensure it is done with as little disruption to the business as possible.


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
aackarAuthor Commented:
How about this:
I export all the Exchange 2003 mailboxes to network share, then I completely remove Exchange 2003 from AD, change the domain name, raise the domain/forest functional level to 2012 and then install Exchange 2013 and move all the boxes to the new Exchange install from the network share. I don't think that all the various versions of Outlook would "break".
What do you think about that?
Simon Butler (Sembee)ConsultantCommented:
The data is only a small part of Exchange.
The method you have outlined will mean the loss of all settings.

- Email addresses
- Permissions within mailboxes

The method you have outlined will cause significant business disruption - a day, maybe more and you still have a domain that is badly configured in place. What does it gain you? A little less work?
It isn't something I would do - the method I have outlined can be done with very little business disruption.

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

aackarAuthor Commented:
So going your way, would it be better to do the migration first and then upgrade from Exchange 2003 to 2013 or would it be better to upgrade to Exchange 2013 in the existing scenario and then do the migration to the new forest?
Simon Butler (Sembee)ConsultantCommented:
If you are building a new forest then deploy the latest and greatest straight in to the new forest.
Then migrate the resources to the new forest going to the latest version. I don't see any point in deploying an older version of something simply to upgrade shortly afterwards.

aackarAuthor Commented:
I appreciate your help. Can you recommend any good guides on the internet that explains the process and any gotchas that might be part of this process?
Simon Butler (Sembee)ConsultantCommented:
Cross Forest migrations are documented on TechNet - I think the Exchange team blog has outlined what is involved. You will not find anything that completely tells you what to do, because each one is unique. You will have to look at a number of resources.

The main problem that catches people out is the account creation. Trying to create the new accounts first doesn't work well.

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
Active Directory

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.