Time Issue

[Jon]

I am having a tough time figuring this one out. I have a WIN2K3 domain.
It is set up with a Root/Child domain structure. Over the last few weeks
some of the workstations in the environment have had their time off by 8 -
10 minutes. It's a random group of systems each day and not always the same
ones.
I ran the w32tm command line utility and synced the systems but it did
not stay resident. The systems would show their times off by 8 - 10 minutes
again the next day. I set up the network to use the 1st root DC as their
time server via a GPO but I am still having the issue. The event viewers
show the workstations are getting their time from either of the child DC's
(which gets their time from the root DC) so everything should be good.
However, the time is still off.

Any suggestions would be fabulous and thanks and advance for any
replies -

Jon

 

[Rich Greenberg]

I am having a tough time figuring this one out. I have a WIN2K3 domain.
It is set up with a Root/Child domain structure. Over the last few weeks
some of the workstations in the environment have had their time off by 8 -
10 minutes. It's a random group of systems each day and not always the same
ones.
I ran the w32tm command line utility and synced the systems but it did
not stay resident. The systems would show their times off by 8 - 10 minutes
again the next day. I set up the network to use the 1st root DC as their
time server via a GPO but I am still having the issue. The event viewers
show the workstations are getting their time from either of the child DC's
(which gets their time from the root DC) so everything should be good.
However, the time is still off.

Any suggestions would be fabulous and thanks and advance for any
replies -

Are these servers powered down nights and/or weekends? A wandering
clock is one symptom of a dying battery, and even if never powered down,
a failing battery can sometimes still affect the clock.