|
1.90
Fixed Bugs
- Roundtrip time will now processed correctly
New Features
- Accuracy of the time improved through optimization of name resolution
- Accuracy of the time improved through optimization of debug entries
|
|
|
|
|
|
1.89
New Features
- Windows Server 2022 is now supported
- Command line parameter "/CONDITIONINSTALL" has been removed.
Instead, the new command line parameter "/FORCE" has been added.
NOTE: The use of the command line setup should be checked, because the update behavior has changed. Further details can be found in the help of Time-Sync (Key "F1").
- Validation of the response packets of the NTP protocol optimized
- Optional disabling of fallbacks to the Time protocol
- Optional activation of an additional plausibility check before synchronizing the time
- Improvement of the debug function
- Improvement of the description in the help
- Signing of the Time-Sync binaries and setup
|
|
1.88
Fixed Bugs
- If the complete log text was too long, the message "A connection to the service could not be established! Please restart the service and execute this application again!" occurred and no log was displayed.
|
|
1.87
New Features
- Windows 11 is now supported
- Minor optimizations of the language files
- Minor optimizations of the help
Fixed Bugs
- If the option "Collect protocol entries and write every full hour" was deactivated all events collected up to that point are no longer discarded and will be written to the Windows Event Viewer.
|
|
1.86
New Features
- A synchronization is now always executed after a stand-by, regardless of the configured interval.
- The first synchronization after the system startup/standby is attempted until it is successfully.
After the first successful synchronisation the configured interval will be used.
There are cyclic log entries about this actions after about one minute.
- Number of log entries increased to 200
- Added "Info"-Tab
Fixed Bugs
- Log entries are now inserted correctly in the Windows Event-Log when Windows shuts down (= Windows Vista).
With Windows Vista, this is not always the case, because Microsoft's Event Log service is often terminated before Time-Sync.
- Memory leak fixed
|
|
1.85
New Features
- Windows Server 2016/2019 is now supported
Fixed Bugs
- Server: Windows Firewall rules for Time-Sync will be added if Windows Firewall is deactivated
- Server: Windows Firewall rules for Time-Sync will be removed correctly during Silent-Setup
|
|
1.84
Fixed Bugs
- Client: First synchronisation on startup works now as expected if "Quick Launch" is activated in Windows 10
|
|
1.83
New Features
- Client-Synchronization: Network tolerance implemented on first synchronization after the service has started.
If you using fast hard disks (for example M.2) there will be no more failed syncs after the system has been started.
- Updated server list for new installations: By default, NTP pool servers are now used.
If you update your Time-Sync version it is recommend to update the server list because the old servers are not maintaned anymore.
For the english version the new servers are:
0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org
|
|
1.82
New Features
- Service "Time-Sync Client" and "Time-Sync Server" depends now on Windows Service "TCP/IP" and "Eventlog".
Fixed Bugs
- Server: Implemented length check in Time-Protocol (TCP and UDP) so that invalid data packts e.g.
from Cisco ASA Firewall with active Captive Portal will not result in an invalid time sychronisation.
|
|
1.81
New Features
Fixed Bugs
- Server: Reference timestamp will now send correctly if the client function is deactivated
|
