Hopefully a quick solution for someone. We are planning the following:
- 2x CAS/HUB combined servers in a CAS array
- 2x Mailbox servers in DAG
- All running Exchange 2010 SP2
The following namespaces are planned:
- Internal and External domains have the same domain name (lets use domain.com)
- The CAS array is outlook.domain.com
- OWA, ECP, etc will be on webmail.domain.com
- Internal and external clients will pass through a hardware load balancer (Netscaler)
Now the questions:
- By default, the external domain is set to webmail.domain.com for all services in 2010 when you install them which is OK
- The internal domain picks up the individual CAS server names and not the CAS array
- Should the internal domain URLs be the load balancer CAS address - ie outlook.domain.com or should they be webmail.domain.com or should they be left at the default of single server names?
I believe the following is required:
- I believe the CAS array does not require an SSL certificate because Outlook clients do not connect over 443 so we are not planning on purchasingoutlook.domain.com on the SSL cert
- Therefore due to clients connecting internally via the load balancer, all the internal URLs should be set towebmail.domain.com to match the external addresses?
- Or should only the OWA and ECP values be webmail.domain.com and the rest of the URLs set toautodiscover.domain.com?
- I am not 100% sure on the above, however, so maybe it should be the CAS array, but then internal clients would get a certificate error because outlook.domain.com is not on the cert for OWA
As far as I understand the CAS array value just sets the rpcclientaccess value for mailbox databases and no services apart from Outlook should use it? I read that in an article about common misconceptions - ie that CAS arrays are for Outlook connections only and not used for load balancing?