Link to home
Start Free TrialLog in
Avatar of musalman
musalmanFlag for Oman

asked on

Windows Server 2008 R2 - Clock Time out of synch


We have 1 Domain Controller Server running Win 2008 r2 in our Head office, we observed that the Windows Server clock is out of synch and is showing 12 mins back than the current time.

Due to this, all our Domain PCs are showing the same wrong time.

this is causing us a lot headache.

Please suggest the simple way to Adjust the Time on the Server as well as Clients.

Note 1: I am having less knowledge about Servers and Network but can do the steps provided.

Note 2: I remember, one time in 2015 , I tried to adjust the Server Clock time directly from the Clock, it caused me a Disaster, where all the Domain PC's lost the Trust Relationship.

I am expecting a safe and secure way to adjust it.

Many thanks
Avatar of Patrick Bogers
Patrick Bogers
Flag of Netherlands image


First you want to know who is the time server and how is it configured.
w32tm /query /status

Is it configured to gets it time from a public ntp server? When was the last update?

Please let us know.
Also if this dc is not the pdc emulator then it's own configuration should be set to use the Domain Hierarchy for it's time synchronization:

Avatar of musalman


From the Server DOS:

Last succ. Synch time: 7th Mar 2017
Source: Free running System Clock

From the Client DOS:
Source: our AD Server Name.
uncheck that in the Settings -> Integration Services on vm
Dear it_saige
Our Server is the PDC.

Dear dj 3094
Which setting are you talking about ?

Please let me know...
dj 3094 is making their recommendation based upon the assumption that the dc in question is a virtual machine instance.  If this is the case then one portion of the solution is to disable the time integration service.

Based upon what you stated about the dc in question being the pdc, my recommendation is to configure your pdc so that it will use an external time source instead of the cmos clock.

I have posted a few EE PAQs in relation to this, one of the most relevant is this one: https:/Q_28597899.html#a40553961

You don't have to set the group policy if you do not want to (I normally recommend it since moving the time service is usually an afterthought if you ever decide to move the PDCe Role or replace the PDCe).

As for the other DC's, member servers and client machines, it sounds as if they are already configured to get their time from the domain hierarchy (which is the way it should be).  Once the PDCe's time changes the others should change as well.  Depending upon the size of your network it could take a little time but it should be a fairly quick and painless process.

Dear it_saige

Please provide me the Exact commands to set the time source as well as how to run them,

Secondly, let me know if there is any consequence possible ?

I remember, one time, when changing the time on Server disturbed the Client Server relationship , and since then, Trust Relationship Error appears on any Client PC while they enter a wrong Password on their PC's.

Avatar of Patrick Bogers
Patrick Bogers
Flag of Netherlands image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Should I run this command on Windows AD Server Command Prompt ?
Will it affect any other setting ?
Will it sync the time at Client PC automatically ?

thank you for your help !

Yes you should
No it shouldnt
Yes they should, you can check with the commands from my first post. They should all say: Source: our AD Server Name

BTW we can assume by now the DC is not a vm right?
You are right - DC is not a VM, Ok I will execute the command soon, and will return back with the results.
One correction, it depends on each individual client pc and member servers time settings as to whether this will sync time automatically on workstations and member servers.  First, the pc's must be set to use the domain hierarchy.  Second, their max/min pos/neg phase correction settings have to be set properly (generally the default values suffice).


P.S. - The previous EE PAQ that I reference has the commands in it as well as links to other time service articles.

It worked fine.