Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 242
  • Last Modified:

CAS array name not changing automatically

Hi,

I have exchange 2010 with 2 CAS server's and 10 databases, 5 database rpcclientaccessserver is cas01 and for another 5 database it is cas02.  Now I created cas array call cas.domain.com.

and updated the RPCClientAccessServer attribute for a mailbox database to new cas array name. But when user opens their outlook, it still shows connection to the cas01 or cas02, it is not changing automatically. But If I configured new outlook profile, it automatically takes cas.domain.com name.

How to resolve the users already configured outlook

thanks
0
kolathaya123
Asked:
kolathaya123
1 Solution
 
basil2912Commented:
Hello,

Except reparing the profiles/deploying a GPO not much can be done, the RPC Client access server is coded in the OST after clients are connecting.

Article http://blogs.technet.com/b/exchange/archive/2012/03/23/demystifying-the-cas-array-object-part-1.aspx explains more on CAS array

From: http://technet.microsoft.com/en-us/magazine/ff626260.aspx

"I’d advise you to create the CAS array before you make any Mailbox databases or move any mailboxes to an Exchange 2010 Mailbox server in a site. Exchange 2010 Mailbox databases have an attribute called RpcClientAccessServer. If there’s no CAS array in the Active Directory site when the database is created, this will be populated with the server FQDN of an Exchange 2010 CAS server in the Active Directory site. If you create the CAS array before any Mailbox databases, this attribute will instead be given the FQDN of the CAS array as shown in Figure 2."

And also:

"Why is this a good idea? The Outlook client (whether Outlook 2003, 2007 or 2010) won’t pick up the change automatically. If you use Outlook 2007 or 2010, you can have the profile updated by making the old RPC endpoint unavailable or by performing profile repair. But Outlook 2003 can’t change the endpoint and doesn’t include a profile repair feature. That forces you to go in and manually change the profile by removing the username, adding it back and then clicking the “Check name” button). This isn’t ideal by itself, and it also involves end users, so you really should create the CAS array beforehand."

Even not strictly enforced it is not done most of the times, therefore the only options are as I've mentioned above.
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now