BlackBerry® Professional Software and BlackBerry® Enterprise Server Express

[leroyplock]

Thanks for the confirmation and the link. I want to change the account because they currently have it set using the domain admin account and I think it should be a separate besadmin account.

[knottyrope]

---

leroyplock wrote:

Thanks for the confirmation and the link. I want to change the account because they currently have it set using the domain admin account and I think it should be a separate besadmin account.

---

Thats a good idea then.

[smitty42]

  I just wanted to say that after having first read this thread 7 months ago I finally migrated my first three test accounts over from BPS 414 to BESX 502 using the transporter and everything went beautifully.  The 9630's did not even need to restart.  Now on to moving the mailboxes from EX07 to EX10..........

I will say this though, after having gotten used to the BPS admin console, trying to get used to the BESX java-web-based admin console is going to take a while.

[knottyrope]

Then when you are done moving users to BES 5 follow this

How to migrate the BlackBerry Enterprise Server 5.0 from Microsoft Exchange Server 2003 or 2007 to M...

[smitty42]

yes, I am reading that now, just one question not really addressed in that article:  move the besadmin mailbox from EX07 to EX10 first before the others or last after everyone else or move all blackberry enabled mailboxes at once?

[knottyrope]

---

smitty42 wrote:

yes, I am reading that now, just one question not really addressed in that article:  move the besadmin mailbox from EX07 to EX10 first before the others or last after everyone else or move all blackberry enabled mailboxes at once?

---

Move BESAdmin before everyone, you can move the uses over after.

[smcnetserv]

First of all - Great post! Now a few questions: I'm running BPS 4.1 on a separate VM and need to upgrade to BESX 5 before EX2010 deployment.

1. Would you recommend using the same VM or creating a new VM with the new DB and using Transporter to move users?

2. What's the exact impact on users when they are transported? I mean everything should be resynced once they're moved to the BESX server, correct?

3. Generally, based on my scenario, what would be the recommended path to take?

4. I understand about BES , but do I need to decommission BPS after the new besx server is in place?

Thank you!

[smitty42]

smcnetserv: I recently moved from BPS 4.1.4 w/ Exchange 2007 to BESX 5.0.2 w/ Exchange 2010.  it seems duanting but is actually pretty simple.

1) I am not 100 percent sure, but I don't think you will be able to install BESX on the same VM that you already have BPS on.  I used another machine for BESX.

2) all of my handhelds were newish (within two years) and suffered no effects whatsoever from being Transported from BPS to BESX.

The recommended process is:  install the new BESX with a new database using the same service account/service mailbox on another VM, then use the Transporter to move all of the BB users from BPS to BESX (recommend installing the Transporter on a separate machine from either BES or BPS), then move the BESADMIN mailbox to the Exchaneg 2010 server then move all the BB user mailboxes to exchange 2010.

Some issues I ran into were:  BESX Admin service initially refused to run after installation.  Had to uninstall some Windows Updates:  

Hotfix for MS10-021 related to Microsoft KB979683 Hotfix for MS10-047 related to Microsoft KB981852 Hotfix for MS11-011 related to Microsoft KB2393802 (recheck after each uninstall for the others, the newest one superceded the older ones which means the older one(s) reappeared in the "installed updates" list after uninstalling the newer one)

The BESAdmin account had to have approriate Exchange 2010 permissions applied to open exchange 2010 mailboxes http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB02276

some users contacts stopped syncing after moving the mailboxes to 2010, i deleted the Desktop [sync] service book from the affected handhelds and the contacts sync returned to normal.