[musy]

I have just installed this in a test enviroment using the LCS/OC option
and it removed the IM connection service and the install forced to add a OCWA server name (which we do not use) all clients cannot use IM

[BBAdmin]

You've got to love the Known Issues section where they start sentences with "Under certain circumstances".......yet they never tell you what those circumstances may be...when it's raining, if you're having a bad hair day, when the wind blows North!?!?

[musy]

Looks like some bright spark @ RIM did not make the distinction between OC clients using TLS/TCP or OC Clients using Web Access HTTP/HTTPS

[jibi]

Originally Posted by musy

Looks like some bright spark @ RIM did not make the distinction between OC clients using TLS/TCP or OC Clients using Web Access HTTP/HTTPS

I think the distinction is this:

Office Communicator = OC Web Access
Windows Messenger = OC Desktop Client

I'm very disappointed in their documentation in this regard. We've been using Office Communicator since it's early beta days (as well as LCS 2003 and LCS 2005) but we've yet to install the OCWA portion as it's not currently required for any of our projects (although I'm sure its in the short-term pipeline).

If you're using Office Communicator w/o Web Access, I'd go with the Windows Messenger installation. I'll see if I can get a bit of clarification prior, though.

[|||||||]

Originally Posted by BBAdmin

You've got to love the Known Issues section where they start sentences with "Under certain circumstances".......yet they never tell you what those circumstances may be...when it's raining, if you're having a bad hair day, when the wind blows North!?!?

That's pretty accurate. Some issues are almost impossible to reproduce.

[gjh]

Been trying to download SP2 for the whole day, it just keeps on dropping out. Any chance of someone temporary placing the file on a FTP somewhere. Don't have a t-support contract.

[BBAdmin]

It kept dropping out for me yesterday too. Having another go at it now.

[RIM_Next_Door]

I don't understand why .wav's are not supported on the 8700 via BES? It says on the support page that 8700 is a support .wav device. Very frustrating for those of us with unified messaging.

[bbmember]

Originally Posted by RIM_Next_Door

I don't understand why .wav's are not supported on the 8700 via BES? It says on the support page that 8700 is a support .wav device. Very frustrating for those of us with unified messaging.

You need device code 4.2 to get it to work. The 4.2 device code is correctly only available for 8100 (pearl). I guess its only a matter of time before they release the 4.2 code for other devices.

[Inphektion]

Originally Posted by RIM_Next_Door

I don't understand why .wav's are not supported on the 8700 via BES? It says on the support page that 8700 is a support .wav device. Very frustrating for those of us with unified messaging.

yep i'm in the same situation but luckily i have a few people on 8100's where it works.

[findmywife]

Upgraded on Thursday from 4.0 SP 4 to 4.1.2, all in one file, upgrade went fine. No IM server or MDS stuff. Worked perfectly.

[tommy.hanks]

I tried the upgrade on BES 4.1 and it keeps giving me database errors!!! Unforutnately I'm going to have to leave my complaint that vague since I can't seem to remember what the exact error was.

[musy]

try making sure that you are using windows authentication as opposed to SQL login for the SP

Quick Observation

I have a test 4.1 sp2 box with appprox 10 users, I dropped the DB's, uninstalled the BES, reinstalled etc. post adding the previous users the new install the accounts re-activated automatically without any intervention and email recon, calendar sync, lcs/em works normally

Some serious DR functionality which is not in the documentation

[marck11]

Hi,

At the moment we are using BES 4.1.1 for Exchange. Furthermore we have SQL 2000 on a separate machine. i would like to upgrade to 4.1.2.

Do I need the update the SQL tables also?

In the upgrade guide there is no info on upgrading from 4.1

Just wanna check, can;t be to careful.


Regards,
Marck

[Korbyn]

I had troubles downloading the first day, but I waiting till after business hours and had no problems downloading it then.

We installed last weekend, 520 users, no complaints. I'm very happy with this service pack, been all long time since I've had no problems. They also fixed the Error Notifications, SP1 we would get a notification but not what it was notifying us of.

