How to update results of DST Query (MOST EXCELLENT INFORMATION!!!)
 

Thanks to mrc7928 for reporting this info that RIM gave him:

Simply select all your users with the DST Patch software config applied and choose "Clear PIM Sync Backup Data" from the Service Control & Customization area. This will clear and resync the server side db's with the device, one of which I assume holds the latest result from the device's DST patcher application.

This works on Groupwise and on my Domino system so no reason it would not also work on Exchange.

Thanks mrc7928, this information will save ALOT of admins ALOT of manual checking!

Yup, this is working!!

Excellent guys!!! So far so good? Any side effect(s) after clearing the PIM Sync Backup Data, mahoward and x14?

No, though it resyncs the data immediately, so you may want to only do 100 at a time or so. I only do this to the people that show an error, not those that were successful.

I think it's also timing. The processed worked for all my test users I did last week. I've been updating about 100 users and the status don't update until a couple of days later.

So far only about 50% of the users I sent patch to has the "Applied" status.

As long as on the handheld it says "patch applied" can we ignore the errors seen on the report generated by query tool? .

The big impact here is if your backup connector doesn't pull the information from the devices in a timely manner. If a user decides to get a new device or their current takes a turn for the crapper, you won't have any backup data restored to them during activation.

The "CAUTION" light seems to be flashing rather brightly. :)

Anyone know for sure? Thanks

"As long as on the handheld it says "patch applied" can we ignore the errors seen on the report generated by query tool? ."

I haven't spoken to TSupport but quite a few ppl in the main DST Thread have said that TSupport have stated many times that the h/h is gospel. So, if the device says it's patched, we are meant to ignore DSTQuery :->

HTH
Stu

Thanks Stu,

I know of at least one incident where an 8707v failed via the browser, then upgraded via PC method, and then on the Hand held it said Patch Applied. However, query tool is still reporting original error, even though I cleared wireless backup data.

Bump
 

Giving this thread a BUMP as we seem to have forgotten about this most excellent info by mahoward.

Gonna give it a shot tonight for my list of misreporting folks.

Latest DSTQuery appears to have solved this issue.. for the most part.

Now now, as an Admin, you know that it's always good to have a backup plan. And then a backup to the backup.
"Redundant information is always worth repeating." Know who said that? Me. (y)

The invokesync parameter, and the talk about running it after hours, scared me. Also, I cannot just restart services on a server whenever I want. So I used the clear pim sync trick to update the final users who were showing waiting for patch.

BTW I have 1410 devices patched, 109 awaiting, 66 no helper, 11 not required, and 8 not supported. I got an initial 83% success rate, now I am having the local techs follow up with the 17% failures.

"talk about running it after hours, scared me"

I have about 500 users on average per BES, I did this after hours, and had no issues. Just an FYI.

Aw hell.... I ran it DURING normal business hours.
This job would be great if it wasn't for the users. LOL (kidding)

I am curious, once you do this process and let it sit for a while, does anyone use the -invokesync on top of it? Will it reverse the effect or cause some havoc?

Puzzled??!!
 

We followed all of the instructions to a T, but for some reason our handhelds will not update. The query finds our handhelds, then tells us that they are not updated. We have a BES 4.0 with Exhchange 2003. Anyone have any thoughts. Could it be a permission issue?

Are you at BES 4.0 exactly or at some revision of 4.0, like 4.04, etc? Have you checked an actual device to see if the patch was applied?

BES 4.0.6.12, and no i have not checked our devices. I'm not real sure where to look on the device.