[Mikey-AGBoston]

W'bar,
Have you tried adding a couple of users to a static agent, and if so what were your findings?

[wunderbar]

the static agent worked fine for a couple of days, but the issues returned after that. I then added users that were in one static agent to another, and they worked fine for a couple of days, and the issues returned again.

My favourite is that whenever I want to activate a device, I have to move a user to a new static agent first before the device will activate. It's so much fun.

[kjarrodc]

KB17325-Issues with the BlackBerry Enterprise Server in a Windows Server 2008 based Microsoft Active Directory environment

If you've got any 2008 domain controllers, check out this KB article.

Easiest way to identify if you're affected by this issue is to change the registry settings as instructed in the KB on your DC's. Watch the logs for a few minutes, and it'll confirm you've got the issue.

We were affected by the issue and it was very difficult to troubleshoot because our symptoms didn't match what the KB describes. However, increasing the number of NSPI connections immediately resolved the issue.

[Mikey-AGBoston]

RU3 announced - possible related BES fix

How it applies:
As I understand 'it'

1.Message received in user mailbox
2.A UDP notification message is sent to the Blackberry Agent process handling the user
3.Message gets received on device

If anything keeps that UDP packet from getting to the agent (high network traffic or a million other reasons) the BES scans the users mailbox every 20 minutes for missed messages and then delivers them to the device which is why RIM is notorious for saying 10-20 minute delays are normal. RIM wonxxx8217;t guarantee the immediate delivery due to the limitations of the UDP protocol

This is why when the BES xxx8211; Exchange connection is optimal we see near immediate delivery and when periods of high use (ie. Business hours) we are more likely to see the delays of up to 20 minutes.
That said, Microsoft announced:
UDP Notification Support Re-added to Exchange 2010 for Roll-Up 3 (SP1 RU3)
(( I would post a link to the article, but I am prohibited from doing so, due to few than 10 posts, here ))

[wunderbar]

That's all well and good, but with an expected release date in March, that is waaaay too long for a possible fix.

The issue is so maddening too. My blackberry has been fine today, but others haven't.

[wunderbar]

Let me rephrase. I can work around it until March, but this is really frustrating.

The only thing that seems to be working for me is moving users to different static agents when mail delivery becomes a problem for them. I can literally move a user from one static agent into another and it begins to work immediately, and will work well for anywhere from 2-5 days, and then it starts to slow down again.

I only have 45 users, so I can live with having people call/email me when their email starts to get bad again and I can move them to a different agent. But it's just going to require a lot of babysitting until it can be fixed.

[kjarrodc]

Can you all confirm whether you're seeing similar issues with Outlook 2003?

In Outlook 2003, e-mail messages take a long time to send and receive when you use an Exchange 2010 mailbox

Also - Here's a link that I believe Mikey intended to post:

http://msexchangeteam.com/archive/20...28/457845.aspx

[BESMstr]

I agree with kjarrodc, we had the same issue plus user's getting a red x when trying to send external email.

Bouncing the Dispatcher was a temporary fix but increasing the NSPI limit from the new default for Win 2k8 Svr of "50" to 2,000 has resolved these issues.

With the default NSPI limit, the first 50 users served are just fine, user 51 on though, can't get an exit.

--BesMstr

[Mikey-AGBoston]

This wins, if your Domain Controllers are on 2008...

[wunderbar]

we have a domain controller on 2008 R2. I tried the fix, it's made the problem a little better, but not resolved.

We've also been seeing the Red X problem, as well as having difficulties getting new devices activated. March can't come fast enough.....

[knottyrope]

please sign up for the webcast

Mitigating potential messaging delays:
BlackBerry and the Microsoft Exchange Server 2010


Lobby

[jbrassQuest]

We have the same issues, RIm support is aware of this issue. It's a software design issue between BES 5.02 for Exchange and Exchange 2010. I have had this issue for about a month now. Some devices even stop receiving messages altogether, untill the Blackberry controller is restarted. I opened a ticket with MS as per RIMS request, I just need to know when this is going to be fixed.

so far I applied these bandaids, and still no love:
enabled 10 agents ber BES server
KB22812 Intermittent mail delivery issues via Load balancerenabled LDAP lookup
KB03193 enable ldap
KB20157 ews Calander helper


John Quest Software.

For more info, go to the Blackberry communities forum, and you'll see many other companies have the same issue.

[MattT123456]

Ok, so it's too early in the game to get too excited about the recent development we've had, but being that delay seems to have disappeared, we're pretty hopeful.

A few things have happened in the last 10 days or so:
--February 28, 2011 - BES has released MR4 for BES 5.0.2 (you still need to do the supplimental fix in addition to MR4 which fixes 3 dll files)

--February 25, 2011 - Microsoft has released CDO 6.5.8211.0, which needs to go on your blackberry servers (and we put it on our client access server for Exchange as well).

--February 28, 2011 - Blackberry has released a technical note called: "Managing The Blackberry Enterprise Server Performance in a Microsoft Exchange 2010 Environment" (you can get here by going to the blackberry documentation area, under documentation for administrators, it's the latest note - I can't post links on this forum, otherwise I would link it).

Inside this last document, it talks about setting up direct LDAP queries to active directory to prevent these queries being made through MAPI (amongst other things like the CDO upgrade). Well, we implemented this last night and so far, all the delays seem to have vanished (though we're going to get a regular day test today, so we're not out of the woods yet). You can get more information on this through Blackberry KB article 03193 (we didn't do the SSL connection one as indicated and it still works ok).

I'll be sure to update everyone as we get more feedback, but again, so far so good.

Our topology (all running on vSphere 4.1):
Exchange 2010 SP1 (no update rollup) Mailbox Servers
Exchange 2010 SP1 (no update rollup) CAS array (there is a hardware load balancer on this array, but BES has a host file entry to always just hit the 1st CAS server in the site)
BES 5.0.2 MR4 + Interm Security Fix deployed in an HA configuration

[wunderbar]

I applied the updates to our environment last night as well, it'll be a few days before I know whether it really worked. Aside from the fact that it was a pain in the ass to do the MAPI, MR4, and the interm security release at one time it went smoothly.

[MikeyAGBoston]

I have updated with MR4, and the new MAPI/CDO (..yes, and the PDF security patch).
So far, deliveries to the handhelds are running close to the minute of actual reception, and have been for the past three hours.
(we have 380+ users)

I am optimistic - Stay tuned

[MikeyAGBoston]

Marked Improvement
My deliveries have gone from batches of emails, delivered in 15 minutes intervals... to delays of zero to three minutes of the originating time stamp.

[MisterGriffiths]

Anyone experienced this yet or know under what conditions it can occur?

Exchange 2010 SP1 Rollup 3 and BlackBerrys sending duplicate messages - Exchange Team Blog - Site Home - TechNet Blogs

[MikeyAGBoston]

I still have a handful of users complaining about delays, while some of us have seen the delays nearly disappear. Have people out there also jacked up the CAS/Mailbox servers memory and then seen much improvement?

[wunderbar]

Well, about 10 days after applying the MR4 upgrade, and the new MAPI/CDO, everything seems to be working pretty much perfectly for us. I'm back to hearing my blackberry buzz before I even see the message in outlook.

We haven't even applied SP1 RU3 yet.

[MikeyAGBoston]

OK - we encountered our first issue.
Activations.
Has any tried to conduct an activation since the upgrade to MR4 (w/new MAPI+CDO)?