DST applied patch, but all alarms are an hour early (fix?)

[Quilliam]

I applied the cingular 8525 patch for DST.

Yes my time adjusted fine, but now all my alarms go off an hour early.

So my 11am alarm goes off at 10am even though it says 11am.

This happens in both Schema and informant.

I don't understand why, but if someone could help me solve this it would be great.

[teambnet]

three weeks earlier. (oops make that '1 hour more')

Most calendar programs record their entires for appointments etc. in raw UTC (ie. without the relative time zone adjustment). Remember DST is only time manipulation there isn't really a "lost hour".

Example: you created an appointment for 9 AM on 3/14/07 last week and you're in the central time zone UTC -6. The program then saves the appointment with a starting time of 15:00 UTC not knowing it has to add an additional hour until after April 1 to it's appointments because local time is now UTC -7. So 15:00 UTC rolls around and the alarm goes off. Only now the local time is now UTC -7 15-7= 8 AM

A lot of calendar programs have this problem until the begining of old DST. It could be worse- I have several clients that exclusively use the "all day function" (0:00 UTC -6 to 24:00 UTC -6) and now for three weeks everything lasts two days.

See if the vendor has an update. MS had one for outlook that was supposed to adjust dates in the WM calendar but I saw one report this morning that improperly patched or configured exchange servers are screwing it up (complicating matters: the time zone is not a gpo and if improperly set (to 'central america' rather than 'central time') the change doesn't happen).

[djstegges]

I applied the fix that microsoft released before the DST came about to my users and all worked and tested all ok.

I have niced that a few of the users that have got lots of calendar entries i had to sync the device with the server after removing all data via active sync.


D

[Quilliam]

So worst case since I have applied the fix,

New apointments I add and apointments next year should not have problems.

Just my old ones?

[y2whisper]

Similar happened to me but everything went an hour later and the time change never happened

[teambnet]

The upshot: DST patching was not our finest hour and we're still endeavoring the issue. :confused:

What kills me is M$ had almost TWO FULL YEARS to fix this and it's clear they didn't build a comprehensive test environment. Nor did they bother to build a proper updating tool or mechanism. Even religiously applied updates didn't work.

Not to mention that unless MS provides a WM5 AKU with the change built in there are a lot of people running around with phones that will revert to old DST rules after every hard reset. :eek: