This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
networking:windows:windows_time [2018/03/22 09:12] 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? | + | https://serverfault.com/questions/ |
===== Configure the Windows Time Service ===== | ===== Configure the Windows Time Service ===== | ||
Line 44: | Line 44: | ||
< | < | ||
netdom /query fsmo | netdom /query fsmo | ||
+ | w32tm /query /source | ||
</ | </ | ||
Line 81: | Line 82: | ||
http:// | http:// | ||
+ | |||
+ | <note tip>If you move the PDC FSMO role to another server, and your PDC is stuck on '' | ||
+ | |||
+ | ==== Check ==== | ||
+ | |||
+ | < | ||
+ | w32tm /monitor | ||
+ | </ | ||
+ | |||
+ | ==== Primary Domain Controller ==== | ||
< | < | ||
net stop w32time | net stop w32time | ||
+ | w32tm /unregister | ||
+ | w32tm /register | ||
w32tm /config / | w32tm /config / | ||
net start w32time | net start w32time | ||
- | w32tm /query /status | + | w32tm /query / |
+ | w32tm /query /source | ||
+ | w32tm /query /peers | ||
+ | w32tm /query / | ||
+ | </ | ||
+ | |||
+ | ==== Member Server ==== | ||
+ | |||
+ | < | ||
+ | net stop w32time | ||
+ | w32tm / | ||
+ | w32tm /register | ||
+ | net start w32time | ||
+ | w32tm /config / | ||
+ | w32tm /config /update | ||
+ | w32tm /resync | ||
+ | w32tm /query /status /verbose | ||
+ | w32tm /query /source | ||
w32tm /query /peers | w32tm /query /peers | ||
w32tm /query / | w32tm /query / | ||
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 | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | These registry entries disable time sync to the virtualization host (drift) when using Citrix Tools and allow NTP to work normally. | ||
==== Virtualbox ==== | ==== Virtualbox ==== |