NTP server on Windows

Ntp even though seems like relatively simple and not too much used functionality of our computers sometimes can cause a lot of issues, specially when we are working with servers that are time dependant and mainly with Active Directory. Active Directory structures usually work out of the box as every Domain controller is running an NTP server that is forced to be a peer of the computer or server that is joined to the domain. With rest of the computers they are usually synced with time.windows.com. Where problems occur is the network delays and connectivity issues. Sometimes we want to hide the computer from the network as well, and CMOS local clock is not always for trust in as it can cause small delays that over time turn to big ones.

Main app for tracking the time status on Windows is w32tm application. In order to simply see the status of current NTP status you can type in Powershell '''w32tm /query /status'''

App as well has an option for '/verbose' if you need more information which we will need in most of the cases. The output of the command should show you next output

''' Leap Indicator: 0 Stratum: 4 Precision: -23 Root Delay: 0.2543448s '''