NTP problem on windows 2016 Active directory virtualized via proxmox 5 and 6.

[José Roberto]

Hello people,

I'm having trouble keeping my active directory schedule on windows server 2016 synchronized with the ntp server, I researched some micorsoft forums and what I saw most was people saying it might be due to hypevision.
In hypeV they have a function that they disable called "time synchronization"

In proxmox 5 and 6 is there anything like this?

The output of the "w32tm.exe /query /source" command
Local CMOS Clock

should be my ntp server, but i can't do it!

 

[José Roberto]

Hello people,

I'm having trouble keeping my active directory schedule on windows server 2016 synchronized with the ntp server, I researched some micorsoft forums and what I saw most was people saying it might be due to hypevision.
In hypeV they have a function that they disable called "time synchronization"

In proxmox 5 and 6 is there anything like this?

The output of the "w32tm.exe /query /source" command
Local CMOS Clock

should be my ntp server, but i can't do it!

Sorted out.

I didn't find a function like this in proxmox, but the problem with windows getting the machine's local time was due to the delay with the ntp server, so it was getting locally.