Another DST question

  • Thread starter Thread starter Art Frank
  • Start date Start date
A

Art Frank

Guest
I noticed that my Windows 2000 server did not change time zones on Sunday
(3/9/08) from PST to PDT. So, I thought it wasn't properly patched, and I
went to Microsoft to follow their instructions (KB914387) for W2K systems. I
used tzedit to edit the timezone, and low and behold, the timezone setting
was ALREADY CORRECT (2nd Sunday in March). However, the time was still PST
and not PDT. According to MS, after editing the time zone, you should change
the time zone then change it back to re-load the time zone database. I did
that, and the server's time was then correct.

My question: Why did I have to do that? (I had to do the same thing with a
stray W2K workstation on my network.) The timezone setting was correct (as
far as I could tell) before the DST change. The server was set to
automatically adjust the clock for DST. I haven't ever touched the timezone
settings on either of these machines (they've been my responsibility for only
a few months) and they've certainly been rebooted in the last couple of
months. I thought this was AUTOMATIC. I would rather not have to do this
again in the fall...
 
Re: Another DST question

This is covered in the KB article that you mentioned, but to keep it brief,
Windows has two locations in the registry for time zone information. The
huge registry section that contains all the updates to the registry is the
section Microsoft refers to as the time zone database.

The date/time applet in the control panel that is used to read the time zone
database and update the second section of the registry that really isn't
covered in detail. It should be noted that TZEdit does not update both
sections of the registry, so both steps are required.

If both steps where followed late last year, I'm surprised you had to mess
with it this year as it should have been automatic.

"Art Frank" <ArtFrank@discussions.microsoft.com> wrote in message
news:B80B2A5C-B787-406D-9522-73F4C44B7B11@microsoft.com...
>I noticed that my Windows 2000 server did not change time zones on Sunday
> (3/9/08) from PST to PDT. So, I thought it wasn't properly patched, and I
> went to Microsoft to follow their instructions (KB914387) for W2K systems.
> I
> used tzedit to edit the timezone, and low and behold, the timezone setting
> was ALREADY CORRECT (2nd Sunday in March). However, the time was still
> PST
> and not PDT. According to MS, after editing the time zone, you should
> change
> the time zone then change it back to re-load the time zone database. I
> did
> that, and the server's time was then correct.
>
> My question: Why did I have to do that? (I had to do the same thing with
> a
> stray W2K workstation on my network.) The timezone setting was correct
> (as
> far as I could tell) before the DST change. The server was set to
> automatically adjust the clock for DST. I haven't ever touched the
> timezone
> settings on either of these machines (they've been my responsibility for
> only
> a few months) and they've certainly been rebooted in the last couple of
> months. I thought this was AUTOMATIC. I would rather not have to do this
> again in the fall...
 
Re: Another DST question

Ah, I did not realize that tzedit did not handle both sections of the
registry. I will revisit KB914387 and make sure that everything in the
registry is correct.

I'm not certain that this was correctly handled last year, since I wasn't
around for "fall back." I assumed that my predecessor had handled this, but
we all know what they say about assuming...

Thanks for your response.

"neo [mvp outlook]" wrote:

> This is covered in the KB article that you mentioned, but to keep it brief,
> Windows has two locations in the registry for time zone information. The
> huge registry section that contains all the updates to the registry is the
> section Microsoft refers to as the time zone database.
>
> The date/time applet in the control panel that is used to read the time zone
> database and update the second section of the registry that really isn't
> covered in detail. It should be noted that TZEdit does not update both
> sections of the registry, so both steps are required.
>
> If both steps where followed late last year, I'm surprised you had to mess
> with it this year as it should have been automatic.
>
> "Art Frank" <ArtFrank@discussions.microsoft.com> wrote in message
> news:B80B2A5C-B787-406D-9522-73F4C44B7B11@microsoft.com...
> >I noticed that my Windows 2000 server did not change time zones on Sunday
> > (3/9/08) from PST to PDT. So, I thought it wasn't properly patched, and I
> > went to Microsoft to follow their instructions (KB914387) for W2K systems.
> > I
> > used tzedit to edit the timezone, and low and behold, the timezone setting
> > was ALREADY CORRECT (2nd Sunday in March). However, the time was still
> > PST
> > and not PDT. According to MS, after editing the time zone, you should
> > change
> > the time zone then change it back to re-load the time zone database. I
> > did
> > that, and the server's time was then correct.
> >
> > My question: Why did I have to do that? (I had to do the same thing with
> > a
> > stray W2K workstation on my network.) The timezone setting was correct
> > (as
> > far as I could tell) before the DST change. The server was set to
> > automatically adjust the clock for DST. I haven't ever touched the
> > timezone
> > settings on either of these machines (they've been my responsibility for
> > only
> > a few months) and they've certainly been rebooted in the last couple of
> > months. I thought this was AUTOMATIC. I would rather not have to do this
> > again in the fall...
>
>
>
 
Back
Top