[rogue_83]

Hi,

We have a decent sized BES environment with just over 400 users. Our current BES 4.1.6 is on a virtual server (one instance only), and we are planning to take the plunge to v 5, via an in-place upgrade.

We have done a bit of testing in our test virtual environment, and found the upgrade to be pretty easy. However, my biggest concern is, will we be required to re-activate our users once the in-place upgrade is complete? If anyone has come across this issue during their in-place upgrade, or have any advice, it would be much appreciated! Am really worried that we would have to be re-activating 400+ users' devices if something goes awry?

Thank you!

[jjbova]

We had that issue with about 10% of our users. We are still working out why it happened, but it seemed that users would drop activation when they plug in to thier workstations and try to sync after the migration.

[Arkanian]

We used the Transporter tool and about of like 800 users we only had to reactivate 3 so we had very good success doing that. We went from 4.1.6 to 5.0.1.

[rogue_83]

Originally Posted by Arkanian

We used the Transporter tool and about of like 800 users we only had to reactivate 3 so we had very good success doing that. We went from 4.1.6 to 5.0.1.

Thank you both for your feedback! Appreciate it. Arkanian, we are also upgrading from 4.1.6 to 5.0.1, but since we are doing an in-place upgrade, we won't be using the Transporter tool. Although its comforting to hear we wouldn't need to re-activate. :D (And the few that might cause problem, i guess we will have no choice)

Cheers

[knottyrope]

Just make sure most users are on OS 4.5 or higher on their device and things will be smoother. 4.3 is a bastard OS and causes issues cept for one version for 8330's.

[junaidi]

Originally Posted by rogue_83

Hi,

We have a decent sized BES environment with just over 400 users. Our current BES 4.1.6 is on a virtual server (one instance only), and we are planning to take the plunge to v 5, via an in-place upgrade.

We have done a bit of testing in our test virtual environment, and found the upgrade to be pretty easy. However, my biggest concern is, will we be required to re-activate our users once the in-place upgrade is complete? If anyone has come across this issue during their in-place upgrade, or have any advice, it would be much appreciated! Am really worried that we would have to be re-activating 400+ users' devices if something goes awry?

Thank you!

sama

[rogue_83]

Originally Posted by knottyrope

Just make sure most users are on OS 4.5 or higher on their device and things will be smoother. 4.3 is a bastard OS and causes issues cept for one version for 8330's.

I read that this is a problem only if you use the Transporter tool, not with the in-place upgrade? Does 4.3 OS cause issues even during an in-place upgrade?

Thanks.