03-30-2009 01:51 PM
With an inplace upgrade, what should we expect our user's experience to be when (after) we run the 4.1.6 upgrade on our current 3.6.7 server?
Will the user's need to do anything with their devices?
Thanks!
Solved! Go to Solution.
I am on AT&T. Please edit your Personal Profile with your DEVICE TYPE, DEVICE OS and Carrier
03-30-2009 02:00 PM - edited 03-30-2009 02:00 PM
There will be a slight delay when service books are resent depending on how many users you have.
No HTML email unless they are on 4.5 OS on their devices and some other features.
You might have a few people that need to re activate, it is rare but happens.
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
BESAdmin's, please make a signature with your BES environment info. SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
03-31-2009 08:41 AM
There would not be a straight upgrade path from 3.6.7 to 4.1.6 however.
Not sure of the top of my head but I think you would need to do:
3.6.7 > 4.x > 4.1 > 4.16 due to the DB extensions that rely on certain earlier DB version levels.
You should be able to find this info in release notes for 4.1.6 and work backwards for each earlier version.
I have seen a 4.05 > 4.16 upgrade that needed 4.0.5 > 4.1 > 4.1.2 > 4.16 due to the schema changes in the DB.
Just a thought. ![]()
I am on AT&T. Please edit your Personal Profile with your DEVICE TYPE, DEVICE OS and Carrier
03-31-2009 10:44 AM
Follow this
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
BESAdmin's, please make a signature with your BES environment info. SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
04-05-2009 11:01 PM
3.6.7 to 4.1.6 is a fully supported upgrade path, the install process even performs the mailbox migration. The most common issue with this type of upgrade is SQL engine related and potentially ESM components depending on the version of Exchange in use. If MSDE7 is the SQL engine being used it needs to be upgraded to at least MDSE2000a to work with 4.1.6. The other thing is not enough space in the transaction log to perform the database upgrade. ![]()