DST Updates - fun, fun


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?
 
Ad

Advertisements

G

Guest

Hi Jeff,
I am seeing the exact same thing with 30+ pcs, on a AD windows 2003
server network. Please help!
 
G

Guest

I'm experiencing the same thing on my PC. My clock keeps jumping forward
every hour. I downloaded an Atomic Clock Sync tool, but I have to manually
ping the clock to fix it every hour.
 
G

Guest

Same problem here except times keep jumping forward and back. Unchecking the
auto synch.box does not help. currently using a 2000 service pack 4 server
with 8 win xp pro mobile clients and 10 xp pro desktops. all are Dells and
all laptops are inspiron1150's. Sort of a trial by fire my MCSE is not
complete yet.
 
G

Guest

I'm going to possibly answer my own post. I think I have figured out the
problem on my network - Time Server configuration!

I found that computers were jumping ahead an extra hour, but not all
computers. After doing some investigating, I have found that we have an old
configuration on a number of machines that are using a server that should no
longer be a time server. In our case, it is a Windows 2000 server that is a
SQL server and was used to synchronize time when we were on a NT 4 domain,
before we migrated to Active Directory on 2003. While a good number of
machines apparently are synchronizing correctly, there are a number of
machines that are synchronizing with the Windows 2000 machine and getting
incorrect times because DST is disabled on that server.

Resetting the NtpServer value in the registry on the local computer,
restarting time service, and then re-enabling DST fixes the issue (if
disabled). Also, I disabled the 2000 server from being a time server by
setting the "LocalNTP" value to "0" instead of "1".

Run this command from the command-line to see what Time Server you are
synchronizing with:

w32tm /dumpreg /subkey:parameters

the Value "NtpServer" has data that shows your time server like this:

NtpServer REG_SZ servername.domain.com


Perhaps your issue is the same as mine, or related to the fact that it is
synchronizing with a server that either a) shouldn't be a time server b) does
not have DST enabled

Just a suggestion, but by examining the registry and using the w32tm tool
(w32tm /? will display help), you might be able to troubleshoot your problem.
 
G

Guest

Hello,
This didn't help. When I ran the command from an XP client it shows
time.windows.com. Which is neither server. I have unchecked the apply dst in
the time window and this works. Otherwise it jumps ahead 2 hours!?! I could
really user the help on this.
 
Ad

Advertisements

G

Guest

I don't feel comfortable modifying the registry myself (I'm not even sure how
to access it) and my office is small so we don't have a real IT person or
department. I was hoping for an easier fix.
Jen
 
G

Guest

Dan,

Here's what I did on my network and this worked like a charm for me. The
problem you're having is that your XP clients are looking towards
time.windows.com for time updates, when if on ADS, they should be receiving
time from your domain controller(s), which should have the DST patch
installed.

I put these commands into a .CMD file and ran it from each client - but
unless you run it as admin, your clients will need power user rights to run
this script (updating registry, starting/stopping services):

net time /SETSNTP:<SERVER>
w32tm /config /update /syncfromflags:DOMHIER
net stop w32time
net start w32time
w32tm /resync

On the first command, replace <SERVER> with the DNS name or IP Address of
your Global Catalog Server (First Domain Controlller in your domain).

The first command updates the NtpServer value in the registry to the correct
server and it should replace "time.windows.com". The second command also
updates the registry, telling the computer to use the Domain Hierarchy to
receive time updates (which should be the default on ADS domains).

The 3rd and 4th command stop and restart the time service on the local
machine and the 5th command tells the local computer to resync immediately.

After running this on a machine, you will have to re-enable the checkbox for
Daylight Saving Time from the Date/Time Properties screen. Also, this won't
work unless both server and client have the DST patches installed, but you
said you took care of that. In my case, my clients were looking towards an
old server (2000 - not properly patched) for time and not the domain.

I also restart each client machine, so it reloads the registry values.

Hope it helps.

Jeff
 
G

Guest

Jen,

First thing is are you sure that all machines have the patches installed?
What version(s) of windows are you running?
Are you on a windows Active Directory network (2000, 2003), NT 4 domain, or
peer-to-peer network?

If you run the command: net time
it will tell you what you are using as a time server.

I can point you in the right direction for patches and/or using the TZedit
tool that microsoft provided.

I would uinstall the Atomic Clock tool too and try to fix the issue.
 
G

Guest

If you have a small network and have Windows 2000 (or XP, or XP sp1) or
earlier machines, use the TZEDIT tool to edit the time zone you're in and it
should quickly fix the problem. Note that this document provides the
download locations for the DST patches as well as the TZEDIT tool.

http://support.microsoft.com/kb/914387
 
A

ATBeckwith

Afterworking 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 savingtimeupdate
via Windows Update as well as 2003 machines

When restarting machines, thesystemtimeis jumping ahead an additional
hour on top of the daylight savingtimeshift.

Example: Computertimereads 12:00 pm. This is the correcttimewithDST
2007. The basetimeof the computer would then be 11:00am (and ifDST2007
didn't exist, this would be the correcttime), with the additional hour added
in. When restarting asystem, thetimethen 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 theirtimeasking:

- 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 savingtimechanges. This appears to prevent anyupdatesand shows
the correct,DST2007time.

My questions:
- I'm wondering if thesystemBIOS could be mistakenly shifting thesystemtimesomehow? So when thesystemrestarts, the BIOS has the correcttime,updatesWindows when it boots and then Windows shifts ahead an additional
hour to compensate forDST.

- Because we are on an ADS network that hastime-updating built in through
the WindowsTimeservice, all computers should eventually synchronize to the
correcttime. Does each computer then apply its own 1 hour shift to the UTC
(universaltime) applied by the server? Or does thetimesent by the server
override this?

Also, thesechangeswere not evident over the weekend when testing was done.
Any suggestions? Anyone experiencing a similar problem?

Hi Jeff,

I experienced a problem similar to yours. W2K server/domain, used
TZedit to modify DST on server. Time on some XP workstations updating
correctly, but some didn't. All patches applied. I verified the
server's TZ....toggled all settings multiple times, still failed.

Try this: Goto Start> Run> timedate.cpl on the W2K server and select
the appropriate TZ and apply.... I was simply double-clicking the
clock or going to the control panel which caused my problems.

Hope this helps!
Aric
 
Ad

Advertisements

Ad

Advertisements

R

Rock

<VBG>

Kelly said:
Awhhhh.....how sweet. Thank you! <big hug>

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm


Rock said:
Just sometimes. One number that doesn't change is where you are in my
book, #1. :)

--
Rock [MS-MVP User/Shell]

Kelly said:
Ah, so numbers do matter! <w>

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm



For English Systems use the edit on line 292:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Afterworking 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
savingtimeupdate
via Windows Update as well as 2003 machines

When restarting machines, thesystemtimeis jumping ahead an
additional
hour on top of the daylight savingtimeshift.

Example: Computertimereads 12:00 pm. This is the correcttimewithDST
2007. The basetimeof the computer would then be 11:00am (and
ifDST2007
didn't exist, this would be the correcttime), with the additional
hour added
in. When restarting asystem, thetimethen 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
theirtimeasking:

- 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 savingtimechanges. This appears to prevent anyupdatesand
shows
the correct,DST2007time.

My questions:
- I'm wondering if thesystemBIOS could be mistakenly shifting
thesystemtimesomehow? So when thesystemrestarts, the BIOS has the
correcttime,updatesWindows when it boots and then Windows shifts
ahead an additional
hour to compensate forDST.

- Because we are on an ADS network that hastime-updating built in
through
the WindowsTimeservice, all computers should eventually synchronize
to the
correcttime. Does each computer then apply its own 1 hour shift to
the UTC
(universaltime) applied by the server? Or does thetimesent by the
server
override this?

Also, thesechangeswere not evident over the weekend when testing was
done.
Any suggestions? Anyone experiencing a similar problem?

--
Thanks, Jeff

Hi Jeff,

I experienced a problem similar to yours. W2K server/domain, used
TZedit to modify DST on server. Time on some XP workstations
updating
correctly, but some didn't. All patches applied. I verified the
server's TZ....toggled all settings multiple times, still failed.

Try this: Goto Start> Run> timedate.cpl on the W2K server and select
the appropriate TZ and apply.... I was simply double-clicking the
clock or going to the control panel which caused my problems.

Kelly did you mean line 392?
 
Ad

Advertisements

K

Kelly

:blush:)

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm


Rock said:
<VBG>

Kelly said:
Awhhhh.....how sweet. Thank you! <big hug>

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm


Rock said:
Just sometimes. One number that doesn't change is where you are in my
book, #1. :)

--
Rock [MS-MVP User/Shell]

Ah, so numbers do matter! <w>

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm



For English Systems use the edit on line 292:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Afterworking 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
savingtimeupdate
via Windows Update as well as 2003 machines

When restarting machines, thesystemtimeis jumping ahead an
additional
hour on top of the daylight savingtimeshift.

Example: Computertimereads 12:00 pm. This is the
correcttimewithDST
2007. The basetimeof the computer would then be 11:00am (and
ifDST2007
didn't exist, this would be the correcttime), with the additional
hour added
in. When restarting asystem, thetimethen 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
theirtimeasking:

- 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 savingtimechanges. This appears to prevent anyupdatesand
shows
the correct,DST2007time.

My questions:
- I'm wondering if thesystemBIOS could be mistakenly shifting
thesystemtimesomehow? So when thesystemrestarts, the BIOS has the
correcttime,updatesWindows when it boots and then Windows shifts
ahead an additional
hour to compensate forDST.

- Because we are on an ADS network that hastime-updating built in
through
the WindowsTimeservice, all computers should eventually synchronize
to the
correcttime. Does each computer then apply its own 1 hour shift to
the UTC
(universaltime) applied by the server? Or does thetimesent by the
server
override this?

Also, thesechangeswere not evident over the weekend when testing
was done.
Any suggestions? Anyone experiencing a similar problem?

--
Thanks, Jeff

Hi Jeff,

I experienced a problem similar to yours. W2K server/domain, used
TZedit to modify DST on server. Time on some XP workstations
updating
correctly, but some didn't. All patches applied. I verified the
server's TZ....toggled all settings multiple times, still failed.

Try this: Goto Start> Run> timedate.cpl on the W2K server and
select
the appropriate TZ and apply.... I was simply double-clicking the
clock or going to the control panel which caused my problems.

Kelly did you mean line 392?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top