Hello,

First, thanks Mr. Johnston and Mr. Evers for writing the book. It has been very informative.

I have a question (many actually, but one to start) about OTA "Pushing" of 3rd party apps via a BES 4.x w/ Exchange using an Application Control Policy. Is it possible to control or determine when an application will arrive on a handheld device?

I found Mr. Johnston's PPT here: http://www.ibbug.org/en-us/meetings/...gJJohnston.pps which refers to the "next app push interval" and states "the default app push interval is 4 hours" which gives me hope the default can be changed. Can it? Is it in the BESMgmt DB and hackable or is it on the RIM NOC side and hopeless?

I also read this: http://www.blackberryforums.com/arch...hp/t-3419.html which is consistent with what I experience, but very close to unacceptable. If it can take 12+ hours and you are testing but "never" get an app push, how do you know where the problem is? Is there a trace or log?

Anyway, hopefully you have a "trick" to push an app in some reasonable timeframe and know it got there.

Thank you,

David

Hi David.

You can change the default (4 hour) app push window. Be careful though because you may cause the BES to work too hard if the interval is too low.
Here is what you need to do:


 

• Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\BlackBerry IT Admin Server.
• Create a new DWORD called AppProvisioningPollInterval. Give it a value. This sets the interval to X number of minutes.
• After making this change, restart the BlackBerry Policy Service.

I caution you to be very careful when changing this interval and if you change it on a production BES, do it for testing only, then set it back to default.

If the application never arrives on the handheld, you can look in the logs. They are:
\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs. The name of the log is <Servername>_POLC_<Date>.txt.

Sometimes the device will need to be nuked and reloaded to correct a situation which causes the push to fail.

I hope that this helps.

Cheers.

---
Craig J. Johnston
---

Thank you so VERY much!!! That will really help troubleshoot the issues we are having.

I am hoping this will let me work out way the Handheld Configuration Tool shows incorrect Modules, versus what the Options Applications Modules shows on the actual device. This is causing "Handheld state invalid" Configuration Status and never seems to clear or resolve.

This all relates to a Software Policy that attempted to drop a 2.0 version over a 1.0 and it can't do that upgrade. (The app. is the RSA SecurID soft token).

Thanks again.

David