I've search these forums for a similar scenario but I could not find one.
I am currently running BES v3.6.2.14 w/MSDE with about 60 users running a mix of 3.6 and 4.0 handhelds. We purchased the 4.0 upgrade but I have run into some problems.
I've tried running an in-place upgrade to v4. I ran into incompatible db issues with msde. I've attempted to install v3.6 sp5 but I do not have the 3.6 install cd(long story).
I am trying to figure out what is the best approach for the upgrade.
Ideally, I would like to have BES v4 running on new hardware. Should I abandon the upgrade and try to run a clean install v4 onto new hardware?
How do I go about moving the SRP ID over to the new server?
Once BES is running v 4.0, will the handhelds need to be cradled to see the new BES 4 server?

Thanks for your help.

I was in a similar situation back in March of this year and ended up doing a fresh install of BES 4 on the new hardware platform.

As far as the SRP ID goes, the best method is one which both migrates your SRP to the new installation and also provides you with a fallback path if you need it. The way this is accomplished is to install BES 4 on the new hardware, but don't allow the services to start until you're ready for the final cutover. At the point in time you're ready to convert to the new install, stop the services on the old BES, then start them on the new BES, import your users, etc.

Many of the users here on Blackberryforums.com have performed similar cutovers in the past months, so just keep this thread moving and others will jump in with more information as you need it.

Baron,
Did the handhelds automatically connect to the new 4.0 server? Or did you have to cradle and update the encryption key? Thanks

A device with v4.0+ code should continue to operate and talk to the 'new' BES, as long as they have the same SRP ID.

The 3.6 to 4.0 in place upgrade worked seemlessly for me. You would have to make sure you are running the latest MSDE or you could possibly get the database incompatability problem you were seeing. I did, however, end up recently moving our BES to new hardware because 4.0 supports up to 2000 users where previously you could only add up to 200. The prvious response was correct that if you go the new hardware route, you simply install 4.0 on the new hardware making sure not to start any services until you are ready to cut over. There are also a total of 3 hotfixes for 4.0 base install, service pack 1, and 2 hotfixes for sp1. Be sure to install all of those on the new hardware and in that order. If you have access to SQL Enterprise Management tools (usually installed with SQL server) then you can perform a backup of your existing database and restore it to your new server. This will allow for your existing user list to be populated. If you do not have access to those management tools then you can do it through DOS commands and RIM has documentation how to do that. My switchover to new hardware worked like a charm and required no assistance from RIM. Now as far as the handheld detection, when we first upgraded to 4.0 (prior to the new hardware) all devices cotinued running fine. After the server was upgraded we went through and upgraded all handhelds to 4.0 so that in the event of any problems down the road they could be wirelessly provisioned (an awesome feature of 4.0). Please let me know if I can answer any additional questions. I've seen and dealt with almost every problem you can imagine with both 3.6 and 4.0. Cheers!

I am in the process(almost done) of doing the same thing. 3.6 to 4.0. Some of our handhelds are on 3.7 and we have started upgradeing the handhelds as well. I seem to be having a problem at the moment of people on the 4.0 server recieving their messages in batches. When I look it seems that that things go pending between 10 - 15 min and then they get sent out. We are running some excange 2003 as well as 2000. ANyone hear of anything like this ? Thank You.