HI All,

I wondered if anyone could help me with a BES headache!
The aim is to upgrade from 4.0.6 to 5.0.3, On a clean server and database (multiple reasons)

Procedure followed

- reset users IT policy to default
- Move using Transporter

This works GREAT!

But I have then recreated some IT policys, When applied to the handsets they can take up to 4 hours to apply. The quickest being 20 minutes (even after forced update)

To make it even wierder, The users that take 20 mins or so are at remote sites, not in the head office in london.....

Network congestion i hear you cry? The users still on 4.1.6 BES, if a policy is changed it updates in around a minute! no matter where they are!

Both servers are in the same rack! same connection! Just different SRP and Id (60 day temp key)

Im going through the logs but cant find anthing untowards..

Can anyone point me in the right direction as there are 160 handsets to move and the IT policys are quite important as it is in the legal sector.

Cheers

Dan

Why not just recreate the IT Policy you want to apply on the new server? When you transport the folks over, put them in the group with the policy already. Once the server reads the device as having a different policy as specified on the server, it should send it out right away and update.

You can also restart the Policy service.

I have tried it that way too, Makes no difference what so ever.

Im going to try it on my test server tomorrow to recreate the issue but im guessing i wont have much luck!

There is absolutley no pattern to it and my client is bouncing around! lol

IT policy distribution has changed from BES 4 to 5. In the management console, check under "Deployment jobs" for the default delay (default = 15 minutes). You can lower that and see if it makes a difference.

You should also check the "Specify IT policy distribution settings" for "Job throttling".

Under "Manage deployment job tasks" you can look at each task and you can probably find out, why it is delayed (dependencies?).

Thanks! thats the one. Its still a bit slower than 4.1.6 but not much.

I understand why they have done it but its not very well documented!