Commands above should be fine if your sources are working correctly and/or your connection is OK (firewall or Microsoft Forefront can be an issue also). The commands below can help with troubleshooting
All above ideas have been tried but did not help. The original problem still exists: "The computer did not resync because the required time change was too big."
Solution is found in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\w32time\Config
change this if the local time is in a hurry (e.g. 31-Dec-2050):
MaxNegPhaseCorrection
change this if the local time is delayed (e.g.
1-Jan-1980): MaxPosPhaseCorrection
The default values are 0xD2F0 (i.e. 54000 sec. = 15 hours)
(use Google for more details)
I use this simple win_clock_sync.bat file from Start Menu StartUp:
Almost none of the solutions (except @Akos) work if the host is an Windows Server 2016 Active Directory Domain Controller (ADDC), as it treats itself as a "reliable" source that cannot make big time change.
w32tm /resync /force does not work, because the /force does not appear in server 2016.
net time /SET /Y does not work either, because it would have asked:
Do you want to set the local computer's time to match the time at
\AD.example.net? (Y/N) [Y]
Of course, it won't work if you are on AD.example.net, /Y just hides the question.
Option /syncfromflags:manual means sync with NTP listed in peer list (i.e. external NTP), /update for notifying the time service the configuration have changed.
Restart the w32time
Stop-Service w32time
Start-Service w32time
Sync
w32tm /resync
This should work.
If you DO need ADDC as a reliable time source, make it reliable again:
As Kyle said
w32tm /resync
is the modern way to do this. See this Link to Microsoft Knowledgebase (KB 307897) for more information on the w32tm command.There is also
net time
which is an older version but perhaps easier.For those that still asking this question.
To update, use the command below (2008 and 2012 server compatible)
change the ntp_server with your source
Restart the time service
Resync the time
Verify your sync status
Commands above should be fine if your sources are working correctly and/or your connection is OK (firewall or Microsoft Forefront can be an issue also). The commands below can help with troubleshooting
To list out peers
To list out NTP Sources:
You can use the following command:
w32tm /resync
You can use:
Additionally, using
w32tm /resync /rediscover
will also "force redetection of network resourced before resynchronization."Or using:
Will prompt you to set the time to the DC. (Works for older versions of Windows)
OS: MS Windows 7
All above ideas have been tried but did not help. The original problem still exists: "The computer did not resync because the required time change was too big."
Solution is found in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\w32time\Config
(use Google for more details)
I use this simple
win_clock_sync.bat
file from Start Menu StartUp:Enjoy! :-)
Powershell one liner if ntp server is configured:
gsv w32time | sasv; w32tm /resync /force
You can put this .bat file in the startup if you CMOS batery failed so it can resync upon OS start:
According to Riot Games
Based on my research, I bookmarked this:
If Hyper-v host server is a part of the same domain, disable time sync for PDC guest vm
On PDC(or any single workstation), update from quoted internal DNS or ip untrusted address(0x8):
W32tm /config /manualpeerlist:"192.168.0.254,0x8" /syncfromflags:manual /reliable:yes /update
Powershell Restart-Service w32time
W32tm /resync /nowait
on dc that is not PDC:
w32tm /config /syncfromflags:domhier /update
W32tm /resync /rediscover
On servers and other stations for update time only, not config:
W32tm /resync /nowait
Check that time is really updating(difference ):
w32tm /stripchart /computer:192.168.0.254 /samples:15 /dataonly
if time service broken or failed and need reset:
Powershell Stop-service w32time W32tm /unregister Timeout 30 W32tm /register Powershell Start-service w32time
Note: NTP port is 123 UDP and should give the same output on any healthy computer
Other commands w32tm /query /status w32tm /query /peers w32tm /query /configuration
Best practice from ms: Time Sync best practices
Almost none of the solutions (except @Akos) work if the host is an Windows Server 2016 Active Directory Domain Controller (ADDC), as it treats itself as a "reliable" source that cannot make big time change.
w32tm /resync /force
does not work, because the/force
does not appear in server 2016.net time /SET /Y
does not work either, because it would have asked:Of course, it won't work if you are on
AD.example.net
,/Y
just hides the question.The steps work for me using PowerShell:
Option
/syncfromflags:manual
means sync with NTP listed in peer list (i.e. external NTP),/update
for notifying the time service the configuration have changed.This should work.