[DarthBBerry]

Now that "the date" has passed, I've been reading posts about the failures that occured and the ongoing issues still being experienced. Some of us have to have success stories in our environments. DST couldn't have dropped it's drawers and taken a big ol' [insert excrement here] on EVERYBODYS Blackberry Server, Desktops or Devices.

Let's turn that frown upside down and put on a happy face!
(Maybe we can get a sticky for this? *HINT HINT HINT*)

I'll go first.
I started studying the DST changes back in the first week of January. Waited and waited for RIM & Micro$oft & Lotus Notes to release patches/hotfixes/etc. When they finally did, I again waited and waited to deploy. I watched the Forums and the updates to the RIM patch site. Only when I was sure it was mostly correct, did I attempt to deploy to a small group of folks. Out of those 4, only 2 worked. I tweaked the deployment and updated to 2.2 on the patcher. I send another deployment to my 2nd test group of 15; less than an hour later, 14 of the 15 worked! EUREKA! I found the formula that worked!

I wrote an e-mail to the Blackberry users describing what they would see, when they would see it, and what actions they needed to take. Finally, I described to them how to verify the patch and who to contact if it was not there. I set up the server to wirelessly deploy the patcher to a group of 25 devices at the end of the day and hoped for the best. Next morning, most of the devices had patched. Seeing as how the process was working, I deployed to the next group of 100. Most of those patched before the end of the day. And so the process continued in batches of 100 until everybody had a DST configuration listed next to their name in the Handheld view.

After the mass e-mail and deployment, I monitored the server and the Query tool to see who got the update and who didn't. Folks who showed Awaiting Patch received an e-mail from me asking them to check their devices and let me know if it was really applied. Folks with errors were asked to contact me individually for a walk-thru of a fix depending on their situation. The ones where Helper not installed was showing on the Query report were badgered by several e-mails to "turn your device on!" Some did and some didn't.

Overall, my deployment was VERY successful. Out of all my devices spread around the organization:
3 - Helper not installed ("Turn your Blackberry on!")
1 - Error

All the rest are PATCHED and functioning as they should.
During this entire process, I also had to patch Commontime mSuite Admin Console for Lotus Notes, several Windows Mobile 2003/2005 devices and a variety of Palm OS devices. Not only did the mSuite software need to be patched, but the DEVICES needed patching. Although there weren't as many of these as the Blackberry group, there were still enough of them to be a pain in my [insert body part here]. I haven't heard any of these folks screaming yet, so I'm guessing they're OK.

Anybody else want to share?
I'm DarthBBerry, and I'm a Blackberry Systems Administrator and Telecom Ninja. And I DO NOT have a Blackberry DST 2007 problem any longer.

[Davidland]

Glad to see you had some luck, I haven't

would you mind posting what you forwarded to the users what they would see happen

I am going to attampt once more the dst update but last time it failed atthe apploader section I followed all processes and then when i went back into blackberry manager they werne't listed like they were suppose to be. ANy thoughts on this

Thanks

[DarthBBerry]

Originally Posted by Davidland

Glad to see you had some luck, I haven't

would you mind posting what you forwarded to the users what they would see happen

I am going to attampt once more the dst update but last time it failed atthe apploader section I followed all processes and then when i went back into blackberry manager they werne't listed like they were suppose to be. ANy thoughts on this

Thanks

Originally sent 03/01/2007

Hello Blackberry Users!

We have recently updated our Blackberry Server software to be in compliance with the new Daylight Savings Time changes coming up on March 11, 2007. An update to your device is also necessary to accommodate these changes. We will begin deploying the 2007 Daylight Saving Time patch (DST 2007 Patch) to your Blackberry devices. Over the next few days, please keep these steps handy in case you need to refer back to them. While you may not see these results immediately, you should check your device daily until March 7, 2007 to ensure the DST 2007 patch has been applied.
What does this mean to you?
For some folks, you may receive a message to reset your Blackberry device similar to the one on the right.
(See pic attached dst[1])

Step 1
If you do receive this message, please select [Yes] and reset your device.

After the Blackberry resets, you will see the hourglass appear on the screen for 10-15 minutes. This is completely normal. The Blackberry is installing the Daylight Savings Time Update Patch.
Step 2
After the Blackberry has completely reset and is back to the main screen, please confirm that the Patch has been applied successfully. Scroll to the Options icon and click the trackwheel.
(Insert pic of Wrench here)

Step 3
At the top of list, you should see a listing for 2007 DST Patch.
Click the trackwheel on 2007 DST Patch.
(See pic attached dst[2])

Step 4
You should see 2007 DST patch applied.
(See pic attached dst[3])


And now you're done. Your Blackberry is now patched and ready for the Daylight Savings change on March 11.
If you do not see the message to reset your Blackberry, please continue with Steps 2 - 4 to verify the 2007 DST Patch has been applied correctly.

Between now and March 7, 2007 you should see the "2007 DST patch applied" message on your Blackberry device. In the event you do not see the "2007 DST patch applied" message by March 7, 2007, please contact the Help Desk at [INSERT NUMBER HERE].

[thunderck]

300 BBs with only 1 Help Desk call! All updates through 'Push'. I got some help off this BF on setting up the ENV for Push software updates. (Application(s) folder not Application) <--- Those that set this up will know what I'm talking about. So thanks BF for the help!

[halflife78]

I consider my story a success so here it goes:

I had no idea any of this had to be done so when I finally came across it I setup the original version of the OTA push and did a test bed of 20 devices. All 20 worked fine so I did an OTA push of about 400 devices with the original verison that came out.

We patched everything out of order, the Outlook crew updates all their stuff first, then I upgraded to the newest version of BES, then I did the CDO.dll update, then the Outlook calendar thing was ran, and we have had the "send as" issue for new hires forever and we are finally working on fixing it to set automatically.

I sent this out twice before pushing the OTA portion out:

Blackberry Daylight Savings Time Patch

All,

We are pushing out a wireless patch over the air to the blackberry devices to update them for the upcoming daylight saving time change. This patch may ask you to reboot the device, if it does please let the device reboot to enable the patch. This reboot could take up to 20 minutes depending on the device so be prepared for your device to be out of service for a few minutes. You can select no for the reboot if you are unable to do so at that time due to a call or meeting and the device will re-prompt you in an hour, please note though after the fourth attempt to reboot the device will automatically reboot itself.

If you have any issues with your device after this patch is installed please shut the device down and pull the battery out for about 2 minutes to reset the device, if this doesn’t resolve your issue please email or call the IT Help Desk and submit a ticket. Please pay attention to upcoming calendar events and so forth that they are retained on the device after the patch. Please check your time after the device is updated and make sure it retains your time zone, if the time zone changes please go into the data/time option and manually change your time zone back to the correct one.

Thanks,

IT Telecom Department


And then after I completed all 400 users I sent out this on Friday twice:

Attention All Blackberry Subscribers,

We have completed our over the air push of the daylight savings time patch that was required to update handheld devices for the upcoming adjustment to daylight savings time. To check and see if the patch is loaded on your device you can go to the tools/options area of your device and the first item under settings should be “2007 DST Patch”, go into this and you should see that the patch is applied.

If you do not see the patch applied to your device you can you go the following link and load the patch through the internet, please have your device connected to your PC through the supplied USB and cable and have desktop manager turned off if you use this application:

BlackBerry

You can also manually change the time back an hour yourself if you choose to do so or if you don’t have the patch loaded on your device. Please closely monitor your calendar appointments to ensure you don’t have any issues with appointment times once DST occurs also.

Thanks,

IT Telecom Department


So far today I have had only 1 person that didn't update and they ran the link above to fix that issue.

During the upgrade I had about 5 devices that needed to be reloaded.

All in all I consider this a success.

[DarthBBerry]

halflife78 - gooood e-mails you sent to your folks.
Gratz on your successful deployment!

[murpheous]

Everything patched flawlessly.

10 BB users, I emailed them with a link to d/l the DST patch to their handhelds.

I pushed the Xp patch via logon script.

Domino was cake to patch, luckily we dont have exchange/outlook.

[DarthBBerry]

Originally Posted by murpheous

...10 BB users...

10? 10? Sheesh. I wish I only had 10 to deal with! LOL

[murpheous]

I'm happy with 10

[juwaack68]

What do you get when you add:
625 devices + 4 servers + countless hours swearing?

Zero support calls on March 12th. Priceless.

Of course, my phone IS forwarded to voicemail, so that stops the annoying ring....

[DarienA]

Well as some of you will recognize my nick I haven't been active here til a bit before this whole process started. I'd been doing the research following the notes and preparing for the AD side of the update for awhile, but need to wait a bit til the RIM stuff got in to full swing, asked and answered questions here as we moved through the process and finally did all my patching.

Today I received the following email from one of our senior associates:

"I was in a meeting this morning where the initial discussion focused on the computer scheduling problems that most all of the others there were having. The others were from large development companies, and law firms. Speaking for myself, all of my dates, times maintained their correct locations. I just want to say thanks to you guys for making that happen without any problem."

Only one of our servers required a reboot on Sunday(it was a Win 2000 server) to get the correct time, and no handhelds have reported problems. A majority were patched wireless, some that failed wirelessly were then patched via USB cable.

To date, 0 problem calls associated with DST.

Thanks to all the folks who answered questions here when I had them. I hope to be able to shake some of your hands at WES if I get there this year(it's back up in the air again apparently, though after this DST work I'd better get approval!).

RIM and MS didn't make this process easy.

[val7250]

For the most part everything here went according to plan, we have had a few issues with laptop users who didn't get the updates because they weren't plugged into the network. As for BB issues we have an issue with users on a different domain keep getting a red x. But that deserves a new topic to be made.

[BB1877]

My situation was 400 users on a 2.2 for Domino BES. Half were North America based, half International. (4.1 puts too much traffic on our network when hitting remote mail servers.)

So I had to backup a step. There were no patches for 2.2, so this was a good excuse to pitch for a new server. Got the hardware in and loaded BES 4.1.2 HF3. Got that up and running on February 9th and moved myself and one other guy and played with it over the weekend.

The week of February 12th, I moved over a group of users from my department to get a feel of the new server, the OTA features (read/unread/forward/delete marks), how to use EA, and how to push the DST2007 patch OTA.

On February 16th, RIM released SP3 for BES 4.1. I pondered that over the weekend and went ahead and installed it on the morning of February 19th.

With my new BES in place, I expanded my pilot to the rest of the IT department with few issues. Next, I camped out in the exec hallway one morning and got them moved and patched.

Then I took an export of my remaining 170 or so users on the old BES and started sending out e-mails. It was a lot at once...I need to move you, you will have to reactivate with EA and then get this DST patch. Oh and by the way, you won't need to use BBDM anymore and there's a bunch of new features I don't have time to explain yet.

This process shook out a some old handsets running 3.7 that didn't have EA, and 7100's with 4.0 that were kind of shaky etc. I was still able to get them running using Desktop Manager.

Really got running during the last two weeks...moving up to 20 people a day. In the end, 169 of 206 made it to the new server in time. 161 of those were able to be patched OTA. Only one device that should have been fine failed this morning...an 8700 that got the patch but didn't reset.

This morning I'm getting e-mails from some that ignored the e-mails to migrate but I think given the short timeframe it was a success. Once I get the rest mopped up I know I'll appreciate having my North America users on a 4.1 BES!

[mahoward]

OTA'd the original 1.5 code to about 50 IT folks, got an 80% success rate. Not too good. Got ready to push to everyone, but just then 2.2 came out. Crossed my fingers and pushed 2.2 w/o any testing.

Worked pretty well, over a few days got about 90% of 1700 handhelds. Then sent an email to the regional IT managers with an excel spreadsheet of those 200 ppl with issues to have their local folks follow up, with instructions on how to manually install. Been seeing the stats go up since, now at about 96%, with the remainder being folks who never turn their device on. Oh well!

Overall, not as bad as I initially thought it was going to be!

Here are my leftovers FYI:

4.0.2.49 1.8.0.142 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.286 2.0.0.123 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.286 2.0.0.123 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.286 2.0.0.123 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.286 2.0.0.123 2.2 Awaiting Patch 0x00 0x00 200
4.0.0.204 2.0.0.28 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.2.0.64 2.2.0.37 2.2 Awaiting Patch 0x00 0x00 0
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.0.0.185 1.6.1.48 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.321 2.1.0.26 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.3 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.3 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.3 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.3 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.3 Awaiting Patch 0x00 0x00 200
4.1.0.268 2.2.0.112 2.3 Awaiting Patch 0x00 0x00 200
4.0.2.49 1.8.0.142 2.3 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.268 2.2.0.98 2.2 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.3 Awaiting Patch 0x00 0x00 200
4.1.0.284 2.0.0.120 2.2 Awaiting Patch 0x00 0x00 200
4.0.0.185 1.6.1.48 2.2 Awaiting Patch
4.1.0.346 2.0.0.143 2.2 Awaiting Patch
4.1.0.309 1.8.0.146 2.2 Awaiting Patch
4.0.0.219 1.8.0.129 2.2 Awaiting Patch
4.1.0.346 2.0.0.143 2.2 Awaiting Patch
4.1.0.346 2.0.0.143 2.3 Awaiting Patch
4.2.0.64 2.2.0.37 2.2 Awaiting Patch
4.1.0.284 2.0.0.120 2.2 Awaiting Patch
4.1.0.346 2.0.0.143 2.2 Awaiting Patch
4.0.2.69 1.8.0.142 2.2 Awaiting Patch
4.0.2.49 1.8.0.142 2.2 Error 0x88 0x00 200
4.2.0.42 2.2.0.28 2.3 Error 0x43 0x00 503
4.0.0.185 1.6.1.48 1.5 Error 0x8D 0x00 200
4.0.0.185 1.6.1.48 2.2 Error 0x8D 0x00 200
4.1.0.346 2.0.0.143 2.2 Error 0x85 0x00 0
4.1.0.309 1.8.0.146 2.2 Error 0xFF 0x00 0
4.1.0.284 2.0.0.120 2.2 Error 0x88 0x00 200
4.0.0.185 1.6.1.48 2.2 Error 0x8D 0x00 200
4.1.0.309 1.8.0.146 2.3 Error 0x8D 0x00 200
4.0.2.49 1.8.0.142 2.3 Error 0x8D 0x44 200
4.0.2.49 1.8.0.142 2.2 Error 0x87 0x83 403
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.2 Error 0x41 0x83 200
4.1.0.309 1.8.0.146 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.2 Error 0x41 0x83 200
4.0.2.32 1.8.0.137 2.2 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.2 Error 0x41 0x83 200
4.0.2.69 1.8.0.142 2.2 Error 0x41 0x83 200
4.1.0.346 2.0.0.143 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.0.2.69 1.8.0.142 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 2.3 Error 0x41 0x83 200
4.1.0.284 2.0.0.120 N/A Error 0x87 0x88 0
4.1.0.284 2.0.0.120 2.3 Error 0x87 0x88 0
4.0.2.49 1.8.0.142 2.2 Error 0x87 0x88 0
4.1.0.309 1.8.0.146 2.3 Error 0x87 0x88 0
4.1.0.284 2.0.0.120 2.3 Error 0x87 0x88 0
4.0.0.215 1.8.0.127 N/A Helper not installed
4.0.0.215 1.8.0.127 N/A Helper not installed
4.1.0.346 2.0.0.143 N/A Helper not installed
4.1.0.346 2.0.0.143 N/A Helper not installed
4.1.0.309 1.8.0.146 N/A Helper not installed
4.0.0.185 1.6.1.48 N/A Helper not installed
4.1.0.346 2.0.0.143 N/A Helper not installed
4.0.0.185 1.6.1.48 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.346 2.0.0.143 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.346 2.0.0.143 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.194 2.0.0.90 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.1.0.346 2.0.0.143 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
4.0.2.49 1.8.0.142 N/A Helper not installed
4.1.0.284 2.0.0.120 N/A Helper not installed
N/A N/A N/A No device info
N/A N/A N/A No device info
N/A N/A N/A No device info
N/A N/A N/A No device info
N/A N/A N/A No device info
4.2.1.72 2.3.0.54 2.2 Patch not required 0x00 0x00 0
4.2.1.72 2.3.0.54 N/A Patch not required
4.2.1.72 2.3.0.54 N/A Patch not required
4.2.1.72 2.3.0.54 N/A Patch not required
4.2.1.72 2.3.0.54 N/A Patch not required
4.2.1.72 2.3.0.54 N/A Patch not required
4.1.0.377 2.0.0.152 N/A Patch not required (Optional patch available)
4.1.0.377 2.0.0.152 N/A Patch not required (Optional patch available)
4.1.0.377 2.0.0.152 N/A Patch not required (Optional patch available)
4.1.0.377 2.0.0.152 N/A Patch not required (Optional patch available)
4.1.0.377 2.0.0.152 N/A Patch not required (Optional patch available)
4.1.0.377 2.0.0.152 N/A Patch not required (Optional patch available)
4.1.0.377 2.0.0.152 N/A Patch not required (Optional patch available)

[m4ilm4n]

Ours went pretty smooth. I had a 7290 user that had to manually reboot, but the rest went OK over the air. The domino servers were a bit cumbersome (install OS patch, reboot, install upgrade, reboot, install fixpack, reboot), but overall it went well with no real big issues on the messaging side.
__________________________________________________ _____________
Domino 7.0.2FP1/BES 4.1.3, only 15 8700cs (and a lone 7290), but growing

[dmbascfan]

I have 1000+ Blackberry users and by the time March 11th came around, we had just under 800 devices patched. Aside from the fact that four versions of the DST Query tool didnt report correctly, it went well. I sent an email out to the 200 some-odd users who didnt appear to have the patch, and my phone started ringing off the hook...LOL.

All in all, I think 80% is a pretty good result.

[chubby_nubby]

Out of 1800 BB's I have only heard from 2 user's one who did not reboot his device, and the other bought a new device on Sunday and wondered why it did not have the patch ..because your old device got the patch . .lol But since the Query Tools did not work I just sorted by Creation time and scrolled manually through to verify the patch went through, and installed on their devices. Took a while but it was worth it.

[mavsx]

i only had 40 handhelds, did not push it out. i used their blackberry browser and went to blackberry.com/dst2007 and did it that way, took about 2 minutes, but hey it was a fun way to spend my friday night!

we did it this way because about 10 units were still running 4.0.X.X, and i wanted to bump them up to 4.1.0.292


no problems here!

[stuwhite]

I'm not going into the details coz DST has, quite frankly, made me wonder why I don't work in Maccie D's but I just wanna say that all is good and I couldn't have done it without you guys. I will be starting a thread when I remember to make sure everyone gets props but after 3 weeks of doing nothing but this (and trust me, I really have better things to do!), the prep work paid off and users have had it fairly easy.

Thanks again guys, buy yourselves at least one beer (but Coke for Darth!)

[DarthBBerry]

Originally Posted by stuwhite

Thanks again guys, buy yourselves at least one beer (but Coke for Darth!)

I like the taste of beer, just not the effects. O'Douls is really good.
And you get to buy the first round!