[TroyB]

Currently running:

BES 4.1.2 on an ESX VM with MSDE

Moving to:

BES 4.1.5 on an ESX 3.5 VM using remote SQL 2005 DB

I will be purchasing the BES Migration Kit and just doing a gradual migration of all the users.

From what I gather, Devices will need to be touched using this method. My question is what's the easiest and most painless method? I'm hoping that I don't actually have to rebuild the device. Do I just have to connect it via wired connection and Desktop manager for the device to recieve the info from the new BES server once I add the user account on it? This is the only piece I;m not real clear on.

All the devices should be running vesion 4.0 or better HH software if that helps.

Thanks for the help!

[hdawg]

Is the 4.1.5 with SQL 2005 already up and running with users on it?

[TroyB]

My appologies for the slow response.

No. It will be a 100% fresh build.

[shuman]

If you are running 4.0 and above on the handhelds, you should be able to do the activation wirelessly. no need to connect.

[TroyB]

That's what I like to hear! It seems 90% of the upgrade questions here relate to knife edge cutover here which is what I'm trying to avoid even if it means more leg work.

So can you give me a basic example of how this will work?

Thanks for the assist! I'm still fairly new to BES admin stuff so any and all pointers are always greatly appreciated.

[hdawg]

Upgrade 4.1 SP2 server to SP5 on the old server
Move database from MSDE to SQL
Install 4.1 SP5 on new server, and connect to shared SQL database
Drag and drop users through BlackBerry Manager from old server to new server
Remove old server from BlackBerry Manager
Uninstall software on old server and refurb

If you've got specific questions ask-a-roo, but that is the basics.

[TroyB]

I guess I need to give more info:

Upgrading my current BES is problematic which is the reason why we're completely wanting to start from scratch. The server is a VM which is OOOOLLLLDDDD. It was built when we were using GSX, then the VM was migrated to ESX 2.x, then migrated again to ESX 3.x. The BES software has also been through a TON of upgrades and we've rigged together solutions to issues with the MSDE database on a number of times.

To make a long story short, the current BES server is limping along and is not upgradable and I think there are enough issues with the current database to where I wouldn't want to just bring that along either which is why my plan is to just start everything up from scratch and move users over even if it will indeed require more leg work in the process.

I took this job over from someone who I don't completely trust knew what they were doing when they built it in the fist place so this will be a good oppurtunity to learn the ins and outs as I work this through.

Hopefully that makes sense as I tend to ramble quite a bit.

[shuman]

The main question is will you be using the same DB on the new server? If so, then you are not going to need to reactivate the handhelds. If not, starting with blank DB, then you will need to reactivate all the handhelds. If you are going to use the same DB maje sure to name the new BES server the same as the current one.

[TroyB]

Yes. It will be a brand new database.