[funy]

Hi All,

I did a search for this but didnt turn up anything much.

We had to switch on logging for a user who was getting abusive/innapropriate sms messages.

To accomplish this i took a copy of the IT policy and switched on logging using the "Disable sms syc" option and setting to false. Applied it to the user and ensure it had been applied sucsessfully.

This worked great and pulled all the logs through and we were able to forward to the authorites.

Once we were finished and no longer needed the logs i then put the user back onto our normal IT policy and assumeed it would switch off, but during normal checks of the phone logs (i have to do a statistics report) i noticed the users sms messages are still being logged.

I have tried creating another policy and putting the "disable sms sync" to true and applying and then also re-applying our normal policy but still the option persists. The device is definatly using correct policy according to console and device.

we are running Blackberry Professional Server 4.1.4.3 on Windows 2003 SBS.

No other issues apart from this one. Its also worth mentioning the setting has traversed from old handset to new handset at recent switch.

Assuming only option left is to remove and re-add the user.

Any thoughts on this?

Thanks

[WickedBez]

Besides changing the policy... have you tried resending the IT policy to that user? (i'm not sure if they have that option on your BES version)

Also you may want to resend service books for good measure.

[funy]

tried re-sending the policy have not tried resending service books, i will give that a try and post back.

user is in the building this morning so might be able to pinch their device for a few mins to double check things that end

[funy]

ok, tried both of those still nothing has changed :(

time to check the hanset and see what policy it thinks it has.

next step i suppose is to wipe the user account and put back

[-EOS-]

Try setting a new activation password for that user, and doing the Enterprise Activation again.

[bulletooth]

Try restartign the Synchronization Service.

Either that or the policy service does the trick- had this same problem before

[funy]

Hi, I had an email back from my trainer from my BES training (i think he is on the boards here actually) saying to try restarting the policy service.

which i did first thing this morning and it seemed to do the trick. very odd as the console was adament that it was applied and even gave me the time it was sent and also when it was applied hehe.

Thanks