Exchange 2016 Mailbox Servers Showing in Exchange 2010 CAS Arrays

We are currently in a state of coexistence with Exchange 2010 and Exchange 2016. Just noticed that the Exchange 2016 mailbox servers are members of the CAS Arrays that were created for Exchange 2010. The Exchange 2016 servers are at least part of the CAS Arrays tied to the respective AD site but wanted to confirm this is expected behavior.
BYSAsked:
Who is Participating?
 
MAS (MVE)EE Solution GuideCommented:
Hi Ben,
When you install new Exchange2013/2016 server to an existing Exchange 2010 environment the new server will be added to CAS array by default and your client interface will be the new server. i.e. in your case Exchange2016.
0
 
RoninCommented:
The connection end-point during coexistence should be the highest Exchange version in the organization, that's MS recommendation.
0
 
Ajit SinghCommented:
Have you followed Microsoft Exchange Server Deployment Assistant ?

Try this:

Point outlook.domain.com to Exchange 2016, with DAG IP or A record in DNS which resolves to either Exchange 2016 servers. Adjust URLs for the Exchange 2010 environment to have Exchange 2016 proxy access to mailbox servers.

Get complete overview on client connectivity in an Exchange 2016 coexistence environment with Exchange 2010: https://blogs.technet.microsoft.com/exchange/2015/10/26/client-connectivity-in-an-exchange-2016-coexistence-environment-with-exchange-2010/

Exchange Server 2016 in co-existence with Exchange 2010:
https://frenchitguy.com/installing-exchange-server-2016-in-co-existence-with-exchange-2010/

Hope this helps!
0
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.

All Courses

From novice to tech pro — start learning today.