I've seen all of the cab files for the DST fixes, but they all require some kind of manual user intervention.
We have about 1,000 users on ranging PPC models (HPs, X30s, X50s, X51s). Needless to say, we're trying to avoid ANY manual user intervention on the end-user's behalf.
With the DST fixes I've seen for non-HP devices, they all require swapping the time zone back/forth to complete it.
Does anyone know of any patch that will automate that manual step? We DO have the ability to make Remote Registry updates, AND sync and execute remote files on the devices.
I had to apply patches to my PC windows XP, my Outlook and my Axim x51v. I had to switch the times zones once back and forth to complete the patch. It took 3 minutes tops to patch 3 things. I don't understand what the problem is, perhaps I am missing what you are trying to say. It was not a big deal to do the updates.
I've seen all of the cab files for the DST fixes, but they all require some kind of manual user intervention.
We have about 1,000 users on ranging PPC models (HPs, X30s, X50s, X51s). Needless to say, we're trying to avoid ANY manual user intervention on the end-user's behalf.
With the DST fixes I've seen for non-HP devices, they all require swapping the time zone back/forth to complete it.
Does anyone know of any patch that will automate that manual step? We DO have the ability to make Remote Registry updates, AND sync and execute remote files on the devices.
Thanks very much for your suggestions!
Isn't the swapping of the time zones just to verify that the DST patch has been correctly applied?
If you can remotely execute files on the devices I would think you would be all set with the CAB file from Microsoft. If not, then you you could just use the registry changes found in this Knowledge Base Article and apply them remotely as you have suggested you can.
there is a program on this forum created by dogfood.
it's basically a cab that you just click and install that's it, you don't touch any registry (which I don't know what to do with the DST) nor swap the timezone.
Hope this helps.
Thanks for the responses, all. It turns out Microsoft released an updated patch and revised their instructions sometime last week.
We only noticed this because when we downloaded the latest patch Thursday, the files were different sizes. The latest patches did not require the time zone swap.