BES and Updating Device OS

03-17-2009, 10:23 AM
|
|
BES Activated
|
|
Join Date: Mar 2009
Location: Woburn,MA
Posts: 3
|
|
BES and Updating Device OS
We are currently running BES 4.1.6.16. I was wondering what other BES admin's are doing to update their user device OS's? Do you simply have them user desktop manager or is there a way to push from the BES itself? We do not have a huge user base, but like most we're stretched thin so anything to make updates easier and "seamless" is what I am looking for!
Thank you in advance for any insight, tips, etc.
Sean
|

03-17-2009, 11:02 AM
|
 |
Super Moderator
|
|
Join Date: Dec 2008
Location: West Michigan
Posts: 763
|
|
It's my understanding that until the device is up to OS 4.5, you can't push an OS upgrade from the BES.
We just (like the last 2 weekends) upgraded to 4.1.6 MR4, and are in the same boat, and have users all over the US, Canada, and various other places in the world. I manually upgraded a bunch of users last week (got lucky with a big Sales meeting being onsite), and other users will be able to contact our Helpdesk (or me) and get assistance.
We packaged Desktop Manager 4.7 in Altiris, and can push that out to the user's PC, and then copy the device OS to their PC and kick off the upgrade for them. They are told to expect to not be able to use their device for ANYTHING for at least an hour.
We also told the users that they do not HAVE to upgrade, unless they want to nifty new features.
__________________
You may know me as Juwaack68
|

03-17-2009, 11:13 AM
|
|
BES Activated
|
|
Join Date: Mar 2009
Location: Woburn,MA
Posts: 3
|
|
Thank you for the update. We too have a desktop management system, I guess I could do the same for now to update those who want/need as you have mentioned. Once again thanks for your time!
|

03-17-2009, 12:35 PM
|
 |
Supreme Commander
|
|
Join Date: Jan 2009
Posts: 114
|
|
I've been manually upgrading departments and user when I can, during departmental meetings, when new devices arrive, old ones have issues, etc.
We still have a considerable amount of users with 8703 models that we are going to be upgrading very soon with 8330s. Since those are shipping with 4.5 already, that eliminates updating those devices.
|

03-17-2009, 12:37 PM
|
 |
Supreme Commander
|
|
Join Date: Jan 2009
Posts: 114
|
|
Also, we have not been actively upgrading personal devices connected to our BES. We are leaving this up to the users to do... for now.
Last edited by Pinjo; 03-17-2009 at 01:17 PM.
|

03-17-2009, 03:21 PM
|
|
BES Activated
|
|
Join Date: Mar 2009
Location: Woburn,MA
Posts: 3
|
|
Thanks for the insight, that makes sense and is something we may consider to make it easier on us for now.
|

03-17-2009, 04:28 PM
|
 |
BES Guru
|
|
Join Date: Dec 2008
Location: Columbus, OH
Posts: 247
|
|
If it ain't broke, we ain't fixing it.
|

03-18-2009, 02:02 AM
|
 |
BES Administrator
|
|
Join Date: Feb 2009
Posts: 13
|
|
my understanding is that you cannot do OTA device OS upgrades from the BES in v 4.1. Aparently this will be available in 5.0
|

03-18-2009, 11:14 PM
|
 |
Proprietor
|
|
Join Date: Nov 2008
Location: Atlanta, GA
Posts: 2,032
|
|
You can't push OS updates at all. You can initiate the OS update, assuming they're at OS 4.5 and above, but it is still carrier-driven with regards to the version. If the carrier doesn't support OTASL, you aren't going to get an option for an available OS update to release to your users. At this time, Verizon is the only American carrier to release an OS through the OTASL channel and that was primarily to address the issues with the beta OS they released on the Storm to bring it to market before Black Friday.
When we first heard about OTASL, as administrators, we were extremely happy and pleased. It was a new way that we could deploy OS's to our users without having to touch the devices, without having to wait on the slow process that is carrier certification, etc - simply load the OS to a shared location and push it to the device. I believe this has a bigger impact on those of with access to beta OS's and a small albeit interested test user base of technophiles.
In all honesty, though, for companies who have a single GSM carrier or a single CDMA carrier, or those who don't readily comply with OS upgrades when they are available, the change in implementation of OTASL (reduction of flexibility for administrators) - that is, assuming this was not simply a misinterpretation of the implementation - really won't have much of an impact on the way we do things, to be honest. I would say this would have an impact on less than 5% of the deployments (my opinion, of course).
__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)
The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.
|

03-25-2009, 09:57 AM
|
 |
Learner
|
|
Join Date: Jan 2009
Posts: 57
|
|
Not to sidetrack the conversation per se'. But, in your organization, are the employee's provided with the BlackBerry's, or do they buy it themselves?
Here, we provide BlackBerry's for the Partners (12 of them), and the rest get there own. So, I don't do upgrades for the general user(s). As for the Partners, well, they are too impatient to hand the BlackBerry to me for about 1-2hours...
Quote:
Originally Posted by Joolie
It's my understanding that until the device is up to OS 4.5, you can't push an OS upgrade from the BES.
We just (like the last 2 weekends) upgraded to 4.1.6 MR4, and are in the same boat, and have users all over the US, Canada, and various other places in the world. I manually upgraded a bunch of users last week (got lucky with a big Sales meeting being onsite), and other users will be able to contact our Helpdesk (or me) and get assistance.
We packaged Desktop Manager 4.7 in Altiris, and can push that out to the user's PC, and then copy the device OS to their PC and kick off the upgrade for them. They are told to expect to not be able to use their device for ANYTHING for at least an hour.
We also told the users that they do not HAVE to upgrade, unless they want to nifty new features.
|
|

03-25-2009, 10:19 AM
|
 |
Super Moderator
|
|
Join Date: Dec 2008
Location: West Michigan
Posts: 763
|
|
Quote:
|
Not to sidetrack the conversation per se'. But, in your organization, are the employee's provided with the BlackBerry's, or do they buy it themselves?
|
The only devices allowed on the server (at least in the US and Canada, since I order them all) are corporate purchased devices. Personal devices are not allowed only because I don't feel like listening to people complain about having a password on their device (which they probably expensed anyway, so technically it's a corporate device!).
There are a few devices connected that are personal devices, but that was before we locked it down.
__________________
You may know me as Juwaack68
|

07-26-2009, 03:04 AM
|
|
BES Activated
|
|
Join Date: Jul 2009
Location: US
Posts: 4
|
|
I'm currently working on a major device os upgrade I'm using the web loader forceload method to accomplish this due to most of the end users do not have the desktop manager- I also look a the webdesktop manager option and I think are the best method available to do do mass upgrade hope it helps.
|
 |
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|