[noname]

A lot of questions on this one, so posting here to share and make aware and also safe keep an online consolidated reference for myself

Article Title: What is a wireless BlackBerry Device Software update
Article Number: KB15631
Link: View Document

Article Title: Requirements to perform wireless BlackBerry Device Software updates
Number: KB15626
Link: View Document

Remarks:
The wireless service provider determines the wireless BlackBerry Device Software updates that are available for BlackBerry smartphones and the date of availability for the updates. For information about support for wireless BlackBerry Device Software updates on a BlackBerry smartphone, contact the wireless service provider (e.g. Verizon wireless... etc).

Somebody consolidated a list of wireless service providers that support OTASL (aka Over The Air Software Loading) but I do not know if they are up-to-date:

Link: OTASL - Official BES Provisioned Versions - Port3101.org : Your BES Connection

[noname]

Just received a good information for BES Admins:

You can check the OTASLLastRefreshTime by looking at the HandheldMgmtConfigProperties column in the GlobalSettings table in the database.

SQL Query:

SELECT HandheldMgmtConfigProperties FROM GlobalSettings

[noname]

2 main Wireless Device Software upgrade using Wireless network.

See section...
4. Updating the BlackBerry Device Software over the wireless network

(1) Permitting the wireless service provider to update the BlackBerry Device Software over the wireless network...............page 18

(2) Using the BlackBerry Enterprise Server to update the BlackBerry Device Software over the wireless network................ page 20

Link: http://docs.blackberry.com/en/admin/...1-5.0.1-US.pdf

[Sp1d3rM@n]

We are just looking into allowing OTASL upgrades from the carrier. We have various BES environments with servers running from BES v4.1 to v5.0 (actually a few v4.0 as well but we know OTASL isn't an option there), all in Exchange 2003 messaging environments.

I have read the pre-reqs and caveats, but one thing that is not explicitly mentioned is re-activation.

Its always been that whenever device software was upgraded, by whatever method, you needed to reactivate. Of course if we stayed wired after the upgrade, that would happen automatically but would still happen.

So when devices upgrade OTASL do they need reactivation? I would have thought so, but an email from RIM says otherwise. What is the experience here in regards to this, and in regards to speed and success. I'm curious if you guys are seeing higher rates of failures with certain models, or just in general compared to wired upgrades.