BlackBerry® Enterprise Service 10

[Zarky]

Here is something a little more out of the box.

Current setup: BES 5.0.3 MR6 on SQL 2005 connected to Exchange 2003 In location A

Target: Exchange 2010 In location B

the WAN connection is 90Mb at best between the sites and the BES database is 500MB for 400+ BES users. Secondly the total exchange mailbox size used by the Same BES users is 380GB.

Goal: migrate exchange users in small batches on both email and BES. This to be done without wiping the devices.

I cannot move all the BES uses at once thus cannot "relocate" the BES and corresponding SQL database.

So my option is to Install a secondary BES server in the new location and connect it to the existing SQL database.

Then use the migration tools for BB to move the user to the new server.

The big question is how to run one BES connected to Ex2003 and the other to ex2010?

Will this line of thinking actually work? RIM?

[knottyrope]

---

Zarky wrote:

Here is something a little more out of the box.

Current setup: BES 5.0.3 MR6 on SQL 2005 connected to Exchange 2003 In location A

Target: Exchange 2010 In location B

the WAN connection is 90Mb at best between the sites and the BES database is 500MB for 400+ BES users. Secondly the total exchange mailbox size used by the Same BES users is 380GB.

Goal: migrate exchange users in small batches on both email and BES. This to be done without wiping the devices.

I cannot move all the BES uses at once thus cannot "relocate" the BES and corresponding SQL database.

So my option is to Install a secondary BES server in the new location and connect it to the existing SQL database.

Then use the migration tools for BB to move the user to the new server.

The big question is how to run one BES connected to Ex2003 and the other to ex2010? Sure you can

Will this line of thinking actually work? RIM?

---

Same exchange org? if yes then should be easy.

If not then its going to be pain ful.

Do you have a second SRP? if yes then easy if no then you will need a Migration kit or use BES Express as middle man.

Moving that amount of data might strangle SQL. Maybe a new database in new Location would be better?