Just load the software on the PC, then go to ?:\program files\common files\Research In Motion\AppLoader and delete the vendor.xml. Then connect the BB, start desktop manager and load away. Beware, this will wipe all settings.
I have done this on 8700s, 8300, 8310, 8800, 9000 Bob Fronk * [email protected] From: Jim Majorowicz [mailto:[email protected]] Sent: Thursday, December 11, 2008 6:57 PM To: NT System Admin Issues Subject: RE: Upgrading BES Yeah. I downloaded Altell's 4.5.089 and some instructions on how to upgrade phones using a different carrier's file. I Just need to find a guinna pig phone to try. From: Martin Blackstone [mailto:[email protected]] Sent: Thursday, December 11, 2008 2:19 PM To: NT System Admin Issues Subject: RE: Upgrading BES I think Sprint is behind the times. Verizon is at 4.5 which is a significant upgrade. From: Jim Majorowicz [mailto:[email protected]] Sent: Thursday, December 11, 2008 2:15 PM To: NT System Admin Issues Subject: RE: Upgrading BES Okay maybe that isn't it. One of the pones with 4.3.0.127 is the phone that I've been testing with. When I check RIM's download page for Sprint 8130 Pearls, I see that it's fully up to date as far as that is concerned. I can't even find 4.3.0.170 Multilanguage... From: Jim Majorowicz [mailto:[email protected]] Sent: Thursday, December 11, 2008 2:07 PM To: NT System Admin Issues Subject: RE: Upgrading BES In desperation I started fumbling around *ALL* the google results I've had searching on this. I finally find one message from May in a crackberry forum that suggests that this is an issue with all 8130 (every device in this company) with version 4.3.0.97 which all but two of the units are running. Apparently the fix is to upgrade to 4.3.0.170 (Multilanguage). (The two that aren't .97 are only .127). So my question is now, how do I upgrade the firmware on these phones? Is this something I'm going to have to touch each phone for, or is this something I can push from the BES. Seems to me that would be something I could do from the server. From: Jim Majorowicz [mailto:[email protected]] Sent: Thursday, December 11, 2008 1:42 PM To: NT System Admin Issues Subject: RE: Upgrading BES What was frustrating was I downloaded it twice with the same result. The third download was to my x64 system at home, where I was able to then extract the files just fine, but it didn't solve my original problem. I haven't applied the Service packs yet, as I need to wait for a time when I can handle the restarts. The software is installed on a SBS 2003 R2 (full patched through Nov.) server, so the CDO.DLL file has to be the same as it's the same server. Any clue if this is a Blackberry or Active Directory issue? I could open a case with either vendor, but I'm afraid if I pose that same question to them they'd just point the finger at the other. I'd say this was definitely a blackberry issue, but the fact that meeting requests from me (an outside domain), the administrator account and my test user account all work fine is driving me nuts. It seems to be inter office requests. From: Martin Blackstone [mailto:[email protected]] Sent: Wednesday, December 10, 2008 7:08 PM To: NT System Admin Issues Subject: RE: Upgrading BES I would be willing to bet the download is corrupt. There is no reason it wouldn't run on 32 bit machine (since that is what BES runs on). A couple of other things that come to mind in regards to meeting requests are permissions and perhaps even the BB OS version on the handheld. Everyone should hopefully be at 4.2 or higher. Then of course also verify that your CDO.DLL files on the Exchange server and BES match. From: Jim Majorowicz [mailto:[email protected]] Sent: Wednesday, December 10, 2008 6:16 PM To: NT System Admin Issues Subject: Upgrading BES I've got a Blackberry server that for whatever reason, doesn't always forward Meeting request emails to the phones of some of the employees. But it only seems to occur between certain users. I can send meeting requests from administrator or newly created users, but not other users. I was going to try upgrading the server (4.1.4.15) to 4.1.6 then apply the two SP, but for some STUPID reason the 4.1.6 updater file doesn't want to run on a 32-bit machine. Anyone have any ideas? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
