08-21-2013 02:02 PM
We have an Exchange 2010 Environment with two sites, one CAS/HUB and one MB server at each site. Both sites are connected together with a 1.5mbps WAN link. Users on one side of the WAN are connected to a BES Express server on the same side of the WAN as them.
The problem is that when the BES installed, it chose the Exchange Client Access Server on the OTHER side of the WAN. This causes our BES to go bonkers whenever the WAN is having problems.
How can I change the "Messaging Server" for each user, and also the BES default to use the Exchange Client Access Server on the side of the WAN the BES server is on?
Solved! Go to Solution.
08-21-2013 02:27 PM
where is your BESAdmin service account located?
you might be better off having 2 BESAdmin accounts and two BES servers as if one goes down that has the BESAdmin account BES will fail. You can have one database to make things easier as BES will work for a few hour even if its down.
If the CAS array is unable to be resolved in Edit Mapi, attempt to resolve a single CAS node in the environment. If a CAS node is resolvable then as a temporary fix to get the BlackBerry Messaging Agents working create a host file with the IP of the working CAS node and the name of the array. This will cause the server to look directly at the working CAS node and start the BlackBerry Messaging Agents. This is a temporary fix in order to allow the BlackBerry Enterprise Server to work until the DNS issue with the CAS array can be resolved.
To create a host file:
1. open Computer > Windows > System32 > Drivers > etc
2. Open the files Hosts with Notepad
3. Make a entry in the file
IP of the CAS node (CAS array name)
4. Open command prompt and enter ipconfig /flushdns
5. Restart the BlackBerry Controller service
08-21-2013 02:47 PM
Well, we aren't using a CAS Array since they are seperate AD sites. Just two different CAS servers.
So you're saying the easy fix is to just put a hosts file entry in with the name of the CAS server in site 2, but with the IP of the CAS server in site 1? I didn't even think of trying that, but I think it just might work :-)
I was just thinking there was a setting somewhere to change it to a different server. I checked the MAPI profile and that is pointed to the correct server, so I was assuming it was somewhere else but couldn't find it.
Per your reccommendation on two BES Servers.....I should have specified but that's exactly what I have: one BES Server on each side of the WAN, and seperate accounts for each BES server. the accounts are located on the side of the WAN the BES server is located. I have them setup as totally seperate databases just because I didn't want WAN interference. The BES server on site 2 has absolutely no problems when there is WAN problems because of this. It's the BES server in site 1 that is pointed to the Exchange server in site 2 that is having problems during WAN problems.
thanks for your reply!
08-21-2013 03:34 PM
It's the BES server in site 1 that is pointed to the Exchange server in site 2 that is having problems during WAN problems.
Then you need to make sure its BESAdmin account is on site 1
08-22-2013 08:54 AM
I beleive the BESAdmin account was originally created at Site 2, then moved to site 1. I moved it a while ago but none of the pointers changed and the BES Server is still going to site 2. At least it was until I changed the hosts file. I guess I'll find out if that worked next time the WAN goes down
08-22-2013 11:41 AM
maybe you need to recreate the mapi profile, lets see what happens next time the WAN goes down. or maybe unplug it off hors for a test