Hi,

Would just like some thoughts, we currently have a multi exchange box domain, at the moment we are having frequent blocked worker thread related issues. This we suspect is mainly down to latency between out location (we have our own Exchange box onsite) and Head Office where the BES is located.
To resolve this issue we would like to install our own onsite BES but have been warned off this as suposedly it can cause issues.
Basically is this correct, to me it seems a bit silly that this cant be achieved when I have read that latency should be no more than 50ms.
Thoughts/advice more than welcome.

THanks

I always keep Exchange and BES servers in the same locale and have come across issues where ping times are 75ms. RIM will say pings south of 100ms will be fatal, but that really depends on how many users, etc. At the end of the day they have recommendations for a good reason, so I always advise people to stick to them. I can't imagine why anyone would be suggesting you'll have issues by keeping BES and Exchange together when clearly it makes sound sense to anyone familiar with the platform - what issues were they suggesting you would experience??

You need to work with someone on this that can suggest a plan of action to load balance your BES infrastructure for you, which actually isn't complicated. At my company one of our BlackBerry clients had a similar problem where through simple expansion they suddenly realised they were having latency headaches across about 3 European sites. We looked at their locations, Exchange sites, BES sites, ping times across all these components and devised a strategy for moving users around and setting up additional BES servers on a couple of the sites, and they've not looked back since - in fact I think we wrote a white paper on it afterwards!

__________________
Si MCTS
Co-Owner
Port3101 - Your BES Connection

Don't forget, you can follow us on Twitter

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

My experience is that the WAN latency shouldn't be higher then 35-40ms. With everything higher, BES will not work reliably. The latency from BES to SQL can be much higher, around 150-200ms. So your planned configuration with the BES local to the Exchange server is the way to go. By using the central SQL your migration from the remote to the local BES will be very straight forward with a "move user" within the Blackberry console.

For some more informations, have a look at View Document.

__________________

Thanks for the replies, I think I could have worded it a bit better!
In essence the question is can you have problems having a single domain with multiple Exchange servers on multiple sites with those sites having a BES in their locale.
We have been advised against this as it supposedly can cause issues, this advice has come second hand from a BES Consultant. But it just seems weird to me.

Thanks again!

Edit* I did try to look at the link but it failed.

Sorry, there was a typo in the link. I have updated my previous post.

__________________

No, you will have less issues. I am running similiar configurations (10+ sites and 10+ BES servers and SQL in a central location). Having the BES local to the Exchange server always makes everything working better. The SQL server can be remote over the WAN and won't cause any issues as the latency isn't too high. At the beginning (a few years ago) we had the BES in the central location and accessed the Exchange mailboxes remotely over the WAN, that caused alot of problems. After doing the migration to local BES, the problems were gone.

__________________

Thanks for the replies, link is exactly what I have been looking for.

Fine, if you have further questions, don't hesitate to ask

__________________

Sorry to wake this thread up.

But In line of this topic I have a few specific questions.

First a backgrounder:
We have one central BES (single BB Domain)
We have one central SQL DB on or BES (same server)
We have one BES service account
We have more than 40+ Exchange servers scattered worldwide.
latency ranges from BES to the Exchange servers ranges from 10ms (same site) to 1000ms (yes one thousand )

What I would like to know is that, what are the best scenarios for our case?

Would it be helpful if we have several service account hosted in each of the 40+ exchange servers?

Or would it be feasible to install one BES per site (locale)?

How many users total?

400+ users (and counting)

I might go the BES route at each location then. If cost is an issue, then use BES Express.

We are planning on moving all BB user's mailbox to an Exchange server located on the same subnet as the primary BES, since we are on native mode in Exchange we can move mailboxes around without problems..

You think this is a feasible solution?

PS: As I write this I am having problems with all the users located on a remote Exchange server with 200+ ms of latency between the BES...and to think this is one of our better latencies.. (the offsite Exchange is in Haiti and users are using DIGICEL)