xcomiii
asked on
Moving all data from one Exchange 2010 to another Exchange 2010 server
I am trying to move all data from a single Ex2010 multirole (CAS/HUB/MBX) server to another multirole server, serverB (CAS/HUB/MBX).
The old server (ServerA) is close to dying and I understand that I need to transfer all data to a new Exchange server.
So far so good. But the problem is pointing the Outlook 2010 clients to the new server.
This is what I have done so far:
1. Moved all mailboxes to a new mailbox database on the new server (ServerB).
2. Enabled and imported a public UCC certificate.
3. Moved OAB generation to ServerB
4. Created receive connectors on serverB, similar to ServerA.
5. Redirected mailflow by updating NAT rules on my firewall (both servers are public internet facing, so mail is flowing in and out correctly.
6. Updated both mailbox databases, so both points to ServerB. (Get-MailboxDatabase | fl rpc* shows ServerB).
But Outlook 2010 clients are still pointing to ServerA and is not starting at all if I shutdown ServerA. I can see in Outlook that it connects to ServerB for OAB, but still 3 connections to ServerA.
Any way I can solve this?
I was thinking that pointing the mailbox databases to the new RPCClientAccessServer would automatically redirect the clients.
The old server (ServerA) is close to dying and I understand that I need to transfer all data to a new Exchange server.
So far so good. But the problem is pointing the Outlook 2010 clients to the new server.
This is what I have done so far:
1. Moved all mailboxes to a new mailbox database on the new server (ServerB).
2. Enabled and imported a public UCC certificate.
3. Moved OAB generation to ServerB
4. Created receive connectors on serverB, similar to ServerA.
5. Redirected mailflow by updating NAT rules on my firewall (both servers are public internet facing, so mail is flowing in and out correctly.
6. Updated both mailbox databases, so both points to ServerB. (Get-MailboxDatabase | fl rpc* shows ServerB).
But Outlook 2010 clients are still pointing to ServerA and is not starting at all if I shutdown ServerA. I can see in Outlook that it connects to ServerB for OAB, but still 3 connections to ServerA.
Any way I can solve this?
I was thinking that pointing the mailbox databases to the new RPCClientAccessServer would automatically redirect the clients.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for a long and thorough explanation.
I will try the solution, however I can not try it yet, since I cannot uninstall the old Exchange server (problems with Windows Installer). But I will let you know :)
I will try the solution, however I can not try it yet, since I cannot uninstall the old Exchange server (problems with Windows Installer). But I will let you know :)
ASKER
Tigermatt, thanks!
That really solved the problem for internal clients in our LAN.
But how can I make it work for users that are outside and user Exchange Anywhere?
I have updated DNS settings externally and directed autodiscover into the new server.
Will a profile repair be enough? Or maybe delete the OST file?
Some users are sitting on very unstable connections and I am a little worried that if those users starts to download the entire OST file with interruptions, it can take several days.
That really solved the problem for internal clients in our LAN.
But how can I make it work for users that are outside and user Exchange Anywhere?
I have updated DNS settings externally and directed autodiscover into the new server.
Will a profile repair be enough? Or maybe delete the OST file?
Some users are sitting on very unstable connections and I am a little worried that if those users starts to download the entire OST file with interruptions, it can take several days.
Sorry for the delay in getting back to you. I was away from my emails for a couple of days.
>> Will a profile repair be enough?
Yes, a profile repair, in theory, from a remote location should be enough.
Deleting the OST file wouldn't really do anything; Outlook could just re-connect to the same CAS as it was using before and re-sync the user's mailbox from there.
-Matt
>> Will a profile repair be enough?
Yes, a profile repair, in theory, from a remote location should be enough.
Deleting the OST file wouldn't really do anything; Outlook could just re-connect to the same CAS as it was using before and re-sync the user's mailbox from there.
-Matt
Open Adsiedit.msc->Config partition->services->Micro