Hello,
I'm weighing the options I have available to move the user base from BES 4x to BES 5 and possibly introducing High Availability. Would appreciate any comments on what path you took and any issues that arrose.

There's a big difference between 4.0 and 4.1 BTW...

To clarify. A phased upgrade requires that the current BES be at 4.0 SP7 or 4.1 SP3.

Also, I mistakenly left out "Cutover" as an option for upgrade path.

Thanks for the results.

Did anyone out there try a phased upgrade? It is where you install a new BES 5.0 server and point it to your BES 4.0 database. Bes 4.0 users are not interrupted in this process. You can then "move" devices to the 5.0 server at will. After all are moved, you can upgrade the 4.0 server.

I ran into a problem performing this phased upgrade approach, link to other thread below. We are still continuing down this path though and once both SRPs are on support contract we will revisit with RIM.
(http://www.blackberryforums.com/bes-...es-tested.html).
I guess this path is not taken by many...

i installed BES 5 onto a new server, joined it to the bb domain then moved the users slowly over to the new server. this has worked great but anyone have some guidance on how i can do the following...

-Move the DB over to the NEW BES server
-Remove the Temp SRP license on BES 5.0 and apply our regular SRP license from our old bes install

I need to do this before Dec 15th... or bye bye mobile email.

I'm running into the same problem i have a trial SRP and that gives me 20 users. I need to move over 60 users and then move my SRP from BES 4. From what i've heard if you have Support with RIM they will give you a miagration kit that will give you a new SRP. But my company will not pay for support. Any one else have a work around?

I recently moved to 5.0 from 4.1.6 and took the path of what they call the phased migration. During the preparation, speaking with RIM peeps, and execution, we ultimately created a new DB for 5.0. RIM support recommended that a new DB be created. While RIM said updating the DB was possible, I got the notion that this could cause more issues down the road than just starting a new DB. This method proved to be very easy.

If you have a temp SRP (migration kit) to set up the 5.0 server, the temp SRP becomes your permanent SRP after the 90 day period. In this instance, your current SRPs do not continue.

At this time, we are running our current 2 BES as well as our 2 new BES. I would have moved everyone over to the new BES by now, but due to a software configuration that has not been compatible with 5.0, I am waiting on the vendor. The 90 day period is a lifesaver. Mixed mode.

Troykent, In testing I installed BES 5 onto a new server, joined ti to the bb domain and moved users over from BES 4.1 to BES 5.0. Every single device went through the EA process and hung, requiring a reboot. I saw articles stating that this could happen when the two BES servers are not set to use the same encryption (AES and DES), but in my situation they were set to the same. I then went a step further and blew away my development bes servers and started from scratch; also totally wiped a new curve and new bold. The problem was still there. Did you not encounter this problem?

- To move the DB, is it MSDE or SQL? Google how to move the data from one server to another. Then you just change the configuration information in the blackberry server configuration program.
- The SRP information is located in BAS for BES 5.0. you can change it there. My dev 5.0 server is down otherwise i would direct you to the area but it's in there


cyclmpc,
It is shocking that RIM support would give the notion that it is better to move users over rather and do a phased migration. There are many RIM online BlackBerry Webinar presentations touting this method as a great way to upgrade BES 4.0. Still we are going to perform the phased upgrade. We have the overpriced support and will use it should we have a problem.

4.1.6 MR6 to 5.0.0 to 5.0.0 MR3 in place here. Everything appeared to work well for about 10 days. But having problems on 12 (reported) of 125 devices with calendar sync, which MAY have been present from the beginning and just wasn't discovered for a while, and mail synch problems on 4 devices that started simultaneously with the discovery of the calendar problem. Opened a support incident. RIM is engaged in searching our logs for clues as I write this.

I can finally report in after our upgrade. Performed a Phased upgrade and moved some users over to the new BES 5.0 with no issues.
This is great, as we are able to keep all the configuration information we have set up in the 4.x environment (IT Policies, groups, software configs).
Next step for us is to move all users to BES 5.0 server, upgrade the BES 4 server and then work on High availability.

Follow up to my prior post--

No solution yet, but it appears unrelated to the upgrade itself. The mail flow problem went away by itself (though it may yet come back by itself). The calendar sync problem is a permissions problem that, per RIM support, is "rare" (lucky us!) and occurs when moving mailboxes to a new Exchange server. The BES service account can access all of the mailbox except the Calendar.

We have also been migrating from EX2003 to EX2007, though most mailbox moves predated the BES 5 install by a couple weeks. Best guess is that it just took a while for the problem to be noticed.

So at this time, it doesn't look like a BES 5.0 upgrade-in-place failure so much as a BES 4.1.6 mail server migration failure that wasn't noticed for a while. In fact, the logs show it affects about 50 users; we still haven't heard from any but the original dozen.

Solution, briefly, is to create a new BES service account, which is a lengthy process they're about to walk me through.

I pretty much nixed inplace as I heavily use groups and groups will not transfer so everything will be new once our BES 5.0 environment is running.

Been building this on and off for the past couple months and will be validating it Q1.