Quote:
Originally Posted by jimfraser
I am on BES and as Sanders said it is not unusual to need to be reactivated on the server. With my bold, I needed to be reactivated on the server for .167, but with .162, .185 and .190 it reinitialized and reactivated over the air without having the IT guys reactivate on the server. Go figure. However, if you are on BES, I would not upgrade the OS without knowing the IT people are available just in case you need to reactivate on the server.
I am upgrading to .216 now so I will see how this one goes.
|
By the way, I did need to have a new password generated for enterprise activation when going to .216. As noted in a previous post by another contributor, others on BES were automatically reactivated on the server when going to .216. As noted in my earlier post, I did not need reactivation on three previous OS updates. I do not know why some OS updates required reactivation for me and others did not.
My caution remains, if on BES you cannot predict if an OS upgrade will require reactivation, so only do it if you know your IT people are available to reactivate/generate a new password, if required.