Another new feature which I didn't find in the readme was that we now get notifications when a user has been added to the BES and also when their Enterprise Activation has completed. Not sure how to turn it off, but I don't think I would want to, kinda handy.

We were on BES 4.1 SP1 using a remote SQL database, no LCS or MDS installations yet, so the upgrade was pretty clean and easy. I've been waiting for the core of 4.1 to be stabilized before exploring off into the LCS world, I think I'm glad I waited...

[Korbyn]

Originally Posted by marck11

Hi,

At the moment we are using BES 4.1.1 for Exchange. Furthermore we have SQL 2000 on a separate machine. i would like to upgrade to 4.1.2.

Do I need the update the SQL tables also?

In the upgrade guide there is no info on upgrading from 4.1

Just wanna check, can;t be to careful.


Regards,
Marck

If you have just the one BES, yes, you'll want to update the SQL database. If you have multiple BES servers connecting to the same SQL database, then you need to be careful of when to update the database.

[BBAdmin]

Another new feature which I didn't find in the readme was that we now get notifications when a user has been added to the BES and also when their Enterprise Activation has completed.

Just to expand a little on this point, you get notifications when adding a new user, removing an old one, and if changing a device for an existing user as I discovered yesterday. Example test:

BlackBerry Messaging Agent - BES sever name entered here - Agent 1 (Application Event Log on BES server name) | 09/18/2006 10:15:28 (6FFFC3B6) -> [AUDIT] - User activated on the BES

I like this feature!!

[Jeeps]

A 68 page install document for a Service Pack. How special.

[adenhaan]

Originally Posted by jibi

I think the distinction is this:

Office Communicator = OC Web Access
Windows Messenger = OC Desktop Client

jibi, Your observation was spot on.... If one needs the communication between BES and LCS to be over TCP or TLS, then choose "LCS/Windows Messenger" during install of SP2. If you choose LCS/Office Communicator, then communication between BES and LCS needs to go through OCWA/AJAX.

Another piece of this puzzle: SP1 only had "lcs" IM client for handheld. SP2 has an "oc" IM client in addition to the "lcs" client.
I believe the "lcs" client in Blackberry nomenclature is referred to as "BlackBerry Instant Messaging for Microsoft Live Communications" and now in SP2 they also use "Windows Messenger" to refer to this kind of client ? The new "oc" client is probably just referred to as "Office Communicator"

Curious if anyone has screenshots / comparison of functionality between these 2 handheld clients.

Terminology.....

[x14]

RIM just posted this. I love their workaround.


Known Issues - Cannot upgrade to BlackBerry Enterprise Server 4.1 Service Pack 2
Last Updated: 22 September 2006
Article Number: KB-05537


--------------------------------------------------------------------------------

Summary
This article applies to the following:

BlackBerry® Enterprise Server software version 4.1 Service Pack 2
IBM® Lotus® Domino®
Microsoft® Exchange
Novell® GroupWise®
SDR103302


--------------------------------------------------------------------------------

Problem
You try to upgrade the BlackBerry Enterprise Server to software version 4.1 Service Pack 2 and the upgrade fails. The reason for the failure may vary (for example, the Transaction Log is full). When the original failure condition is corrected and you try to upgrade again, the BlackBerry Configuration Database upgrade fails. The DB_Install.log file displays the following:

[10000] (09/13 23:14:07.682):{0x1878} SQL Error Message from CBESDBInstaller::ExecuteSql.executeDirect: SQLSTATE: 42000 Native error: 3725 Message: The constraint 'PK_MDSConfig' is being referenced by table ' ', foreign key constraint 'FK_RelationSCMDS_MDSConfig'.
[10000] (09/13 23:14:07.682):{0x1878} SQL Error Message from CBESDBInstaller::ExecuteSql.executeDirect: SQLSTATE: 42000 Native error: 3727 Message: Could not drop constraint. See previous errors.


Workaround
Please contact your service provider.

This is a previously reported issue that has been escalated internally to our development team. No resolution time frame is currently available.