[Gotrek]

FYI you cannot setup both applications on the same server.

It's either stay with 2.2 or upgrade users to 2.3

With half our roll out done we've opted to keep 2.2 hopefully trying to setup the second app won't have screwed up our roll out.

We wanted to leave the 2.2 users at 2.2 but upgrade the users we haven't applied the policy too with 2.3 but no go.

[amukhey]

We are currently upgrading from 2.2 to 2.3 (Pilot Group) and then do a mass deploy to the rest of the company on 2.3

[doni]

i'm upgrading my two test groups from 2.2 to 2.3 right now. btw, -invokesync with the new query tool did nothing; still shows improper Awaiting Patch. hoping some better results with 2.3, but not holding my breath.

[amukhey]

Doni-What time did you run this? also did you restart the windows svc for the sync? This takes anywhere from 2-4 hours. We have had much better results when we re-deployed 2.3. The percentage went up from 12% to 50% over the weekend.

[cartwfh]

Unfortunately I am on of the few people who decided to try pushing the patch manager as early as possible to have a bit of reaction time if it did not work. Our current version is 1.5 but because of ll of the failing devices i would like to have the option to deploy 2.3 before it gets to be too late. How do I double back to update the units that I have already pushed patch manager version 1.5? it seems like getting them to patch manager 2.3 wirelessly would be the most direct fix for some of our issues. Any thought or help would be appriciated.

[DarienA]

cart all I did was unzip the files to the same folder as the original shared patch folder, when I did a configuration check with the handheld configuration it updated status to show update required and eventually pushed the new one out.

[stella]

When we did a test on an earlier patch manager I think it was 1.0 or 1.5 there was an extra time zone called New Mexico City, this was one of the ways checking if the DST patch had installed correctly besides checking options and from the patch 2007 had be successfully installed or not. Now in the later 2.2 or 2.3 patch manager the New Mexico City timezone seems not to appear anymore but options DST2007 displays installed. Has the patch manager actually installed or not, is there another check that we can do? I know DSTQuery tool reports this but is there another quick check or test that can be carried to check to see if the patch actually works?

[cartwfh]

Darien,

Did you have to re-index the shared directory in which the patch manager files were installed?

[DarienA]

I honestly don't remember, but doing that wouldn't hurt.

[BBQueen]

When we saw the erratic results we were getting with the PUSH, we chose to manually update our executives' devices. The Query tool was laughable, when not frustrating.

It's amazing to me that both RIM and Microsoft waited until the 11-1/2th hour to write and test the updates. They knew this was coming one and a half years ago! SHAME on them.