Domain Client using Local CMOS clock

Domain client time off from domain controller time:
ISSUE: Some of my Windows 10 machines in AD domain were off by a few minutes. After running w32tm /query /status
I found that the source was set to local CMOS clock on the domain client machine. I tried the standard fix to update client to domain:
w32tm /config /syncfromflags:domhier /update
net stop w32time net start w32time
But that didn’t work and neither did any of the other suggestions I tried.

After running DCDIAG on my Domain Controller I noticed that it stated that it was not advertising as a time source. Upon further investigation, I found that my Domain Controller VM had the setting to use time integration services with the Hyper-V Host. Once I changed that setting – I reset the NTP settings on the domain controller holding the PDC role with the following settings: w32tm /config /manualpeerlist:time2.google.com /syncfromflags:manual /reliable:yes /update
Then run: net stop w32time and net start w32time

I ran DCDIAG again on my DC and it now shows that it passed test advertising. You can wait a while and the domain clients should start using the Domain controller for time once they check back in or if you can’t wait then you can remote desktop to your domain client(s) and run:
w32tm /config /syncfromflags:domhier /update net stop w32time and then
net start w32time Verify time settings on your client using: w32tm /query /status w32tm /query /configuration