BES OTA Device upgrade reverts to other version?

[eBoyDog]

I'm getting ready to to OTA device OS upgrades to several 8350i's on my BES, on my test BB it had 4.6.1.83..... Ok.

Installed the newer 4.6.1.204 package on my BES, everything was fine, did the upgrade and it reactivated to my BES so I thought all was good.

Now, a few days later, I look at it on the server and it tells me the upgraded device is running 4.6.1.128 which then I check the BB and sure enough, it downgraded to 128 ?!?!?!

What did I miss? And were did it get the 128 version as I never installed it on the server? I have some other 8350i's running 128 but this one that I'm testing with started with 83 so if fo some reason it reverted to the older version, why wouldn't it go back to the version it had?

Anyone with any insight on this?

[bhopkins]

Are you running BES 5?

[eBoyDog]

No, BES 4.1 for GroupWise

[Rh1noo]

This happened to my storm. We are running 4.1.6 internally. I upgraded the firmware and then enterprise activated.

The next day I found out that the firmware had reverted to the earlier version. The software will have come as an over the air update from the network provider but I'm not sure of the settings on the BES to do this.

I'll try and find out and let you know.

[CanuckBB]

The upgrade package is coming from the carrier. You need a newer version of the HH OS on the BES to trigger the update process, bt the code will ultimately come out of your carrier.

You will not be able to push non-carrier approved OS versions OTA,

[eBoyDog]

I believe I was mis-understood....

Device had 4.6.1.83 on it

activated on my BES

Had 4.6.1.204 installed and indexed on my BES as a OTA installed package. FYI (I Believe) when you install it on the BES and all the vender stuff matches, the actual upgrade package comes from the BES, while it can come from your carrier this process from the BES allows the admin to control what OS in on the devices including locking the device by policy so users can't upgrade their BB's on theor own.

Sent the upgrade notification to the device which it received and I started the upgrade to 4.6.1.204

Everything upgraded and it reactivated to the BES, all was good.

Then a couple days later I'm browsing the manager on the BES and I notice that the device I ugraded was now running 4.6.1.128 which, one it never had installed on it and two I never installed it on the server.

????