This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 64%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
I have gone around and around with synchronizing network time for months and frankly I'm sick of it. Time was always a set it and forget it configuration in the past, not so anymore.
I have 70 systems. Of those systems have have a dozen that simply will not keep time. Net Time on any system will point to the designated server for time. I have set and reset time on more systems more times than I care to admit and the file server dedicated to serving time is accurately configured drawing from time.microsoft.com. I have workstations that always fall 2 minutes behind, others that start out accurately and end up hours or days off, and some that simply refuse to stay in sync even for a few seconds...all confirmed to be pointing to the proper server.
Enough! I'm not taking this nonsense into the new year.
Are there any recommended, or even known, third party non-microsoft domain time synchronization applications in the market for purchase? I've got more to do that tinker with something that should never be difficult.
Yes you can from cmd.exe do an
w32tm /query /configuration
then look for Type: NT5DS
--please don't forget to Accept as answer if the reply is helpful--
Okay, I've followed the instructions given on the PDC as well as the DCs. I've also checked some of the problem systems and ran a w32tm /resync after verifying net time and its now saying successful. I did notice that all 5 systems are not synchronous time-wise even after resync. One was a minute ahead and a few were a minute behind. I could excuse that as the local system clock having a slight variance but pointing to a DC to get time should bypass any local settings on a domain authenticated workstation, no?
The default configuration will keep the time sync to something less than five minutes. If you wanted high accuracy time then there are more requirements and steps to achieve this. First support boundaries must be met
https://learn.microsoft.com/en-us/windows-server/networking/windows-time-service/support-boundary
I look more deeply into this. One of our applications is very time sensitive. It just refuses to work if the time falls too much our of sync.
Thanks
Sounds good.
Some general info about Windows Time service
--please don't forget to Accept as answer if the reply is helpful--
It's been a long road but I already had this bookmarked so I assume I've already attempted this. It can't hurt to try again. Hopefully this time things stabilize.
I've used an external time source time.microsoft.com and also two additional options from UofA in Southern Arizona.
All of my servers are 2019 (Current) and all of my workstations are Win10 (current). Is there a quick and direct way to ensure all of my servers, aside from the PDC, are NT5DS?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 28.999999999999996%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVW%3C/text%3E%3C/svg%3E)
Hi,
I am glad to hear that your issue was successfully resolved\I am pleased to know that the information is helpful to you. If there is anything else we can do for you, please feel free to post in the forum.
Best Regards,
Vicky
It been more than a week since re-configuring time across my network and time has held to within 3-5 minutes.
Thank you
Good news.