Forum Discussion
Setting Time on Domain
I am wanting to configure Time on my Domain Controller running Server 2016 so that all my other servers and workstations show the same time. Are there any simple step by step instructions on how to do this? Thank you!
- All domain members should use NT5DS domain time.
- Desktops and member servers sync with any domain controller.
- Domain controllers sync with PDC emulator (one per domain)
- PDC emulator in child domain can sync with any domain controller in parent domain.
- PDC emulator in parent domain syncs with either a hardware clock or possibly an external source.
https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/
for all domain members (aside from PDCe) should have happened by default but you can confirm by running;
w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32timethen checkw32tm /query /source
w32tm /query /configuration-----------------------------------------------for the PDCew32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /manualpeerlist:<preferred ip address> /syncfromflags:manual /reliable:yes /update
net stop w32time
net start w32time
then checkw32tm /query /source
w32tm /query /configuration(please don't forget to mark helpful replies)
3 Replies
- All domain members should use NT5DS domain time.
- Desktops and member servers sync with any domain controller.
- Domain controllers sync with PDC emulator (one per domain)
- PDC emulator in child domain can sync with any domain controller in parent domain.
- PDC emulator in parent domain syncs with either a hardware clock or possibly an external source.
https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/
for all domain members (aside from PDCe) should have happened by default but you can confirm by running;
w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32timethen checkw32tm /query /source
w32tm /query /configuration-----------------------------------------------for the PDCew32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /manualpeerlist:<preferred ip address> /syncfromflags:manual /reliable:yes /update
net stop w32time
net start w32time
then checkw32tm /query /source
w32tm /query /configuration(please don't forget to mark helpful replies)Thank you . I recently had few issues with PDC time sync which points to infoblox ntp and used a lot command on your list, the stratum numbering help resolved my issue .
The highest stratum supported is 15, and my Infoblox stratum was showing 14, which makes the PDC a stratum 15 – all other DCs will be a Stratum 16 or more which is unsupported.
Just a tip in case anyone run into Domain hierarchy time issues using third party ntp time source
All machines that are domain members should automatically sync their time with the domain controller that they authenticated against last. Those DCs will sync from the DC with the PDC Emulator role on it. That machine should be pulling time from an external source (make sure firewall is open). I believe it defaults to time.windows.com. This can be customized.
A good reference is here:
https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/windows-time-service-top
