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
Hi Brian,
I understand, when ambiguous URLs are implemented, that customers should follow the guidelines in this blog so all internal Outlook clients use OA to access Exchange 2010 mailboxes.
But what if you're not using ambiguous URLs and Exchange 2010 currently runs with outlook.contoso.com (mapi/rpc) & mail.contoso.com (https)? I assume you have nothing to do?
I have the same question regarding the design of a new Exchange 2010 environment. Exchange is designed conform MS best practices with outlook.contoso.com (mapi/rpc) & mail.contoso.com (https). Should internal Outlook 2007/2010 clients use MAPI/RPC or Outlook Anywhere (RPC over HTTPS)? I'm currently designing a new Exchange 2010 environment and there is some discussion about this. I know that with Exchange 2013 all Outlook clients use OA by default but that's a architectural change.
So, regarding Exchange 2010 and not using ambiguous URLs, does MS have any recommendations? Should internal Outlook clients use mapi/rpc by default or force OA? Are there any performance considerations (mapi/rpc clients directly access CAS Array FQDN & OA clients access RPC proxy endpoint)?
Regards, Martijn