DST 2007 hell

[bustamove]

Applied patch according to Microsoft KB. everything seems to be OK OWA/Outlook.

After DST time change Sunday, Outlook calendars are OK, but some OWA recurring appointments are one hour off (10AM instead of 9AM). It looks random... we have mixed users of Outlook and OWA. I dont know what to do now....

 

[RichardHuang]

I have the similar problem. Through OWA, the recurring appointents shift one hour (from 9am to 10am)during DST period. However the appointments change back to normal after April 1. I appiled the Windows 2003 DST update KB931836, Exchange DST update KB926666 and run outlook update tool. Can anybody please help??

 

[ShackDaddy]

If you ran the Calendar Update Tool before running KB926666, you shouldn't have trouble with your OWA-created appointments. If you ran KB926666 before TZMOVE, then the OWA-created appointments will be screwy. Most of the docs say that if you have some heavy OWA-calendar users, you should install KB926666 after the TZMOVE operation. You may have to fix them manually at this point.

ShackDaddy
Shackelford Consulting

 

[bustamove]

Remember Microsoft changed the patching order a few weeks ago? We did what they said initially and had to remov and reinstall KB926666, so I guess we are using the right order. Anyway, Lesson learned: never start early!

 

[MichealC4]

I'm having a similar issue.

I installed the DST patch on Exchange 2003 SP2 (including a bunch of other updates off Microsoft Update), and now the time is ahead by 1 when sending to another user. Doesn't matter of it is Outlook or not (I'm using Thunderbird over IMAP). OWA is okay, if you use it directly from the server itself. There's this lovely yellow bar now that tells me to set my timezone in OWA.

----------------------------
"Will work for bandwidth" - Thinkgeek T-shirt

 

[MichealC4]

Well, manually changing the time on the server that runs Exchange fixed the time received in both OWA and the clients (thunderbird, outlook, etc.). However, in OWA, the sent time reads an hour behind.

----------------------------
"Will work for bandwidth" - Thinkgeek T-shirt

 

[ShackDaddy]

TechieMicheal, you still haven't mentioned whether the time change on the server was a correction or whether you've just set it for the wrong time. Are you in a DST-correction region? Is the "update clock for DST" checkbox on your server checked? Did you run KB926666 on your server?

ShackDaddy
Shackelford Consulting

 

[MichealC4]

The time on the server had been correct before I started messing around with it (it seemed to properly set itself March 11th). I am in GMT -5, with the update automatically for DST checked. I did run 926666 successfully. I changed the timezone to GMT -4, changed the time back to the correct time, and from there the correct received time appeared.

----------------------------
"Will work for bandwidth" - Thinkgeek T-shirt