[boma0021]

Hi all,

here is my problem I downloaded the newest OTA Version 2.0.25,I extracted the file and the Sametime ALX file was missing. So I downloaded the normal version too and copied the ALX File to the OTA Folder. After reindexing - the software was getting to the user device and installed without any errors, only the Icon is not showing up.
I searched this forum and the KB. xxx8211; I set the xxx8220;Allow Public IM Services xxx8221;IT Policy to true. /Downloaded the Install files three times to make sure xxx8211; not to have a corrupt file. / I have set on the device show all Icons and pulled the battery three times.
We are running Domino 6.5.5 and BES 4.1.3
Any ideas appreciated xxx8211;thanks

[noname]

Because you are deploying files taken from different versions?

[boma0021]

I was hoping that the ALX is fitting but your answer makes absolutely sense. Where the heck I am getting a full OTA installation (including the ALX), the one form the RIM site is messed up.?

[WickedBez]

I'm not sure on this... but you may want to try resending your IT Policy. Considering you made a change and all.

[noname]

boma0021, boma0021.... so you are the one started using SametimeOTA.zip.... hmmm

See my post in http://www.blackberryforums.com/bes-...e-ota-bes.html

To err is human

Cheers!

[boma0021]

Thanks , I take the blame.
I've following the other post too.

and here is my philosophical way to see it

Without any errors there would be no mankind as a wise man once said.
'The development of all kinds is based
on mutations, mutations, however,are nothing else than errors while copying the genetic material'

[Jadey]

I did it wrong too, and didn't follow anyone's lead... just assumed the OTA file would be used for, er, OTA deployment from BES.

Anyhoooowww.... As per the task that noname linked, see my emails with RIM. Even the tech guys from RIM took a while to spot the OTA issue, and then said they would recommend that the file names are looked into!

[Jadey]

OK, this is not fixed.

I just downloaded the newest version of SameTime client, 2.1. I downloaded the WIRED deployment as per RIM and all the discussions here. I deleted the old SameTime app config from BES, and deleted the app files from the shared directory. I extracted the new version into the right folder, indexed, created a software config in BES. I assigned the config to my own BB (which did NOT have a sametime client on it) and after a while, BES reports app status as "Up to date"
My BB has no SameTime client - no icon and nothing in the application list. Have rebooted BB. Still not working.

??!?!?!?!????????!?! It never used to be this hard to get ST working! Do Lotus still make a client?

[pierrebnh]

Make sure the BES' device.xml is current.

Yes, IBM makes their own BB client, which is distributed with their software.