Windows Time - Conflicting DCs

Experts,

I am battling within my windows environment to set the correct time across all clients and servers. I believe that I have two conflicting domain controllers issuing the times to request.

On DC1 which is the PDC emulator it is set to receive its time from an external time source (Verizon NTP UK).

On DC2 it receives its time from the free-running system clock, this is the faulting server which lags 6 minutes behind.

I've been able to work this out by running w32tm /query /status on each domain controller.

From what I've seen most of the clients and servers are pulling its time from DC1 correctly apart from an odd few that pull from DC2. For Example on Server1, Its 6 minutes behind. I run "net time" and it returns "Current Time at \\dc1 is XX (correct time)" Yet it isn't according to the time in the task bar. To find out where it's really pulling the time from, I run w32tm /query /status on Server1 and it returns telling me its pulling time from DC2 - so no wonder its wrong!

Can anybody help me please to change DC2 to the right time and force a resync throughout the faulting servers?

We are running Windows server 2008.

Thank you
AucklandAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Miguel Angel Perez MuñozCommented:
Try with this command:

NET TIME /domain:your_domain /SET /Y

Then, restart time service.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AucklandAuthor Commented:
@Drashiel

Should I run this on DC2, and restart the time service on DC2 after also?
0
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Best practice for time configuration is as follows:

1.  Root domain PDC emulator should sync time with an outside trusted time server
2.  All other DCs will by default sync time with Root DC PDC Emulator
3.  If DCs are virtualized then ensure to have hypervisor servers sunch wiht root DC PDC emulator or stop syncing virtual DC time with host server
0
Miguel Angel Perez MuñozCommented:
Yes, on affected DC.

Consider post of mnkhawaja, point 3 is important, disable on tools sync hypervisor time with virtual machine.
0
JaihuntCommented:
Check the below link

http://www.petenetlive.com/KB/Article/0000705.htm

In DC2 check the registry value HKLM > System > CurrentControlSet > services > W32Time > Parameters->type -> NT5DS

http://systemadmyn.wordpress.com/2012/05/18/windows-time-service/
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.