User Tools

Site Tools


networking:windows:windows_time

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
networking:windows:windows_time [2017/09/07 10:51]
gcooper
networking:windows:windows_time [2024/05/06 11:09] (current)
gcooper
Line 1: Line 1:
 ====== Windows Timekeeping Configuration ====== ====== Windows Timekeeping Configuration ======
  
-http://support.microsoft.com/default.aspx?scid=kb;EN-US;223184+https://serverfault.com/questions/584397/active-directory-time-synchronisation-time-service-event-id-50/584420#584420
  
 ===== Configure the Windows Time Service ===== ===== Configure the Windows Time Service =====
Line 44: Line 44:
 <file> <file>
 netdom /query fsmo netdom /query fsmo
 +w32tm /query /source
 </file> </file>
  
Line 53: Line 54:
 </file> </file>
  
-:!: If you  get the error ''The computer did not resync because no time data was available.'', try a reboot of the DC.+:!: If you  get the error **''The computer did not resync because no time data was available.''**, try a reboot of the DC and **check that NTP traffic is permitted in the firewall** (UDP/123).
  
 If your time is off by too much (more than 3600 seconds), you'll have to set the time manually with the Date and Time applet. If your time is off by too much (more than 3600 seconds), you'll have to set the time manually with the Date and Time applet.
Line 81: Line 82:
  
 http://nefaria.com/2013/03/configure-windows-server-20082012-to-sync-with-internet-time-servers/ http://nefaria.com/2013/03/configure-windows-server-20082012-to-sync-with-internet-time-servers/
 +
 +<note tip>If you move the PDC FSMO role to another server, and your PDC is stuck on ''Local CMOS Clock'', you may need to use a GPO shown here: https://theitbros.com/configure-ntp-time-sync-group-policy/</note>
 +
 +==== Check ====
 +
 +<file>
 +w32tm /monitor
 +</file>
 +
 +==== Primary Domain Controller ====
  
 <file> <file>
 net stop w32time net stop w32time
 +w32tm /unregister
 +w32tm /register
 w32tm /config /manualpeerlist:"0.us.pool.ntp.org 1.us.pool.ntp.org" /syncfromflags:manual /reliable:yes w32tm /config /manualpeerlist:"0.us.pool.ntp.org 1.us.pool.ntp.org" /syncfromflags:manual /reliable:yes
 net start w32time net start w32time
-w32tm /query /status+w32tm /query /status /verbose 
 +w32tm /query /source 
 +w32tm /query /peers 
 +w32tm /query /configuration 
 +</file> 
 + 
 +==== Member Server ==== 
 + 
 +<file> 
 +net stop w32time 
 +w32tm /unregister 
 +w32tm /register 
 +net start w32time 
 +w32tm /config /syncfromflags:domhier /reliable:NO 
 +w32tm /config /update 
 +w32tm /resync 
 +w32tm /query /status /verbose 
 +w32tm /query /source
 w32tm /query /peers w32tm /query /peers
 w32tm /query /configuration w32tm /query /configuration
Line 92: Line 122:
  
 ===== Virtual Machines ===== ===== Virtual Machines =====
 +
 +FIXME Need verify this statement:
  
 The most accurate way to keep guest operating system time synchronized with real time is probably to use the **VMware Tools** or **XenServer Tools** time synchronization functions. The most accurate way to keep guest operating system time synchronized with real time is probably to use the **VMware Tools** or **XenServer Tools** time synchronization functions.
 +
 +==== Citrix ====
 +
 +FIXME Need verify registry entries
 +
 +{{ :networking:windows:vm_time_sync_disable.reg.zip |Citrix Registry Entries for PDC}}
 +
 +These registry entries disable time sync to the virtualization host (drift) when using Citrix Tools and allow NTP to work normally.
  
 ==== Virtualbox ==== ==== Virtualbox ====
networking/windows/windows_time.1504803068.txt.gz · Last modified: 2017/09/07 10:51 by gcooper