[OliG]

Hi all,

I tried to activate the 'Content Protection'-Policy (Level 0) on some handhelds and finally found out, that it was not such a good idea. I already knew before that performance will suffer, but I never thought that it would be in a that massive way (particulary on the 7730 Model). There are some other known adverse effects like over-the-air-password-resets and not mapping names of incoming phone calls when locked.

Due to the performance lack I decided to turn it off again, but:

After disabling the encryption, the 'set password and lock'-function in Adminpanel still does not work. More precisely, the handheld still demands for the old password first. Could it be, that once enabled (and later disabled) the handheld effectively keeps that existing data encrypted and must be killed if someone would lose his password?

Thanks in advance for your help
OliG

[Ekrimmer]

A password, once set, remains even if the policy requiring it is disabled. In our situation for example, we require passwords. However, when a user leaves the firm I send a default policy to their BB. This doesn't remove the password but removes the requirement for it (the user can now turn off the password requirement). Perhaps this policy is similar - I don't have specific experience with Content Protection.

[OliG]

Thanx for answer, Ekrimmer.

That would mean, the encrypted data is locked forever (because no policy can unlock content - they only could define that further content will not be encrypted anymore). but actually I don't need the data - I just want to get the ability to reset passwords over the air again.

Well, in the meantime I've killed one the affected devices. after reactivation it got the same policy like it has before (with content protection disabled). now a reset over the air is possible again.

Can it be true, that I really have to kill and setup all affected handhelds to get rid of that password-issue?

[vdw4u]

Did you find a resolve to this problem because I have the same situation.

We enabled the content protection policy and then found out about the password issue.

I have more than a thousand users and I know all of them will not follow the instructions on how to disable.

I cannot believe RIM did not give a workaround for this problem.