Easy way to identify What DC a server connects to for time sync?

[leeland]

I was asked by my manager to monitor what domain controller an individual server is attempting to synchronize the time against.

Currently he was working with an infrastructure guy and they are using a freeware program

http://www.greyware.com/software/domaintime/instructions/misc/agent/agent-free.asp

which works as intended. the only crappy part of this application is, once it is installed it doesn't really have an 'off' switch...you install it, and if you log off the app dies...and requires an uninstall and re-install.

After several issues with time sync across a landscape of servers (60+) they want to gather information as to what DC an individual server is connects to...for the time source...

I don't feel like remoting 60 machines, installing this app and monitoring the application.

I was hoping for a scripting method...or a command line method that can either output WHAT DC is being used to sync time...and if at all possible the time deviation between polls...


These servers are all windows 2008


Sorry if this is confusing...any questions please let me know.

Thanks,
Lee

 

[stlcardinals]

Windows Time Service Technical Reference should be a good starting place.

 

[stash]

It uses the DC that authenticates the user or computer. To see which DC authenticated your user account, open a command prompt and type 'set logonserver'

 

[stash]

You can also check the deviation between the client and DC by using the following:

w32tm /stripchart /computer:targetDC

 

[leeland]

Windows Time Service Technical Reference should be a good starting place.

Thank you for the link posted...

I have gone through that site and many others regarding commands that can be run to display information about time...configuration...etc...

What I cannot find is a command that says something similar to the event log which actually identifies what DC was used to update the time from...

The closest I can come is a query against the server registry to read a value for the 'DCName'

 

[stlcardinals]

How is your AD topology? Do you have sites laid out? How many DCs do you actually have? Is there any replication problems?

 

[SnOop005]

I believe generally speaking, the DC that holds the PDC fsmo role would be the server that syncs time against the external time source then updates to other DCs.

 

[leeland]

I don't have the info regarding the whole DC layout and how many there are...I know of the main DC in regards to the time sync, the DC I am reviewing from our standpoint connects directly to the main DC for its time sync.

#1(Main DC for Time) <--------> #2(DC in other location which pulls from A)

The question that was 'asked' of me to 'investigate' is to see if / when DC #2 has an issue or goes OTL for a stretch...if all the computers / servers that were using DC #2 for its time sync do a poll...then not connect to DC #2 and then go to the next DC and get a different time (either change time forward or backwards)

The event of the time sync is causing issues with applications that are sensitive to time...

I don't know much about group policy...and I have been told it is probably related to how it is 'designed'

I was also told that we could fix our issue if we went to Server 2008 R2 for the DC's in location #2 but there hasn't been a huge push for it...and this investigation is an outside way to 'make that push'

It is a learning experience on the fly for me so any info is appreciated.

On a side note I did find a registry key that indicates the 'DCName' which I have been querying...it is pulling up correctly across all servers...I am just not sure that the registry key gets updated to the 'new' DC name in the event the 'original' DC goes OTL...