We have had an issue recently relating to chronyD which primarily affects our redhat 7 servers and not the redhat 6 boxes, seems redhat 6 is a little bit more flexiable with regarding timesources but thats another story.

Typically we get out timesources from our fortigate (Stratum 2) resource (Stratum 1 being fortiguards NTP source where it gets the time form and stratum 0 being atomic clock)

We then cascade that down to the PDC role on the DC which is the stratum 3 source and then this rolls down to the other DCS’s Stratum 4).

Anyway when using time on redhat its always best to go for the fortigates rather than the windows timesource.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Add-PSSnapin VMware.VimAutomation.Core
Connect-VIServer -Server vcenter.local -User username -Password Password
$ServerList = Get-Content C:\serverlist.txt

Foreach ($vm in $ServerList)
{
New-AdvancedSetting -Entity $vm -Name tools.syncTime -Value '0' -Confirm:$false -Force:$true
New-AdvancedSetting -Entity $vm -Name time.synchronize.continue -Value '0' -Confirm:$false -Force:$true
New-AdvancedSetting -Entity $vm -Name time.synchronize.restore -Value '0' -Confirm:$false -Force:$true
New-AdvancedSetting -Entity $vm -Name time.synchronize.resume.disk -Value '0' -Confirm:$false -Force:$true
New-AdvancedSetting -Entity $vm -Name time.synchronize.shrink -Value '0' -Confirm:$false -Force:$true
New-AdvancedSetting -Entity $vm -Name time.synchronize.tools.startup -Value '0' -Confirm:$false -Force:$true
New-AdvancedSetting -Entity $vm -Name time.synchronize.tools.enable -Value '0' -Confirm:$false -Force:$true
New-AdvancedSetting -Entity $vm -Name time.synchronize.resume.host -Value '0' -Confirm:$false -Force:$true
}

Always remember to make the following vmx changes to the VM’s

And of couse set chronyd with the

1
maxdistance = 16