Wednesday 7 August 2013

Configure Windows Server 2008 domain controller to sync time with an external NTP

What:

Windows Server 2008 R2

Problem:

Clock on domain controller is drifting.

Event ID 12: Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.

Solution:

1. Start > run, cmd hit enter
2. Type in
w32tm /query /status
In output you should find line saying:
Source: Local CMOS Clock
3. Choose your server from the list NTP servers
4. Use the following command to see the time difference
w32tm /stripchart /computer:uk.pool.ntp.org /samples:4 /dataonly
5. Set a new NTP server
w32tm /config /manualpeerlist:uk.pool.ntp.org /syncfromflags:manual /reliable:yes /update
6. Sync your time
w32tm /resync
7. Confirm a new set up
w32tm /query /status
w32tm /stripchart /computer:uk.pool.ntp.org /samples:4 /dataonly

If you server is not a domain controller use the following command.

w32tm /config /manualpeerlist:uk.pool.ntp.org

Source

3 comments:

  1. PERFECT! SIMPLE, CLEAR AND BETTER THAN A TECHNET ARTICLE... :)

    ReplyDelete
  2. After searching (wading) thru MS Tech Net and others, a simple set of commands to correct what was a disaster. (2008R2 PDC in a VM)
    Appreciated. Thanks

    ReplyDelete
  3. Thank you so much. I've had this problem for quite a while now.

    ReplyDelete