[JRV]

Setting up BES v4 + SP1 + Hotfix 1, BBs are v4.

We want browsing to go through our proxy server. Regarding the "Allow other browser services" IT policy, BES docs say:

This rule specifies whether users can use other browser services on the handheld...Set this rule to false to force all browser traffic through your organization’s BlackBerry Enterprise Server and prevent users from installing other browser services.

That sounds like exactly what I want, so I set it to FALSE. Thereafter, all BB web browsing fails with an HTTP 400 error: Bad request. When I remove the policy or set it to TRUE, browsing works normally.

I know browsing is going through our proxy because our proxy is prompting for credentials. Also, if I get a 404 error, it's our proxy's custom 404 page.

What does this policy really do?

[jibi]

Its because they are using the provider's browser instead of the MDS/BlackBerry Browser.

[JRV]

Thanks for your reply. That raises several questions--

1. How do I verify that? FWIW, the icon you click on the BB to use the browser is labeled "BlackBerry Browser".

2. How do I change it (hopefully from BES) to use the BB Browser instead of Nextel's?

3. If using Nextel's browser means we're getting web access through Nextel, why am I prompted for credentials by our proxy server?

[bfrye]

I think if you disable other browser services, it will hide/remove the icon for your carrier browser. That's what it did for our TMO/ATT/Cingular devices at least.

[JRV]

Thanks for your reply.

The only browser icon that's ever been visible on the BB, regardless of the IT Policy setting, has been the one labeled "BlackBerry Browser".

[corey@12mile]

All you need to do for this is to put in the Proxy info under the MDS Server properties on your BES server. It's pretty straight forward.

If you do have a WAP browser and/or IBS on the handhelds, those both have entries in the IT Policy to disable/remove/hide them.

You may have to fiddle with the username and password for the proxy setup on the BES server if you use domain based authentication for your proxy, but other than that it's all pretty straight forward.

cd.

[JRV]

The policy seems to be working correctly now. I'll have to chalk up the fact that browsing worked for the 1st time when I removed this policy to coincidence. I must've changed something else at the same time...sure wish I knew what it was!