Exchange 2007 to 2013 migration

Dear Forum members,

I'd like to ask you about best practices during an Exchange 2007 to 2013 migration. We have two public IP address, and an old SBS 2008 machine. Our best plan is to install two Exchange 2013 in a DAG, plus one round robin DNS record (no HW load balancer is available), and make it available from the internet via the second IP address.

So the question would be that if I do this, and then on the Exchange 2013 web console, set the URL-s to the correct new DNS name, then when I move the accounts from the old 2007 system to the new, would they realize these new URL-s? What I'm really afraid is the Exchange Autodiscover service gives bad URL-s to users so the infrastructure would be not accessable.

In your opinion, what is the best way to do this? I appreciate every comment, since you may know these best practices much more than me!

Ps.: Maybe the inside clients are the best with this change since Outlook quickly realizes the new server DNS record, but what is it with the external Outlook Anywhere and Exchange ActiveSync clients? Would they break after this change? Or still survive if nothing happened?

Thank you really much for your help,

Best Regards,

Chris

March 9th, 2015 6:55am

Please walk through this informative technet blog that covers all the parts and provides step-wise instructions to achieve this goal : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

You can also follow Exchange server deployment assistant that is available from Microsoft team and would be a good assistance for you. Please check this : https://technet.microsoft.com/en-us/office/dn756393.aspx

Moreover, if you are still concerned about data security, You may also consider on this automated solution (http://www.exchangemailboxmigration.com/) that could be a good alternative approach to get this job done in more hassle-free manner.

Free Windows Admin Tool Kit Click here and download it now
March 10th, 2015 3:18am

So the question would be that if I do this, and then on the Exchange 2013 web console, set the URL-s to the correct new DNS name, then when I move the accounts from the old 2007 system to the new, would they realize these new URL-s? What I'm really afraid is the Exchange Autodiscover service gives bad URL-s to users so the infrastructure would be not accessable.

Hi Chris,

Don't worry about this, if you set the url correctly, the exchange autodiscove services will auto identify the correct url.

If the mailbox in exchange 2007, it will redirect the RPC request to exchange 2007 CAS server automatically.

I also recommend you refer to the following article to migrate :

Step-by-Step Exchange 2007 to 2013 Migration

Best regards,

March 10th, 2015 8:56am

Hi Chris,

Any update?

Best regards,

Free Windows Admin Tool Kit Click here and download it now
March 11th, 2015 9:09pm

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

Other recent topics Other recent topics