Hi, what are the options for deploying multiple CAS servers, same country but in separate datacenter's in separate cities?

I thought GeoDNS might do the trick, but that seems limited to continental regions, and there doesn't appear to be many providers in NZ.

The aim is to have the following:

CAS1 - Residing in DC1 in City 1 - Companies in this City, or proximity will connect to this server as their MBX server is located in this DC as well.

CAS2 - Residing in DC2 in City 2 - Companies in this City, or proximity will connect to this server as their MBX server is located in this DC as well.

If a user in City 1 goes to City2, they will still go through CAS1 as this is the default for their site because they are only there temporarily. I think I could use Netmask ordering internally (for Citrix/RDS etc) based on origin subnet but that doesn't solve the issue for external clients.

This is a multi-tennant environment. Any ideas apprec

Hi. It's simple. Read the article and if you have any questions, then try to answer.

Namespace Planning in Exchange 2013

Client protocol connectivity flow in Exchange 2013/2010 coexistence 

Hi David,

Since session affinity is not used by the load balancer in Exchange 2013, Exchange 2013 includes a built-in monitoring solution, known as Managed Availability.

If the load balancer health probe receives a 200 status response, then the protocol is up; if the load balancer receives a different status code, then Managed Availability has marked that protocol instance down on the Client Access server. As a result, the load balancer should also consider that end point down and remove the Client Access server from the applicable load balancing pool.

More details about Load Balancing in Exchange 2013, please refer to: http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx

I think the problem is not in the Load Balance, and the in names and connection policies, as well as in understanding operation CAS services. In Exchange 2013 CAS simply proxies the user's connection to the active database. If you want the user to be connected to the new location. You have to move a mailbox in the active database in the DC / Site, where the user is localized. I see no problem in changing the point of connection of users. When the correct architecture of the network must support all users connected to the same site as this is the DR and HA.

NetMask - It is used to send and receive connectors, but not in the case of CAS. The CAS controls autodiscover and name (url) the connection.

Thanks Oleg, the requirement is for the traffic to go to the local servers, through the local connection. My understanding is if User A with mailbox in Site B connects to the external CAS FQDN in Site A, then it will be proxied over to Site B through the Datacenter to Datacenter link (WAN). Instead, I want it to go through the local Datacenter internet connection too.

Hi,

It depends on the namespace when  deploy a site-resilient solution for two datacenters as Oleg mentioned.

Here's an blog about how CAS 2013 functions, for your reference: http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx

Hi Dave,

As you said you don't have the option of GeoDNS, you need to have 2 namespaces, one for each DataCentre for it to work as you want. Use internet and not WAN.