Originally Posted by VIOLATOR
If I am understanding everything - this feature has been disabled by the administrator of the BES from his place of employment.
He needs to get with that individual to see about getting that particular feature enabled.
I hope I am not missing something here but from what you have described that is the solution?
This is not a solution
(see last paragraph). The admin doesn't have the capability to do anything about it.
If no one on this board is willing to give advice or lend a hand, which is painfully obvious considering the number of views this thread has, then here's my fix-all solution:
(P.S.- I'm going to post results when this is done, along with detailed instructions, so that anyone else who needs to do it, can do it, with little to no problem, and without having to touch ANYTHING at the BES level).
--Open phone, to make sure no pins are pulled (none are, thank goodness)
--Back up the DoD Root Certificates (DONE)
--Extract the bluetooth pairing PIN from either the reader or the phone (DONE)
--Extract firmware image. Make backup for "oops" purposes.
--Make sense of code (iffy). Identify portion of code that deals with settings.
--Wipe the firmware, restoring it with the version it already has on there (126.96.36.199)
--Lock setting out from WAP push, or modify settings update switch (if possible, if exists)
--Re-connect smartcard (CAC card) reader.
--Re-install DoD Root Certs
--Assuming coding was at least *somewhat* understandable-- Import critical and non-critical settings into phone (such as phone book info)
--Connect Bluetooth headset
Not trying to criticize, but since I don't hesitate to help others (regardless of the circumstances), I will do the work on this one, document the results, and work on some sort of automation to make this job easier in the future (like perhaps an executable?). And the viewing public of this board (all 200 and-some-odd of them that were interested in this thread, anyway) will get to reap the results.
After having to deal with this for the last two weeks (and the lack of interest...I guess mine is the only brain that cares about solutions to problems like this, everyone else seems to cop out), I am never buying a blackberry. Yes, I've thought about owning one for years. Yes, they're pretty. Yes, they're convenient. Yes, they even deliver email messages in real time (MOST of the time). Yes, I even like them. They're shiny, and I like shiny things with fancy features and lots of buttons (I'm a geek! Surprise!). I do not, however, like shiny things that are a pain in the butt to fix something this *bloody* simple on. Furthermore, from a sys admin perspective (at least, judging by this ONE problem, and the lack of people/online resources to fix it), I'd much rather deal with something else, like Palm, or Windows Mobile.
Blackberry's programming pretty much seems to be shrouded in mystery. I don't like that. When it comes to smartphones, I'm quite happy with my Nokia N95, personally. The next phone is either going to be a Palm or Windows Mobile (GSM). I may yet consider owning a blackberry, but with some of the apps I use, unless the programming changes significantly, forget it.
David, thank you for your suggestion. (However....it's a BUREAUCRACY!!) I did indeed speak with the person in question that handles such things, and she said she doesn't have the ability to change it. She didn't have a problem with it being changed for this person, because of the nature of the work he does. She gave me all the relevant documentation on BES's (which were an interesting read, to say the least), which weren't a help. We can't update the setting via WAP push. If this is successful, the results will be sent to her, so that the other people in this department, with this problem, can get it fixed.