2013/2010 Co-existence - outlookanywhere external ?

Hi all

i have been doing several exchange migrations from 2003 /2007 to 2010 and i am inteeding to do my first migration from 2010 to 2013.

in my orga 2010 we do not use outlook anywhere.

seems to be easy but i dont get something :

why should i enable OA on my 2010 cas in order to migrate to 2013? obviously, i m aware of since Ex2013 all traffic goes to RPC/HTTP (rpc/tcp = mapi /rcp no longer exist)

but during the Co-Existence period,

For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array, right ?

For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2013, they will connect to the Exchange 2013 MBX through the cas2013, right ?

But what if we won't intend to use OA on Ex2013 either  ? ( i mean leave the external hostname entry blank)

we dont have to enable OA on ex2010 as mentioned everywhere ?

i suppose everythin gonne be ok ?

thanks a lot

Regards

March 20th, 2015 12:32pm

If you do not want to use Outlook Anywhere externally , then you can probably get away with not enabling OA on the 2010 CAS, assuming you are keeping the 2010 and 2013 namespaces separate.

Also note that leaving the external host name blank is not enough for the 2013 OA config. The internal host name has to also be unresolvable externally.

Free Windows Admin Tool Kit Click here and download it now
March 20th, 2015 3:40pm

thanks a lot Andy for your time.

The internal host name has to also be unresolvable externally. => nice tips.

why should i care to keep 2010 and 2013 namespace separate ? i plan de keep the same :D

we have urls below :

outlook connectivity internal

-outlook.company.com=> casarray

outlook connectivty external

-none

others urls : internal + external (split dns)

-mail.company.com

so with ex2013 outlook anywhere wil be : mail.company.com as well.

is it right ?

March 20th, 2015 5:04pm

thanks a lot Andy for your time.

The internal host name has to also be unresolvable externally. => nice tips.

why should i care to keep 2010 and 2013 namespace separate ? i plan de keep the same :D

we have urls below :

outlook connectivity internal

-outlook.company.com=> casarray

outlook connectivty external

-none

others urls : internal + external (split dns)

-mail.company.com

so with ex2013 outlook anywhere wil be : mail.company.com as well.

is it right ?

If you use mail.company.com as the internal Outlook anywhere host name in 2013 and are using split DNS, then external users will be able to connect using Outlook Anywhere.

Free Windows Admin Tool Kit Click here and download it now
March 20th, 2015 5:56pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics