Setting up PDC to be Authoritative Time Server
Posted on 2007-11-15
We're novices at the whole NTP/Time Service setup, so here goes:
Currently whenever a NET TIME command is run from a client PC on our domain, it returns a "Could not locate Time server" message. Although we are part of a larger Forest, we also have a member server that runs our Time & Attendance system on site and syncs with a Galleon Atomic clock.
I'd like an opinion on whether this scenario would be OK:
Set the PDC to be our local domain internal authoritative time server by pointing it at the T&A server (not an external NTP) using this command from the Microsoft site:
w32tm /config /manualpeerlist:<servername> /syncfromflags:manual /reliable:yes /update
Or should we sync with either 1) time.windows.com or 2) a PDC further up the domain forest?
Some experience/advice would be much appreciated.