Setting A Reliable Time Server For Your PDC Emulator

Sharing Options:
Setting A Reliable Time Server For Your PDC Emulator
Rate this post

Setting A Reliable Time Server For Your PDC EmulatorSetting A Reliable Time Server For Your PDC Emulator


ISSUE

You need to set an authoritative time server on your PDC emulator and make it remain a reliable time source for your domain.

APPLIES TO
Windows Server 2008/2008r2/2012/2012r2.  The authoritative time is configured only on the PDC emulator for your domain.  The other domain controllers will pickup the time changes at next sync.  You can optionally run the w32tm /resync command on the additional domain controllers to make them pickup changes immediately.

RESOLUTION
Follow these steps to set a new time server source and make your PDC emulator a reliable time source for your domain.

  1. Find out who your PDC emulator is. Run the following command on a domain controller in a command prompt:
    • netdom /query fsmo
  2. Login to the PDC emulator that you discovered from step 1.
  3. Open an administrator command prompt (run as administrator), and run the following commands (shown in BOLD):

w32tm /config /syncfromflags:manual /manualpeerlist:”<time server #1>, <time server #2>”
You can specify NTP and SNTP servers, you must enter at least one address of a trusted time server.

You can use FQDN and/or IP Address.  We recommend:  time.nist.gov and utcnist.colorado.eduIf you decide to use these time servers, you can simply copy the following line and paste in to your command prompt:
w32tm /config /syncfromflags:manual /manualpeerlist:time.nist.gov,utcnist.colorado.edu

See available public NIST time servers here -> http://tf.nist.gov/tf-cgi/servers.cgi

w32tm /config /reliable:yes
This command makes the PDC a reliable time source for your domain, this is a requirement!

net stop w32time
Stops the time service

net start w32time
Starts the time service

If the time is now correct on your PDC, you are done!  Check your event log on the PDC emulator, look under ‘Windows Logs’ -> ‘System’.  You should see the time service synchronized and received valid data from your selected server(s) above.

If not, run these additional steps (from your administrator command prompt, still)

w32tm /query /configuration
Queries your current configuration (review it)

w32tm /resync
Forces a resync of settings.

w32tm /config /reliable:yes
Forces the new configuration to be a reliable time server for your domain.

Tags: #windows #time #nist #windowsserver #techsupport

Sharing Options:

Be the first to comment

Leave a Reply