With the recent releases of Exchange Server 2013 RTM CU1, Exchange 2013 sizing guidance, Exchange 2013 Server Role Requirements Calculator, and the updated Exchange 2013 Deployment Asistant, on-p...
Updated Mar 24, 2020
Version 3.0
Blog Post
11 MIN READ
Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
@Barebodkin, you can use the -OutlookProviderFlags:ServerExclusiveConnect parameter with Set-OutlookProvider cmdlet mentioned in the article to force that tickbox on. I don't remember exactly what client versions started respecting the setting so you'll want to make sure you are using at least the Exchange 2013 compatible client versions as they definitely do.
@Robert, you are not affected because your system was never setup with a proper CAS Array Object, thus you won't be moving the current server's FQDN to point at 2013. Your users will connect via MAPI/RPC to 2010 until you move their mailboxes to 2013. Once you move them the 2010 box will issue a ecWrongServer response and trigger a profile update.