I am trying to create a method for the bloomberg software to run through its monthly update process, without having to open up the policy for 3rd party app downloads. I set up a whitelist, but I noticed that after bloomberg updates itself, the policy removes the icon as the version isn't the same as the version specified in whitelist. Have any of you seen this? Any ideas on how I can let this software update monthly without completely opening up those users?

thanks in advance,

Paul

Anyone have any ideas here? Has anyone worked with Whitelists at all?

yea, welcome to he!!. I been going the rounds with RIM on this since I got back from WES. They are supposed to be escalating it, but I haven't heard from them in a over a week. The whitelist doesn't work in my opinion. They are very specific on how you are supposed to use it and it is more of a pain than it is worth. They told me that the idea is that you set up the whitelist, apply the software config to newly activated devices and never touch it again. it doesn't allow for upgrades easily. I was using google maps to test it.

I had it installed on my device manually, I set up the whitelist and applied it and it removed the app from my device - actually, all the devices because I got a bit overzealous (lesson learned). I was able to push it back down after upgrading the software on the server, but not in whitelist format - just a push with no policy.

If I set up a software config with no policy and it is the same version as what's on the device already, it comes up "up to date" if I set it up as a whitelist, it removes the app no matter what version was installed. If I apply the whitelist to a newly wiped and reactivated device (apps manually removed), it installs all the apps.

I am convinced that there is some flag or something in the DB that is not talking correctly because once the whitelist has removed apps, I can't use software config to push them out again unless the device is wiped and reactivated. RIM tells me that it is part by design due to data usage and server resource usage considerations. I informed them that I am in the US and unlimited data means unlimited data and I also have a server that isn't in any danger of being overloaded. At that point, they offered to escalate. I should call them today. This has gotten me all riled up again...

Cliffs: software config doesn't work like we all think it should and RIM thinks that is OK.

This why I haven't contacted T-support yet. I spent 3 weeks with them trying to figure out how to remove sametime, only to find out that sametime can't be removed remotely, because it is considered a RIM app, and RIM apps can't be removed remotely.

That run-on sentence doesn't even begin to describe my frustration.

I seem to remember a conversation like this over lunch one day. And we still dont have a resolution! HA!

It was partly that conversation that got me looking into it. And glennco, I hear ya on the frustration. I have been practically pulling my hair out while trying to be polite to the CSR. I even changed the push time on the server so that I didn't have to wait the 4 hours every time I made a change, but since it is a hack, they made me wait anyway. grrrrrr.

The solution is so obvious it hurts

The device needs to be able to see the difference between an OTA/desktop manager install and one pushed from the BES.