Can not change source time from Local CMOS Clock on DCs W2K19.

Question

Hi everyone!

We have several DC W2K19 that we would like to sincronize time using NTP servers. Perhaps, I've tried setting the time via w32tm commands, but the source remains as Local CMOS Clock. Why?

C:\Users\Administrator>w32tm /config /manualpeerlist:"pool.ntp.org" /reliable:yes /update
The command completed successfully.

C:\Users\Administrator>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 23/11/2021 16:22:25
Source: Local CMOS Clock
Poll Interval: 6 (64s)

I tried stopping and starting w32tm services after making changes. Same result!

Firewall is turned off.

Time synchronization is turned off in Hyper-V Integration Services. All the DCs are VMs running under W2K19 core Hyper-V host server.

Hope I was clear enough.

Answer 1

Some general info

• All domain members should use NT5DS domain time.
• Desktops and member servers sync with any domain controller.
• Domain controllers sync with PDC emulator (one per domain)
• PDC emulator in child domain can sync with any domain controller in parent domain.
• PDC emulator in parent domain syncs with either a hardware clock or possibly an external source.
  https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

for all but the PDC emulator

w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Hello @DorianO

In this case, you should change the time reference in the Domain Controller of your Domain, and the any client (Server or client OS) to be synched with the domain hierarchy in order to maintain the time service health.

After you configure the DC, you need to run on the clients:
w32tm /config /syncfromflags:domhier /update

then:
net stop w32time and then net start w32time

There will be a lapse of time of around 15-30 minutes to refresh the information, but surely after 30mins, when you check again it should be correct for this.

Hope this helps with your query,

------
--If the reply is helpful, please Upvote and Accept as answer--

Answer 3

Thanks @Anonymous and @Limitless Technology !