Exchange 2010 CAS Arrays are a great high availability feature, but are organizations making the best use of them?
One of the best practices when deploying Client Access Server Arrays is to establish the CAS Array first before configuring mailbox databases in the same site. Or at the very least, making sure you update each existing mailbox database with the correct “RPCClientAccessServer” attribute before migrating users to them.
The advantage of this is that Outlook profiles get automatically configured with the name of the CAS Array rather than the real name of a Client Access server in that site.
Considering the benefits of this, such as:
- making it easy to scale out the CAS Array name to multiple Exchange 2010 Client Access servers
- making it simpler to replace a Client Access server with a new one of a different name
- migrating the MAPI endpoint to future versions of Exchange Server
…does it make it a sensible best practice to always configure CAS Arrays for AD Sites that contain Exchange 2010 mailbox servers, even when only one Client Access server is deployed?
Update: Microsoft now recommends that you always create a CAS Array in each site, even if you have only one Client Access server in the site.
Please give your opinion by voting in this poll. If you wish to expand on your vote in more detail please leave a comment below.
Should all Exchange 2010 sites have CAS arrays?
- Yes (82%, 95 Votes)
- No (18%, 21 Votes)
Total Voters: 116