09-08-2009, 07:27 AM
Thumbs Must Hurt
Join Date: Feb 2005
Location: Windsor, On
Carrier: Bell Mobility
Post Thanks: 0
Thanked 0 Times in 0 Posts
slahm, I opened a support case and they mentioned this encryption as one of the first possible causes. Both my 4.1.6 server and 5.0 servers are set to 3DES/AEP so this may not be the problem. I am going to test a move again.
If your BES servers use different databases, you could use a new tool called the Enterprise Server Transporter. I tested this product. Basically it will move a user from one BES to another with minimal interruption to the user. The few things I saw that the user was required to do was that a) any 3rd party applications that originally had to ask for permission to do something came up again and b) things like IT policies etc are not ported to the new BES, so the end user experience may change.
But to get to the main answer for noname, a phased upgrade is when you install BES 5.0 on a new server and point it to a live 4.1.6 database. Both BES servers become part of the same BES domain, allowing you to simply move users from one BES to another with no user interruption. Obviously I'm testing this at the moment and running into an issue but it will be resolved. The one caveat I've found is that as soon as you install BES 5.0 in this manner, you need to start using the new Blackberry Administration Service web based GUI to admin all users whether they are on 4.1.6 or 5.0 servers. If you have delegated roles to other admins, you need to prepare them first before doing the install; the old Blackberry management console will not load. We installed in a test environment in order to give our admins a peek at the new GUI, and to write the required documents.
I'll post more when I have a solution to my move issue.
History: PB32, 9800, 9700, 8310, 8700, 7100r, 7780, 7280, 6710, 957, 950