[chedardog]

Good Morning,

The following updated DST 2007 tools will be available on the website this morning. www.blackberry.com/dst2007/patch:

1. Patch Manager v2.3

This is a brief note to say that there is a new version of Patch Manager (v2.3) being posted to the website this morning. BlackBerry. This new patch manager fixes various issues we have received via Technical Support from the currently posted Patch Manager v2.2. The final release notes will be posted with the updated Patch Manager, but the 2 main fixes are as follows:

· In DST 2007 patch manager version 2.2 and earlier, the user was prompted twice to restart the BlackBerry® device but was not forced to restart it. In DST 2007 patch manager version 2.3, the user is prompted up to four times, once per hour. The DST 2007 patch manager forces a restart after the fourth prompt.
· In DST 2007 patch manager version 2.2 and earlier, if the BlackBerry Enterprise Server Mobile Data Service transport was not available, the DST 2007 patch manager did not work correctly with the BlackBerry Internet Service Browser. This issue has been resolved.
Note: If companies have already deployed the DST patch with previous versions of the patch manager then this is not required to be used unless they require the above fixes.

2. DST2007Query.exe Tool Update

There will also be an updated DST2007Query.exe tool posted to the DST2007 website today. This new DSTQuery tool will also help various issues we have received via Technical Support from the currently posted DSTQuery.exe tool. The final release notes will be posted with the new tool, but below are some of the key highlights.
· (SDR121742) Previously, the DSTQuery tool would report users in an "Awaiting Patch" state when they in fact were already patched. The new DST2007Query.exe tool will now have an added command line switch to 'force' a synchronization of the DST information to make sure the accurate information is returned to the server to be queried. This will work regardless of what version of Patch Manager (1.5, 2.2 or 2.3) is on the device(s) in question.
· High level steps to diagnose and address this scenario are:
(1) Run the DST2007Query tool and check for devices in the 'awaiting patch' state;
(2) If there are then run the new tool with a command line switch "-invokesync" during off hours;
(3) Reboot the SYNC server;
(4) Wait to let the data sycnhronize; and
(5) Then re-run the tool again (Step #1) hours later, or ideally the next morning.
· (SDR120331) Previously, the "Patch Not Required (Optional patch available)" status was not returned for device software versions 4.1.0.375, 4.1.0.377, 4.1.0.378 that already have the updated DST table. See BlackBerry.
(SDR122287) Support for IBM DB2 databases (not just SQL)

Now where did I put that number for Goodlink... It's around here somewhere

[DarienA]

Yeah this is mentioned in the main sticked DST thread, crazy.

I'm pushing out my patches this evening, I'm thinking about waiting for this 2.3 though... 2.2 doesn't automatically restart? Ugh...

[FPhillips]

I went to the site and it does not seem to have the updated version. Any ideas on when that page will be updated or is there an alternate site to download it from?

[Ekrimmer]

Not there yet...8:10am PST

[amukhey]

Hey guys, thanks for the info but I have not been able to see the v2.3. Anyone have it / seen it posted? I still see 2.2

[DarienA]

It's not posted yet.

[amukhey]

fyi that post was done at 12:33pm EST 03/02/2007

[ts937km]

Tsupport said today sometime. Just hung up with them....`

[Gotrek]

Does anyone know if we update the patcher to v. 2.3 will there be a visual impact to the user if they are already successfully patched? (reboot required or ???)

[juwaack68]

It might hose their device. I had a handful of 7100i's that already had patcher 1.5, and when 2.2 came out I assigned the 2.2 to them...and their devices got the dreaded JVM 102 and I had to rebuild them....

If they are already showing patched on the device, no need to repatch them.

[Gotrek]

Originally Posted by juwaack68

It might hose their device. I had a handful of 7100i's that already had patcher 1.5, and when 2.2 came out I assigned the 2.2 to them...and their devices got the dreaded JVM 102 and I had to rebuild them....

If they are already showing patched on the device, no need to repatch them.

In testing we went from 1.5 - 2.2 without any problems (replaced the files, reindexed them and that's it)

We started roll out today to approx 1500 handhelds using 2.2 I'm debating replacing the patch again or creating a new software configuration and using the new configuration for the new users leaving the 2.2 users alone.

[ZeroKool]

I would think that if the 1.5 patch manager works and they are showing patched via the query tool then you shouldn't need to push the new patch manager. Just create more problems. If however, the 1.5 manager isn't working, then yes, re-create config and send it.

[Gotrek]

We're using patch manager 2.2. 1.5 was only used in initial testing. Live roll out with 2.2 but it's only just begun (300 users or so)

[Gotrek]

Originally Posted by juwaack68

It might hose their device. I had a handful of 7100i's that already had patcher 1.5, and when 2.2 came out I assigned the 2.2 to them...and their devices got the dreaded JVM 102 and I had to rebuild them....

If they are already showing patched on the device, no need to repatch them.

That's the other catch with so many users spread across the country we don't have the man power to follow up with each user to confirm they've been patched. We're using dstquery and Boxtone at this point for reporting.

[ts937km]

Same problem. Down to 217 not patched.... All over the world. Blackberry said go get the handheld delete the service book, resend service books, and hope for the best.

Curious what they smoke at the support center.

Who is up for a bet as to what patch level they will be on March 10th?

[Gotrek]

We have 100+ users who have not reported to Bes in "a while" (one 86 days ago). I'm not worried about those they are either still at firmware 3.6 or not in use. those users likely have issues as they stand and require support they've yet to ask for. I'll cross that bridge when we get there.

So far our roll out is going well. of 300 devices pushed so far 258 have downloaded the patch manager and 130 have been patched.

[DarthBBerry]

Originally Posted by Gotrek

(one 86 days ago).

Gotcha beat on that one.
Last contact time was 3/23/2006 3:14:41 PM
He didn't want the Blackberry to begin with; management made him get it.
His device was activated on 3/20/2006 11:17:04 AM
He used it for a whole 3 days; almost. LOL

[BirdmanSTX]

2.3 is out. 325p Central

[gwgaston]

Yep testing it now... the updated zip was available for download a good while before they updated the website to reflect so.

[DarienA]

So would I just download the new patchmanger, unzip the two files, drop them in the shared folder I created at the beginning and that's it? That seems to be the case because when I did it and updated the configuration check on my own handheld(which still has the DST configuration attached to it) it says upgrade required.