| | Best Practice Software Config Update?
Please Login to Remove!
Hi all. I have a question on upgrade procedures for a current software configuration that is set up on my BES.
I have a current software configuration, let's call it version 1.0. No issues, OTA works great for me. I have received files to upgrade it to 1.5. Ran some tests off another shared directory and it works with my BB models. Cool.
I'd like to now put it into production and update all of the BB's with the current version. What's the best way? I've come up with two ways and wanted to see if anyone could add their 0.02.
-Update the current configuration with the new files and reindex it. I assume this would push out to the users with the old version and update it to the new version.
-Delete the current configuration and treat the upgrade as a new software configuration, then just push away. I am assuming that the application will just update itself on the target BBs and not add itself along side it. (fingers crossed)
I spoke to RIM supoprt this AM and was told to treat it like a new configuration and delete the current one, but the person I spoke with didn't give me much confidence as he had to put me on hold several times to 'do some research', then came back with an answer that had nothing to do with my question.
I did a couple of searches here and came up with a couple of threads, but they are a year or more old and use some older versions of BES.
I'm actually lost...