Forum Discussion
How to Sync Windows Server Time to Redhat NTP Server
- Oct 24, 2018
I would say that you should adjust this to a GPO in AD and not use the time commands. If you review these links, they should walk you through setting things up properly for using a WMI filter to "walk with" your PDCe role and then setting your time for that system for NTP targeting your Red Hat systems or any other Stratum 1 NTP source (tick or tock, time.windows or something else).
https://blogs.technet.microsoft.com/askpfeplat/2018/10/01/tick-tock-time-to-dive-deep/
For the back end TechNet reference go here: https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/windows-time-service-tools-and-settings#windows-time-service-group-policy-settings
John Vincent Manansala wrote:
C:\Users\administrator>w32tm /unregister
The following error occurred: Access is denied. (0x80070005)
Sounds like things failed. I'd try it all over again but with elevated permissions (run as administrator)
Result should have been; (no registry editing is needed)
C:\Windows\System32>w32tm /unregister
W32Time successfully unregistered. <----------------------------------
C:\Windows\System32>net stop w32time
The Windows Time service is stopping.The service name is invalid.
More help is available by typing NET HELPMSG 2185.
C:\Windows\System32>w32tm /register
W32Time successfully registered.
C:\Windows\System32>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
C:\Windows\System32>w32tm /config /manualpeerlist:192.168.49.64 /syncfromflags:manual /reliable:yes /update
The command completed successfully.
C:\Windows\System32>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.
C:\Windows\System32>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
C:\Windows\System32>w32tm /query /configuration
[Configuration]
EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (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: 100 (Local)
[TimeProviders]
NtpClient (Local)
DllName: C:\Windows\SYSTEM32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 1024 (Local)
Type: NTP (Local) <--------------------------------------------
NtpServer: 192.168.49.64 (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)
C:\Windows\System32>w32tm /query /source
192.168.49.64
C:\Windows\System32>
I would say that you should adjust this to a GPO in AD and not use the time commands. If you review these links, they should walk you through setting things up properly for using a WMI filter to "walk with" your PDCe role and then setting your time for that system for NTP targeting your Red Hat systems or any other Stratum 1 NTP source (tick or tock, time.windows or something else).
https://blogs.technet.microsoft.com/askpfeplat/2018/10/01/tick-tock-time-to-dive-deep/
For the back end TechNet reference go here: https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/windows-time-service-tools-and-settings#windows-time-service-group-policy-settings