Moving data between two Exchange 2010 servers (same forest)

Dear all,
We had a major crisis here in the office with our Windows 2008 R2 Std. Running Exchange 2010 Std. The short story is that we are now running the old server as a VM on a Datto appliance (dont ask me why restore to old server didnt work, thats a whole new discussion - not happy with Datto right now!).

Anyway, I had to rebuilt the old server, fresh new OS and Exchange install. I need help in migrating data between these two Exchange 2010 servers. The ideas is to move data over the weekend here, and then shutdown the old Exchange 2010 (VM session). Both server are on the same domain/ forest.

Please advise on settings permissions, mailbox move, connectors, the whole nine yards. I have an SSL key for OWA on the old one, but I know how to move it to the new server with changing the firewall to point to the new server.

Looking forward to your responses. Thanks in advance.
SpiderPigAsked:
Who is Participating?
 
marcoseguracrConnect With a Mentor Commented:
In the microsoft documentation, the right way to find your solution is:

Exchange Server 2010 - Server Move (to new hardware)

If you use this in google you will find your answer, but in general there is not a lot of stuff there, because normally you find only migrations to new version, but I use this one years ago when move one of my client stuff (was really heavy because in my case I get some error like cannot demote because the client migrate from 2003 => 2007 => 2010 ( a lot of bugs) but I hope you cannot get this kind of issues:

http://www.anthonygarmont.com/1/post/2012/07/exchange-server-2010-server-move-to-new-hardware.html

In general you need to:

Change the source transport server on your send connector(s) to the new server.

For the receive connectors, create any additional/custom ones on the new server and direct those hosts that use them to the new server (hopefully they've been using a DNS alias for this so you can just update that one DNS alias. If not, consider doing that from this point forward )

You'll also need to look at any external URLs for services such as OWA, ActiveSync, and how you've published those to the internet (eg ISA/TMG firewall rules would need updating).

For your SSL cert, it won't be useful for the new server because the FQDN of the server is different (if you have a domain like *.contoso.com you can use it if not buy new one). You'll need to acquire a new SSL cert that includes the new server's name. Depending on who your certificates were purchased from they may allow a free re-issue with the new name, check with them for whether that is the case or not.

Also check any incoming SMTP firewall rules or smart hosts, make sure they're routing incoming internet mail to the new server.

As I explain you before not 2010->2010 stuff out there  Just proceed cautiously and use things like protocol logs, message tracking logs, IIS logs, to verify that services are no longer seeing hits before you decom the old server. And decom with care, perhaps shutting it down for a few hours first and running a series of tests to verify all is working.

CAS is the most important stuff you need care.
0
 
marcoseguracrCommented:
Ok,

Looks like you need STAGE MIGRATION, with both server coexisting both together. In general you can have your old one (VM) running normally. You need to install the same SSL in the new one, but rather, point your firewall to different external ports (this is to allow OWA access to accounts that you migrae from one server to other. Your old Exchange SMTP server will the only valid SMTP. In general you need to transfer all important stuff to the new server, and move the mailboxes one by one from one server to the other until get all ready to demote the old one.

After you demote, you can point back all your firewall rules to the new server.

Your case is really similar to migrate mailboxes from Exchange 2010 to Office365, you can access that info easy from google.

If you are not Exchange Pro, I recommend you contact an specialist, sometimes demote old Exchange Server is not easy and you need some PowerShell Skills, depending about how damage it is or how the actual configuration is, when non standard configuration are deployed before.

Marco
0
 
SpiderPigAuthor Commented:
Marco, thanks for the reply. Everything you wrote about is known and understood. I need the exact how-to here. I have done numerous 2003-2007 and 2007-2010 migrations in the past. I know this should be easy since it's the same version. Just need exact bullet point to-do list.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
SpiderPigAuthor Commented:
O.K you point me at the right direction. I installed a fresh new Exchange ran into some issues, but were able to finish a successful install. I then started moving all mailboxes (70GB total), which worked fine after I used the BadItemLimit, I then update AutoDiscovery, SSL, FIrewall, and CAS. I tested incoming and out going emails and all is working fine.

One issue remaining is that when I remote in to TS and open Outlook I found that Outlook 2010 still points to old exchange server. How do I force it to auto update? Should I create a CAS array?
0
 
marcoseguracrCommented:
In normal configuration, when you login to outlook, It detect what is your Exchange Server automatically, where ever change you made. It happens to all clients or only TS remote clients with Outlook?

In general when you move accounts and users from servers you don't need to change nothing in client side.

And most important:

CAS ARRAY is the first step, if you not make it first, you can try to make one, but this will not update the clients in some cases, and you need to make some powershell updates in your Exchange enviroment to get this done, normally is not the same for all.

Actually the main issue here is the CAS array my friend

:)
0
 
SpiderPigAuthor Commented:
Sounds good, well it was a long weekend. I am here at the client office this morning and everything is working smooth. All Outlook clients are happy :)

It looks like the migration was successful! I disabled all Exchange services on the old server. I will keep it there for a week before uninstalling Exchange from the old server.

Anything special I should keep in mind when uninstalling the Exchange 2010 or is it a simple uninstall?

Thanks a lot for your help. It was really useful.
0
 
marcoseguracrCommented:
If you already migrate all roles and connectors all will be ok. Sometimes if you have PUBLIC FOLDERS, you will get some issues to uninstall it, but you can solve it with PowerShell and wait for move the objects

If my advisory was good for you please post the right answer and this cases like complete my friend.

Greetings

Eng. Marco A. Segura
Windows Specialist
HP Proliant Server Specialist
HP Storage Specialist
Elastix ECE
HP - Cisco Networking Specialist

S.J. - Costa Rica
0
 
SpiderPigAuthor Commented:
Good info, pointed me to the right direction. Thank you.
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.

All Courses

From novice to tech pro — start learning today.