See what time the domain thinks it is:
Net time /Domain:domain.name.fqdn
I found this command useful as it was reported that three computers were all set at different times. I used the domain command and the following command to query all four devices for their time nearly simultaneously.
See what time each computer says it is:
Net time \computer-name
After running the above commands, I found that one of the computers was about a minute and a half ahead of the others which were correctly pulling the domain time. It’s not enough of a difference to cause issues with Kerberos authentications but the computer is part of a fail-over system with logs that would have a hard time syncing up alarms with different timestamps.
See where the computer is pulling its time from:
W32tm /query /source
After running the above command, it returned an IP address that meant nothing to me. It was pulling its time from some other server and that was the source of the problem.
You can ask Windows for its Windows Time configuration. It’s not very informative if everything is working properly but gives you something to compare to a working computer.
Hope this information can help you
when I ran w32tm /query /services its coming back as VM IC Time Synchronisation Provider
Whats best practice here is it to follow the below article?