• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 360
  • Last Modified:

Migrate Exchange 2010 to new hardware

I need to move an Exchange 2010 build off of some legacy hardware. I'm hoping to do a VM connected to a new SAN. Are there any guides on moving from Exchange 2010 to Exchange 2010? I don't want downtime. If possible, I might look at p2v conversions. We also don't have System Center so I would have to use the Xen p2v which makes me a bit uncomfortable for a critical application.
0
LCNW
Asked:
LCNW
  • 5
  • 4
  • 3
4 Solutions
 
AmitIT ArchitectCommented:
Follow this
https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/

I used it and migrated nearly 80 servers on 40+ sites...As far as downtime is concerned, mailbox move from Exchange 2003 to 2010 is offline, so users who's mailbox are in move process will be offline rest will be working.

P2V is not required here, just setup new 2010 server in same Exchange org and follow the articles given above.
0
 
LCNWAuthor Commented:
This is for 2003 > 2010. Will this be applicable for 2010 > 2010?
0
 
Simon Butler (Sembee)ConsultantCommented:
If you want no downtime then P2V isn't an option.
A regular migration is completely risk free and involves minutes of downtime per user. As such if you schedule it correctly then it can be done with zero downtime for users. It is the only option I would consider.

Simon.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
LCNWAuthor Commented:
Ok. So is there a guide for 2010 to 2010?
0
 
Simon Butler (Sembee)ConsultantCommented:
You don't really need one.
Install Exchange, replicate public folders, move OAB, move mailboxes. When you run add/remove programs it will tell you if anything has been missed.

The biggest headache people have is moving the clients, because unless you have an RPC CAS Array you will not get the clients to move to the new server. That will mean touching every client to get them to update.

Simon.
0
 
AmitIT ArchitectCommented:
There is no migration guide within same exchange org, As Simon said you need to setup new Exchange server and move over the mailboxes etc. to new server.

My suggestion would be keep both servers and load balance accordingly.
0
 
LCNWAuthor Commented:
I think I'll look at doing a CAS array. In the past, I had a login script that pushed a PRF file to switch servers in Outlook. I'm curious as to if that will still work. I'll have to test.
0
 
AmitIT ArchitectCommented:
In 2010 that is not required as you have auto discover feature. I installed several servers and moved mailboxes and never touched a single user for any change.
0
 
LCNWAuthor Commented:
I wish I could ask a few more questions. I've moved a mailbox and Outlook automatically pointed to the new server. I'm trying to understand whether or not I need the CAS Array. I'm having a lot of trouble trying to get answers.
0
 
Simon Butler (Sembee)ConsultantCommented:
As far I am concerned, you need a CAS Array.
Every implementation I do gets a CAS Array whether they want one or not.

Simon.
0
 
LCNWAuthor Commented:
Fair enough. So do I only point new databases on new server to it since the old one is going away?
0
 
Simon Butler (Sembee)ConsultantCommented:
Set the CAS Array on all databases in the AD site. Then you can repair the profile on all mailboxes before or after moving them - it doesn't matter.

Simon.
0
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 5
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now