I'm going to do upgrade using "Upgrade The BES using an in-place process" method.Upgrade manual states " You cannot remove BES 4.1 and return automatically to the earlier version".

Now I'm confused about the rollback scenario. In case we faced a problem during upgrade ; can I go back to my backup ( I'm going to stop server and have full backup just before the upgrade ) and continue with 2.2 ?

for us the upgrade of the BES server was good but we discovered that all the handhelds running an ios<4.0 were unable to connect to our BES v4.0 server.
RollBack !

I just posted a question about this a few minutes ago and this is exactly the scenario I was inquiring about. Is this typical behavior? I was informed by the RIM docs that we could do the server upgrade and the < 4.0 handhelds would operate with < 4.0 features.

I just posted a question about this a few minutes ago and this is exactly the scenario I was inquiring about. Is this typical behavior? I was informed by the RIM docs that we could do the server upgrade and the < 4.0 handhelds would operate with < 4.0 features.

Which way is it?

Thanks.

John Rowland

it's meant to be that any version h/h and any version bes shall place nicely together - i.e. you can have 3.x devices on a 4.x BES and 4.0 devices on a 2.2.x BES.

I still think it's better to blow the handhelds first as that means that when the upgraded is completed you've got a 'big bang' launch with everyones devices taking the new features.

If you're not doing an in-place upgrade the definately blow the devices first cos if you end up moving devices between BES's then they can cope much better if on 4.0 or 4.1 handheld code, as the new authentication code is auto pushed out to the device (IIRC)