View Single Post
  #1 (permalink)  
Old 03-04-2012, 01:55 PM
millardus millardus is offline
BES Administrator
 
Join Date: Oct 2009
Location: Warwickshire
Posts: 29
Default BesAdmin and ClientAccessArrays?

Hi guys

I have BES 5.0 MR3 in my environment, and have moved the BESADMIN account onto an Exchange 2010 Database. At the moment, all users are still on Exchange 2007 and BES has worked for 2 weeks for them no problem.

Tomorrow we start moving 2010 users on...I have tested activating a brand new 2010 user on it and it worked well..though at that stage we DID NOT have the ClientAccessArray setup. At that stage all 2010 DB's had a specified CAS stipulated as their *RPCClientAccessServer*.

MY QUESTION:

How does BES access its mailbox and other mailbox's in 2010? With the RPC endpoint being on the CAS now, does BES just select any 2010 CAS in the environment? OR, does it look for a *clientAccessArray* object and then send RPC requests to whatever IP address that resolves to?

Reason being, I have created a clientaccessaray and assigned it to all 2010 databases, but it has no DNS entry or IP address. The reason being that all my RPC User connections are via Outlook Anywhere (not direct MAPI), so I have set a Host file value on each internet facing CAS which resolves 127.0.0.1 to the ClientAccessArray name when an external Outlook Anywhere connection hit them. Point being, the CAS that my external Load balancer SENDS the OutlookAnywhere connection to, will be the CAS that then handles the RPC connection also.

So what I am wondering or worried about is that since creating this CASARRAY last week, will the besadmin account *know* how to connect to other 2010 user mailboxes....?

I am thinking I need to temporarily create a hostfile entry on the BES server that resolves the *clientAccessArray* to a specific CAS server....

Ta for any thoughts
Reply With Quote
Sponsored Links