[sniffs]

And the newest software was just released and it supports OTASL. AT&T supports OTASL deployment, as well as the BES version 4.1.5+ supports it.

To Deploy it, do I just install the OS update on the BES, setup a package and point to it?

Or is there more config involved?

[penguin3107]

The Bold needs to be AT&T branded, and it must currently be running an AT&T released version of the handheld code.
OTSAL has been available on the Bold for a while now. 4.6.0.167 was capable of it.

You do NOT install the OS on the BES.
The BES' role in this process is merely to request the wireless update on behalf of the user.

I would suggest that you run through the documentation for wireless updates and it should explain the entire process to you in more detail should you need it.
http://www.port3101.org/featured-bla...using-bes.html

(As a side note, there have been some problems with wireless update for the new AT&T OS on BES versions prior to 5.0. You might not be able to get this working yet.)
See here:
OTASL - Official BES Provisioned Versions - Port3101.org : Your BES Connection

[sniffs]

Perfect.. now I have to figure out why one of my old BES servers shows all the Bold's as "Software Upgradeble: True" whereas my newest BES server shows them all as "False"

All the 'Default' IT policies are the exact same, Allow non-enterprise upgrades is set to True, and the BB configs are all the same.


any ideas?