Time issue with Domain

The issue might be very simple, but I want to avoid any outages.  Basically I want to sync all time to the PDC, and sync the PDC to an external time source server.

Here's my dilemma
We have a PDC running all 5 FSMO roles.  All DCs, servers, clients are showing the same time.  Right now it is off about 5 minutes which is causing some issues internally with the users.  The problem with tinkering with this is all time is set on a Desktop Authority server pushing the time source to each client and server as one of the old DCs.  

I'm more curious what would happen if that setting were to stop setting automatically on the clients and if they'd default back to the domains.

Can anybody send me the sequence of changing this without interrupting any communication within the domain?  

Thanks!!
OCUWAsked:
Who is Participating?
 
Gary PattersonConnect With a Mentor VP Technology / Senior Consultant Commented:
If your users all have local Admin rights, you could just add a line to their login script:

;Configure time service to sync from the domain hierarchy
w32tm /config /syncfromflags:domhier /update

If they don't all have admin rights, you could use a WMI script to run the command on each workstation in the domain.

But I think the best method is to use Group Policy.  Note that you need to set up one GPO for domain controllers and a different one for domain members:

http://blogs.technet.com/b/nepapfe/archive/2013/03/01/it-s-simple-time-configuration-in-active-directory.aspx

Test it on a small subset, and make sure and test it for each different OS version in your network.

- Gary Patterson
0
 
Gary PattersonVP Technology / Senior Consultant Commented:
How does desktop authority push out time settings?
0
 
OCUWAuthor Commented:
I have no idea to be honest.  There is a setting labeled "Time Synchronization", and from there the settings include just a server name.  

Upon checking the settings again, it looks to be pointed at the PDC, which is what I would want.  But on my client machine I do a net time and see it looking at the old DC.
0
 
OCUWAuthor Commented:
Seemed to fix the issue.  The remaining DCs had a weird GPO attached labeled as something else, screwing up the connection.  And the PDC seemed to be using the CMOS as a time source.  I slowly crept up the CMOS so it wasn't >5min apart from the DCs, set the DCs by removing the GPO, set up the domheir settings, then went to the PDC and pointed it to the NTP server.  

Took a few minutes to get everything going.

Thanks for the help :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.