[hb88xx]

What are your experiences with SP from RIM?

I hoped that a service pack would solve known issues and expected it regression tested thoroughly.

But SP3 disapointed me.
-Basic features like agenda synch failed, waiting for a hotfix to be released this week.
-It adds new features that needs to be patched in the registry to stay like before, with documentation typos, and did not work.

============
We have discovered that there is a spelling error in the release notes that are bundled with the software regarding the registry key (should be EmbeddedMessages not Embedded Message). The correct instructions are as follows:

1.On the computer on which you host the BlackBerry Enterprise Server, start the Registry Editor.

2.In the left pane, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents.

3.Create a new DWORD value called DisableEmbeddedMessages.

4.Right-click the DisableEmbeddedMessages value, and click Modify.

5.Set the value to 0.

6.Click OK.

7.On the computer on which you host the BlackBerry Enterprise Server, in the Services window, restart the BlackBerry Controller service.

(SDR 117007)
=================

[hb88xx]

Agenda fixed by HF2!!
Still unbeleivable they broke it and released it.

[BBAdmin]

Thread moved to GW section.

[Legros]

We are still in the debate here to decide if we move from our beloved and extra stable 4.0sp5 to the new feature (messenger, role base access on the BES, etc) but somehow less stable 4.1. I was hoping that sp3 would clear the last fear of instability but seems not..?

[dropscience]

Here's my experience with BES v4.1.3 Hotfix 2:

1) Filters - Create a filter for a user, on the server, which restricts which emails are allowed redirection to handheld. Once the filter is applied to the handheld it automatically changes the condition from "No" to "Yes". The "Yes" needs to be manually changed to "No" on the handheld in order for the filter work correctly.

RIM T-Support: Known issue that will be addressed in the next Hotfix.

2) Address Book Synchronization - Assign an address book for a user, on the server. Let the address book synchronize to the handheld.

Disable address book synchronization. Clear the address book entries on the handheld through DTM.

Wait 4 hours (specific for GroupWise System Synchronization/Update)

Assign the user to a new GroupWise address book, on the server, and re-enable synchronization. Either two things will happen: a) You will not get an address book synched/pushed down to your handheld b) You will receive an address book but it will be the OLD address book that you were synchronized to previously.

RIM T-Support: Known issue that involves the Synchronization Service not picking up the new information. Currently have a call with 2nd level escalation to investigate this issue.

... and that's my experiences so far with v4.1.3 Hotfix 2!

[Legros]

Woah... The address book problem seems to be kinda common since i saw that from the start of 4.1 ... I was hoping that sp3 solves these issue.

Thanks again for the reply.

[dropscience]

There's more, but this may not apply to your particular environment. It's with regards to our Firewall and how BES v4.1.3 is apparently more strict with the amount of X-headers is appended to EA activation emails. As a result, we are unable to Wirelessly Enterprise Activate with v4.1.3 consistently. We can still do this with v4.0.3 though.

[James_acc]

Hmm.. now i'm worried.

Were running 4.1.2.25 & Groupwise 7.1, for some reason if the BES is rebooted, when i comes up, is say's that the Groupwise service has failed to start (although when you look in services it has). The upsot of this is, no emails are forwarded for a good couple of hours!

We have been advised to upgrade to service pack 3, but after reading this im wary!

[THafemann]

Here, with my first experience with BES, I ran into ALL of these problems. I got on the phone with Tech Support and they helped me get them working, kinda.

As far as the activation, you hit it right on the head! It took us 5 hours to get our devices to activate after wiping the devices several time, rubbing our bellies and scratching our heads.

The address book thing still gets me. We originally had it setup for SOAP but on my first experience with tech support, I got kicked in the head with, "Didn't you read the readme?" Somewhere in the mound of readme's after the 4.1.3 sp3 install document and the online Webcast on how to install it (where they tell you to use SOAP) there is a document that says to not use SOAP. Hum...I must have missed that one.

Anyway, I did get a helpful chap today who gave me the mysterious unknown install document for Groupwise Messenger. It isn't as simple as Installing it. there is a bit of config needed, although pretty simple. And best of all, IT REALLY WORKS.

That's my 2 cents.

Tom

[earny99]

I would at least wait until the next hotfix but who knows what will break in the next hotfix/SP. Only positive thing out of SP3 is that message flow recovers quickly after the controller is restarted. Seems like hung threads occur more than 4.1.2. but they are blaming it on a groupwise defect. It broke address book sync for users who were syncing to shared address books. Anyone try rolling it back to 4.1.2?

[dropscience]

^ I didn't "roll back" perse to 4.1.2 but we are running 4.1.2 in a test environment now. the entire 4.1.3 platform has been abandoned as it's been deemed too buggy for us. wiped that server and put 4.1.2 hotfix 3 on. currently feature testing before production rollout and all seems well... so far.

[THafemann]

Hey there,

This was my first experience with BES so I got them on the phone to help me install it. So, guess what I got? The latest, and not so greatest thing in BES. Roll back you say? I am not sure I know what I did in the first place to be able to roll back

I went through the "Installing BES for Groupwise...." webcast which is almost a year out of date, and the install documentation is so (Magoo) full of good informaton, all but how to actually install. I wonder truely, how many environments are going to dedicate 2 or more servers to a BES, let alone the 4-10 servers they say you 'can' use.

We are somewhat small and I can only see having about 10-20 users having a Blackberry in the next 2 years.

Tom

[hb88xx]

in the EOL chart you can see when next version is coming up and that they will force you to go version 4.1 next year!!

BlackBerry

Product Name and Version General Availability Support End Date Sales End Date
BlackBerry Enterprise Server v4.1.2 for Novell GroupWise Available TBD TBD
BlackBerry Enterprise Server v4.1 for Novell GroupWise Available TBD TBD
BlackBerry Enterprise Server v4.0.6 for Novell GroupWise Available Jan 31, 2008 Mar 31, 2007
BlackBerry Enterprise Server v4.0 for Novell GroupWise Available Jan 31, 2008 Mar 31, 2007
BlackBerry Enterprise Server v4.1.4 for Novell GroupWise Sep 27, 2007 TBD TBD

[hb88xx]

Originally Posted by Legros

We are still in the debate here to decide if we move from our beloved and extra stable 4.0sp5 to the new feature (messenger, role base access on the BES, etc) but somehow less stable 4.1. I was hoping that sp3 would clear the last fear of instability but seems not..?

We came from 4.0.3. Maybe if we go virtualize BES I will create two of them. one 4.0 image and one 4.1 image. Maybe they even can co exist next to each other?

[eganders]

I've been wondering when 4.1.4 will come out. Thanks for the info.