One of my customers had some time sync issues, we’ve build a new domain based on Windows 2008 R2 and all the DC’s in the new domain where configured with the core switch(es) as NTP server and the time on these switches where right. So we went on searching and apparently somebody turned on the following feature:
By doing this the RES AM Agent syncs the time of the target machine with the datastore and there was a mismatch between the datastore and the NTP servers. After disabling this feature the NTP functionality made sure that the time was in sync with the original NTP servers again.
The following two tabs change content below.
Kees Baggerman
Kees Baggerman is a Staff Solutions Architect for End User Computing at Nutanix. Kees has driven numerous Microsoft and Citrix, and RES infrastructures functional/technical designs, migrations, implementations engagements over the years.
Latest posts by Kees Baggerman (see all)
- Nutanix AHV and Citrix MCS: Adding a persistent disk via Powershell – v2 - November 19, 2019
- Recovering a Protection Domain snapshot to a VM - September 13, 2019
- Checking power settings on VMs using powershell - September 11, 2019
- Updated: VM Reporting Script for Nutanix with Powershell - July 3, 2019
- Updated (again!): VM Reporting Script for Nutanix AHV/vSphere with Powershell - June 17, 2019
Known issue indeed Patrick, you can use AM do schedule a “net time /yes” command to all agents to fix it….
This isn’t Patrick’s blog Rob 🙂 And I tend to use a regular NTP server rather than using a clientside application to sync time