The result of my install was another entry in Options labeled 2007 DST Patch. One click opens another screen that reads '2007 DST patch applied.' Pretty simple. I wasn't prompted to reboot and haven't done so yet, but I will when I get the time to do so. All my appointments seem to be correct, but I also have to say that I didn't have any that started within the Spring of Fall window laid out in RIM's documentation...

I pushed from BES, and when I go into Options and look at it, it says 2007 DST Patch Manager is running...Patch not found : Trying again at : Feb 12, 2007 12:32 PM. Then when it hits that new time, it goes out to the website and can't find the patch, and starts the cycle again...any ideas?

http://www.blackberry.com/DST2007/pa...07_Changes.pdf

4. Run the RIM Set Send As Permission tool.

...hmm...

I'm confused......
So, according to the following instructions:
"On the host computer, install the BlackBerry Device Software for the BlackBerry devices that will receive the DST upgrades."

This means I'll have to go hunt down the device software for every device and every carrier that we use, then install it to the server?
Help please!

Hey guys .. working with the patch now and had a question about the policy ..

do you need to adjust the Internal / External network connections? mine are set to prompt user.

I'd like this to push and be seemless to the end user.

Thank you!

Followed the above guide and I am waiting to see how long it takes the server to push the app to my handheld. Will let u all know

Also, Not sure if anyone else noticed. The DST query tool is in that zip as well.

Have not pushed any out since we have a relatively small user group, but according to this doc from RIM's site:

http://www.blackberry.com/select/dst...007_Update.pdf

you'll need to allow external connections.

Thanks for the link .. one would think they'd include this PDF with the download!!!

I'm using a 7250 on Verizon. Testing 8703 next.

Took less than 10min. I got alot of activity and then a message box saying...

(1of 4) Time zone information has been updated. Reset device now? Yes or No option.

It's been sitting at the hourglass screen for the last 10min. This is not looking good

Thank GOD, it worked. Successfully pushed app to 7250 with default IT policy. I got a message saying the device needed to reboot. It turned off then back on and sat at a blank screen with the hourglass moving for about 10min. Finally came back up though and the DST 2007 Patch now has it's own line under Options.

I'm guessing the server pushes the patch manager program to the device (.alx / .cod) and then the program runs when rebooted and downloads the specific patch for the device. Doesnt explain why KOR didnt have to reboot though. Guess his device is cooler than mine. Testing push to 8703e next. We will see if it requires reboot.

Thanks | | | | | | and Kor for the Doc links.

I have all the proper settings in the IT Policy, as we don't block anything. BES pushed it to all the devices, but all of them say Patch Not Found.

Check out the new thread, http://www.blackberryforums.com/bes-...-upgrades.html

You probably don't have MDS/MDS connection service set up for external connections

It downloads the necessary patch over the air prior to reboot. The reboot allows it to actively load the patch to the OS. The reboot is probably only necessary if a file required is in use at the time of installation.

Hmmm, we don't use MDS...

Hmm, 2 hours now and still nothing on my Cingular 7290.

Wonder what decides when the BES will contact the device to update the DST after you have assigned the DST configuration..... anyone?

The BES im testing this on has 3 users. Mine went through in under 10min. The other 2 people are going on an hour without contact.

It can take up to four hours for the software to install unless you add a registry key. Most of mine went through, but I've got a few 6510s and they say Not capable of Wireless Application Delivery, and they have 4.0.0.160. They don't have any different IT policy. Is there something I'm doing wrong? These are the only 6xxx models I have, everything else is a 7 or 8000 series.

Not sure why I didn't get prompted to reboot, but will when I'm done working for the day. As jibi pointed out, my device was doing nothing during the process. In addition, I pulled the patch. Don't know if that makes a difference, but based on the all the documentation I've seen & read, RIM might not be able to tell you either. Gotta admit, it worked better than I thought it would.

Post back when you're done with the 8703; I'm interested to know if you get a reboot prompt.

Well, had to wait for some processing to run on something and rebooted. Let the device off for ~ 30 sec and it came back a champ. So, I would guess that jibi hit the nail on the head.

I didn't get a reboot request on my 8703, but a 7130e got it, and took over 5 minutes to reboot.

Thanks for the info. I've got one of those in the mix of devices to update. I think the RIM docs said up to 15-20 minutes, so 5 is promising.

Can someone screenshot the restart message. I need it for instructions for my users. I don't want to rebuild mine to get it.

Here ya go.....

No restart on all my 8703's as well.

I found out why the patch was not able to connect to the web page to download it. We are behind a proxy which requires login, so I turned that off, and the patch downloaded just fine.

Can anyone tell me how I can see if the patch was successfully applied to my devices?

It's the 2nd and 3rd screenshot provided by RacerGregg.

I think if you download the PDF files listed on the Download page (as opposed to just the patch files) you all will have a much better understanding of what is being done and exactly how to troubleshoot problems you may be having.

Patch successfully applied OTA to my wife's 7130e (non-BES) and to my 8703e (MailStreet BES). When I asked MailStreet about the DST patches, they thought I was talking about Desktop Server Tools. So, despite my earlier protestations, MailStreet isn't quite sure what's going on.

I figured installing the patch wouldn't hurt and if they tried to push it to the device later via BES, it would see the patch was already installed.

Keeping my fingers crossed.

I have created the software configuration and assigned it to a few test users. They have not received it yet. Under their handheld I see for configuration status check required. What does this mean?

I, too, am trying to create the configuration. After following the updated instructions, I looked at one of the test users whom I've deployed it to and it says Unknown Configuration. What's wrong?

EDIT:

I clicked on Update Config Check Status from under Device Management and it looks like something changed. I am now getting this:

Config Name: DST2007
Status Check Time:
Config Status: OK
System Status: Up to date
Application Status: Install Required

What does that mean that its up to date? Is it telling me the version of th epatcher is up to date and all it needs to do now is run it on the handheld? When I look at the handheld I don't see 2007 DST Patch under Options...

fyi.

We had a problem with the DST patch on the BB this morning. The "2007 DST Patch" showed up in Option but when you go into it the message was "2007 DST patch cannot be downloaded".

Upon investigating it looks like the TimezoneOtaPatcher is nothing more than a patch installer utility. The TimezoneOtaPatcher seems to download the actual timezone patch from RIM.

From the documentation I read, all 4.0.0 devices could get the helper app wirelessly. I have some Nextel 6510 units that users still have, and they have the message "Not capable of Wireless Application Delivery." They have the same IT policy as others, including 7750s. The 6510s have 4.0.0.160. I asked RIM, and they responded that they should be able to get it wirelessly, since they are at 4.0. They asked for screenshots, which I sent. They then responded that it isn't possible. Anyone else see this?

I created the package and applied to my 8700c as a test. The application pushed fine within an hour or two of updating my account's Configuration Status Check.

However, I got no reboot prompt. After manually rebooting it, I checked under Options and opened the DST 2007 Patch item. It says 2007 DST Patch Applied. Is that that the location that you're referring to when you say "when you go into it the message"?

In my entry under the Blackberry Manager, under the Configuration Name that I gave it, it shows the Configuration Status as OK, System Status as Up To Date, and Application Status reads as Install Required.

I don't know whether to believe the Blackberry Manager or the Device. I reckon I need to call T-Support tomorrow and find out their interpretation as well as what I need to do to make the bloody devices prompt for a reboot after the patch is pushed down.

I'm having the same issue with 6750 devices in my enviroment running 4.0.0.117. I have a ticket open with support now (they have said the same thing they said to you, and requested screenshots). I'll post if I get a response.

-zip

If your Blackberry handheld software is of a revision that does not require at DST patch then your will not be prompted. Your 8700c is probably at 4.1.0.377 which does not need the patch.

Believe the device.

Is it possible to tie a software configuration to an IT Policy, so that everyone with that IT Policy will get the particular software configuration pushed? I don't wanna be adding/re-adding new users, and have someone forget to apply the DST software configuration.

I was told they thought it was because of available space on the device. Granted there isn't much available, one has 179 k, but another got it (the manager, still waiting on the patch) and currently has 30k.

EDIT: nevermind. i tried my suggestion and didn't work.

I think you can in fact apply the configuration to a user group, thus applying the configuration to everyone within that group. But I am sure some of the admins we have will forget to add a new user to a certain group, or add the software configuration to the user. I just want to have a way to make this a default configuration so that as soon as someone is added to the server, this software configuration will apply to that user as long as that user is on this server, because I assume this needs to be done until all new users we ever add or re-add has the future software versions with the update already incorporated, which is highly not likely for a while.

Well, we have started patching with mixed results so far. I did my device first, 7250, and all went pretty good. The reboot took about five minutes and it was back up and running.

I have now sent the patch to three other 7250's but it does not seem correct on them. The device shows that the patch is applied, but when i use the DST2007Query tool my device is the only one that shows that the patch has been applied to.

Any one else seeing the same results like this using the query tool?

Thanks,

Rim also says to run the DST query tool from a different machine other than the BES. Is anyone doing this?