Home / server / Questions / 968462
In Process
Jason O
Asked: 2019-05-23 09:21:09 +0800 CST

Domain-joined computer won't switch time source to domain from "Local CMOS Clock"

  • 772

My situation is almost identical to the one cited in this post:

How to change time source from "Local CMOS Clock" to "DC"

I have a domain-joined computer that is showing "Local CMOS Clock" as the source despite my attempts to change it. Here's what I've tried so far:

  1. Ran the following terminal commands to confirm that the computer clock is off from the network server clock (by about two minutes): Net time /Domain:local.mydomain.com & Net time \\WORKSTATION-NAME

  2. Ran the following command to confirm that the local machine set to "Local CMOS Clock": W32tm /query /source

  3. However, running the following commands did not change the setting: w32tm /config /syncfromflags:domhier /update net stop w32time && net start w32time

  4. Running W32tm /query /source still returns: “Local CMOS Clock”

What do I do now? I'm not sure how to force it to change.

active-directory

2 Answers

  1. Try this. After you run these commands give it some time to reflect the change. If it hasn't reflected the change after an hour then additional troubleshooting is going to be needed.

    net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /config /syncfromflags:domhier
w32tm /config /update
net stop w32time
net start w32time
    • 0

  2. 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 remove 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 Then run: net stop w32time and net start w32time Now when I went back to my Windows 10 clients I could run: w32tm /config /syncfromflags:domhier /update and net stop w32time and then 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!

    • 0