Hey Rick, I noticed two snippets:
"From there, you can configure Active Directory domain controllers with the PDC emulator role in a domain to use this list of servers explicitly for their time"
"I recommend applying this configuration to all domain controllers and possibly even making it a Group Policy object as a startup script for the \Domain Controllers organization unit within Active Directory."
Unless I am losing my memory, Isn't there only one DC in any child (or root) domain that carries the PDC FSMO role for that domain?
So If one has two or more DCs for any given domain in a forest, shouldn't this be specific to the PDC role holder only?
Also, if you set the PDC Role holder DC in the forest root to be reliable and pointing at an external pool of NTP servers or a hardware clock solution for the enterprise, isn't that the only one you need to worry about?
All DCs whether Peer in the forest root, or in child domains will reference the Authoritative and Reliable DC in the root, and AD will make sure that behavior is replicated to them
All workstations in the child domains will choose a domain-local DC to synchronize their time to
a discussion on the subject:
Keep Up with TechRepublic