From what I can tell the server in question doesn't have the new DST
patch from MS. I manually changed the time on a DC to the correct one.
All the servers have the correct time, but client stations are all one
hour ahead. (The clock on the servers do not have auto adjust for DST
checked while the client stations do). Is there an easy way to fix
this domain wide?

Re: DST Foolishness by Bob

Bob
Tue Mar 11 05:22:05 PDT 2008

You mean you manually changed the server to the wrong time. Since you
didn't patch the machine, DST hasn't started yet.

Daylight Saving Time Help and Support Center
http://support.microsoft.com/gp/cp_dst

nick wrote:

> From what I can tell the server in question doesn't have the new DST
> patch from MS. I manually changed the time on a DC to the correct one.
> All the servers have the correct time, but client stations are all one
> hour ahead. (The clock on the servers do not have auto adjust for DST
> checked while the client stations do). Is there an easy way to fix
> this domain wide?


Re: DST Foolishness by nick

nick
Tue Mar 11 05:36:06 PDT 2008

On Mar 11, 7:22=A0am, Bob I <bire...@yahoo.com> wrote:
> You mean you manually changed the server to the wrong time. Since you
> didn't patch the machine, DST hasn't started yet.
>
> Daylight Saving Time Help and Support Centerhttp://support.microsoft.com/g=
p/cp_dst
>
>
>
> nick wrote:
> > From what I can tell the server in question doesn't have the new DST
> > patch from MS. I manually changed the time on a DC to the correct one.
> > All the servers have the correct time, but client stations are all one
> > hour ahead. (The clock on the servers do not have auto adjust for DST
> > checked while the client stations do). Is there an easy way to fix
> > this domain wide?- Hide quoted text -
>
> - Show quoted text -

It's probably so simple that I'm complicating it. From what I know
none of the machines in the domain are patched. But right now on the
servers it is 8:35. On every domain computer it is 9:35. The servers
have adjust for daylight saving time on them since I put that back.
The client stations have the same adjust for daylight saving time
checked as well. Why do the client stations "see" the server time, but
decide to jump it ahead 1 hour?

Re: DST Foolishness by Bob

Bob
Tue Mar 11 07:19:44 PDT 2008



nick wrote:
> On Mar 11, 7:22 am, Bob I <bire...@yahoo.com> wrote:
>
>>You mean you manually changed the server to the wrong time. Since you
>>didn't patch the machine, DST hasn't started yet.
>>
>>Daylight Saving Time Help and Support Centerhttp://support.microsoft.com/gp/cp_dst
>>
>>
>>
>>nick wrote:
>>
>>>From what I can tell the server in question doesn't have the new DST
>>>patch from MS. I manually changed the time on a DC to the correct one.
>>>All the servers have the correct time, but client stations are all one
>>>hour ahead. (The clock on the servers do not have auto adjust for DST
>>>checked while the client stations do). Is there an easy way to fix
>>>this domain wide?- Hide quoted text -
>>
>>- Show quoted text -
>
>
> It's probably so simple that I'm complicating it. From what I know
> none of the machines in the domain are patched. But right now on the
> servers it is 8:35. On every domain computer it is 9:35. The servers
> have adjust for daylight saving time on them since I put that back.
> The client stations have the same adjust for daylight saving time
> checked as well. Why do the client stations "see" the server time, but
> decide to jump it ahead 1 hour?

Presuming of course all the machines are set to the same time zone, are
you sure that the clients haven't been patched?


Re: DST Foolishness by nick

nick
Tue Mar 11 07:45:19 PDT 2008

On Mar 11, 9:19=A0am, Bob I <bire...@yahoo.com> wrote:
> nick wrote:
> > On Mar 11, 7:22 am, Bob I <bire...@yahoo.com> wrote:
>
> >>You mean you manually changed the server to the wrong time. Since you
> >>didn't patch the machine, DST hasn't started yet.
>
> >>Daylight Saving Time Help and Support Centerhttp://support.microsoft.com=
/gp/cp_dst
>
> >>nick wrote:
>
> >>>From what I can tell the server in question doesn't have the new DST
> >>>patch from MS. I manually changed the time on a DC to the correct one.
> >>>All the servers have the correct time, but client stations are all one
> >>>hour ahead. (The clock on the servers do not have auto adjust for DST
> >>>checked while the client stations do). Is there an easy way to fix
> >>>this domain wide?- Hide quoted text -
>
> >>- Show quoted text -
>
> > It's probably so simple that I'm complicating it. From what I know
> > none of the machines in the domain are patched. But right now on the
> > servers it is 8:35. On every domain computer it is 9:35. The servers
> > have adjust for daylight saving time on them since I put that back.
> > The client stations have the same adjust for daylight saving time
> > checked as well. Why do the client stations "see" the server time, but
> > decide to jump it ahead 1 hour?
>
> Presuming of course all the machines are set to the same time zone, are
> you sure that the clients haven't been patched?- Hide quoted text -
>
> - Show quoted text -

I checked under the installed programs, and didn't see the patch
there. I'm trying to figure out the logic here....why would client
stations see the correct time under "net time" yet decide to go ahead
and increment by an hour?