EXCHANGE 2010 MIGRATING TO NEW HARDWARE HOW TO OUTLOOK 2003 CLIENTS BEST WAY
I have a windows 2008 exchange 2010 member server HYPER V VM with 2 domain controlllers. I want to move away from Visrtual Exchange 2010 server and move it to a NEw Physical machine. as it has been runnning very slow, now I have address books distribution lists, everything you can possible configured on this server like 10 connectors for different smtp servers we have setup. I have done alot of work on this exchange server 2010. How could i transfer all my settings to new exchange 2010, I need to do this on a sunday i know there must be a procedure that will move all my settings to a new servers. and the other thing is the computer name how do i get around the outlook 2003 clients having the computer name of the email server. it would be a nightmare if i need to go around every computer to change the name. need advice on whats the best way to make this project go smooth. thanks guys for your help in advance.
August 3rd, 2012 12:47pm

Updating the connectors, replicating Public Folders, rehoming OAB, and moving mailboxes is fine. The problem I see is that your outlook 2003 will not redirect to the new server if you did not create a cas array when setting up your first server. And since you are on outlook 2003 you cant force an autodiscover (not supported on 2003) on the client by making the server unavailble by shuttding down the server or removing the DNS record. The only way I can think of if you don't want to reprofile each outlook is to migrate everything over the weekend including decomissioning the old server than changing the dns record of the old mail to point to the new mail server or push out an outlook prf file with the updated settings. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2012 1:05pm

Updating the connectors, replicating Public Folders, rehoming OAB, and moving mailboxes is fine. The problem I see is that your outlook 2003 will not redirect to the new server if you did not create a cas array when setting up your first server. And since you are on outlook 2003 you cant force an autodiscover (not supported on 2003) on the client by making the server unavailble by shuttding down the server or removing the DNS record. The only way I can think of if you don't want to reprofile each outlook is to migrate everything over the weekend including decomissioning the old server than changing the dns record of the old mail to point to the new mail server or push out an outlook prf file with the updated settings. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
August 3rd, 2012 1:13pm

how would i replicate folders. i was planning to do it on the weekend but is there a way to keep the same name ? or is that just not a option. how does someone start the migration process what steps need to be taken first second and so on. I dont want to mess this up as we depend on email so much, this is the project i dreaded doing because i knew it was going to be difficult. -martin
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2012 5:01pm

Just create a replica you can use the gui instructions below. There is no option to keep the same name. You can read the section below it will take you what you have to migrate. You also have to move the arbitration mailbox since it's 2010 and not 2007. Just start the migration process and if you're stuck at a section post back. Just make sure PF, OAB, Connectors, arbitration mailbox etc is all migrated over. Than test by moving a single mailbox to 2010. And log into his outlook (which will likely fail since its pointing to old, so for this account just create a new profile using new servername. Than test send receiving email and make sure that external email is going out using your new server and not routing to old server. Make sure this account can access PF and it's connecting to the new server not old, you can test by opening outlook /rpcdiag and it will show the connection. Once you're comfortable that this one mailbox is working, than migrate all mailboxes to new server. Than uninstall the old server. The uninstall may complain if you haven't completly migrated all components over in which you have to follow the instructions. Step 1: Prepare the Exchange 2007 organization to remove legacy Exchange servers -------------------------------------------------------------------------------- http://technet.microsoft.com/en-us/library/gg576862.aspx Configure Public Folder Replication http://technet.microsoft.com/en-us/library/bb691120 James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
August 3rd, 2012 6:14pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics