[stuwhite]

Originally Posted by stuwhite

Nope, you can't force the reset.

The awaiting patch message could be false, as the BBs aren't always reporting their patch status properly. Apols to whoever posted this as I can't find the msg but this is really useful stuff:

It was mrc7928 via mahoward. In This thread.

[stuwhite]

Originally Posted by stuwhite

Well, mine is now back to xx:35 with the others, last one was at 8:35am. Let's see if they all change at 12:35......

Yup, polls every 4 hours +/- 2 mins.

[stuwhite]

Originally Posted by juwaack68

Since the new DST que at RIM seems to be useless, can some knowledgeable person here help me get a few questions answered?

1. Do we really need to run the SendAs tool? Seems like we had an issue with ‘send as’ stuff around the time we installed SP2 on the BES, and it was resolved at that time. Is there a way to check if we need to run it (other than people suddenly can’t send)?

2. If we need to run the SendAs tool, is it run on the BES or on the Exchange server (or both)?

3. Can I register the new CDO.DLL file before the Exchange servers are patched (this weekend)? Seems like I heard/read somewhere that as long as the CDO.DLL on the BES is equal or newer than the Exchange server then it’s ok.

I apologize if this has already been answered out here, but I can't seem to find the answers.

1. Depends how you got round it last time. Unless your besadmin account has full rights to each exchange server, you probably will. Someone mentioned the MS sendas tool being a better bet (I think it was SoUnCool).

2. It probably doesn't matter but I would choose the Exchange server, as you are running against AD, so less chance of errors.

3. According to what I have read, absolutely not, but I won't be doing my CDOs till this weekend, and will be doing Exch then BES.

HTH
Stu

[Gino]

I think that we could all benefit from splitting these DST threads up to individual threads based on the method of DST installation. I know that most folks here are trying to push the DST patches out to their devices by using the BES OTA process.

I have been trying to use the Blackberry Website recommended procedure for updating each device individually becuase we have a BES 3.6 server with 14 devices.

They suggest one method of sending a link to the Blackberry and having the device connect to the link and download Patch Manager 2.2. I have only been successful with this delivery late in the evening due to what I assume is high traffic.

The second method suggests using a computer to browse to their DST site and choosing a link that after prompting to connect the device with a USB cable it will install the Patch Manager 2.2. I have only been successful in using this second process also late in the evening.

Since I am unable to upgrade our users late at night, I have tested another manual delivery method that may help others in this same situation. I have downloaded the push files from: Blackberry dot com DST2007/patch/manager/patchmanager.zip

I then unzipped the files and used Desktop Manager to install Patch Manager 2.2 using a USB cable to connect the device to computer. Patch Manger 2.2 installed and the device (8703e) rebooted and then showed the patch successfully installed. I have not ran a query tool against the device to verify the patch status. This at least gives us one method that we have control over the delivery since I have the downloaded files. I know this is of little help to those with many devices to patch, but I am glad to have something to work with.

If anyone has any better suggestions, please share them.

[blakeatl]

A little to the left here, but does this patch have to be done to BIS as well or do we automatically change to DST?

[stuwhite]

Originally Posted by blakeatl

A little to the left here, but does this patch have to be done to BIS as well or do we automatically change to DST?

No idea about BIS but I do remember from way back near the start of the thread that there is a BIS thread somewhere

[JRV]

Originally Posted by blakeatl

does this patch have to be done to BIS

BIS users have to visit the RIM DST web page to obtain the DST patch or else manually adjust the time twice a year as per this page: BlackBerry

[DarthBBerry]

Originally Posted by DarthBBerry

UPDATE:

Procedure

1. Windows Server '03 Patch - COMPLETED
2. Upgrade to BES 4.0.6 HF2 Now with HF4, w00t!
3. Download .COD & .ALX
4. loader.exe \Index .COD & .ALX
5. Share files from PF\Common Files.... \DST Upgrade location
6. Create software configuration
7. Set / apply Application Control Policy
8. Wait 4+ hours - This is the hard part and where I am now...
9. Wish really hard the darn thing works
10. Run query tool and hope for good results!

