We have had a few instances where a server (and sometimes a DC) have been unavailable due to the server's time being off by over an hour or two, and sometimes more. I am not asking this question on the SCOM forums since most network monitoring solutions are built on monitoring using Windows Authentication, which of course won't help when it comes to the time being off.
My question is has anyone had experience monitoring time skew using other means and/or tools (free and/or costly)? We thought, for example, to have a script contact some external time source and compare the time locally to the time on the external source, and if it fails, fire off an e-mail and/or snmp trap. Alternatively, even when the time is off, is there a way possibly via SNMP to determine that so as to not have to rely on Windows Authentication?
in a domain the time source for all is the PDEMulator. Please see http://msmvps.com/blogs/mweber/archive/2010/06/27/time-configuration-in-a-windows-domain.aspx about the setup.
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
- Proposed as answer by Arthur_LiMicrosoft contingent staff, Moderator Wednesday, April 24, 2013 8:18 AM
Thanks for responding. Unfortunately, I wasn't looking for information on how to configure NTP. I was looking for information as to how I can detect after the fact when a server's time was misconfigured. I see this post re: SCOM and was looking for other possibilities.