#Hello, guys! #Here is a new tip of the day (TOTD). #Today we discuss how to fix the most common warning which you may receive on DCs #You run dcdiag on your DC and receives warning "..is not advertising as a time server" dcdiag /q Warning: nameofdc is not advertising as a time server. ......................... nameofdc failed test Advertising #The main time source in domain is DC with PDC role . Run the following command to query FSMO owners: netdom query fsmo #On your PDC you have to set up w32tm with external (generally) or internal time source. for example, pool.ntp.org w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:yes /update #On your additional DCs run w32tm /config /syncfromflags:domhier /update #Restart w32time service on each DC net stop w32time net start w32time #Update w32tm config w32tm /config /update #Resync time w32tm /resync #Re-run dcdiag dcdiag /q /s:yourDCname
Time Synchronization in an AD DS Hierarchy
2 thoughts on “TOTD: DC is not advertising as a time server”
Thanks a lot!
Worked Perfectly … thanks for taking the time to post !