Quote Originally Posted by 105547111
Does this mean I can get rid of fixtime.cron completely as my Windows 2003 Server accounts for daylight savings If I check at 05, the server will report the new time (DST or no DST)?

It executes so much faster than fixtime.cron, even though fixtime is looking at the same server....
05 * * * * ntpdate 192.168.0.1
Means execute 5 minutes on the hour "ntpdate"

The way time sync works:
http://www.eecis.udel.edu/~mills/ntp/html/notes.html
In particular, NTP does not attempt to synchronize clocks to each other. Rather, each server attempts to synchronize to Universal Coordinated Time (UTC) using the best available source and available transmission paths to that source. This is a fine point which is worth understanding. A group of NTP-synchronized clocks may be close to each other in time, but this is not a consequence of the clocks in the group having synchronized to each other, but rather because each clock has synchronized closely to UTC via the best source it has access to.
So in theory, you shouldnt need fixtime.cron