Synchronizing all clocks within your system (Advanced) - Security Center 5.9

Security Center Hardening Guide 5.9

series
Security Center 5.9
revised_modified
2020-11-30

It is considered best practice to synchronize the clocks on all machines running Genetec™ software using the Windows Time server (W32Time), which is based on the Simple Network Time Protocol (SNTP).

If your network doesn't have a domain controller, manual configurations need to be made. Following the configuration of the time server, it will synchronize the client clock periodically.

Synchronization does not always instantly change the time on the local machine. If the local clock time of the client is less than 3 minutes ahead of the time on the server, W32Time will quarter or halve the clock frequency for long enough to bring the clocks into sync. If the local clock time of the client is more than three minutes ahead of the time on the server, or behind the current time received from the server, W32Time will change the local clock time immediately.

Forcing the use of Active Directory on all client machines and servers running Security Center will enforces strict time synchronization between all users.

For more information about W32Time, see How the Windows Time Service Works.

For more information about configuring W32Time, see Windows Time Service Tools and Settings.