SOLVED

Setting Time on Domain

%3CLINGO-SUB%20id%3D%22lingo-sub-1324853%22%20slang%3D%22en-US%22%3ESetting%20Time%20on%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1324853%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20wanting%20to%20configure%20Time%20on%20my%20Domain%20Controller%20running%20Server%202016%20so%20that%20all%20my%20other%20servers%20and%20workstations%20show%20the%20same%20time.%20Are%20there%20any%20simple%20step%20by%20step%20instructions%20on%20how%20to%20do%20this%3F%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1324853%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1325009%22%20slang%3D%22en-US%22%3ERe%3A%20Setting%20Time%20on%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1325009%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F238560%22%20target%3D%22_blank%22%3E%40Tim%20Hunter%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20machines%20that%20are%20domain%20members%20should%20automatically%20sync%20their%20time%20with%20the%20domain%20controller%20that%20they%20authenticated%20against%20last.%20Those%20DCs%20will%20sync%20from%20the%20DC%20with%20the%20PDC%20Emulator%20role%20on%20it.%20That%20machine%20should%20be%20pulling%20time%20from%20an%20external%20source%20(make%20sure%20firewall%20is%20open).%20I%20believe%20it%20defaults%20to%20time.windows.com.%20This%20can%20be%20customized.%3C%2FP%3E%3CP%3EA%20good%20reference%20is%20here%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fnetworking%2Fwindows-time-service%2Fwindows-time-service-top%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fnetworking%2Fwindows-time-service%2Fwindows-time-service-top%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1325040%22%20slang%3D%22en-US%22%3ERe%3A%20Setting%20Time%20on%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1325040%22%20slang%3D%22en-US%22%3E%3CUL%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EAll%20domain%20members%20should%20use%20NT5DS%20domain%20time.%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EDesktops%20and%20member%20servers%20sync%20with%20any%20domain%20controller.%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EDomain%20controllers%20sync%20with%20PDC%20emulator%20(one%20per%20domain)%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EPDC%20emulator%20in%20child%20domain%20can%20sync%20with%20any%20domain%20controller%20in%20parent%20domain.%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EPDC%20emulator%20in%20parent%20domain%20syncs%20with%20either%20a%20hardware%20clock%20or%20possibly%20an%20external%20source.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fnepapfe%2F2013%2F03%2F01%2Fits-simple-time-configuration-in-active-directory%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fnepapfe%2F2013%2F03%2F01%2Fits-simple-time-configuration-in-active-directory%2F%3C%2FA%3E%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Efor%20all%20domain%20members%20(aside%20from%20PDCe)%20should%20have%20happened%20by%20default%20but%20you%20can%20confirm%20by%20running%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CDIV%3E%3CSTRONG%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Ew32tm%20%2Funregister%3CBR%20%2F%3Enet%20stop%20w32time%3CBR%20%2F%3Ew32tm%20%2Fregister%3CBR%20%2F%3Enet%20start%20w32time%3CBR%20%2F%3Ew32tm%20%2Fconfig%20%2Fsyncfromflags%3Adomhier%20%2Fupdate%3CBR%20%2F%3Enet%20stop%20w32time%3CBR%20%2F%3Enet%20start%20w32time%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Ethen%20check%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSTRONG%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Ew32tm%20%2Fquery%20%2Fsource%3CBR%20%2F%3Ew32tm%20%2Fquery%20%2Fconfiguration%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B-----------------------------------------------%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Efor%20the%20PDCe%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CSTRONG%3Ew32tm%20%2Funregister%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Enet%20stop%20w32time%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Ew32tm%20%2Fregister%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Enet%20start%20w32time%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Ew32tm%20%2Fconfig%20%2Fmanualpeerlist%3A%3CPREFERRED%20ip%3D%22%22%20address%3D%22%22%3E%20%2Fsyncfromflags%3Amanual%20%2Freliable%3Ayes%20%2Fupdate%3C%2FPREFERRED%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Enet%20stop%20w32time%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Enet%20start%20w32time%3C%2FSTRONG%3E%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3Ethen%20check%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSTRONG%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Ew32tm%20%2Fquery%20%2Fsource%3CBR%20%2F%3Ew32tm%20%2Fquery%20%2Fconfiguration%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftf.nist.gov%2Ftf-cgi%2Fservers.cgi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftf.nist.gov%2Ftf-cgi%2Fservers.cgi%3C%2FA%3E%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B(please%20don't%20forget%20to%20mark%20helpful%20replies)%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Contributor

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!

3 Replies
Highlighted

@Tim Hunter 

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...

 

Highlighted
Best Response confirmed by Tim Hunter (Regular Contributor)
Solution

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 w32time
then check
w32tm /query /source
w32tm /query /configuration
 -----------------------------------------------
for the PDCe
w32tm /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 check
 
w32tm /query /source
w32tm /query /configuration
 
 
 (please don't forget to mark helpful replies)
 
 
 

 

@Dave Patrick.

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