I'm trying to set the time sync on my Primary Domain Controller (PDC) to use 1.us.pool.ntp.org, but I think I've messed up something basic. I've disabled Hyper-V's time pass-through and followed a sequence of commands. Here's what I've done: I stopped the time service using 'net stop w32time', then used the command to configure my NTP server, and finally restarted the service with 'net start w32time'. However, when I run the update command, it fails because the service isn't running. After starting it, the update works but I still don't see 1.us.pool.ntp.org listed as my NTP server. Any thoughts on how to fix this?
3 Answers
You have most of it down! To manage time servers for a PDC efficiently, consider implementing a GPO that applies the time settings to the PDC role. You can create a filter to target the PDC in Group Policy Management. From there, enable the Windows NTP Client and configure it similarly to what you’d do manually. It can help ensure that if the role moves, the NTP settings go along with it.
It seems like stopping the time service might be causing the issue. You could actually set everything up in one command, and it's recommended to use multiple pool servers for better reliability. Try running this command instead: w32tm /config /update /manualpeerlist:"0.us.pool.ntp.org,0x8 1.us.pool.ntp.org,0x8 2.us.pool.ntp.org,0x8 3.us.pool.ntp.org,0x8" /syncfromflags:MANUAL /reliable:YES.
Just a heads up, going direct to/from a VM for NTP can be problematic since the VM may not recognize when it's been frozen. It’s often better to sync with the host instead.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures