Well the push ended up being a package problem. Since we are BB newbies, we tried to get too smart - we opened the package and did things like take out language packs. Tried again with the package as-is from RIM and it went out fine. A couple of devices we had to push 2x but it's there.
Now the problem is the BB will send but not receive. Baby steps :) On Mon, Oct 20, 2008 at 11:48 AM, Bob Fronk <[EMAIL PROTECTED]> wrote: > IIRC, sometimes the OCS client will not install by push if the Blackberry > Messenger is in place. > > > > We have had a similar issue, sometimes the client installs, sometimes it > does not. I have not spent a great deal of time on it. We normally do not > send a BB out without the OCS client installed. (We connect it to a desktop > to get the software and activate for the user before issuing it) > > > > Bob Fronk > > [EMAIL PROTECTED] > > > > *From:* Kevin Lundy [mailto:[EMAIL PROTECTED] > *Sent:* Friday, October 17, 2008 4:31 PM > *To:* NT System Admin Issues > *Subject:* blackberry and OCS > > > > Has anyone managed to get the Blackberry for OCS client installed and > working? > > > > We installed the latest BES. Configured the options for OCS and are > getting no errors on the server. So we then went to install the client. > Pushed it out to 3 devices from the BES. Made it mandatory. > > > > I watched my 8830 and it had lots of data activity and then ... nothing. > Same thing on the other devices. BES reports "up to date". > > > > We've only been using the BES for about 3 months, so it is very likely > something we are doing wrong, or not doing. However, we have pushed other > softare using the same steps. > > > > Thanks for any pointers > > Kevin > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
