[MarkF]

Didn't even try to rollout the DST patch, was still reeling from upgrading from v3.6 to v4.1.2 and the nightmare of having 5000+ devices wirelessly activating for the first time. We're down to 200 or so users whose activations hung and have to be individually contacted to re-activate.

I considered just sending users to RIM's website to wirelessly download the patch but after sending a group of 30 there and getting back 25 questions, I gave up on that idea. Good thing is I canlearn from everybodies experiences and be ready for the fall DST.

[DarthBBerry]

Originally Posted by MarkF

Didn't even try to rollout the DST patch, was still reeling from upgrading from v3.6 to v4.1.2 and the nightmare of having 5000+ devices wirelessly activating for the first time. We're down to 200 or so users whose activations hung and have to be individually contacted to re-activate.

I considered just sending users to RIM's website to wirelessly download the patch but after sending a group of 30 there and getting back 25 questions, I gave up on that idea. Good thing is I canlearn from everybodies experiences and be ready for the fall DST.

Don't mean to be rude, or overly blunt... but OMG ARE YOU FREAKIN' KIDDING ME?!
How are your devices synching info without the correct time?
Did you patch your server?
How do you expect to correct this problem with the fall DST "fallback" when the devices will revert to the ~correct~ time?
Have you even tried the wireless rollout to a few test devices?
If you sent to 30 and got 25 questions, were they the same questions? (If so, then your directions were... well... umm... slack.)

Jeez man, you're trying to put water on a fire that's already burned the building down and been extinguised!

[ladydi]

Originally Posted by stuwhite

This is gonna sound stupid but can't you just disable the app install deny like we did for DST, or is this a compliance thing for you guys?

I did. My DST rollout went great. I threatened the lives of my users to prevent them from installing anything and disabled the policy for the short amount of time it took to push DST.

My concern was over FUTURE rollouts for new devices (assuming they are on OS that doesn't include DST updates) - I really should create a new thread because it has morphed into a different topic. I'm just lazy Perhaps next week...