I'm working with that protocol, actually. It just isn't useful to most people, and there's a lot of marketing BS around it. The referenced article, however, is pretty thin.
Is the Windows own time stuff going to be so far off of NTP that it matters? By default Windows gets time from time.windows.com, but all the other choices in the pulldown are *.nist.gov" which I presume are NTP servers. I think you an also just type in any old server name you want in there.
"A remote attacker can send a carefully crafted packet that can overflow a stack buffer and potentially allow malicious code to be executed with the privilege level of the ntpd process."
Comments
NTP 101
It's probably good enough. If you fuck with Windows' own time stuff, you can break your kerberos auth to AD.
This is the only NTP implementation on Windows of which I'm aware or have ever used that worked:
http://www.meinbergglobal.com/english/sw/ntp.htm
"A remote attacker can send a carefully crafted packet that can overflow a stack buffer and potentially allow malicious code to be executed with the privilege level of the ntpd process."
The Linux distros are way behind on NTP versions too.