Owner Information disapearing

[Silvan1]

Hey all,

My company has just upgraded all of our BB's to Bold 9700's. We are about 35 people here with them and i've started the upgrades of some people including myself and the CEO. We have an IT policy on our BES (still running 4.3) that restricts users from changing owner information and nothing has changed on the BES.

The CEO emailed me this weekend saying his owner information has disapeared so I re-applied it on the BES. He showed me his phone again today and it is gone. I thought it was just him but then I realized mine was gone as well, I never used to set it before the upgrade so I didn't realize when it had left but i'm going to keep an eye on it now.

Any ideas of where I should be looking? I tried google and came up with absolutly Nothing.

We had a mix of Curves and Bold 9000's before-hand and never had issues with this.

[Silvan1]

so I re-applied the owner information yesterday afternoon. It was still on my phone when I went to bed around 11-11:30 last night. When I woke up at 7:30am it was gone.

[Silvan1]

anyone?

I did further testing and it appears that when the IT Policy is applied it is erasing the owner info.

I tested with a new blank IT policy and same results. The only that I had set in the policy was the Lock Owner information & Name.

I set owner info on the BB. Then after I re-sent the IT policy the owner info erased.

[kylebrophy]

Hi There,

I have the exact same issue.

Its to do with the firmware v5 release on the 9000 Bolds. Also the 9700s come with v5 firmware anyways.

Its not an issue if i downgrade the bolds to the v4.6 firmware (at least the NZ firmware i use).

We are using BES Express Server 5.0.2 - so its not due to the server version.

[pphunkymunky]

i'm having the same issue. just built up a brand new environment and i'm now migrating users across.

exact same thing happens, as soon as the policy is applied, the owner information disappears.

doesn't seem to matter what the firmware revision is on the handsets, 4.5+ to 6.0.

BES 5.02

This didn't happen with BES 5.0.