We want to capture "reasonably significant" adjustments made to the clock frequency without overrunning the event log.Īll clock adjustments below TimeAdjustmentAuditThreshold (min = 128 parts per million, default = 800 parts per million) aren't logged.Ģ PPM change in clock frequency with current granularity yields 120 µsec/sec change in clock accuracy. System clock frequency is constantly modified by W32time when the clock is in close synchronization. We ignore TimeJumpAuditOffset setting while logging this event since that setting was meant to throttle events in the Windows System event log. This event should happen rarely on systems with reasonable time synchronization, and we want to log it each time it occurs. This event logs each instance when System Time is modified using the SetSystemTime API. W32time periodically logs its configuration and status. Identify Peers w32tm.exe /query /peers Event description Ntp Client is receiving time data from the following NTP Servers:
0 Comments
Leave a Reply. |