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
LVL 13
Guy LidbetterAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MAS (MVE)EE Solution GuideCommented:
When you install an Exchange2013 to an existing 2010 organization Exchnage2013 CAS servers will be added as a member of CAS Array automatically.

Then your interface will be Ex2013 CAS servers. or Load balancer VIP if you have a load balancer.
i.e. you should point autodiscover.domain.com and commonname.domain.com to Exchange2013 CAS server
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Guy LidbetterAuthor Commented:
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
0
MAS (MVE)EE Solution GuideCommented:
Ensure Outlook anywhere is enabled on all clients/PCs as Exchange2013 works only on RPC/HTTP (Outlook Anywhere)
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Guy LidbetterAuthor Commented:
Thanks MAS.
0
Jon DoeCommented:
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.
0
Guy LidbetterAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.