Has anyone thrown SP5a onto their BES 4.0 server yet? I'm planning on it this weekend and just wondering...

Good or Bad Service Pack?

Kman

Read the release notes and decide for yourself.This is not a HF its a SP,it has to be good.

On a semi related note is there going to be a Domino SP5?

Going by the release notes, it's looking pretty good, just curious if anyone had actually done it yet on real world production boxes. We have about 10 of the items identified as issues in our environment, but it seems with every SP, some new issue comes up. The 'a' in 5a was also a bit of a yellow flag to me so evidentally they had some sort of issue they had to quickly resolve. I have a copy of the SP5 release notes, I'll have to compare it to the SP5a release notes and see.

I haven't heard anything on a sp for Domino, but then again, I don't work with it so I don't keep mindfull of it, sorry.

Installed SP5a for BES 4.0 for Exchange this morning, so far so good, all the basics seem to still work They update the Java client too but not to v.1.5, just to 1.4_11 I think it was.

It would seem that my issue was with the MS security patch MS05-051. Our server team noticed it missing and decided to reinstall it. Once removed I haven't had any further issues with SP5a. RIM says they do have an issue with 5-051 but didn't give me any details as to their work around, I'm assuming that it's just remove it...

Now I've upgraded to 4.1 SP1, woot woot. And I'm still having an issue with the Router dll with regards to the perlib. Seems to come with both SP5a for 4.0 and for SP1 with 4.1. Still an open ticket with RIM with no ETA.

The SP5 fixes a lot of issues but there is also a HF just released for it in additon to the SP5

SP5 treats me right. It doesn't resolve an issue with IT Policy and version 4.0 devices, but c'est la frakkin' vie.

There's actually two post sp5a hotfixes now. But it doesn't look like you policy issue is fixed. I have noticed in the past when policy's don't apply to devices, there may be something actually wrong with the device. I usually nuke it, reload the OS and reactivate the user. That either fixes it, or the nuke ends up revealing that the device was toast anyway and needed to R&R'ed anyway.

Here's whats fixed in HF2:
BlackBerry Policy Service
* SDR 98602
In the BlackBerry Enterprise Server Version 4.0 SP5 for Microsoft Exchange, if the BlackBerry Enterprise Server detected changes to the BlackBerry Device Capabilities for BlackBerry devices with BlackBerry Device Software earlier than Version 4.0, IT policies were delivered to the BlackBerry devices continuously.
In BlackBerry Enterprise Server Version 4.0 SP5 HF2 and later for Microsoft Exchange, if the BlackBerry Enterprise Server detects changes to the BlackBerry Device Capabilities for BlackBerry devices with BlackBerry Device Software earlier than Version 4.0, IT policies are not delivered to the BlackBerry devices continuously.
BlackBerry MDS Services

SDR 93346
In the BlackBerry Enterprise Server Version 4.0 SP5 for Microsoft Exchange, you could not retrieve the status of a certificate from an external HTTP based Certificate Revocation List (CRL) on the BlackBerry device, and the "Internal Proxy Provider Error" message appeared.
In BlackBerry Enterprise Server Version 4.0 SP5 HF1 and later for Microsoft Exchange, you can retrieve the status of a certificate from an external HTTP based CRL.
Wireless calendar synchronization

SDR 88504
In the BlackBerry Enterprise Server Version 4.0 SP5 for Microsoft Exchange, if a meeting organizer sent a meeting invitation to a large number of individual invitees, this might have caused high CPU usage and the BlackBerry Enterprise Server stopped responding.
In BlackBerry Enterprise Server Version 4.0 SP5 HF1 and later for Microsoft Exchange, the BlackBerry Enterprise Server allows meetings that have a large number of invitees to be sent successfully.