Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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

To do that I use this command:

w32tm /config / /syncfromflags:manual /reliable:yes /update


w32tm /resync /rediscover

In the client servers I use

net time \\<> /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. (

On the clientend, source is Local CMOS Clock

share|improve this question
What is the output of the w32tm /status and is the DC advertising as a time server? See – 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
up vote 3 down vote accepted

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.

share|improve this answer
thanks, it worked – Jaba jubhyl Nov 26 '12 at 8:53
Glad to hear it! – SturdyErde Nov 27 '12 at 9:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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