Migrate single Exchange 2010 to Exchange 2013.

Hi,

I just read the blog post from the Exchange Team over at http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx and got some questions.

We have a fairly small Exchange 2010 environment with only one Exchange server running the following roles: Mailbox, ClientAccess, UnifiedMessaging, HubTransport.

We publish external access to Exchange 2010 through TMG 2010. We also use split DNS.

Now we are planning for a migration to Exchange 2013.

The hostnames we have are the following

Get-WebServicesVirtualDirectory | Select-Object ExternalUrl, InternalUrl | fl
ExternalUrl : https://autodiscover.externaldomain.tld/ews/exchange.asmx
InternalUrl : https://exchange2010server.internaldomain.tld/ews/exchange.asmx

Get-EcpVirtualDirectory | Select-Object ExternalUrl, InternalUrl | fl
ExternalUrl : https://mail.externaldomain.tld/ecp
InternalUrl : https://mail.externaldomain.tld/ecp

Get-OwaVirtualDirectory | Select-Object ExternalUrl, InternalUrl | fl
ExternalUrl : https://mail.externaldomain.tld/owa
InternalUrl : https://mail.externaldomain.tld/owa

Get-OutlookAnywhere | Select-Object ServerName, ExternalHostname | fl
ServerName       : exchange2010server
ExternalHostname : autodiscover.externaldomain.tld


Our OutlookProviderFlags looks like this

Get-OutlookProvider -Identity EXPR | Select-Object Name, OutlookProviderFlags | fl
Name                 : EXPR
OutlookProviderFlags : None

Get-OutlookProvider -Identity EXCH | Select-Object Name, OutlookProviderFlags | fl
Name                 : EXCH
OutlookProviderFlags : None


Looking back at the blog post from the Exchange team, is there anything I need to change, or need to be worried about :) ?

Regards Erik