Over the past few weeks, I noticed my computer's time was drifting several minutes behind. This actually caused me to be late to a couple different meetings because I kept working on my computer instead of leaving the house. Well, since it's a Saturday and I had some time to fix the problem once and for all, I wanted to share what I've learned since it took longer than I expected to configure NTP on a Windows Server.
It all began several months back when I setup a Windows 2008 R2 Server and thought "wouldn't it be cool if I set my desktop's clock to update from the server instead of a reliable external source?" So, I unwittingly redirected my desktop from its reliable 0.us.pool.ntp.org to my server's ip address with the assumption the server was already getting it's time from a default external source. Hence the source of my lateness months later.
Fast forward to today. I figured it would be a quick 5 minute fix to remote into the server, find some sort of ntp settings tab in a properties window, then add my multiple servers. I should have known better than to assume Microsoft would have added such a logical GUI feature.
After searching the Internet, reading through several Microsoft technet articles, and testing multiple configurations, here's what I've got...
Recent comments
20 min 16 sec ago
17 hours 16 min ago
21 hours 13 min ago
2 days 2 min ago
5 days 1 hour ago
6 days 5 hours ago
6 days 7 hours ago
6 days 9 hours ago
6 days 12 hours ago
6 days 14 hours ago