Hi All!

I've searched high and low for this, but haven't been able to find exactly what I'm looking for, with regards to disabling a Blackberry user's application permissions.

My environment:

BES 4.1 (SP 7)
Exchange 2003
Windows Server 2003

I have a test BES server setup with a development environment for a shop working on a Blackberry utilities application. Some of our users that are on BES themselves have noticed that when installing the app, when asked to set permissions, they are entirely greyed out / disabled.

From what I understand, this is a software configuration on the BES server. However, I set one up (one with disposition set to "disallow" and all permissions set to "deny"), pushed it to the user and set their configuration status, waited the up to 4 hours and...nothing.

I know (think?) I'm doing something completely wrong. Maybe this isn't even possible or something, since I'm not pushing applications down to the device through BES. But my understanding was, with this type of a config, user's would not be able to assign permissions to any application they just downloaded - and those that are pushed down from BES would have the default app permissions configured in the ACP enabled.

Help!

Thanks!

You're understanding is correct. You need to configure a bare software configuration (point it to the directory and assign it to an application control policy). The application control policy should be configured as you mentioned, although I would change it to Optional (if it was set to Disallow, it should disable the application completely rather than only the permissions for it). Once you assign the software configuration to the user, right-click on the user account and choose Deploy Applications (this bypasses the 4-hour wait time).

For BES 5.x, there's an unlisted applications policy that can be configured separately. This is more obvious and much easier to configure now.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Otto - thank you so much for verifying!

I've done exactly that, and also updated my device.xml and vendor.xml files and installed the latest device software on the BES server. However, for some reason the application event logs are showing:

HHCM_DEVICE_NOT_SUPPORTED

From what I understand, this indicates the actual device isn't recognized by the BES itself? Not sure why I would still be seeing this after updating the XML files and re-running loader.exe /reindex (just to be sure)?

Thanks again!

I had made a mistake in the software configuration process and got the error I posted previously to clear by sharing the folder:

c:\program files\common files\research in motion

And NOT the folder:

c:\program files\common files\research in motion\shared

I then ran loader.exe /reindex from the cmd line.

However, it doesn't seem to have taken. The device still allows all software permissions to be set at the user's will - for all existing applications on the device as well as new applications downloaded on to the device....