TOTD: DC is not advertising as a time server


#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

pdc

Links:

https://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx

2 thoughts on “TOTD: DC is not advertising as a time server”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: