asked on Best way to setup a CAS Array in a DAG enviroment in mulitple sites
I have a client that wants us to setup a DAG enviroment for them with their exchange 2010 and they want one of the 2 servers in the dag to be at another site. My questions is what is the best way to setup the CAS Array between the 2 different sites so that in the event that the server at the main site goes down, how would the users connect or what would need to be done for them to be able to get their email now from the remote server in the DAG?
Would this involve changing of MX records possibly or whatever else?
Would this involve changing of MX records possibly or whatever else?
Exchange
Last Comment
vmich
ASKER
They are currently on exchange 2010 and we will be building them 2 new exchange 2010 servers in the DAG enviroment and migrating the users to the 2 new exchange 2010 servers.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
solved
It is for Client Access Only and should be an internal record, it does not need to resolve externally and should not be on the SSL certificate.
CAS Array's are also AD site specific. Therefore if you have two sites you would have an RPC CAS Array in each site. In the event of a failover the DNS entry would be pointed to a server in the other site. That would either be a manual change or automatic using a load balancer.
If you already have Exchange 2010 live and users on it, then implementing the CAS Array is going to also require visits to the clients. They will not use it automatically.
Simon.