Hyper-V NTP config on DC is localCMOS

Question

Hyper-V NTP config on DC is localCMOS

GlenTech 496

Can't seems to get two of my Hyper-V DC’s to point the to the DC with the PDC emulator role for NTP. They both say local CMOS even after following the steps below. I’ve made sure that time sync is off in the Hyper-V settings for those two VMs. The DC with the PDC Emulator role is correctly pointed to an external NTP. Anything else I can try?

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

Accepted answer

2 additional answers

Your answer

Answer 1

Anonymous

if I check a member only server, it's pointing to OSTDC

That's fine. 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/

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

GlenTech 496 Reputation points

2023-02-07T16:20:46.6733333+00:00

Yep, below is how I typically setup the DC's with regards to NTP but I never had it not work before. As for the replication issue, I used one of our 15 action pack Microsoft incidents to open a case. Perhaps it's all realted and once that get's resolved I can get NTp working properly.

net stop w32time w32tm /config /syncfromflags:manual /manualpeerlist:"pool.ntp.org" w32tm /config /reliable:yes net start w32time w32tm /query /configuration Then verify source and config All other DC's should point to that server and the type should be NT5DS Below is how to reset the other DC's w32tm /unregister net stop w32time w32tm /register net start w32time w32tm /config /syncfromflags:domhier /update net stop w32time net start w32time then check the result by running; w32tm /query /source w32tm /query /configuration
Anonymous

2023-02-07T16:38:02.6+00:00

but I never had it not work before.

Not sure what is meant. Desktops and member servers can sync with anydomain controller. So it looks fine.

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

2023-02-07T17:26:35.4666667+00:00

We added each servers own IP to the DNS entries like you said, disabled IPv6 on OSTDC and DC3, and decommissioned the 2012r2-dc and all the replication issues went away and NTP is working properly now.
Anonymous

2023-02-07T17:57:44.6033333+00:00

Glad to hear all is good.

Answer 2

Anonymous

w32tm /query /source
w32tm /query /configuration

What was the result?

GlenTech 496 Reputation points

2023-02-06T20:24:43.84+00:00

Here you go...

C:\Windows\System32>w32tm /query /source

Local CMOS Clock

C:\Windows\System32>w32tm /query /configuration

[Configuration]

EventLogFlags: 2 (Local)

AnnounceFlags: 5 (Local)

TimeJumpAuditOffset: 28800 (Local)

MinPollInterval: 6 (Local)

MaxPollInterval: 10 (Local)

MaxNegPhaseCorrection: 172800 (Local)

MaxPosPhaseCorrection: 172800 (Local)

MaxAllowedPhaseOffset: 300 (Local)

FrequencyCorrectRate: 4 (Local)

PollAdjustFactor: 5 (Local)

LargePhaseOffset: 50000000 (Local)

SpikeWatchPeriod: 900 (Local)

LocalClockDispersion: 10 (Local)

HoldPeriod: 5 (Local)

PhaseCorrectRate: 7 (Local)

UpdateInterval: 100 (Local)

[TimeProviders]

NtpClient (Local)

DllName: C:\Windows\system32\w32time.dll (Local)

Enabled: 1 (Local)

InputProvider: 1 (Local)

CrossSiteSyncFlags: 2 (Local)

AllowNonstandardModeCombinations: 1 (Local)

ResolvePeerBackoffMinutes: 15 (Local)

ResolvePeerBackoffMaxTimes: 7 (Local)

CompatibilityFlags: 2147483648 (Local)

EventLogFlags: 1 (Local)

LargeSampleSkew: 3 (Local)

SpecialPollInterval: 3600 (Local)

Type: NT5DS (Local)

NtpServer (Local)

DllName: C:\Windows\system32\w32time.dll (Local)

Enabled: 1 (Local)

InputProvider: 0 (Local)

AllowNonstandardModeCombinations: 1 (Local)

VMICTimeProvider (Local)

DllName: C:\Windows\System32\vmictimeprovider.dll (Local)

