I've been searching the past two days and reading a lot, and I still have some questions about the best next steps in our migration. We have a very simple 1 server Exchange 2010 environment (Server 2008 R2 in Hyper-V) with a Barracuda device sifting email before delivery. I installed Exchange 2013 as a new Server 2012 Hyper-V VM after reading the guides and making sure we have Exchange 2010 SP3 and installing Exchange 2013 CU1. Things are fine so far, but unfortunately we have the "Ambiguous URL" situation discussed in this article:http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
I have enabled Outlook Anywhere on 2010 for all connections (fast/slow) using the method suggested in the article.
I have not fully configured all the URLs on 2013 yet since I don't know the full effect it might have.Currently,"mail.domain.com" is just a CNAME pointing to "exch2010.domain.com" and all URLs on 2010 are using that FQDN.
I'd like to update things so that we are using recommended values for the CAS and everything else, and I'd like "mail" to be used in the URLs for client access (OWA, IIS) so this isn't such a headache next time. I think my next step should be to change the URLs on 2010 to use "mail.domain.com" instead of the FQDN and then set up "mail.domain.com" on 2013 as well before eventually repointing "mail" in DNS.
Does that sound right? Should I expect any difficulties or temporary outages for users in Outlook or on mobile devices?