Question

Locked

System Time in Windows XP 1 Hour Ahead after DST Change

By tjohnston ·
My organization has 75 users running Windows XP. We're running Exchange 03 on a Windows Server 03 machine.

After the DST time change over the weekend, We've had an issue with our System clocks and times in Outlook being 1 hour ahead. Some users reported it on Monday, others on Tuesday, and more still Today.

Here are the time settings:
Time Zone GMT -5:00 (in South Carolina)
Auto. Adjust for Daylight Saving Changes
Sync. with Internet Time Server: time.windows.com

If I open the Time settings and manual set the clock, or get it to sync with the internet server, the correct time is displayed for the duration of that Windows Session. If I log off and come right back, the clock again will be displayed an hour Ahead.

We've already installed Windows Update KB955839: http://support.microsoft.com/?kbid=955839. This update supposedly addressed the DST changes for windows time.

I've also noticed the Received time stamps on incoming mail in Outlook appears an hour ahead as well.

If I uncheck the "Auto. Update for DST changes" and hit apply, the clock goes to the correct time and my email times appear correct.

Has anyone else experienced this problem? Anybody have any ideas on how to fix it?

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Run tzedit on one of those machines

by Kenone In reply to System Time in Windows XP ...

What dates are set for DST?

Collapse -

Same Issue one Exchange client

by isaac In reply to System Time in Windows XP ...

Have the same issue with a client machine. I have double and triple checked all dst updates are applies, updated to SP3. Definetly an issue with the machine because I can log into OWA and I have the same issue. I would rather not rebuild a computer for a clock issue.

Collapse -

If you can log into OWA....

by ThumbsUp2 In reply to Same Issue one Exchange c ...

.... and have the same problem... then it's not a machine problem. It's a server problem. Are you sure the server/machine is set to the correct time zone... the new one used after the time zone change took place in late 2007? Did you run the TZEdit program?

Back to Networks Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums