DST Foolishness

  • Thread starter Thread starter nick
  • Start date Start date
N

nick

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




- Show quoted text -
Click to expand...

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?
 
nick said:
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?
Click to expand...

Presuming of course all the machines are set to the same time zone, are
you sure that the clients haven't been patched?
 
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 -
Click to expand...

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?
 
Back
Top