CAS array on different network

CAS Arrays are AD site specific.

So while you could have a single CAS Array across two sites (not advised though), if you have them in separate AD sites then you cannot have them in the same array.

This is a good thing, as it allows you to control where the traffic goes. Autodiscover is also AD site aware.

Simon.

Got it.

Here is my problem though.  I point the webmail to specific server located in Network A.  When the databases moved to another site for some reason to network B;  I have a CAS box in that location.  That takes care of my Outlook users.  They get a message on Outlook that they need to relaunch and all is well.  But my Webmail goes down because it is pointing to specific server on Network A.  I have to go manually change the IP address of Webmail to get it working again.  I really don't want to do that and I don't know how to solve this issue.

If you have mailboxes in Site A and you failover to Site B, then you need to ensure that the CAS role holder in Site B does NOT have an external URL configured.
That way CAS will proxy the traffic.
If you do have an external URL configured it needs to be different to the main server. Exchange will then redirect the users.

You need to look at the proxy/redirection TechNet Article to get the configuration correct.

The CAS Array address should be unique to the CAS Array and used internally only. It is only for Outlook MAPI traffic.

Simon.

Thanks I will look into this.  I let you know if something comes up.

Hi Simon,

What if my CAS box on site A goes down completely which holds the external URL.  All users are in site B now and they all point to Site 2 CAS box which does not have external URL configured, how the users are going to get to Webmail?