The misconception about Outlook Anywhere in 2010 > 2013 migrations


Guys,

there is a misconception about the need to enable the Outlook Anywhere in the Exchange 2010 servers as a pre-requisite to move mailboxes to the Exchange 2013 servers. Actually, if users don't need to access resources in the Exchange 2010 servers through OA you do not need to enable it. Sometimes, you can face a customer that has a security statement against the OA. In such scenario, you do not need to enable Outlook Anywhere in the Exchange 2010 servers only to migrate to the Exchange 2013 servers. Obviously OA must be always enabled in the Exchange 2013 servers "just" because this is the only way Outlook can connect to Exchange 2013.

😉

Comments (4)

  1. Deivid Foggi says:

    @turbomcp, I’m talking about OA is not a requirement for Exchange 2007/2010/2013 coexistence and my guess is you are talking about namespace planning. If you have the same namespace for MAPI/RPC and HTTPS, you are running in an ambiguous URL scenario and
    we really do not recommend this kind of namespace plan once Exchange 2013 CAS doesn’t know how to handle direct MAPI/RPC connections. If you are running 2010 in the recommended scenario, which means one FQDN for MAPI/RPC, another one for HTTPS workloads and
    your MAPI/RPC FQDN only resolvable via internal DNS, there are no need to enable OA once the Autodiscover will delivers to the those Outlook clients connecting to the not yet migrated mailboxes a FQDN for the RPCClientAccessServer/ClientAccessArray different
    from that one used by Exchange 2013 OA. Thanks for the comment.

  2. Tiago Souza says:

    Boa Deivid! Bem relevante, vou linkar no meu Blog.

  3. turbomcp says:

    Thanks
    that is very true except for one scenario
    if the 2010 made the mistake of using cas array name the same as the other name they use
    like mail.contoso.com for all naming uses…

  4. PinkY says:

    @turbomcp
    can you explain in more detail? thought that CAS array name is used only as placeholder, not as an actual connection point for the clients…
    tnx

Skip to main content