Never saw this occur before. Am at small site, running servers in AD, all
2003 R2. All clients WERE in a workgroup (amazing, after all these years,
that this is still out there...) Anyways... I am migrating PC's running XP
to domain as I can. ALL XP pc's are joining domain OK. ALL are set up with
correct time and time zone prior to joining domain.

ALL servers are displaying correct time and time zone.

ALL PC's and servers are in same small campus/LAN.

When the XP PC's join the domain, they add an hour to their time. So,
server is at 1:00PM. PC running XP (with ALL patches, yes even the daylight
savings time patch) is showing 1:00 PM. I join the PC running XP to the AD
domain. The PC goes from 1:00 PM to 2:00 PM. If I set it back to 1:00 PM,
it resynchs itself to time server (Which is the domain PDC, verified by doing
a "net time" at the command prompt) and changes itself back to an hour
forward, i.e. from 1:00pm to 2:00 pm.

This has occurred with three PC's I have moved into domain so far. I have
temp fixed by changing the PC time zone to one with a one hour difference
from our "real" time zone.

And again, all patches are there. All are synching to a 2003 server with
correct time and time zone. and used "net time" to verify the time is
correct on the time server from the PC point of view. I mean really, the PC
shows 2:00pm, the server shows 1:00 pm. I do a "net time" at the PC, and it
shows "time server blah-blah 1:00 pm". Time zones are set OK, patches are
all on. Has to be a server issue, but I cannot find any patch info for
server for time synch issues.

Not a horrible thing, but it should not be happening.

Windows Server 2003 SP level? DST patch (and other patches) installed on the
server?

Run this on PC and server:
net time /querysntp

What does it show?

"ex-CTP" <exCTP@discussions.microsoft.com> wrote in message
news:EF12DB30-269A-455E-A3DD-712FDB9E1C57@microsoft.com...
> Never saw this occur before. Am at small site, running servers in AD, all
> 2003 R2. All clients WERE in a workgroup (amazing, after all these years,
> that this is still out there...) Anyways... I am migrating PC's running
> XP
> to domain as I can. ALL XP pc's are joining domain OK. ALL are set up
> with
> correct time and time zone prior to joining domain.
>
> ALL servers are displaying correct time and time zone.
>
> ALL PC's and servers are in same small campus/LAN.
>
> When the XP PC's join the domain, they add an hour to their time. So,
> server is at 1:00PM. PC running XP (with ALL patches, yes even the
> daylight
> savings time patch) is showing 1:00 PM. I join the PC running XP to the
> AD
> domain. The PC goes from 1:00 PM to 2:00 PM. If I set it back to 1:00
> PM,
> it resynchs itself to time server (Which is the domain PDC, verified by
> doing
> a "net time" at the command prompt) and changes itself back to an hour
> forward, i.e. from 1:00pm to 2:00 pm.
>
> This has occurred with three PC's I have moved into domain so far. I have
> temp fixed by changing the PC time zone to one with a one hour difference
> from our "real" time zone.
>
> And again, all patches are there. All are synching to a 2003 server with
> correct time and time zone. and used "net time" to verify the time is
> correct on the time server from the PC point of view. I mean really, the
> PC
> shows 2:00pm, the server shows 1:00 pm. I do a "net time" at the PC, and
> it
> shows "time server blah-blah 1:00 pm". Time zones are set OK, patches are
> all on. Has to be a server issue, but I cannot find any patch info for
> server for time synch issues.
>
> Not a horrible thing, but it should not be happening.