Configure an NTP server in your Active Directory [Full Guide]


The protocol NTP to network Time Protocol is protocol that synchronizes , via a computer network, local clock computer from other servers references .

at first, you will connect the Domain Controller your AD bringing the role FSMO of PDC Emulator as c is it used as a reference for the clock in an Active Directory. If you are in an infra test, you may not have changed the layout FSMO roles or you have only a single CD, use it.

To verify that you are on a Domain Controller that features well FSMO role of the PDC Emulator, you can do the following:

  • log in RDP with the desired DC,

  • Open Active Directory Users and Computers

  • right-click on the domain name and select from the popup menu Operations Masters

  • then go to the PDC to see the name of the DC server that carries this FSMO role.


You can also use the following command

net dom query fsmo

Now we will tell our Domain Controller to sync with a specific server. It can be a public time server (not recommended because it means that your DC that directly contacts the) or you have an NTP relay within your infrastructure. This connects to a public time server and then the CD (or other service) that connects to update automatically.

FYI, the port is used to communicate the 123 / UDP ( for openings flow ). 🙂

Login therefore the Domain Controller and run the following commands:

w32tm / config /manualpeerlist: / syncfromflags: manual / reliable: yes / update

Replace the IP address of course with what suits you. You can find public time servers at the following address: . You can also use a hostname in the previous command rather than an IP

To force the synchronization, use the following command:.

w32tm / resync

Finally, once the change is taken into account, you can also check your configuration by running the following commands:

w32tm / query / configuration


w32tm / query / status


You can check the timings are going well. Especially with the following parameters: Last Successful Sync time


No comments:

Powered by Blogger.