Port3101.org : Your BES Connection

Port3101.org : Your BES Connection (http://www.port3101.org/)
-   Port 3101: The BES Admin Bar & Grill (http://www.port3101.org/port-3101-bes-admin-bar-grill/)
-   -   BesAdmin and ClientAccessArrays? (http://www.port3101.org/port-3101-bes-admin-bar-grill/2636-besadmin-clientaccessarrays.html)

millardus 03-04-2012 01:55 PM

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*.


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 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

PSCArmstrSM 03-30-2012 03:36 PM

RIM's recommendations...
BES has proven to have difficulty connecting to CAS Arrays that are behind HLB's, so RIM has told us to have a host entry on all BES servers pointing the CAS name to a single CAS member's IP...

Quote: mymail.mycompany.com
The alternative is to tweak the TTL on the HLB to allow the BES to maintain a connection...

I think this is what you will need to do for your issue as well...

bb_paws 06-02-2012 09:57 PM

It's probably too late now but you could have tested this by adding a new user to Exchange 2010 to see what mail server it retrieved for the user. My guess is that it pulled the CAS array fqdm.

In Exchange 2010 environments, the BES will point to the CAS array to access mailboxes. After moving a mailbox to Exchange 2010, ScanGAL should see the move within 12 minutes and start pulling from the new location.

In Exchange 2010 environments, the GC the BES uses is the CAS array fqdm. If the LB is pointing to a CAS in the array that is having issues, you can use the host file to point this to another CAS. I don't recommend pointing to a specific CAS.

You may want to consider changing the messaging agent algorithm if you only have one CAS host name in your Exchange 2010 environment. The default Complex algorithm used by the messaging agent doesn't efficiently use all available resources. You should change to the Simple algorithm via a registry key.

All times are GMT -4. The time now is 07:45 PM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.

SEO by vBSEO 3.3.2 PL2