Have a pesky domain controller who keeps getting out of sync, and subsequently sets the clock on all domain members? There are a number of reasons why the drift occurs, but the easiest fix is to configure an external synchronization with a reliable time source. This should happen on your PDC Emulator role holder, the server with the responsibility of maintaining proper time across the domain.

I prefer the NTP pool project (info at www.pool.ntp.org), so in North America, use:
w32tm /config /manualpeerlist:”0.north-america.pool.ntp.org 1.north-america.pool.ntp.org” /syncfromflags:manual /reliable:yes /update
Be careful with the spacing and quotes on multiple entries, if you get this wrong, it just won’t work.

To verify your list of peers:
w32tm /query /peers 

You should see something close to:

#Peers: 2

Peer: 0.north-america.pool.ntp.org
State: Active
Time Remaining: 61.4014750s
Mode: 1 (Symmetric Active)
Stratum: 2 (secondary reference – syncd by (S)NTP)
PeerPoll Interval: 15 (32768s)
HostPoll Interval: 6 (64s)

Peer: 1.north-america.pool.ntp.org
State: ActiveTime Remaining: 61.5932833s
Mode: 1 (Symmetric Active)
Stratum: 2 (secondary reference – syncd by (S)NTP)
PeerPoll Interval: 15 (32768s)
HostPoll Interval: 6 (64s)

The above command works well on Server 2008 or later, for earlier OSes:
w32tm /dumpreg /subkey:parameters