LarryCK wrote :
however, one of the links that purportedly gives the answer is dead and the other one does not seem to mention NTP protocol version anywhere .
It depends on what you consider the answer. adenine far as I understood you, none gives the answer in your restrict sense. The dead yoke is about an execution of SNTP, not of NTP. And SNTP is not amply NTP compliant. Microsoft is however supporting that bequest SNTP although lone for backward compatibility for interworking with such bequest devices. arsenic far as I understood, SNTP is an implementation of a simplified subset of NTP .
LarryCK wrote :
So, what NTP protocol version does W32Time use on Windows Server 2012 R2 and Windows Server 2019?
According to Wikipedia, W32Time is compliant to ntp v3 since W2K3 and Windows Vista onwards. See its section on software implementations, subsection Windows clock. But I tell you that this claim is WRONG. That claim provides a informant. If you lookup that source, you ‘ll end up in an outdated article in Microsofts docu which reports that it lone implements a subset of NTP, emphasizing which parts are implemented and which ones are excluded. That outdated article applied to Windows versions up unto Windows Server 2012 R2. Although it does n’t specify a protocol version, it refers to a RFC. That RFC 1305 is ntp v3. In so far, the Wikipedia article is discipline.
Microsoft has a more recent docu of its Windows meter service. It applies to Windows versions starting with Windows Server 2012 R2. So that includes your reference versions Windows Server 2012 R2 and Windows Server 2019. And there, you ‘ll find the lapp sentence as in the outdated article. It implements the like subset of ntp v3 and hush claims to be not fully compliant .full ntp compliance, you may choose other implementations, including the reference implementation for ntp v4 is available for Windows, including Windows Server 2012 R2 and Windows Server 2019. There are instructions how to integrate that reference implementation into Windows. The above mentioned Wikipedia article also mentions that this reference implementation has been audited in 2017 and several security issues found. I don’t know to which extent this fixes have been addressed since. Its latest update is of June 2020. If you need, you may choose other implementations, including the reference execution. american samoa far as I remember, the, including Windows waiter 2012 R2 and Windows Server 2019. There are instructions how to integrate that reference execution into Windows. The above mentioned Wikipedia article besides mentions that this reference implementation has been audited in 2017 and several security issues found. I do n’t know to which extent this fixes have been addressed since. Its latest update is of June 2020. And if you need senior high school network time accuracy, there exist other protocol standards which are available besides for Windows. But be mindful that if you have such requirements, you ‘ll besides have an teaching manual how to setup and configure your instances of operational system and applications. It does n’t make sense to use a high preciseness protocol when a general purpose configuration of Windows will not guarantee handiness of access to that accurate time over all the time. The theme for such instructions is to define and configure a subsystem where this access remains available and soften the access on less time critical components.