A typical network time synchronization scenario is depicted in the diagram shown below.
Each workstation running PresenTense Time Client synchronizes to a central PresenTense Time Server on the corporate LAN. This guarantees a coherent propagation of time to all clients. The corporate time server synchronizes to one or more local GPS Master Clocks and also has the backup
option of synchronizing to a time server on the internet using the Network Time Protocol. With the correct time set on the computer running PresenTense Time Server, this computer can offer time services to clients/workstations as well as other devices which
support the NTP protocol. Such devices can be routers, switches, storage devices as well as security and door access systems. Time services may be offered according to one or more of the common time protocols depending on the accuracy desired.
PresenTense Time Client operates as a true system service all Windows operating systems later than Windows NT to synchronize their system clocks to a corporate time server.
Although a corporate time server is not necessary, it is recommended. Disadvantages with configuring each time client to synchronize to internet based time servers are:
1. Increased bandwidth demands and costs
2. Due to traffic, some time servers block a site which has too many clients synchronizing
3. Less coherent time across LAN due to internet delays
For optimum security and accuracy, a GPS Master Clock connected to PresenTense Time Server is recommended as the primary time source for PresenTense Time Clients. The advantages of this are:
1. Secure, no need for access through corporate firewalls
2. Operates in environments where no internet access is available
3. More accurate as internet jitter is eliminated
4. Fault tolerant as there are no external dependencies