Prior to BES 5, when the Resend IT Policy command was issued from BlackBerry Manager, it would basically be done immediately. That was nice.

I'm noticing now that with BES 5 and BAS, resending an IT Policy to a handheld takes around 15-20 minutes on average.
Looking at the queued task in BAS, I see that Resending an IT policy is defaulting to a "Medium" priority.

Does anyone know how to alter the priorities for tasks? I don't want to wait 15 minutes for an IT Policy update. (Assuming that the change in priority will address this.)

__________________

How does the POLC log look when you trace the command? When does it see the send and ACK?

__________________
http://blog.port3101.org/hdawg/

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

Perhaps it's just me, but does this sound confusing to anyone else?

P.S. - This is quite annoying when not only resending IT policies, but also simply assigning the damn things!

__________________
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.

You can change the job throttling settings by going to Deployment jobs > Specify job schedule settings > Default delay (minutes) and changing it to lower than 15 minutes. However, I believe this impacts everything. I'm trying to see if you can simply revert back to the BES 4.x implementation. I'm all about improving load on the messaging environment, but this change is pretty ridiculous.

__________________
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.

Giddyup! This is what I was looking for.
I think this whole scheduling and task deployment model is a crock.
If we terminate an employee, I want his device locked down now, not 15 minutes from now.

We're a small shop with relatively low BES/messaging traffic.
I set it to 1 minute and will watch it to see if starts to bottleneck.
My guess is I'll be fine.

Thanks, Otto.

__________________

IT commands, such as Lock Device, would still be issued immediately, though. It's just the setting of the IT Policy itself. To be honest, I'm not even sure how setting a device IT Policy could have any impact on the messaging environment. I thought that would have been purely IP-based traffic.

__________________
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.

Problem for us that part of our lockdown procedure is done via IT Policy.
We send a restrictive IT policy to the device which locks down the phone/browser/messaging/etc.

__________________

I'm asking for a 'better way' to revert the behavior of sending the IT policy (either via resend or assignment) as it was with BES 4.x. Something tells me this will be an SDR-based thing. Regardless, for the sake of our current processes, this needs to be flexible enough to allow us to send these immediately if we choose to do so.

__________________
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.