Our domain's PDC emulator is about two minutes fast, and its reported time source is Local CMOS Clock. It's a physical server. Can I point it at an external NTP server, or should I plan for disruption?
Is it safe to fix a PDC emulator that's two minutes fast?
Answers
Two minutes is generally a manageable correction, but I wouldn't call it risk-free. Confirm the offset against a trusted time source rather than relying only on phones, and check whether other domain controllers and clients have similar offsets.
I'd make the change during a quiet period and watch authentication and application logs afterward. Systems don't necessarily correct at the same instant, so temporarily different clocks can matter, especially if any machines are already close to the allowed Kerberos time skew.
Reply to this answer
For the PDC emulator, you can configure manual NTP peers from an elevated command prompt. For example, run w32tm /config /manualpeerlist:"time.windows.com,0x8 pool.ntp.org,0x8" /syncfromflags:manual /reliable:yes /update, then run w32tm /resync.
Check w32tm /query /source and w32tm /query /status afterward. If the resync fails or the source stays local, check that the server can reach the chosen peers over UDP 123 and that policy isn't overriding the configuration. Use sources your organization is allowed to query.
Reply to this answer
Check the rest of the time hierarchy too. Other domain controllers and domain members normally follow the domain hierarchy, rather than each being manually pointed at public servers. Verify their actual sources after the PDC is corrected.
Group Policy can manage this, but plan for the PDC role moving. The new role holder needs the external source configuration, and the old one needs to return to the domain hierarchy. A policy filtered for the role can help, provided the fallback configuration is also handled.
Reply to this answer
You don't have to use a public server directly if there's a reliable internal NTP service available. A small number of internal time servers can sync from trusted upstream sources and serve the rest of the network. Just trace the dependencies so you don't create a time sync loop.
Reply to this answer
I'd skip a blanket reboot just for this. Check the correction and the health of authentication and affected applications first. If something behaves oddly after the clocks change, investigate that specific service rather than assuming every machine needs restarting.
Reply to this answer
Add your answer
Answers are reviewed before publication.
!7v+clamporbit_582:
A restart of the Windows Time service may help apply or troubleshoot the change if the update and resync don't work as expected.