Last Updated: 2/23/2021 (this is an artificial date)
No matter what environment you are working in setting the time is always an important component.
The following is the quick version for setting A domain controller up as a time source.
net stop w32time w32tm /config /manualpeerlist:”0.us.pool.ntp.org 1.us.pool.ntp.org” /syncfromflags:manual /reliable:YES /update net start w32time w32tm /config update w32tm /resync /rediscover
A quick note: If you are setting up your domain controller, please remember to include the /syncfromflags:manual setting. If you don’t when you query your peers you might only see one peer.
w32tm /stripchart /computer:dc0
If there is a BAD problem you can always use the following two commands. They effectively unregister the “Windows Time” service and delete the key that is being used. Using the /register parameter configures the Windows Time Service and establishes a fresh set of keys. You might also do a “NET STOP w32time” before doing this.
w32tm /unregister w32tm /register
This is useful to confirm that the source is no longer set to “local”
w32tm /query /source
w32tm /query /status
The following might be useful if troubleshooting.
w32tm /query /monitor
Note: This is an expanded demo. Please note the 0x1 for time.windows.com which then uses the “SpecialPollInterval” See the registry key path below. While not stated in the Microsoft doc explicitly it is of type DWORD
w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org, time.windows.com,0x1" /reliable:yes
The valid settings for the mode used with the /manualpeerlist switch include:
- 0x01 – use special poll interval SpecialInterval
- 0x02 – UseAsFallbackOnly
- 0x04 – send request as SymmetricActive mode
- 0x08 – send request as Client mode