Synchronizing Windows 2000/2003 Server Clock with Internet Time Server
By default, Windows-based computers use the following hierarchy:
- All client desktop computers nominate the authenticating domain controller as their in-bound time partner.
- All member servers follow the same process as client desktop computers.
- Domain controllers may nominate the primary domain controller (PDC) operations master as their in-bound time partner but may use a parent domain controller based on stratum numbering.
- All PDC operations masters follow the hierarchy of domains in the selection of their in-bound time partner.
It is therefore a good idea to synchronize your DC's with a Internet Time Server to ensure that your clock is up to date.
Windows 2003 Script
The following script will synchronize a Windows 2003 Server clock with a Internet Time Server. Generally, I create a batch script and schedule a Windows Task to run the script nightly.
w32tm /config /manualpeerlist:"tick.usno.navy.mil" /syncfromflags:MANUAL
w32tm /config /update
net stop w32time
net start w32time
w32tm /resync /nowait
Windows 2000 Script
The script is different for Windows 2000, but performs the same function.
net time /setsntp:tick.usno.navy.mil
NET STOP w32time
w32tm -once -v
NET START w32time
Ensure that the Network Time Protocol port, port 123, is open.
References