[chedardog]

I received the Draft Release Notes from one of my carrier contacts, but RIM's website still seems to be serving up version 1.5?????

Anybody know when it will be released to production?

excerpts for those of you who may not have seen:
=============================================

Fixed issues
This section lists fixed issues from build 1.5 to build 2.2 for the DST 2007 Patch Manager.
Previously, occasionally using the DSTQuery.exe tool would show a device in “Awaiting Patch” state even though the patch had been “Applied”. Changes have been made to improve the patch managers reporting to the BlackBerry Enterprise Server to address this.
HTTP Errors 401 (Unauthorized) and 407 (Proxy Authentication Required) will now trigger patch manager to try next available transport such as BIS, WAP or TCP (if any are available). This is relevant if a “Proxy server is restricting access to DST 2007 upgrades” as per KB12286 (BlackBerry Search Results) and there are alternate transports the device could use to access the patch.
Previously, older devices such as the BlackBerry 6750 may not show the Options-2007 DST Patch option when the patch manager is loaded.
For device software versions prior to v4.1.0.344, including v4.1.0.347, the default Application Control policy must be set to Optional (not Required) on the BlackBerry Enterprise Server’s Software Configuration to guarantee the patch is applied. Please reference <INSERT KB Article on this topic here> for further information.
The previous patch manager would download the patch, attempt to install it, the installation would fail because their specified Application Control policy did not allow the patch to be applied yet the Event Logs for the device would still incorrectly report “EVENT_PATCH_INSTALLED_NO_RESET_REQUIRED (0x15)”.
The user will be able to see this error in Options-2007 DST Patch and can attempt to retry the download once the Application Control default policy is set to Optional.
The IT Administrator would see this user/device as being in the “Awaiting Patch” state using the DSTQuery.exe tool.
Previously, when prompting to reboot there was not a space between ‘x’ and ‘of’ when showing “x of 4” prompts remaining.
Extra logging and debugging information was added.
Deploying Patch Manager v2.2 over v1.5
This section lists key things to remember when deploying Patch Manager v2.2 over top of existing Patch Manager v1.5 deployments. Please also reference relevant Knowledge Base articles located at: BlackBerry
If patch manager v1.5 is already installed on the target device then the user will be prompted to reboot when the new version 2.2 is installed.
When patch manager v2.2 is installed on top of patch manager 1.5 you may end up with multiple entries in Options-Advanced-Applications, but only one net_rim_bb_timezoneotapatcher.cod in Options-Advanced-Applications-Modules.

DST 2007 Patch Manager User Impacts
Reminder: The following user impacts may be seen when deploying the DST 2007 patch manager.
• Permission settings have become more restrictive (KB12257) - BlackBerry Search Results
• BlackBerry device user is prompted to restart after installing the 2007 DST upgrade (KB12258) - BlackBerry Search Results
• Slow synchronization process is initiated after installing 2007 DST update (KB12259) - BlackBerry Search Results

[ts937km]

I just got off the phone with tSupport and they also said a patch was coming out but no eta. Hopefully early this week.

I have 500+ that the helper app is not installed, but awaiting patch.

[jibi]

...should have been the initial release of the patch manager.

[rsun]

You are luckier then me on calling into support, all they would tell me is that to keep checking the webpage, didn't even acknowledge that there was a newer version. You would think support is there to save your time, not add to it.

[mebiuspower]

A patch over a patch? Brilliant!

[centrekin]

So this means that we will have to create new Software configs?

[mfruechte]

I just called tsupport and they just said to update the patch files to the new one as soon as it is released and re-run the loader.exe / index to inform the server of the new version. All handhelds assigned to this app will automatically get the updated one.

[centrekin]

so, when will they release it?

[jcard71]

Originally Posted by centrekin

so, when will they release it?

Can we sign up for an email update as soon as the 2.2 updated patch is available?

[jibi]

It is available now:

http://www.blackberry.com/DST2007/pa...tchmanager.zip

PDF documents contained in ZIP file.

[stuwhite]

Originally Posted by jibi

It is available now:

http://www.blackberry.com/DST2007/pa...tchmanager.zip

PDF documents contained in ZIP file.

Yeah, any users hitting the site from their device now get 2.2, joy.

[chubby_nubby]

Are they serious...I just finished deploying the patch to 2200 blackberry's now there is an upgraded patch? Is my users currently have the 1.5 patch, what is the benefit of patch manager 2.2? The reason I am asking is with all of these users, they will be concerned to see another DST patch, and another reboot.

[stuwhite]

Originally Posted by chubby_nubby

Are they serious...I just finished deploying the patch to 2200 blackberry's now there is an upgraded patch? Is my users currently have the 1.5 patch, what is the benefit of patch manager 2.2? The reason I am asking is with all of these users, they will be concerned to see another DST patch, and another reboot.

All of the details are at the top of this thread but if your users are patched fine, don't worry about 2.2. It bascially provides some extra device support and makes reporting of status back to the BES better. If your BBs are patched, they will be fine for DST so shouldn't be an isssue (I bloody hope so, anyway!).

[Mazie]

I copied the new files and reindexed (loader /index). This did NOT update my .pkg or .xml files. The PkgDBCache.xml file still reported the old version (1.5) and file size.

I deleted the .xml and .pkg files and reindexed again. Now the info is correct.

Would the change have taken effect in a few minutes? Or do you have to manually delete the files before reindexing?

Thanks

[rsun]

I had to do the same thing and delete those files.

[gwalker]

Will this fix the "Helper not installed" I am getting from most of my devices through the query tool?

[gwalker]

Disregard Last post

[pej]

We replaced the patcher 1.5 files with the patcher 2.2 files in 'DST Upgrade' directory.
The 'loader.exe /index' took a minute or so to update the files.
We remove everything in our "PackageCache" directory as a precaution and bounced the Policy service.

We're test rolling the 2.2 patcher roll out to a few folks who already had 1.5 installed, and so far we are seeing duplicate 'net_rim_bb_timezoneupdater' modules on devices when viewed in the BES Manager. The Software Config status for these devices is now showing "Device Status Invalid". The DST2007Query tool reports TWO entries in it's output for these users, one for v1.5 and another for v2.2.

Yay...this is progress?

[Frank Castle]

I'm having mixed results, my test group is around 30 users .. the ones that were stuck on (running ...) a battery pull and the patch installed and prompted for a reboot (yea!!) .. others are not so lucky .. seems the ones that have the option to download the patch (% shows) still fail.

I'm going to add some clean users today and see if it works as it should. If not I'm going to push everyone the link to download via Blackberry Browser.

[dcpuser]

The actual patch itself hasn't changed as far as I know. It's just the patch manager that's downloading it. So if your users already have the patch, dont bother with this. For me, I'm only deploying this to users I haven't reached yet or users showing some oddities when I run the query tool.