Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 468
  • Last Modified:

Blackberry 5.0.1 Upgrade

Hi ,
We are planning to upgrade our blackberry server to 5.0 HA
Can you please outline the steps in details for the entire migration process?
Environment details:
Windows server 2003 SP2- exchange 2003 & 2007-BES 4.1.6-local MSDE database
to Windows server 2003 SP2-exchange 2003 & 2007-BES 5.0.1-Remote SQL mirroring
Migration process will be cut-over (one shot migration)
will we need a SRP ID for the existing setup as well as the new 5.0.1 set-up? If yes how to get the temporary SRP ID till migration from RIM?
Should we create IT polices similiar to the ones existing in 4.1 on 5.0.1 so that they can be mapped to the users? or can it be assigned in course of the migration using BET
Steps for using BET
Currently we have IM integeration with LCS 2005. Steps to migrate the IM integeration to 5.0.1
Should we install the sp1 after the entire migration process is complete? or directly install 5.0.1 base software on the new server.
Any known issues expected after the migration and solution.
0
priyaexch
Asked:
priyaexch
  • 2
1 Solution
 
priyaexchAuthor Commented:
And in this scenario, do we have to use the BET to migrate the users or restore the MSDE database to the new database?
0
 
RobMobilityCommented:
Hi,

I suggest you consider BES 5.02 with the latest interim update rather than 5.01?

I'd be inclined to create a new SQL database for BES 5 which will be populated by the BES 5 installation.

Then manually set the IT Policies - there are many more in BES 5 than in BES 4 so direct migration isn't really an option.

Then use the Transporter to migrate the users.

Regards,


Rob.
0
 
priyaexchAuthor Commented:
Expert has answered a part of the question.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now