{"id":298,"date":"2014-05-01T16:45:08","date_gmt":"2014-05-01T16:45:08","guid":{"rendered":"http:\/\/www.itcrumbs.com\/?p=298"},"modified":"2019-02-07T04:39:45","modified_gmt":"2019-02-07T04:39:45","slug":"setting-up-ntp","status":"publish","type":"post","link":"http:\/\/www.itcrumbs.com\/?p=298","title":{"rendered":"Setting up NTP"},"content":{"rendered":"
http:\/\/blog.mpecsinc.ca\/2014\/05\/hyper-v-standalone-configure-host-as.html<\/a><\/h5>\n
Hyper-V Standalone: Configure the Host as Authoritative Time Server and Guests to Use It<\/a><\/h5>\n

We have a number of single server virtualization solutions where the VMs are running at quite a high load point. <\/p>\n

This tends to create timing issues with the VMs not being able to keep up with keeping time. In some cases we have SQL VMs that can skew time visibly. <\/p>\n

So, we need a reliable time source. We are not able to set pool.ntp.org as the time source for the primary DC in this situation as it would not be keeping time very well either thus requiring a more frequent polling interval. Do that with ntp.org and the server will receive a Kiss-of-Death packet in short order. <\/p>\n

So, we configure our Hyper-V host to be an authoritative time server polling ntp.org’s servers every 30 minutes. <\/p>\n

To do so we need to set things up on the host. <\/p>\n

    \n
  1. Allow UDP Port 123 Inbound on the firewall <\/li>\n
  2. Configure the host as a time server: <\/li>\n
  3. We run the Fix It Myself steps <\/li>\n
  4. Verify Type<\/strong> is set to NTP<\/strong>\n