Hi all,

Currently running a 2003 domain with XP clients. I was under the impression
that being in a domain made the PDC the time source, which all XP clients
sync with using the W32TM service.

However I have noticed that some PC's seem to be losing the time? I am
trying to understand how this is not being corrected. I understand that PC's
uses the CMOS for a clock, (We have simply been changing this battery and
setting the time - which does fix the problem).. but why does it come to
this...

I have found this registry key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\w32time\Config

Which seems to contain various settings, but it stil is not making sense...
even if the CMOS clock is wrong, why does it not automatically set the
Windows clock back during boot up?

Not sure, time is kind of difficult. It might be that if the time
difference is greater than 5 minutes it gradually fixes it.

You could use a computerscript or something along the lines of

net time /set /domain

UselessUser wrote:
> Hi all,
>
> Currently running a 2003 domain with XP clients. I was under the impression
> that being in a domain made the PDC the time source, which all XP clients
> sync with using the W32TM service.
>
> However I have noticed that some PC's seem to be losing the time? I am
> trying to understand how this is not being corrected. I understand that PC's
> uses the CMOS for a clock, (We have simply been changing this battery and
> setting the time - which does fix the problem).. but why does it come to
> this...
>
> I have found this registry key
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\w32time\Config
>
> Which seems to contain various settings, but it stil is not making sense...
> even if the CMOS clock is wrong, why does it not automatically set the
> Windows clock back during boot up?