What is the best method to get a Windows domain back on the correct time?

I have a site that has a Windows 2003 Active Directory Server.  The time is currently off by about 6 minutes into the future.  The site has about 20 Windows 7 Pro workstations and 3 other Windows 2008 Servers.

What is the best method and procedures to get the time accurate again?

I had considered bringing all other workstations and servers down, manually fix the time on the Active Directory Server, and bring up the other servers and workstations.  It appears this is not a good solution from some reading I've done.

Please advise.
AnthonyMCSEAsked:
Who is Participating?
 
Zephyr ICTCloud ArchitectCommented:
Make one of your DC's an authoritative Time Server and let your workstations sync with it (which they normally will do automatically), use an external NTP source if you don't have a trusted one on the network, something like pool.ntp.org
0
 
Seth SimmonsSr. Systems AdministratorCommented:
the domain controller holding the PDC emulator role should be configured as an authoritative time server

How to configure an authoritative time server in Windows Server
https://support.microsoft.com/kb/816042?wa=wsignin1.0
0
 
AnthonyMCSEAuthor Commented:
The other servers and workstations are already in sync with the PDC, my sense is that it is the PDC itself that is not syncing with an external time source.  Once I configure the PDC with an external NTP source, will the server suddenly jump back in time 5 minutes?  Can this cause issues?  Also don't want the workstations and other servers to slowly get in sync again with the PDC, I'd rather they all get in sync immediately.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Also note that if you have a forest (root domain with child domains) then you should make your forest PDC emulator (root domain PDC emulator) as the authoritative time server.
0
 
AnthonyMCSEAuthor Commented:
Just the one domain and just the one domain controller for now.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
shouldn't be issues when the PDC and members make the adjustment
0
 
AnthonyMCSEAuthor Commented:
OK, so I noticed that my active directory server had almost been correctly configured for an external time source, the NTPServer registry entry had the place holder values of "Server1,0x1 Server2,0x1"  which I replaced with "0.us.pool.ntp.org,0x1 1.us.poolntp.org,0x1"
Then I stopped and started the w32time service.  The PDC updated its time within a few minutes.

The member servers don't appear to updating their time, at least not very quickly.  Using the command "w32tm /query /status" they appear to be updating their time, perhaps by 1 second every minute, based on this output:

C:\Users\administrator.DFP>w32tm /query /status
Leap Indicator: 3(last minute has 61 seconds)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.1249542s
Root Dispersion: 7.6108138s
ReferenceId: 0xC0A800CA (source IP:  192.168.0.202)
Last Successful Sync Time: 2/16/2015 5:10:48 PM
Source: dfp-server.dfp.local
Poll Interval: 10 (1024s)

Why is it doing that?
0
 
AnthonyMCSEAuthor Commented:
And looking at a workstation, I see this:

C:\Users\Officemgr>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0312500s
Root Dispersion: 10.1061775s
ReferenceId: 0xC0A800CA (source IP:  192.168.0.202)
Last Successful Sync Time: 2/16/2015 4:34:29 PM
Source: dfp-server.dfp.local
Poll Interval: 12 (4096s)
0
 
AnthonyMCSEAuthor Commented:
Hmm...now the member server above shows the right time and looks like this:

C:\Users\administrator.DFP>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.1249542s
Root Dispersion: 4.9915208s
ReferenceId: 0xC0A800CA (source IP:  192.168.0.202)
Last Successful Sync Time: 2/16/2015 5:39:17 PM
Source: dfp-server.dfp.local
Poll Interval: 10 (1024s)

I don't get it.
0
 
AnthonyMCSEAuthor Commented:
Hmmm...and here is one of my Hyper-V VM's....Looks like it is dueling the domain controller time with the VM Integrated Services time...that can't be good:  

C:\Users\administrator.DFP>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.1249542s
Root Dispersion: 1.7611385s
ReferenceId: 0xC0A800CA (source IP:  192.168.0.202)
Last Successful Sync Time: 2/16/2015 5:43:12 PM
Source: dfp-server.dfp.local
Poll Interval: 10 (1024s)


C:\Users\administrator.DFP>w32tm /query /status
Leap Indicator: 3(last minute has 61 seconds)
Stratum: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 0.0100000s
ReferenceId: 0x00000000 (unspecified)
Last Successful Sync Time: 2/16/2015 5:58:03 PM
Source: VM IC Time Synchronization Provider
Poll Interval: 10 (1024s)
0
 
AnthonyMCSEAuthor Commented:
Well, it took a few hours but times all seem to be synced up now.  I'll double check in the morning.  Just had to be patient. The dueling VM time sync right above has me a bit concerned, but the Hyper-V host is synced with the domain controller. Still doesn't seem like I should have two time sources duking it out.
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.