Time Sync

[Phil]

When a timesync occeurs in a domain between an XP xlient
and a 2000 server, is the client BIOS clock updated or
just windows time?

i.e. after a client reboot should its time still be
accurate with the server or will it need to re-synchronise?

 

[Lanwench [MVP - Exchange]]

The clock is the clock is the clock....it's the system BIOS clock; Windows
doesn't have a separate one.
Are you having problems with this?

 

[Phil]

A problem indeed!

I have a 100 station test network and need to record some
accurate boot and logon times, but I'm finding that the
clock is out by up to 3 minutes when booted up and it
takes a while for the timesync to kick in and sync the
time with a server. One in sync another reboot of the
station puts it all back to square one

!?

 

[Alex Nichol]

The clock is the clock is the clock....it's the system BIOS clock; Windows
doesn't have a separate one.

That is misleading. Windows keeps its own time, set initially from the
BIOS clock at boot, and then maintained by counting timer interrupts.
It is because it sometimes gets the wrong idea about interval between
these that you get the windows clock running at a very bad rate. And
the answer to that is *not* the motherboard battery, as we get rather
tired of saying here. Provided the errors are within limits, the
Internet Time sync will calculate the actual interval and adjust things
for it, so that the clock runs at correct rate.

The Windows clock updates the BIOS one when you set time manually, and
at shut-down: I presume it does at an Internet sync, but cannot be
certain of that one