For all clients, DCs, and servers except the authorative time server:
. Starting and stopping W32time will resysnch the computer on which the command is run. (except for Win NT based PDCs, where the settings are .ini based and not registry based as in Win2k, XP and Win2003. W32time -update is required as a statement between stopping and starting the time service.)
. net time domain /set will do a resynchronization
. W32tm -once will do a resynchronization
. W32tm -s will do a resynchronization
Any changes to the time server in Win2k will require a stop and restart of the time service so that the registry values are re-read. This will also resynchronize the authoratiative time server. In a complex Domain it is recomended that the FSMO primary domain controller emulator serving as authoratative time source be rebooted after configuration changes to the W32time service. For XP and Windows 2003 enhancements to the W32tm command avoid this:
w32tm /resync [/computer:<computer>] [/nowait] [/rediscover] [/soft]
Tell a computer that it should resynchronize its clock as soon as possible, throwing out all accumulated error statistics.
computer:<computer> - computer that should resync. If not
specified, the local computer will resync.
nowait - do not wait for the resync to occur;
return immediately. Otherwise, wait for the resync to
complete before returning.
rediscover - redetect the network configuration and rediscover network sources, then resynchronize.
soft - resync utilizing existing error statistics. Not useful, provided for compatibility.