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

Doria 1,221 Reputation points
2021-11-24T13:21:42.277+00:00

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.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
2,210 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
8,257 questions
No comments
{count} votes

Accepted answer
  1. Dave Patrick 330.7K Reputation points
    2021-11-24T14:01:44.38+00:00

    Some general info

    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--


2 additional answers

Sort by: Most helpful
  1. Limitless Technology 37,351 Reputation points
    2021-11-24T19:00:24.957+00:00

    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--

    No comments

  2. Doria 1,221 Reputation points
    2021-11-24T19:36:34.5+00:00