I'm running this from my workstation but we use SQL.

I've seen some discrepencies myself. I have a few showing as error, but I look at the Blackberry and it's done. It still says error hours later. But you do have to be patient, it can take 4 hours or more for units to get the helper.

Doh! I had so much going on yesterday, I didn't even think about the implications of already having 4.1.0.377 onboard!

Thank you so much for the clarification! That makes me feel safer for when we go live with the push. Interestingly enough, when I removed the patch and downloaded it directly from the Blackberry Browser, I did get the reboot prompt using that method. Go figure.

I pushed the patch to all my users with various devices. I have run dst2007query.exe several times and the only devices that show applied are the ones I did the day the patch was relesed. I called tsupport this morning and after a while explaining to the technican what was happening he stated that if the last HTTP collumn shows 200 it means the patch is applied. I'm wasn't sure if this was correct or he was just trying to get me off the phone so I sent an APB to all my users explaining the situation. I asked them to check the status of the patch. So far 3 of them have responded that the DST Patch states applied on their devices. Guess I will go with that until DST day and all you know what breaks loose.

endtrans

I think he's confused. Two of my test users received the reset prompt this morning. The DST2007Query from last night showed the same two users with a Last HTTP Response of 200.

The 200 response may mean the patch manager is installed but definitely not the patch itself.

Yeah, I think we are in the same boat. Mine was the first patched and it shows as 'Patch Applied' and the Last HTTP response is 0, while the others show 'Awaiting Patch' and the Last HTTP reponse is 200.

Time to get comfortable and call support

I've come across something that concerns me, and I'm wondering if others are seeing the same thing. I didn't have any problem with the installation of the patch on a 8700, but while the 2007 DST Patch is applied (according to the new option at the top of the Options list), under the Date/Time option my time zone is listed as:

Pacific Time (-8) (GMT-08:00) Pacific Time (US & Canada), Tijuana

That's the only GMT-8 choice. Mexico didn't change their DST rules, so won't this cause a problem for a number of Mexican Blackberry users?

Hmm, you should have the following as an additional option:
Tijuana (-8) (GMT-08:00) Tijuana, Baja California

I pushed the patch to three handhelds on Wednesday. My handheld is running the handheld software 4.1.0.377 (which doesnt need the patch) and the other two are running 4.1.0.194. The patch hit all three handhelds in under 3 hours and all three have the "2007 DST Patch" under Options and they all say Applied.

When I ran the query tool from the BES, my status reads "Applied" but the other two show "Awaiting Patch". I called RIM tech support and they said to believe what the handheld shows. They also said that it could take some time for the database to update. When I said that it had already been two days, he said it could take longer.

I find this a little troubling since I'm going to push this to approximately 1100 handhelds and I need a way to confirm that the push was successful.

Any thoughts?

I'm looking at the "How Administrator can assign DST upgrades wirelessly"

On the 1st page you have this...

Task 1


Configure a host computer from which the DST upgrade files will be shared, then move the COD and ALX files to a DST Upgrade folder on the hard disk drive of the host computer.

Note: The host computer can be the BlackBerry Enterprise Server computer.

On the host computer, go to C:\Program Files\Common Files\Research In Motion\Shared and create a folder called Applications.
In the Applications folder, create a subfolder to contain the DST upgrade files (for example, a folder named DST Upgrade).
Place the two DST upgrade files that you downloaded in the subfolder you created in step 3.
From a command prompt, type cd C:\Program Files\Common Files\Research In Motion\Apploader and press ENTER.
Type loader.exe /index and press ENTER.
Share the C:\Program Files\Common Files\Research In Motion directory



I don't have a SHARED folder?? Why is that?

Should I just create one?

Yes, you have to create it.

Here is a list of the BB devices in my user group. Are all these fine to push out the DST patch? Does anyone know which ones will require a reboot?

I appreciate all the help on this forum!

8100
7290
8703e
7250
8700
7130e
7280
7100

I've reinstalled the patch manager and patch (by going to RIM's DST page, not through BES) and restarted by Blackberry several times.

I still only have one GMT-8 time zone:
Pacific Time (-8) (GMT-08:00) Pacific Time (US & Canada), Tijuana

Are others seeing both of these:
- Pacific Time (-8) (GMT-08:00) Pacific Time (US & Canada)
- Tijuana (-8) (GMT-08:00) Tijuana, Baja California
after patching?

I have several users that need this update but we don't have a BES. Can I post the files on a website and have them download the files OTA? Or do I have to use the Desktop Manager?
Thanks,
Chris

So far 7130e (vzw) / 7250 (vzw) / 7290 (cing) / 8700 (cing) / 8703e (vzw) all needed reboot.
I have a feeling that some device's are not getting prompted to reboot so when DSTquery is ran it displays that its not finished yet even though the device says applied. But who knows. That tool has been goofy

Get this... Some 8700's needed to reboot twice.

Got message (1/4) and (2/4) and then was OK.

So, the "Updating Your Blackberry Environment to Support DST 2007" document recommends everything be installed in this order:

1. Update each Microsoft Windows Server® that is running Microsoft Exchange or the BlackBerry Enterprise Server.
2. Update the Microsoft Windows® clients.
3. Update BlackBerry devices.
4. Run the RIM Set Send As Permission tool.
5. Apply the most recent Collaboration Data Objects (CDO) to the BlackBerry Enterprise Server and the Microsoft Exchange Server.
6. Run a Microsoft calendar update tool (optional).

What exactly happens if I update my handhelds before I get any of the other updates out as long as they're all applied before the Daylight Savings changes go into effect?

Has anyone seen this when they run the DST2007QUEREY tool ?

[40000] (02/15 15:48:57.579):{0x16D0} Daylight Saving Time 2007 Patch Query Version 4.1.2.6
[40000] (02/15 15:48:57.579):{0x16D0} Modification date: Feb 8 2007
[20000] (02/15 15:48:57.579):{0x16D0} Downloading: http://www.blackberry.com/DST2007/pa...rrier/list.txt
[10000] (02/15 15:48:58.001):{0x16D0} Unable to download versions list. Error: [0x80070005]
[10000] (02/15 15:48:58.001):{0x16D0} Unable to download versions list from [http://www.blackberry.com/DST2007/pa...rier/list.txt]

I was having the issue of Pearl's (8100's) not receiving the patch, however it listed as App Status: up-to-date in BB Mgr. The problem was my old device.xml had no entry for the 8100. Even if you are on the latest versions of BES, ensure that:

1. The device.xml in the sw config location is the very latest. You do not have to replace the version on the BES servers in c:\progra~1\common files\research...etc , just the sw config location you have shared out (if that is a separate location which in my case is on our attachment server). Download the latest Desktop Mgr 4.2 SP1 and grab it from there if you need the latest version.

2. Delete all cached pkgs on each BES server in the packagecache directory. During the next 4 hour re-send it will rebuild the packages and include the newer device.xml from #1 above.

To summarize: You can still deploy this patch to newer devices w/o upgrading the whole BES box, just update the device.xml in the sw config locations and clear the package caches on all your 4.0 BES servers.

There is no blackberry software needed, BUT it seems you must run the DST Exchange20003-kb926666 (etc) program on the server and choose System Manager only. It should then install the cdo.dll and other related files. Is that correct. This is the typical update we have done when the Exchange Server was updated.

We only have 110 users and in reading this i am inclined to install as many manually as possible when people are in the office. Does that make sense?

Thanks

Anyone know?

Hello
Thanks in advance for any help. I'm confused. I have updated my server. I've changed my DST in Console1. I've copied files and shared them properly. I checked the IT policy to verify 3rd party apps are allowed. I've assigned the new software configuration that I created with the DST patch. But my test handheld doesn't change. Where exactly am I supposed to see that the patch is applied? In an earlier test, I tried re-applying the IT policy to this handheld and I did get a reboot message but after the reboot, the device kept generating errors. RIM said to wipe and re-provision and start over. Now I don't get anything.
Peter

jrbes what explicit rights did you give the group (send/receive as)? We just updated to Exchange environment to SP2 and to 4.1.3 BES. Everything worked fine until the DST patch for Exchange, now we get red X when sending email from the device. the BESAdmin account has send/receive as rights at the server and info store level in exchange. Has anyone run into this, any suggestions?

Thanks in advance!

Hi,

I'm running BES 4.1 and just sent the DST patch to my BB and I was wondering if there is a way to see the progress somewhere on the server
and find out if the patch was sucessful?

The info from this thread is amazing and at the same time overwhelming for one night.

For the guys with the same experience / in the same boat as I am , please let me know your thoughts / suggestions:

1. Update RIM server to BES 4.0 SP6 HF1 (and when HF2 gets released).

2. Update SQL Server with the code released.

3. Create software config and sent to a test group to ensure wireless deployment works properly. Once deployed and confirmed, qc.

4. Deploy to all the devices in the firm.

*Upgrading to BES 4.1 is not an option as of right now*
**Domino is on 7.01 and does not require to be on a higher version?!?**

Any thoughts or suggestions would be appreciated.

Thank you.

amukhey, if your BlackBerry Device Software Version 4.2.1 or later, then there is no worries on upgrading the device software.

But for other versions, the DST Patch file is required. See below link for more info on the various deployment options:

Impact to BlackBerry Devices

amukhey,

You do not need to upgrade to 4.0 SP6, in fact I wouldn't. I already did and there is a bug where if you restart the BES task ALL pending messages sitting on the BES box are LOST and never delivered. This will be fixed in HF2 coming out supposedly this week.

4.0 SP6 is only required if you want to update newer devices via the SyncDeviceMgmt table, but there are not many out there. I would suggest just pushing the patch OTA to all devices instead of upgrading the server as long as you are at 4.0 SP5.

sberghorn,

Looks like wherever you are running the DST query tool cannot access the RIM website. Trying pasting the url in a browser and opening it that way, is it possible?

All,