Enabled: 1 (Local)

InputProvider: 1 (Local)

C:\Windows\System32>

Anonymous

Please run;

`Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log`	(run on PDC emulator)
`repadmin /showrepl >C:\repl.txt`	(run on **any** domain controller)
`ipconfig /all > C:\%computername%.txt`	(run on **EVERY** domain controller)
`ipconfig /all > C:\problemworkstation.txt`	(run on problem pc)


Also check the domain controller ***System*** and ***Replication*** (DFS or FRS) event logs for errors since last boot. Post the ***Event Source*** and ***Event IDs*** of any found. (no evtx files)
  
then put `unzipped` text files up on [OneDrive](https://onedrive.live.com/about/en-us/) and share a link.

GlenTech 496 Reputation points

2023-02-06T20:58:02.4933333+00:00

https://drive.google.com/drive/folders/1bI1uDqipHSMmQdHYmr7T_0bPwMZYMrwq?usp=sharing

Answer 3

Anonymous

This NC (DC=DomainDnsZones,DC=ost-ny,DC=opensystemstech,DC=com) is supposed to be replicated to this server, but has not been replicated yet. This could be because the replica set changes haven't replicated here yet. If this problem persists, check replication of the configuration Partition to this server. OSTDC failed test VerifyReplicas

Same problem for 2012R2-DC failed test VerifyReplicas, Same problem for DC3 failed test VerifyReplicas

On each of the domain controllers I'd also add server's own static ip address listed for DNS. As to the time service issue; do any other members have this problem? DC3 is advertising as a time server. As a side note you could check the event logs for more details on the failed replicas.

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

GlenTech 496 Reputation points

2023-02-06T22:03:41.3433333+00:00

I have the loopback address listed on each DC as one of the entries as I thought that's what was preferred to using its own IP?
Anonymous

2023-02-06T22:17:35.3833333+00:00

That's correct, plus actual address.

GlenTech 496

Easy enough to add in.

As for the replication issues, I'm planning on getting rid of the 2012 R2 as soon as possible and last week I spun up DC3 to have another DC on a different Hyper-V host. DC3 now has all the roles and is the DHCP servers for the domain.

What's odd is that I didn't see that replication error when running the following commands on OSTDC. I checked the event viewer, but nothing stands out.

C:\Users\administrator.xxxxx>repadmin /replsummary
Replication Summary Start Time: 2023-02-06 17:13:02

Beginning data collection for replication summary, this may take awhile:
  ......


Source DSA          largest delta    fails/total %%   error
 2012R2-DC                 24m:20s    0 /   6    0
 DC3                       25m:41s    0 /   6    0
 OSTDC                     25m:41s    0 /   6    0


Destination DSA     largest delta    fails/total %%   error
 2012R2-DC                 25m:41s    0 /   6    0
 DC3                       24m:21s    0 /   6    0
 OSTDC                     22m:18s    0 /   6    0



C:\Users\administrator.OPENSYS_PDC>repadmin /showrepl dc3
Default-First-Site-Name\DC3
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 645d2837-350e-4cff-bdc5-d0072b2b83e1
DSA invocationID: 0f14ca9b-8664-41c7-9094-8ce960394347

==== INBOUND NEIGHBORS ======================================

DC=ost-ny,DC=opensystemstech,DC=com
    Default-First-Site-Name\2012R2-DC via RPC
        DSA object GUID: 4ee3bd9f-1c23-4a44-bb24-23d00f5df3cb
        Last attempt @ 2023-02-06 17:09:45 was successful.
    Default-First-Site-Name\OSTDC via RPC
        DSA object GUID: 89d723f5-4355-4bc2-9854-705d364a2abf
        Last attempt @ 2023-02-06 17:11:55 was successful.

CN=Configuration,DC=ost-ny,DC=opensystemstech,DC=com
    Default-First-Site-Name\OSTDC via RPC
        DSA object GUID: 89d723f5-4355-4bc2-9854-705d364a2abf
        Last attempt @ 2023-02-06 16:48:42 was successful.
    Default-First-Site-Name\2012R2-DC via RPC
        DSA object GUID: 4ee3bd9f-1c23-4a44-bb24-23d00f5df3cb
        Last attempt @ 2023-02-06 16:48:42 was successful.

CN=Schema,CN=Configuration,DC=ost-ny,DC=opensystemstech,DC=com
    Default-First-Site-Name\OSTDC via RPC
        DSA object GUID: 89d723f5-4355-4bc2-9854-705d364a2abf
        Last attempt @ 2023-02-06 16:48:42 was successful.
    Default-First-Site-Name\2012R2-DC via RPC
        DSA object GUID: 4ee3bd9f-1c23-4a44-bb24-23d00f5df3cb
        Last attempt @ 2023-02-06 16:48:42 was successful.

GlenTech 496 Reputation points

2023-02-06T22:56:59.6233333+00:00

Rebooted 2012R2 and it seems successful but will continue to monitor the DFS Replication logs on DC3 tomorrow

The DFS Replication service successfully established an inbound connection with partner 2012R2-DC for replication group Domain System Volume.

Additional Information:

Connection Address Used: 2012R2-DC.ost-ny.opensystemstech.com

Connection ID: 84561143-1922-4689-B686-8E7BA7B53779

Replication Group ID: 98392244-88B6-4A7D-85FA-86F0B2AAD0C3
Anonymous

2023-02-06T23:09:27.3166667+00:00

Glad to hear, please don't forget to close up the thread by marking answer. You could start a new thread to deal with the replication problem.
GlenTech 496 Reputation points

2023-02-07T13:43:58.4+00:00

Getting back to the NTP issue, if I check a member only server, it's pointing to OSTDC even after runing the "w32tm /config /syncfromflags:domhier /update" multiple times. Sometimes it flips to localCMOS and then it goes back to OSTDC

C:\Windows\system32>w32tm /query /source

OSTDC.ost-ny.opensystemstech.com

C:\Windows\system32>w32tm /query /configuration

[Configuration]

EventLogFlags: 2 (Local)

AnnounceFlags: 10 (Local)

TimeJumpAuditOffset: 28800 (Local)

MinPollInterval: 10 (Local)

MaxPollInterval: 15 (Local)

MaxNegPhaseCorrection: 4294967295 (Local)

MaxPosPhaseCorrection: 4294967295 (Local)

MaxAllowedPhaseOffset: 300 (Local)

FrequencyCorrectRate: 4 (Local)

PollAdjustFactor: 5 (Local)

LargePhaseOffset: 50000000 (Local)

SpikeWatchPeriod: 900 (Local)

LocalClockDispersion: 10 (Local)

HoldPeriod: 5 (Local)

PhaseCorrectRate: 1 (Local)

UpdateInterval: 30000 (Local)

[TimeProviders]

NtpClient (Local)

DllName: C:\Windows\system32\w32time.DLL (Local)

Enabled: 1 (Local)

InputProvider: 1 (Local)

CrossSiteSyncFlags: 2 (Local)

AllowNonstandardModeCombinations: 1 (Local)

ResolvePeerBackoffMinutes: 15 (Local)

ResolvePeerBackoffMaxTimes: 7 (Local)

CompatibilityFlags: 2147483648 (Local)

EventLogFlags: 1 (Local)

LargeSampleSkew: 3 (Local)

SpecialPollInterval: 3600 (Local)

Type: NT5DS (Local)

VMICTimeProvider (Local)

DllName: C:\Windows\System32\vmictimeprovider.dll (Local)

Enabled: 1 (Local)

InputProvider: 1 (Local)

NtpServer (Local)

DllName: C:\Windows\system32\w32time.DLL (Local)

Enabled: 0 (Local)

InputProvider: 0 (Local)

Share via

Hyper-V NTP config on DC is localCMOS

2 additional answers

Your answer