Automatic Domain Time Synchronization

[shaazaminator]

I have a Computer Configured GPO that synchronizes the time on the clients PC to the DC that synchronizes to a NIST Server, and has been running flawlessly since implemened until now when the old Daylight Savings Time was supposed to end.

The odd thing is my DC has the correct time as do all the PC's in the domain except three of them.

GPI states the RSOP of the GPO is applied to these PC's, as does Group Policy Modeling in the GPMC.

I haverun "gpupdate"and "w32tm /config /syncfromflags:domhier /update" from the command prompt and have stopped and restarted the time service to no avail.

Daylight Savings Time stops this weekend, but I would still like to know why the GPO has not been applied to these PC's.

Any ideas??????

- Doug

[jdobiash]

Is it possible that those 3 machines still are under the old DST settings? If so they would show the wrong time even if synced to the server properly.

[shaazaminator]

Sorry for the delay, unexpected things always seem to crop up...

Thought about that, so I reset the time manually on the PC's (it reset
itself later) tried changing the DST checkbox, running GPupdate (no
change) and w32tm /update (no change) all users have (gasp!!) admin
rights to their PC's Hmmmmmmmm

[jdobiash]

Sorry for the delay, unexpected things always seem to crop up...

Thought about that, so I reset the time manually on the PC's (it reset
itself later) tried changing the DST checkbox, running GPupdate (no
change) and w32tm /update (no change) all users have (gasp!!) admin
rights to their PC's Hmmmmmmmm

Is it possible that those 3 computers are still running on the old DST time, which would have switched over a week ago? If so, checking or unchecking the DST checkbox wouldn't have any effect as they would already think it ended.

Download the following program from Microsoft:
http://download.microsoft.com/download/5/8/a/58a208b7-7dc7-4bc7-8357-28e29cdac52f/tzedit.exe

Run it on those machines and see if it shows "First Sunday of November" as the End Time instead of "Last Sunday in October" like it used to be.

[shaazaminator]

BINGO!

That is exactly what it was.
Changed the settings using the tzedit app from MS, reset their DST and all is well.

Thanks for your help, it's little things like this that just nag at a person.

Happy Halloween!

[jdobiash]

And only 2 days to spare, lol You should check to make sure they are correct for the March changeover as well, so you don't run into this again next year. It should be "Second Sunday in March" instead of "First Sunday in April".