In a domain, I want to set DC as time server.

To do that I use this command:

w32tm /config /manualpeerlist:europe.pool.ntp.org /syncfromflags:manual /reliable:yes /update


w32tm /resync /rediscover

In the client servers I use

net time \\<comp.name.of.ad> /set /y 

but some of the clients still use Local CMS Clock.

What can I do?

Thanks in advance.


I also run

w32tm /resync [/computer:<computer>] [/nowait] [/rediscover]

on client end but the time server is still Local CMOS Clock for the client.

On the AD source is what I set. (nist.expertssmi.com)

On the clientend, source is Local CMOS Clock

  • What is the output of the w32tm /status and is the DC advertising as a time server? See serverfault.com/a/449832/20701 – Greg Askew Nov 22 '12 at 11:40
  • Have you tried this from the client end - w32tm /resync [/computer:<computer>] [/nowait] [/rediscover] – ServerFaulter Nov 22 '12 at 11:40
  • Did you stop and restart the time service by running this command? net stop w32time && net start w32time – SturdyErde Nov 23 '12 at 12:25

To configure a client computer or a member server to sync time from the domain, run the following command:

w32tm /config /syncfromflags:domhier /update

And then stop and restart the time service by running:

net stop w32time && net start w32time

This should be all you need to do.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.