G
Guest
After working hard to make sure that all systems on our network were patched,
(XP, sp2, Windows 2000 Pro/Server, 2003 Servers), we are experiencing strange
issues with this. Most XP machines received the daylight saving time update
via Windows Update as well as 2003 machines
When restarting machines, the system time is jumping ahead an additional
hour on top of the daylight saving time shift.
Example: Computer time reads 12:00 pm. This is the correct time with DST
2007. The base time of the computer would then be 11:00am (and if DST 2007
didn't exist, this would be the correct time), with the additional hour added
in. When restarting a system, the time then shifts to 1:00 pm.
As you can imagine, on a network, this is causing all sorts of minor issues,
but most of all it is annoying. And before anyone wastes their time asking:
- all Windows XP, sp2 computers have been patched and verified.
- all Windows 2000 machines, including 2 servers, have been patched and
verified.
- all Windows 2003 Server machines (including our Global Catalog Server)
have been patched and verified.
- Exchange 2003 Server / Outlook clients, have had the Outlook Tool ran
against each mailbox to update calendar items.
On most computers, I have manually taken off the checkbox to update for
daylight saving time changes. This appears to prevent any updates and shows
the correct, DST 2007 time.
My questions:
- I'm wondering if the system BIOS could be mistakenly shifting the system
time somehow? So when the system restarts, the BIOS has the correct time,
updates Windows when it boots and then Windows shifts ahead an additional
hour to compensate for DST.
- Because we are on an ADS network that has time-updating built in through
the Windows Time service, all computers should eventually synchronize to the
correct time. Does each computer then apply its own 1 hour shift to the UTC
(universal time) applied by the server? Or does the time sent by the server
override this?
Also, these changes were not evident over the weekend when testing was done.
Any suggestions? Anyone experiencing a similar problem?
(XP, sp2, Windows 2000 Pro/Server, 2003 Servers), we are experiencing strange
issues with this. Most XP machines received the daylight saving time update
via Windows Update as well as 2003 machines
When restarting machines, the system time is jumping ahead an additional
hour on top of the daylight saving time shift.
Example: Computer time reads 12:00 pm. This is the correct time with DST
2007. The base time of the computer would then be 11:00am (and if DST 2007
didn't exist, this would be the correct time), with the additional hour added
in. When restarting a system, the time then shifts to 1:00 pm.
As you can imagine, on a network, this is causing all sorts of minor issues,
but most of all it is annoying. And before anyone wastes their time asking:
- all Windows XP, sp2 computers have been patched and verified.
- all Windows 2000 machines, including 2 servers, have been patched and
verified.
- all Windows 2003 Server machines (including our Global Catalog Server)
have been patched and verified.
- Exchange 2003 Server / Outlook clients, have had the Outlook Tool ran
against each mailbox to update calendar items.
On most computers, I have manually taken off the checkbox to update for
daylight saving time changes. This appears to prevent any updates and shows
the correct, DST 2007 time.
My questions:
- I'm wondering if the system BIOS could be mistakenly shifting the system
time somehow? So when the system restarts, the BIOS has the correct time,
updates Windows when it boots and then Windows shifts ahead an additional
hour to compensate for DST.
- Because we are on an ADS network that has time-updating built in through
the Windows Time service, all computers should eventually synchronize to the
correct time. Does each computer then apply its own 1 hour shift to the UTC
(universal time) applied by the server? Or does the time sent by the server
override this?
Also, these changes were not evident over the weekend when testing was done.
Any suggestions? Anyone experiencing a similar problem?