Checking Windows time synchronization
Why an accurate system clock matters when reviewing timestamped Syspeace activity.
Syspeace’s Access Log, Access Report, and block records are all timestamped. If the system clock on a protected server or an administrator’s workstation has drifted, timestamps between them can appear inconsistent even when nothing is actually wrong — which makes correlating an incident, or reporting one to support, harder than it needs to be.
Windows Server keeps its clock synchronized using the built-in Windows Time service (w32tm). If you suspect clock drift:
w32tm /query /statusThis reports the current time source and how far the clock has drifted from it. Consult your organization’s own time-synchronization policy (for example, a domain-joined server typically synchronizes against a domain controller) before changing time-sync configuration — this is standard Windows Server administration, not a Syspeace-specific setting.
When contacting support about a timestamp-related question, include the timezone alongside any timestamp you report.
Still stuck? Contact support with your Syspeace version, Windows Server version, and a description of what you're seeing.