[TroyB]

Just to be clear, if I'm currently running BES 4.1.2 then install BES 4.1.5 on a totally different server but point it to the 4.1.2 database and have it upgrade the DB, I'll be fine right? I'll see both BES servers so I can move users back and forth I just have to use the management console from 4.1.5? Is that assumption correct?

Anyone know of a kb article that discusses this approach using the BES Migration Kit?

[CanadianCrack]

I don't think you can move the users from one database version to another without interruption to their service. Their bb's would have to be re-activated.

I'm currently at 4.1.4 and upgrading the BES software to 4.1.5 (probably 6 now) on new hardware and want to complete the upgrade without interruption to the users.

In KB12304 under method 3 it advises to upgrade the BES software on the old server to the version you want, and then do a knife-edge cutover.

Not sure if your situation is the same as mine, but the KB article covers different scenarios that may help you.

[TreeDude]

I could be wrong, but I believe this approach only works when going to the next immediate release. Meaning it would work for 4.1.5 to 4.1.6. But not across multiple service packs. Now what you could do is a knife edge cutover. It is similar the only difference would be that all your users would then be on the 4.1.5 server and the other server would be shut down. You could then upgrade the second server to 4.1.5 and distribute your users across both.

Might want to get some feedback from some of the more seasoned people here. I have never actually done anything like this so this is just from reading about stuff.

[TroyB]

Originally Posted by CanadianCrack

I don't think you can move the users from one database version to another without interruption to their service. Their bb's would have to be re-activated.

The database would remain the same. It would be upgraded and only managed through the new BES version.

[shuman]

Originally Posted by TroyB

Just to be clear, if I'm currently running BES 4.1.2 then install BES 4.1.5 on a totally different server but point it to the 4.1.2 database and have it upgrade the DB, I'll be fine right? I'll see both BES servers so I can move users back and forth I just have to use the management console from 4.1.5? Is that assumption correct?

Anyone know of a kb article that discusses this approach using the BES Migration Kit?

You are correct.

[noname]

TroyB, your approach is correct. That's the whole point of having your BES servers installed within a BlackBerry Domain aka sharing same SQL instance's BESMgmt DB - moving users across them "seemlessly" and without interrupting their BB services.