• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Time Synchronization in a windows domain

Chiefcrowe

Diamond Member
I just want to clarify something before I start making changes.

Some background:
I have a domain in which I recently added 2 new DCs, with 4 total at the moment.
I transferred the FSMO roles to one of these new ones, so eventually I can demote/remove the 2 old DCs.
Now, I noticed that the 2 new DCs are still referencing the first old DC as the time source that they sync to.


On the new DC, I am planning to set it to sync to the hardware clock or an external time server.
Then after I demote the 2 old DCs, then the other one that's left should point to the 1st DC as time source.

Does this sound right? thanks,
 
I have to look it up, but DC's eventually reset time sync to one of the FSMO role holders. Which FSMO role I have to go google for. *unless specifically overridden which tends to be "bad mkay?"

EDIT:
It uses the 'PDC Emulator FSMO role holder'
 
Last edited:
so if everything is working correctly i shouldn't have to do anything?
I can just demote the old DCs?

Yup. The computers only check for time source periodically (from DNS ie the _ms[something].domain.local) and moving the pdc role will update the record. When the time server stops responding they typically will recheck and move on their own.
 
I use a nifty piece of software called 1st Clock. If installed in all computers, it can be set to auto sync their time with a selected national atomic clock. I have them do it once a week. It can be set much more frequently. The net result is that all machines are then sync'd to the same standard.

http://www.1stclock.com/
 
I use a nifty piece of software called 1st Clock. If installed in all computers, it can be set to auto sync their time with a selected national atomic clock. I have them do it once a week. It can be set much more frequently. The net result is that all machines are then sync'd to the same standard.

http://www.1stclock.com/

This is very bad to use in a windows domain network. The domain controllers should always provide clock. The DCs can be configured to poll pool.ntp.org but *all* workstations should time sync to them.

If you are not using a domain, the "net time" command can do the same thing and set all devices to pick a time source.
 
Back
Top