2013/2010 Co-existence - why outlookanywhere is compulsory ?

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


  • Edited by kimimcp 14 hours 45 minutes ago
March 20th, 2015 4:31pm

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 7:39pm

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 ?



  • Edited by kimimcp 22 hours 19 minutes ago
March 20th, 2015 9:03pm

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 9:55pm

you are right but look :

in place 2010

outlook connectivity internal (rpc/tcp)

-outlook.company.com=> casarray

outlook connectivty external

- none (vpn require)

OWA, EWS, ASync.... internal and external

- mail.company.com

Co-existence 2010/2013

outlook connectivity internal (rpc/http)

-mail.company.com

outlook connectivity external (rpc/http)

- not set...

but as you said it will be routable. so CAS2013 will receive some rpc/http(s) requests but wont be able to proxy to cas2010 because AO anywhere wont be enable on existing 2010 orga ?

only maiboxes already moved to exchange2013 will be able to connect from outside with AO on 2013.

so if i conclude, the only reason to enable AO on 2010 orga during a co-existence with 2013 its just to proxy AO request from outside to exchange2010.

But if mailbox are still on ex2010, if a internal client attempt to connect we wont care about outlook anywhere. just connect with casarray just like before co-existence ?????

i hope i made myslef clear





  • Edited by kimimcp 21 hours 53 minutes ago
March 21st, 2015 5:15am

you are right but look :

in place 2010

outlook connectivity internal (rpc/tcp)

-outlook.company.com=> casarray

outlook connectivty external

- none (vpn require)

OWA, EWS, ASync.... internal and external

- mail.company.com

Co-existence 2010/2013

outlook connectivity internal (rpc/http)

-mail.company.com

outlook connectivity external (rpc/http)

- not set...

but as you said it will be routable. so CAS2013 will receive some rpc/http(s) requests but wont be able to proxy to cas2010 because AO anywhere wont be enable on existing 2010 orga ?

only maiboxes already moved to exchange2013 will be able to connect from outside with AO on 2013.

so if i conclude, the only reason to enable AO on 2010 orga during a co-existence with 2013 its just to proxy AO request from outside to exchange2010.

But if mailbox are still on ex2010, if a internal client attempt to connect we wont care about outlook anywhere. just connect with casarray just like before co-existence ?????

i hope i made myslef clear





Correct. If you don't enable OA on the 2010 CAS, then any OA connections from the 2013 CAS will fail.

You can verify this with https://testconnectivity.microsoft.com/

Free Windows Admin Tool Kit Click here and download it now
March 21st, 2015 3:04pm

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

Other recent topics Other recent topics