Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Welcome back! In Demystifying the CAS Array Object - Part 1 we covered these three items to begin demystifying the CAS array object in Exchange Server 2010.
- A CAS array object does not load balance your traffic
- A CAS array object does not service OWA, ECP, EWS, Autodiscover, IMAP, SMTP, or POP
- A CAS array object does not need to be part of your SSL certificate
Here in Part 2 we will cover the following three items, and once and for all lift the fog away from the CAS array object to help you correct existing deployments and/or plan more strategically for future deployments.
- A CAS array object should not be resolvable via DNS by external clients
- A CAS array object should not be configured or changed after creating Exchange Server 2010 mailbox databases and moving mailboxes into the databases
- A CAS array object should be configured even if you only have one CAS or a single multi-role server.
Read the complete blog at https://blogs.technet.com/b/exchange/archive/2012/03/28/demystifying-the-cas-array-object-part-2.aspx
Read my favorites blogs:
Designing a backup less Exchange 2010 Architecture
Microsoft Exchange 2010 CAS Array – Steps and Recommendations
Appear Offline in Microsoft Office Communicator Server 2007