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