Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

do i need a CAS server per AD site?

$
0
0

Hi!

So I have been browsing through a lot of Exchange Server documentation, guides and best practice but I have not found (or misunderstanding) the CAS placement for my situation.

We are currently in the process of upgrading to Exchange server 2013. As we have an Exchange 2003 only deployment, we will first need to move to Exchange 2010 and get rid of all the Exchange 2003 servers and then move on to Exchange 2013. We have a single domain with 21 AD sites. 8 of these sites (Vessels at Sea) are connected by vSat the other 13 of these sites a remote offices with a more stable connection than vSat.

We want to have a MBX server at every site and what I get from the available documentation on the internet I will also need a HUB server per AD site. What I am not sure about is, do I also need a CAS server per site? What I get from this excerpt:"A new service was introduced with Exchange Server 2010 to allow these MAPI connections to be handled by the Client Access server. The RPC Client Access service provides data access through a single, common path of the Client Access server, with the exception of public folder requests, which are still made directly to the Mailbox server. This change applies business logic to clients more consistently, and provides a better client experience when failover occurs." (ref Understanding RPC Client Access.), is that I also need a CAS server per site.

Can somebody give me any definite insights in this one?

To summarize the question:
In a multi site AD with a MBX server per site, do I also need a CAS server per site?

Your help is much appreciated!

Regards,

Erik


Viewing all articles
Browse latest Browse all 7129

Trending Articles