[JPenrose]

Hi,

So, I've read quite a few posts here and elsewhere concerning upgrades of a BES from 4.0 to 4.1 (and some of the horror stories that go with it).

Not to beat a dead horse but some of the tales and advise are quite old so I'm asking for some experience based advice for our (seemingly simple) upgrade from anyone that's done one recently.

Exchange 2003 SP1 on Windows Server 2003 SP1
Dedicated BES server on Win2K3 SP1 using MSDE

Currently on BES 4.0.5
Moving to 4.1.5 [direct d/l from RIM via carrier link]

My biggest concern is the DB update and the possibility of drama with the Send As: permissions (AdminDSHolder). The Send As: issue was mitigated during our DST updates last year so I can't imagine that a straight forward product and DB upgrade would affect that agian but I'm here asking anyway.

My plan is to do my backups, execute the update, reboot the box, let the DB upgrade complete, verify that all the BES services are running and test.

I've read posts that say it's a no-brainer and posts that detail horror and pain.

Advise and guidelines are much appreciated.

TIA
-J

[knottyrope]

BACKUPS are key!!!

Might as well upgrade everything else to SP2 while you are there.

[gibson_hg]

Upgrading the BES will not induce the Send As, but installing SP2 on the Exchange tools might do it. It's not an issue you get from RIM, it's purely Microsoft.

While I do agree with upgrading the Exchange portion to SP2, the best way to avoid the Send As is installing any updates/patches that can induce that.

The biggest issue with upgrading the BES from 4.0 to 4.1 is the DB upgrade failing. Just back everything up. You can always get it working.

How many users do you have on the BES? Just backup the DB and perform the upgrade, it usually works but the there are times when it fails.

The "horror" stories can sometimes be traced back to unsupported configurations also. You have a pretty standard setup, I wouldn't worry about it.

[JPenrose]

Thanks for the replies.

We have 60 users on the BES and, IMO, a pretty simple, straight forward implementation.

SP2 for Exchange isn't approved for use here yet so it would appear that this install should go in without too much drama.

If I run into trouble, I sure know where to go for help.

Thanks again,
-J

[rasobey]

We're on 4.0.6 and about to do the same thing, albeit Windows Server 2003 SP2 and Exchange SP2. One thing I have read is that's *recommended* to be on 4.0.7 before you go to 4.1.x. I'm not sure why. Can anyone shed any light on this? My rep said 4.0.6 should be fine too though.

[JPenrose]

Originally Posted by rasobey

We're on 4.0.6 and about to do the same thing, albeit Windows Server 2003 SP2 and Exchange SP2. One thing I have read is that's *recommended* to be on 4.0.7 before you go to 4.1.x. I'm not sure why. Can anyone shed any light on this? My rep said 4.0.6 should be fine too though.

RIM KB05217 wants you to be at 4.0 SP 3 or better prior to an upgrade to 4.1

BlackBerry Search Results

I think if you're already at SP6 you've met that requirement and then some.

[JPenrose]

Just an FYI about this upgrade:

Afer doing some backups and verifying that the pre installation checklist was satisfied, I pulled the trigger on Sunday morning.

The install, DB upgrade and various other tasks the install routine performs went off flawlessly. Couldn't have been easier IMO.

I will note that handhelds didn't start receiving mail and doing successful look ups for about 30-40 min after the upgrade while new service books were pushed (I can't say that for sure but it seems resonable). PIN and Web worked straight away.

Thanks for those that offered advice in this thread.

-J

[knottyrope]

Yes the service books would have to be sent before email is sent.
Is a blurb about it in the upgrade guide somewhere.

[JPenrose]

I went back to check for that and found a section that shows you how to configure some reg keys to make the process more efficient.

-J

[knottyrope]

Hard to digest all that upgrade info in a few days.
Lucky you know of this great forum.
Congrats on the upgrade.

[SoUnCool]

Originally Posted by JPenrose

I went back to check for that and found a section that shows you how to configure some reg keys to make the process more efficient.

-J

what value you used for SBThrottleLimit ? The default is 60 i am assuming this means 60 devices will receive service book in one hr ?

[kenjancef]

Originally Posted by rasobey

We're on 4.0.6 and about to do the same thing, albeit Windows Server 2003 SP2 and Exchange SP2. One thing I have read is that's *recommended* to be on 4.0.7 before you go to 4.1.x. I'm not sure why. Can anyone shed any light on this? My rep said 4.0.6 should be fine too though.

On Tuesday (5/27) I did a migration to a new BES server for a client. They are running BES 4.0.3.2 in an Exchange SP2 environment. The migration was unbelievably smooth, I'm still shocked!

What we did was back up the database on the old server. We also set up a new BESAdmin user, because the old user account was kinda messed up, and I followed the "send as permission" steps in the Knowlegebase. I also installed Exchange System Manager and Exchange SP2 on the new server.

I was on the phone with a T-2 tech at Blackberry and he was really good. We ended up installing 4.0.3.2 on the new server and restored the database, and all 12 Blackberry units worked right away! It was actually kinda awesome...

So... I then asked if we could upgrade to 4.1.5, but he said no, we would have to upgrade to 4.0.7 first, then 4.1.5. I didn't ask why, but since he got us up and running so smooth I didn't ask.

We didn't do the upgrades yet because we ran oout of time, but the tech did say to go to 4.0.7 first.

Hope that helps....


Ken