
Setting A Reliable Time Server For Your PDC Emulator
ISSUE
You need to configure an authoritative time source on the PDC Emulator so the domain has a reliable time hierarchy.
APPLIES TO
Windows Server 2008 / 2008 R2 / 2012 / 2012 R2 / 2016 / 2019 / 2022 / 2025
The authoritative time source is set only on the PDC Emulator. All other domain controllers will pick up the change at the next sync, or you can force them to update now with w32tm /resync from an admin Command Prompt.
RESOLUTION
Identify the PDC Emulator. On any domain controller, run:
- netdom /query fsmo
Log in to the PDC Emulator found in the netdom /query fsmo step.
Open an elevated command prompt (Run as administrator), run the following commands. Set the external time sources with the time servers of your choice:
- w32tm /config /syncfromflags:manual /manualpeerlist:”time.nist.gov”
You can use FQDN or IP. At least one trusted time server is required. We recommend: time.nist.gov as it is highly available and works well for most in the USA. See all available NIST time servers: http://tf.nist.gov/tf-cgi/servers.cgi
Mark the PDC as a reliable time source (required):
- w32tm /config /reliable:yes
Restart the time service:
- net stop w32time
- net start w32time
Verify. Check the System event log on the PDC Emulator (Windows Logs → System). You should see the time service synchronized and receiving valid data from the configured servers.
IF THE TIME IS STILL INCORRECT
From the same elevated command prompt, run:
- w32tm /query /configuration
- w32tm /resync
- w32tm /config /reliable:yes
Then restart the time service again and recheck the event log.
![]()