I have alot of interesting research results on applying this patch to different devices / code levels. Here are my findings:

1. Once the patch is delivered, it will update the SQL db with it's status only ONCE. So if it fails initially and is later successful, you will never know b/c only the initial failure will register in SQL.

2. Most 8700's on the latest OS version 4.1.0.346 work perfectly the first time and do not need a reboot. One, if you went in to check the status, said it needed to restart but never prompted with a popup. Weird.

3. One 7290 ran out of memory upon patch delivery and so registered an 0x44 error. This means it started the Java cleanup code and so deleted stuff off the device to make room. Bad.

4. One 7290, upon patch delivery and restart, set the device date to 1/24/2006. User didn't notice and went into calendar which was showing everything GONE, of course b/c it was 2006. Updated to network time manually and it is back to normal except for interim msgs which still sort down on the bottom to 2006 dates. This is bad too.

5. If the user doesn't check and has the prompt to reboot the device waiting, you will see "Error 0x88 0x00" show up in DST query tool, and it will never update itself even when the user finally goes in and reboots.

In summary, for most of the newer 8700 devices this is no problem. For the rest of the mishmash of devices it is looking like it is going to be hit or miss, and requiring the end user to check status since the tool doesnt update. Not looking forward to full deployment.

That's why we are planing to send emails to the users the day of their update and to verify the patch status after the reset.

On the 7290, I have installed the DST patch i.e. can be seen in Options, but errors out with patch not found. This has been running for 3 days and same error and I keep on saying dwnload patch again when prompted. Iam running 4.0.0.x on the handheld. anyone seen this ?

then I tried also running dst2007query tool from my workstation and got the following error, any ieads whas happening please

Command used:
dst2007query -n srvbes001 -db srvbes001 -b srvbes001 -OL c:\out.txt
syntax: dst2007query -n <configuration servername> -db <BES db name> -b <bes servername> -OL <output file>

Daylight Saving Time 2007 Patch Query Version 4.1.2.6
Copyright (c) Research In Motion, Ltd. 2000-2007. All rights reserved.
Modification date: Feb 8 2007

[20000] (16:31:57.080):{0x0F8C} Downloading: http://www.blackberry.com/DST2007/pa...rrier/list.txt
[20000] (16:31:57.370):{0x0F8C} Versions list saved to: DST2007Query_WebVersionsList.txt
[20000] (16:31:57.370):{0x0F8C} Reading versions list: DST2007Query_WebVersionsList.txt
[20000] (16:31:57.370):{0x0F8C} Connect to database server: srvbes001
[20000] (16:31:57.370):{0x0F8C} Database name: srvbes001
[10000] (16:32:13.824):{0x0F8C} Failed to open database connection

any ideas why it cant open the database connection ?

Good thread, lots of good info... a question though...

Where exactly is this RIM Set Send As Permission tool located? And do I need to use it if I've followed the MS page that describes the specific Send As rights that need to be assigned to each blackberry use? Don't have the link to that page handy but it's the page that discuss the whole can't send email after other patch is applied page.

EDIT:

Disregard... found it... after doing a bit more searching... just in case I'm not the only one that missed this link:

http://www.blackberry.com/DST2007/pa...Permission.exe

Hey guys,

We're running exchange 5.5 with a blackberry enterprise server.

We have the BES updates ready to roll out.

If we don't purchase the 5.5 exchange update from microsoft, will the time still be off for all mail? is there any workarounds to avoid the $4000 fee/upgrading to exch 2003?

thx

This has me feeling sick.

So lemme see if I got this straight. I run Exchange 2000 SP3 and BES 4.0.5.


I either have to fork over $4000 to MS or upgrade to 2003 SP2?

Just as a clarification. When RIM says that devices running 4.1.0.377 or higher, are we talking about the package version, or the version as shown on the Berry in Tools-About?

The are talking about the software version (Options, About) not the release version.

Looks like that is what it has come to. Apparently the original price for the patch was $40K. How generous of them to bring it down.

You do not need to upgrade to 4.0 SP6, in fact I wouldn't. I already did and there is a bug where if you restart the BES task ALL pending messages sitting on the BES box are LOST and never delivered. This will be fixed in HF2 coming out supposedly this week.

Does this include BES for Groupwise 4.0.6? (The new hotfix, that is)

Thanks,
I am still sick about this. Somehow, I have got to figure out how to get a new server, install Exchange 2007, migrate all my accounts and link the BES to it before the 11th.
I work well under pressure, but this feels insane.

Ok thanks for the info, however..

You are right about upgrading to BES SP6, there was a problem which is why I used a test box to go to BES Sp6 HF1 and that fixed the issue.

However, I cannot find any documentation that speaks of Updating the Domino Version of the BES Server.

Other domino servers such as mail and smtp are running 7.02Fp1 which makes it steer clear.

Any ideas? My current bes server is running 7.01

FYI: I upgraded my GW BES last week to version 4.0.6.4 and it didn't lose any pending messages. Infact, after the amount of time I spent sweating over it, the update was a big fat non-event (kinda like Y2K).