For arguments sake, let's call them BES1 (current/old) and BES2 (new). If you're running Exchange, how is your environment set up? Do you have a local exchange server in both site locations site1/site2? I'll proceed with the assumption that you have a DC/GC and exchange at both locations. So here we go in a nutshell:
1. Obtain all BES info from BES1 - SRP, SRP auth, all CAL's and the database server\SQL instance as well as the BES1 service pack like 4.1.4, 4.1.5 etc. and back up your besmgmt database
2. Make sure the besadmin permissions are correct for site2's exchange and users/OU in AD
3. Verify good connectivity from site2 to your SQL/DB server
3. On BES2, install exchange management tools (ESM) plus all applicable service packs. If you're using Exchange 2003 then apply Ex2003 SP2 + the DST update (MSKB#: 926666)
4. When performing the BES software install on BES2 note the following: install BES with the same SRP, SRP Auth and CAL's as BES1, do NOT point it to your SQL/DB server and at the very end (presuming it's 4.1.x) make sure that you do NOT start BES services. Once the install on BES2 is complete, set all BES services to manual startup except database consistency which should remain disabled
5. Schedule downtime
6. Stop all BES services on BES1
7. Move your besadmin mailbox from site1 exchange to site2 exchange
8. With all BES services stopped, point BES2 to your SQl/DB server, verify connectivity and open the BES Management Console to make sure you see your users and recent stats listed.
9. Once #8 is done, open regedit on BES2 and browse to: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles then delete any subdirectories of profiles. Then go start > programs > BES > blackberry server configuration > blackberry server > edit mapi profile & point it to your site2 exchange then click check name. Close the server configuration window, open the BES management console and click OK when prompted to edit your MAPI profile repeating the same step
10. Start the BES services on BES2 in the following order: router, dispatcher, controller, policy, synch, attachment, alert, MDS connection
11. Keep an eye on your server-level pending messages. Depending on the size of your organization, users and mailboxes it might take awhile for those pending messages to increase/decrease - realistically more than 30min. As long as the pending messages number changes - even if it's steadilly increasing that's good
~ CFJ
