A problematic messaging agent is the bane of any BES Administrator. I've previously blogged about implementing / tweaking the NumAgents and MaxUsersPerAgent registry keys ... well I've got one more for you. These tweaks are great if you've got a BES communicating with several Exchange servers and want to ensure that you have at least a single messaging agent for each server, or if you've got a heavily loaded BES and want additional agents to further spread out the load, but what if you've got a...

I see this time and time again ... A single BES with users from 20+ Exchange servers. One Exchange server has poor performance and instantly 20% of all BES users experience message delays, and all of their mailboxes are in a constant state of RESCAN instead of messages being delivered by UDP NOTIFY.

In addition, you notice errors in the MAGT, ALRT, and then the CTRL log indicating that it has restarted a given agent a maximum amount of times within 24 hours and it will not restart:...