The CAS array is apparently just an AD object that tells internal Outlook clients where to find CAS servers. If you don't create one at Exchange 2010 installation, one is created for you with the fqdn of your mailbox server. The issue is down the line (like now, for me) when you want to move mailboxes to a new server in order to decommission the old one. Outlook doesn't update and each user profile has to be reconfigured either manually or via pushing a prf file. (I may have some of the description not quite right, but that's the gist of it.) I figure it's better to fix the problem now rather than leave it to the next person to figure out.
On Wed, Feb 25, 2015 at 3:37 PM, Steve Ens <[email protected]> wrote: > I dunno Richie, do you really need an array for 100 users? I have a > single server virtualized. Never any problems with client access. > > On Wed, Feb 25, 2015 at 2:29 PM, Richard Stovall <[email protected]> > wrote: > >> I will soon be moving Exchange 2010 to new hardware (or maybe virtual >> hardware, but that's another question). >> >> I have a single server with fewer than 100 users spread across two AD >> sites. Of course I did not create a CAS array all those years ago, so I am >> preparing to deal with the ramifications of that now. >> >> Currently all mailboxes are (obviously) hosted on one server in one of >> the sites, but that may change in the future if we grow, add data center >> capacity, whatever. >> >> Given the need to create a CAS array now, should I create a single >> site-specific array for each site? Can an array for site 2 specify an ip >> in site 1? If not, should I create a single array and not specify the site? >> >> Thanks for the help, >> >> Richard >> > >
