Windows Server: The System Clock does not Synchronize due to a Large Time Difference

• The time on a Windows system is incorrect.
• The Windows Time service is configured to synchronize with a time source, but it fails to do so.
• The w32tm /resync command returns "The computer did not resync because the required time change was too big."
  
• The System event log contains Time-Service error 34, which also refers to a large time difference.
  

Often, no action is necessary, and the Windows Time service eventually synchronizes the local system clock with its source. If immediate synchronization is needed, one of two registry values can be modified to make this happen.

Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config

• MaxPosPhaseCorrection: This value specifies the largest positive time correction (in seconds) that the system will make.
• MaxNegPhaseCorrection: This value specifies the largest negative time correction (in seconds) that the system will make.

If the system lock must move forward to reach the correct time, set the value of MaxPosPhaseCorrection. If it must move backward, set the value of MaxNegPhaseCorrection. The time difference between the local clock and its source is given in the description of Time-Service error 34, as shown above. Set one of these registry values to be greater than what is shown in the error, or set it to FFFFFFFF (hexadecimal) to specify no limit.

Restart the Windows Time service for the change to take effect. The clock should synchronize shortly after the service is restarted. The registry change can then be reverted.