[knottyrope]

Originally Posted by SmoothRunnings

Will this update work on BPS 4.1.4??

Andrew

It is for BES not BPS.

[audit]

Originally Posted by knottyrope

It is for BES not BPS or express.

Uh yes it does work for Express.

[SmoothRunnings]

Originally Posted by audit

Uh yes it does work for Express.

So how do I know if it will work with BPS?

Andrew

[knottyrope]

Originally Posted by audit

Uh yes it does work for Express.

well I stand corrected then

[knottyrope]

Making the Jump in 5 min.
Doin it now
Could not delete a service rebooting now?

[knottyrope]

OK looks like all is working, HTML email working as well. (yes I upgraded to OS 4.5)

Time to monitor and check into more HH OS Upgrades.

[Tailor]

Won't allow an update on BPS, asks for a key to upgrade to BES.
Chuffing annoying as now we are 2 service packs behind!

[knottyrope]

I know your pain, we were on BPS before, but BPS is a limited version of BES.

[VizioNy]

is it possible to OTA a new O/S to each handheld from the BES server?

[penguin3107]

Originally Posted by VizioNy

is it possible to OTA a new O/S to each handheld from the BES server?

Not yet.

[knottyrope]

Hope fully soon when all devices are at 4.5 OS level.

[knottyrope]

Bumpity Bump

[blueshockeynut]

Wish RIM and/or Novell would get on the ball and release 4.1.6 for Groupwise already.....

B

[m4ilm4n]

Installed SP4.1.6 on our BES, which also hosts Sametime (I know, an unsupported config - I have to make do with what little hardware I get). Anyway, the SP4.1.6 install breaks SameTime server - leaves it in an unusable state. The web conferencing server still works, even though the install changed the Domino web service port from 80 to 8088 without telling me. However, Sametime clients - including BB ones - cannot log in to the ST server.

My solution - I'd rather have a dead SameTime server than a vulnerable BES. If management wants SameTime back, they'll have to pony up a new server for it.

[knottyrope]

Thats a kewl way to hopefully get new hardware.
I wish you luck.

[knottyrope]

Originally Posted by m4ilm4n

My solution - I'd rather have a dead SameTime server than a vulnerable BES. If management wants SameTime back, they'll have to pony up a new server for it.

Did you get the new server or find a workaround?

[DarthBBerry]

Originally Posted by m4ilm4n

Installed SP4.1.6 on our BES, which also hosts Sametime (I know, an unsupported config - I have to make do with what little hardware I get). Anyway, the SP4.1.6 install breaks SameTime server - leaves it in an unusable state. The web conferencing server still works, even though the install changed the Domino web service port from 80 to 8088 without telling me. However, Sametime clients - including BB ones - cannot log in to the ST server.

My solution - I'd rather have a dead SameTime server than a vulnerable BES. If management wants SameTime back, they'll have to pony up a new server for it.

So lemme make sure I got this right.... 4.1.6 broke your ST server as it was on the same box as the BES.
Anybody have ST issues after upgrading to 41.6 with ST being on a separate box?

[shashinp5]

Just upgraded to 4.1.6 but all of our devices are still on 4.0-4.2. Where the heck do I get 4.5? I don't see it on Sprint or T-Mobile's site.

[hansenc]

Why is BPS not supported? Whats the difference between BPS and Express? I thought BPS was Express just renamed but it looks like they removed a lot of features.

[m4ilm4n]

Originally Posted by knottyrope

Did you get the new server or find a workaround?

Since I have a Domino Express license (which lets me put Domino on any number of servers as long as I don't use clustering or failover - or so my sales rep says), I found (read "stole from another group") an available server to run SameTime on. I had no Win2K3 Server license available, but no worries - I installed CentOS 5 (repackaged RedHat ES 5), installed Domino for Linux, and prepared to install SameTime 8 for Linux.

Lo and behold, the SameTime for Linux install crapped out with a "This software is incompatible with this operating system" error. Yes, Sametime Linux would not install on Linux. Go figure. After some serious Googling, the workaround for that was to "export SkipOSCheck=true" before starting the install. Worked like a charm. It turns out the install checks the /etc/redhat-release file, so I could have changed the text there just as well.

So now I have SameTime 8 on a CentOS 5 server running Domino 8.0.1. It took a while to get the address book replication working properly, and I had to dig thru the BES Manager menus to find the spot to change the SameTime host name, but we're back on the air. Now I'm working on distributing OS4.5 to the handhelds.

Oh - one other thing I noticed specific to Domino and BES. Our NOC sends out status messages to BlackBerries and cell phones (via SMS). I noticed that after the upgrade to SP4.1.6, some messages were not handled by the BES properly (users got the same red failure message as they got when I shut off PDF processing).

Turns out the error was caused by two new users in the NOC having their Notes database design at v8.0.1, where everyone else's design was still at 7.0.2. The upgraded nsf design impacted the memo template used for the notices, turning the ones destined for BBs into HTML mail and the ones going to cell phones into MMS instead of SMS. It took the better part of five days to figure that mess out.