I'm trying to use 3rd Party IT Policy to control an application of mine, and when we upgraded to 4.0.2, we found that changing 3rd Party IT Policy stopped working (we could assign the policy but not alter any of the existing items in it). [This is all BES for Exchange]
We discovered that SDR 44122 in the release notes for 4.0.1 and 4.02, which documented the above issue as known. The hotfixes for 4.0.2 make no mention of it.
The release notes for 4.0.3 and 4.0.4 make absolutely no mention of the issue, either as known or resolved. Now, before I go crazy trying to test this, does anyone know if this issue was just completely ignored by RIM (which wouldn't surprise me, given the shoddy state of the release notes) and it magically went away, or has it been fixed? Anyone else run into this issue?
(from the 4.0.2 release notes)
"BlackBerry Policy Service
SDR 44122
When you assign an IT policy that contains custom policy rules to a handheld that previously had an IT policy assigned, the IT policy is not sent to the handheld. An error is written to the BlackBerry Policy Service logs.
Workaround: Make the handheld unavailable. Delete all stored information from the handheld. Assign the custom IT policy to the user. Reactivate the handheld.
Note: Back up all handheld information before making the handheld unavailable and deleting all of the stored information."
(the procedure is pretty vague... grr)
[edit] Just read the SP5a release notes, and it has a few policy related fixes. It looks like I'm going to have to do another upgrade ASAP, because I need this functionality to just work, like it did back in 3.6.5
(Yeah, all the timestamps on IT Policy status are like, 30 years in the future)
I'm downloading SP5a right now, will install soon. Of course, the downloads from RIM are about as fast as cold maple syrup... (HA HA Canadian joke)
[edit2] Oh, what do you know. SDR 44122 is in 4.0.5a release notes. I wish I didn't have to support and deal with RIM's crap. WM5 looks better every passing minute. It looks like I'm going to have to get my customers set up for disappointment.
[edit3] Does anyone with 4.1 (HF1 or not) know if this issue still happens? Because, as usual, the release notes from RIM for 4.1 DON'T MENTION IT. WTF!? It magically goes away!
Last edited by DoomBringer; 07-18-2006 at 01:57 PM..
No one should be running 4.0.2. it was pulled from RIM's website not long after it was released. Havn't yet heard any issues with SP5a.... But SP4 HF3 is also a good one.
In regards to your exact issue. There are a few things missed in the release notes that are fixed but not sure if this is one of them.
Hate to necro-bump (that is, post to a thread that is long dead)...
I'm running 4.0.4 (HF2) and the issue still seems to manifest itself. I will do more testing and try an upgrade to 4.0.5, but I'm expecting the worst.
Not to bump my own thread a zillion times, but I've been going through support on this issue.
So far, I've upgraded the MDAC installed on the machine, and updated a device to 4.0.2 of the OS. This resolved it for that device in particular, however, not all carriers have released 4.0.2, so I could not upgrade them all (I'm not going to hack vendor.xml, as it isn't a feasible solution for my purposes).
Anyone else who runs into this issue should note that OS 4.0.2, 4.1, and 3.7 all received the IT Policy updates without issue. Though the 3.7 devices seemed to die randomly. I suspect a packet of death was causing them to die.
SDR 44122 - 3rd Party IT Policy
