Hello,
I have a new 8800 which works fine when not activated. The software Telmap which comes with the device for a one week test period recognizes the internal GPS and shows the map. As soon as the device is connected to a BES 4.1 SP3 HF1 and Exchange environment the Telmap software is telling me that the GPS device is not connected. The same with other GPS software like Spot.
To me it looks like that an IT policy or application policy prevents the information transfer between the internal GPS and the GPS application. Unfortunately I have not found any policy which reflects this setting.
I tried also a blank policy and moved my account but no difference.

Any ideas?

Thanks a lot.

Kind regards

I've moved this to the BES Admin Corner in the hopes that someone there will be able to help you out.

~John

According to the policy reference guide on the RIM site:
BlackBerry_Enterprise_Server_Policy_Reference_Guid e.pdf
as you suggested it is possible to restrict access to the onboard GPS via an application control policy, but as that's not how Telmap got there I can't see that it can be that.

I'm guessing, but the next place to look might be in the security policy group of the IT Policy that you have applied (even if it's the default one it's possible that it has been modified). Maybe one of the options in there could prevent access to the GPS? I'd have a look for settings that are not the default - the PDF should show which are the defaults, and if I remember correctly the help on the BES manager does too.

The same issue applies to Bluetooth keyboards. They work fine with BIS, as 'event injection' is allowed by default, but if you are using BES, 'event injection' is disabled by default, and you have to create a software configuration for the Bluetooth keyboard driver, with an application control policy that allows event injection.

We don't have any GPS BB's, but I noticed there is a 'Device GPS' setting in the Application Control Policy. Maybe you should try to create a software configuration for the GPS application, and make sure 'Device GPS' is set to 'Allowed'.

Our BES has this set to 'Prompt user' as default, so maybe this is not the problem anyway..