The 4 hour wait was, well.... trying. After 4 hours I went back and removed/readded the app policy then tried again. Waited overnight to see if it worked.....and it did! (but only on 2 of the 4 devices.) Got my hands on the devices and clicked [Download The Flippin' Patch] on the Blackberry. Update complete after a prompted reboot.
Also performed changes based upon KB12424 and tried again with another batch of 15 users. Awaiting results.

DST2007Query tool shows devices updated as they should. Also shows which are still Awaiting The Flippin Patch.
Interestingly enough, the server shows "Update Required" for the patch where the 1.5 was applied before the 2.2. The 2.2 folks are showing perfect on the server and the query. The 1.5 folks still show as patched.

More to come as I get more results.
Props to General Zod (stuwhite) for previous posts! "Yes, my Lord Zod."
Slops to me and General Zod for not RTFM when we should.
/Happydance since some of them actually worked

[acf]

Love this message about the pre-4.0 patches. My guess is they will be released on 3/10...

NOTE: These patches are targeted for release in the near future, please check back frequently for details.

[Jacob G]

Please do fill us in. I am about ready to push 2.2 to my 2000 + users since 1.5 sucked

[mahoward]

I pushed 2.2 to >100 users this morning. At first I got about 50% 0x43 503 errors, which freaked me right out, however they seem to be clearing up nicely over the last few hours, turning into "Awaiting Patch" and then eventually..... "Applied". Right now I have 55 done, 40 waiting, and 12 still at an 0x43 error status.

Looks like the 2.2 version is doing it's job of updating with it's status correctly.

[slate]

Hope I am not asking something that has already been answered, I have searched the forum but no luck. I have 87 users on BES, over 24 hours ago I pushed DST 2007 patch v2.2 out to all users. Everybody with a 7100,7280 or 7250 (36 users) got the patch in under 4 hours. DSTQUERY shows status "applied". Everyone without exception who has an 8700 or 8100 (41 users) did NOT get the patch. DSTQUERY shows "helper not installed" but on the BES handheld configuration tool shows all software status as "up to date" and the correct configuration applied. No sign of the patch in the options menu on the units themselves. What am I missing that I must do on the 8700's and pearls to make it work

Here is the version level for all of our pearls in case that helps narrow it down.
Handheld Model: 8100
Platform Version: 2.2.0.32
BlackBerry Version: 4.2.0.51

Thank You very much in advance for any assistance you might offer.

[DarienA]

Well continuing to test I downloaded patch mgr this morning(I have no idea which one it is, how do I check) and pushed out the patch to my co-workers 7290.

His Blackberry reports the patch applied yet according to Boxtone.. yup you guess it... awaiting patch.... <sigh> At this point I think I'm just going to have to manually verify with my users on Monday that their patch status shows patch applied.

[DarthBBerry]

Originally Posted by slate

Hope I am not asking something that has already been answered, I have searched the forum but no luck. I have 87 users on BES, over 24 hours ago I pushed DST 2007 patch v2.2 out to all users. Everybody with a 7100,7280 or 7250 (36 users) got the patch in under 4 hours. DSTQUERY shows status "applied". Everyone without exception who has an 8700 or 8100 (41 users) did NOT get the patch. DSTQUERY shows "helper not installed" but on the BES handheld configuration tool shows all software status as "up to date" and the correct configuration applied. No sign of the patch in the options menu on the units themselves. What am I missing that I must do on the 8700's and pearls to make it work

Here is the version level for all of our pearls in case that helps narrow it down.
Handheld Model: 8100
Platform Version: 2.2.0.32
BlackBerry Version: 4.2.0.51

Thank You very much in advance for any assistance you might offer.

Did ya try this link? Check out BlackBerry Device Software v4.2.0 (for example, BlackBerry® Pearlxxx8482; 8100 device).
You might need to download the file and run the script.

EDIT: and what mahoward said! (devicesrc version="1.0.0.35")

[mahoward]

Originally Posted by slate

Hope I am not asking something that has already been answered, I have searched the forum but no luck. I have 87 users on BES, over 24 hours ago I pushed DST 2007 patch v2.2 out to all users. Everybody with a 7100,7280 or 7250 (36 users) got the patch in under 4 hours. DSTQUERY shows status "applied". Everyone without exception who has an 8700 or 8100 (41 users) did NOT get the patch. DSTQUERY shows "helper not installed" but on the BES handheld configuration tool shows all software status as "up to date" and the correct configuration applied. No sign of the patch in the options menu on the units themselves. What am I missing that I must do on the 8700's and pearls to make it work

Here is the version level for all of our pearls in case that helps narrow it down.
Handheld Model: 8100
Platform Version: 2.2.0.32
BlackBerry Version: 4.2.0.51

Thank You very much in advance for any assistance you might offer.

Slate, you will need to replace the device.xml in your apploader directory with one that has the 8100 and 8700 device model numbers in it. Delete any subdirs in the packagecache directory, then try it again. It should now recognize the devices and report the correct status instead of up to date. It will also then push out the code, which it is not doing now and reporting bogus status.

[slate]

Thanks, Mahoward, I did as you suggested and replaced the file. Those blackberries now show "install required" I will let you know in 4 hours if they are updated properly. Again, Thank You.

[SoUnCool]

Originally Posted by stuwhite

1. Depends how you got round it last time. Unless your besadmin account has full rights to each exchange server, you probably will. Someone mentioned the MS sendas tool being a better bet (I think it was SoUnCool).

2. It probably doesn't matter but I would choose the Exchange server, as you are running against AD, so less chance of errors.

3. According to what I have read, absolutely not, but I won't be doing my CDOs till this weekend, and will be doing Exch then BES.

HTH
Stu

my advise stay away from SEND AS tool, rogers enterprise support told us so, and MS has a better solution i posted earlier

[stuwhite]

Originally Posted by DarthBBerry

<snip>

More to come as I get more results.
Props to General Zod (stuwhite) for previous posts! "Yes, my Lord Zod."
Slops to me and General Zod for not RTFM when we should.
/Happydance since some of them actually worked

you're gonna make me blush Lord BBerry! I have to give props to mahoward, jibi and the rest though, coz mostly I am making educated guesses based on their leads

Glad to hear all is going well. My user patching is going well but slow so I will push out to the rest from Thurs but as they are global, it should be fun :-> Most of the test groups have been fine though so I am not too worried but I am not touching 2.2

Now you got me wishing I set my tag to General Zod

[stuwhite]

Originally Posted by DarienA

Well continuing to test I downloaded patch mgr this morning(I have no idea which one it is, how do I check) and pushed out the patch to my co-workers 7290.

His Blackberry reports the patch applied yet according to Boxtone.. yup you guess it... awaiting patch.... <sigh> At this point I think I'm just going to have to manually verify with my users on Monday that their patch status shows patch applied.

Did you try This to get BoxTone showing the right info. Works a treat for me.

[jsplit]

Originally Posted by stuwhite

Did you try This to get BoxTone showing the right info. Works a treat for me.

STU - thanks for the good answer there - that's the best workaround...