If you got this message regarding your AD server that has PDC emulator role doesn’t have a proper NtpClient set up, like below:
Here is how you can get this sorted out:
Log on to the AD server (with PDC role) with administrator account and open elevated command prompt, and run the following commands:
net stop w32time w32tm /config /manualpeerlist:"0.uk.pool.ntp.org,0x1 1.uk.pool.ntp.org,0x1 2.uk.pool.ntp.org,0x1 3.uk.pool.ntp.org,0x1" w32tm /config /reliable:yes net start w32time
If all went well, running w32tm /resync should get a successful message.
If not, go to Event Viewer to find out more details why it failed.
To force all domain computers to sync the time with the DC you just set up, run the following commands in the elevated command prompt window.
net stop w32time w32tm /config /syncfromflags:domhier /update net start w32time
That’s probably all you need to get your AD server to act as the NTP server in your domain.
Here are a few more useful w32tm commands that come handy:
w32tm /query /configuration – check NTP configuration
w32tm /query /source – display time source
w32tm /query /peers – display the list of all configured NTP servers and their status
w32tm /query /status – display time service status