Skip to content

Time for time

Time servers send out an epoch pulse with descriptive data. Time clients then transpose that based on locally configured offsets.

Windows runs everything through AD, including the time for AD. The official schpiel from Redmond is “Make sure the hardware clock on your AD Forest PDC is set correctly.” Wut?

Most important factor is one time server/pool. Not everyone doing their own thing.

Centos:

Specify ntp servers in /etc/ntp.conf.

  • yum install ntp
  • nano /etc/ntp.conf
  • service ntpd start

ESXi:

  • Host-> Configuration -> Software -> Time configuration. This becomes the HW clock for VM’s.

Windows 2008 R2:

http://support.microsoft.com/kb/816042

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type|Type = NTP
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags|AnnounceFlags = 5
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer|Enabled = 1
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters|NtpServer = (space delimited addresses)
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval|TimeInSeconds = 900
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection|TimeInSeconds = 3600
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection|TimeInSeconds = 3600