Time services on Domain Controllers

Several times now I have seen issues where the local domain controllers can loose their time accuracy. I think there are several reasons for this, most notably is where the Domain Controller is a virtual machine.

To fix the time service in Server 2008R2 – 2012R2 – 2016 use the following command prompt:

net stop w32time
w32tm /config /syncfromflags:manual /manualpeerlist:oceania.pool.ntp.org
w32tm /config /reliable:yes
net start w32time
w32tm /query /configuration

This forces the Domain controller to both sync against an outside time source as well as advertising to the network that it is a reliable time source.