Windows 2019 member time sync?

Keith Hampshire 96 Reputation points
2023-04-25T18:55:50.1433333+00:00

I am having an issue syncing the time on only one particular member server 2019. I have all 2022 domain controllers (2016 forest or domain levels). I have a GPO that is set to sync all domain computers to "pool.ntp.org. 0x1" external source. The GPO works just fine and all workstations and servers are syncing except for one 2019 member server (we'll call it memserv01). When running the "w32tm /query /source" command on memserv01, I receive "Local CMOS Clock". Meaning it is not syncing with what the GPO is set to. After running the "gpresult /r" command, I do see that the "NTP_Sync" GPO is being applied. When manually running the command "net time \domaincontrollerFQDN /set" it will sync with the domain controller just fine. Why am I having this issue with the time not syncing with this server (memsevr01)? User's image

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,768 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Amit Singh 4,896 Reputation points
    2023-04-26T08:33:06.99+00:00
    0 comments No comments

  2. Limitless Technology 44,346 Reputation points
    2023-04-26T11:31:06.7333333+00:00

    Hello Thank you for your question and reaching out. 1. If its is VM then Disable Time Sync from VM Settings 2. Then run below cmds from elevated mode from the Member server. net stop w32time w32tm /unregister w32tm /register net start w32time w32tm /config /syncfromflags:domhier w32tm /config /update net stop w32time net start w32time --If the reply is helpful, please Upvote and Accept as answer--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.