Time issue with Domain

Posted on 2014-01-29
Medium Priority
Last Modified: 2014-02-10
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?  

Question by:OCUW
  • 2
  • 2
LVL 36

Expert Comment

by:Gary Patterson
ID: 39819571
How does desktop authority push out time settings?

Author Comment

ID: 39819586
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.
LVL 36

Accepted Solution

Gary Patterson earned 1500 total points
ID: 39821030
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:


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

- Gary Patterson

Author Comment

ID: 39848071
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 :)

Featured Post

WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

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.

Join & Write a Comment

This installment of Make It Better gives Media Temple customers the latest news, plugins, and tutorials to make their Grid shared hosting experience that much smoother.
BMC's Track-It! provides a plethora of tools to help keep your IT Help Desk running smoothly, including a work order system, inventory management, report generation, and much more.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question