asked on

Exchange 2010\2013 co-existence CAS Array members

Hi All,

i have a client that is having some really odd Outlook behavior.

Could somebody with a 2010\2013 co-existence sanity check something for me (google trawling has not helped)

Do Exchange 2013 CAS servers add themselves to the 2010 CAS Array for a site?

i.e.

Get-ClientAccessArray | Select -expandproperty Members

Open in new window

contains 2013 servers...

I've done a few migrations, but have never noted this.... the customer is stuck in co-existence due to an old blackberry deployment.

Any help would be appreciated!!

Guy

ASKER CERTIFIED SOLUTION

M A

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Guy Lidbetter

ASKER

Hi Mas

Thanks for this, i am very familiar with it all, I had just not ever taken note that the 2013 CAS populated itself into the 2010 CAS Array. Struggling to find any mention of it in documentation.

Turns out the issue was a hosts file entry on the terminal server pointing the autodiscover namespace to a 2010 CAS box that was removed. Why it was even there befuddles me...

Thanks for confirming this for me...

Guy

M A

Ensure Outlook anywhere is enabled on all clients/PCs as Exchange2013 works only on RPC/HTTP (Outlook Anywhere)

Guy Lidbetter

ASKER

Thanks MAS.

Jon Doe

You do not need to ensure Outlook anywhere is configured on Outlook clients. Outlook will query the SCP and find the new Exchange 2013 server after redirection on Casarray. Domain.com through the Autodiscover service. The only time it needs configuration is when you are not on the LAN or VPN.

Guy Lidbetter

ASKER

Hi Sunit, i think MAS is commenting on how Outlook will handle RPC/HTTP as opposed to the old RPC/TCP connections. As you mentioned from Outlook 2010 onward it should happen automatically.

As Exchange 2013 CAS is session-less and RPC end point is no longer used. RPC/TCP has been deprecated so essentially any connection to a 2013 CAS box is technically Outlook Anywhere. The same as setting up Outlook 2010 to use HTTP mode as its default.