15

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

and 

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.

Edit:

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

Sam Erde
  • 3,549
Barny
  • 153
  • 1
  • 1
  • 6

3 Answers3

12

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.

Sam Erde
  • 3,549
3

I went thru all the above on my domain joined Windows 10 machine trying to get it to resync. What fixed this for me was I first ran DCDIAG on my domain controller and saw the error that said this server is not advertising as a time server. So then I ran w32tm /query /status on my DC. Which returned an answer of vmnic something. My DC was using the time integration services from the Hyper-V host. I went to the Hyper V Manager and went to the setting on my DC and removed the check box from time integration services. Then I reset my DC to use an external time source:

w32tm /config /manualpeerlist:time2.google.com /syncfromflags:manual /reliable:yes /update 
net stop w32time && net start w32time

Now when I went back to my Windows 10 clients I could run:

w32tm /config /syncfromflags:domhier /update
net stop w32time && net start w32time

That fixed the time sync immediately. After about 15 minutes the rest of my domain joined PC's had also updated to the correct time. Hope this helps you!

Community
  • 1
Steve S
  • 41
0

I had the same problems, but the suggestions above didn't help (w32tm /resync brought "The computer did not resync because no time data was available"). Until I found out that there was no secure channel to the DC (tested with nltest /sc_verify:<domain name>), and the cause was that the machine account password didn't work. I fixed that with Reset-ComputerMachinePassword -Server "<dc-name>" -Credential <domain admin account> in a Powershell. Now the w32tm /query /source showed that time was received from the DC, and not from CMOS clock anymore.

Christoph J
  • 1