CMOS (non-volatile harware) clock sycronisation
- From: Brian McCauley <my-name-with-a-dot-in-it@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 29 Apr 2008 08:04:02 -0700
I have a number of Windows member servers in an AD forrest and in steady
state w32time keeps there clocks approximately right (+-200ms). However when
they are rebooted their clocks are (for a short time) all over the place (for
10-30 minutes) because, it would appear, that nothng is keeping the CMOS
(non-volatile harware) clock in sycronisation with the Windows clock.
On Linux I'd just create a cron job to do "clock -uw" periodically but I
can't find any equivalent on Windows.
Please note: I'm asking how to get Windows to keep the *CMOS* clock synced
so that when servers are rebooted their clocks start out *approximately*
right *before* w32time manages to syncronise to a time server.
.
- Follow-Ups:
- Re: CMOS (non-volatile harware) clock sycronisation
- From: Pegasus \(MVP\)
- Re: CMOS (non-volatile harware) clock sycronisation
- Prev by Date: RE: Internal network remote desktop control
- Next by Date: WSUS client stops talking to server
- Previous by thread: Adding Server 2008 DC to 2003 Domain
- Next by thread: Re: CMOS (non-volatile harware) clock sycronisation
- Index(es):
Relevant Pages
|
