Migrate Exchange 2010 to Exchange 2013

Hi Exchange Experts,

I have a simple and small  exchange 2010 environment and will be migrating to Exchange Server 2013 in a month or so.

Current environment:
OS; Windows Server 2008 R2
Exchange 2010 SP3  - running all roles in single server

New  Environment
OS: Windows Server 2012 R2
Exchange 2013 - all roles in single server

Note: Exchange environment is not connected to the internet.

The new Exchange 2013 will need to co-exist with 2010 for couple of weeks before decommissioning.  There are many articles out there on the internet most of them involve complex environment.  

I know  this should be easy and simple but I don't want to miss anything.

Please point me to the right direction how to achieve the above.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Since you'll only have one server (per Exchange version) and wont have to deal with load balancers, it should be really easy..  Especially (and I'm assuming) if your users are all on the domain that Exchange is in, (??)

First, make sure you're on the latest rollup on your Exchange 2010.. Currently SP3 RU11 I believe..  There are always co-existence improvements in the updates, so being on the latest will be helpful.

Install Exchange 2013 and all roles on the new server.  It will see your existing exchange environment, and it actually should pretty much integrate itself..  You'll be able to manage your 2010 environment through the old EMC still, and you'll be able to manage your 2013 through the management web page.

You should be able to move a test mailbox over to 2013, and your client should auto-detect it, and move over too..  (May have to exit / re-run outlook).  If you have an Outlook Web access DNS entry, at this point, move it to point to the 2013 server, because it will intelligently proxy back to 2010.  

Once you've tested interaction between the test mailbox and the old 2010 server (send mail both ways, etc..) you can just move all the mailboxes.

You said it's not connected to the Internet, but assuming there's SOME external connectivity, you'll need at this point to move any inbound/outbound connectors to the 2013 server, and verify they're working.  After this, just do an orderly uninstall of Exchange from the 2010 server, and you should be done.

Most of the complexity you would have in this would be if you have multiple servers, so you'd typically have a load balancer for the CAS role, but given that you don't have a DAG configured, and there's only one server, there's no implication of failover anyway..

Good luck!   I've done similar in my home lab, although in my testing, I had 3x 2010 servers, and 3x 2013 servers to provide HA/DR via DAG, and it wasn't much more complex than this anyway..
Ganesh Kumar ASr Infrastructure SpecialistCommented:
As advised by Pilot, it is easy since you dont have DAG and single server. There is much effort required, it is easier you should ensure a single mailbox movement and test if
the moved mailbox can access Exchange 2013 owa, outlookanywhere, and other required client protocols. You also can use use this step by step article for easy understanding : http://www.petenetlive.com/KB/Article/0000788.htm

Read this article this will help you on each part safely : http://msexchangeguru.com/2013/05/10/exchange2013-migration/
DeoraliAuthor Commented:
Thanks 172Pilot and Ganesh Kumar.

Any namespace, dns record change planning required?
As long as your clients belong to the domain, they should use the domain to locate pretty much everything you need..  If you have external machines sending SMTP mail in, then you'd have to look at whether they're pointing to an IP address which would need to be changed, or to a DNS "A" or mx record which may need to be changed, but since you're not using a load balancer, and  you're probably leaving all of your exchange autoconfigure directories at the default, it should do pretty much everything else automatically..

If I were to do it on a larger scale, where I had a load balancer pointing to all my 2010 CAS servers, and another one pointing to the 2013 CAS servers, I would have to do a "cas cutover" at which point the hostname for the CAS would have to be changed to the new load balancer, and give the old one a legacy name, but in your case, I think you'd be good..

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
DeoraliAuthor Commented:
Running into namespace question. Will open a new thread.
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

From novice to tech pro — start learning today.