Quantcast
Channel: Windows Server
Viewing all articles
Browse latest Browse all 26364

w32tm wont update configuration on DC with FSMO

$
0
0

Hi all, I'm having some trouble working out this problem.

Scenario:
New AD, with 2 new DC's.
DC1 is FSMO, and PDCe

On DC1 I run the standard command to configure time sync from an external source and setup the DC as the local reliable time source.

>w32tm /config /manualpeerlist:"0.au.pool.ntp.org 1.au.pool.ntp.org 2.au.pool.ntp.org 3.au.pool.ntp.org" /syncfromflags:manual /reliable:yes /update

then run

>net stop w32time && start w32time

Everything so far looks to be successful. Confirmed that the registry was updated with the config I entered in to the command line.

>reg query HKLM\SYSTEM\CurrentControlSet\Services\W32Time\ParametersHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
ServiceDll REG_EXPAND_SZ %systemroot%\system32\w32time.dll
ServiceMain REG_SZ SvchostEntry_W32Time
ServiceDllUnloadOnStop REG_DWORD 0x1
Type REG_SZ NTP
NtpServer REG_SZ 0.au.pool.ntp.org 1.au.pool.ntp.org 2.au.pool.ntp.org 3.au.pool.ntp.org

So according to the output, the type is correctly shown as NTP and not Nt5Ds.

I then run a sync.
>w32tm /resync
Sending resync command to local computer
The computer did not resync because no time data was available.

Ok so we have an issue.

I check the peers list.
>w32tm /query /peers#Peers: 1

Peer:
State: Pending
Time Remaining: 834.4330849s
Mode: 0 (reserved)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 0 (unspecified)

So even though the server type is set in registry, and the peers list is in registry, Windows isn't using the list.

I query the configuration.
>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 (Policy)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Policy)
ResolvePeerBackoffMaxTimes: 7 (Policy)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 0 (Policy)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Policy)
Type: NT5DS (Policy)

NtpServer (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)

VMICTimeProvider (Local)
DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)

And I wind up at a WTF?

Registry says it's configured as a reliable time source and syncing externally from the au NTP pool.

But w32time says its a local time service only, syncing from the domain hierarchy, and has no idea about the external peers.

Any one seen this before or any ideas how to resolve? It shouldn't be this hard :(

Regards

Andrew K


Viewing all articles
Browse latest Browse all 26364

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>