Changelogs

With TSplus Advanced Security v7.5.7.14, we have updated the GeoIP database for the Geographic Protection feature. Geographic protection allows remote access to your client machine or application server from only specific countries.

Did you know that Geographic Protection can be configured to restrict the access to your machine to only private and specific whitelisted IP addresses ?

Also, this release allows to retrieve the license status following each Volume License command execution, through the VOLUME_LICENSE_STATUS environment variable. Volume Licensing is a scripting licensing solution available with all TSplus products which enabled automated and scripted deployment of TSplus products. See https://docs.tsplus.net/tsplus/volume-licensing/ for more detailed about Volume Licensing.

Here is the complete changelog:

Improvements

• Geographic Protection: updated IP / Countries database

• Volume License: set the VOLUME_LICENSE_STATUS environment variable following each command

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!

We have added compatibility updates to support the latest updates of Windows 10 1809, 21H2, 22H2 and Windows Server 2019, 2025 latest updates. These improvements are available in TSplus Remote Access 19.40.7.14, TSplus LTS 18 version 18.2026.7.14 and TSplus LTS 17 version 17.2026.7.14.

What’s new in TSplus Remote Access

We fixed an issue that allowed unauthorized access to the Web Credentials configuration file, improving protection of stored credentials.

Here is the complete changelog for TSplus Remote Access 19.40.7.14 release:

Improvements

• Compatibility: TSplus is compatible with Windows 10 1809, 21H2, 22H2 and Windows Server 2019, 2025 latest updates

Fixes

• Security: fixed access to Web Credentials configuration file

• Farm/applications: Improved UI responsiveness when one or several application servers are down

What’s new in TSplus LTS 18 and TSplus LTS 17

All available compatibility updates have been included into TSplus LTS 18 version 18.2026.7.14 and TSplus LTS 17 version 17.2026.7.14.

Additionally, we backported in TSplus LTS 18 and LTS 17 the mandatory activation of Network Level Authentication (NLA) during initial setup.

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!

With TSplus Remote Access 19.30.6.24, TSplus LTS 18 version 18.2026.6.24 ans TSplus LTS 17 version 17.2026.6.24, we have updated the code signing certificate used to sign application binaries. This ensures continued compliance with security standards and maintains a trusted installation.

What’s new in TSplus Remote Access

Here is the complete changelog for the TSplus Remote Access 19.30.6.24 release:

Improvements

• Security: enable Network Level Authentication (NLA) during initial setup

• Security: updated the code signing certificate to ensure continued trust and security for application binaries

• Compatibility: TSplus is compatible with Windows 11 24H2, 25H2 latest preview updates

Fixes

• Setup: fixed migration from lower version does not create the required file for RemoteApp mode

• 2FA users management - fixed slowness when searching/removing/editing users

• HTML5 (v8.90): added port-binding checks to prevent multiple html5service.exe instances and ensure silent exit with a 30-second grace period

• HTML5 (v8.90): introduced W.controlBindEvents to disable built-in mouse/touch events, allowing to register custom gesture handlers

What’s new in TSplus LTS 18 and TSplus LTS 17

Additionally, we fixed an issue in TSplus LTS 18 and LTS 17 where migrations from earlier versions did not create the required file for RemoteApp mode.

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!

We updated the OpenSSL library to version 3.0.21. This helps protect your system with more recent security standards and fixes known vulnerabilities.

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!

Remote Access version 19.30.6.12 brings an important security update and several fixes to improve stability and installation.

OpenSSL security update

We updated the OpenSSL library to version 3.0.21. This helps protect your system with more recent security standards and fixes known vulnerabilities.

Local account synchronization in a farm

We fixed an issue where local accounts were not always correctly synchronized to application servers. Account synchronization should now work more reliably across your farm.

Silent installation

We fixed a problem where some required components, such as .NET Framework, were not installed when using silent mode. Silent installations should now complete properly without missing prerequisites.

Oopsie. Rollback fix for Active Directory domains

We removed a previous improvement related to Active Directory domains using different DNS and NetBIOS names. This change was causing performance issues in some environments, so reverting it helps restore normal performance. Stay tuned for the definitive fix!

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!

TSplus Remote Access v19.30.9.6 improves support for Active Directory domains with different DNS and NetBIOS names.

This release also includes a fix for a previous compatibility issue for Windows 10 21H2, 22H2 on x86 machines released February 10th, 2026.

All available compatibility updates have been included into TSplus LTS 18 v18.2026.6.9 and TSplus LTS 17 v17.2026.6.9.

TSplus LTS 17 v17.2026.6.9 now embed Connection Client version 108 which now sign RDP file used to start the connection to your server, whether from a .connect file, or by selecting the “remoteapp“ display mode from your Remote Access web portal.

This RDP signing mechanism has been added to comply with Microsoft new security policy regarding un-signed RDP usage. More information at:

https://docs.tsplus.net/tsplus/client-setup-program/#enable-rdp-file-signature-to-prevent-security-warnings

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!

With this new version, TSplus Remote Access stays compatible with latest Windows preview updates.

Also, we fixed the Manage 2FA Requests screen not displaying the failed connection attempts correctly in some regions.

At last, on application assignments interface: when assigning applications to servers (instead of users), application launchers are now hidden, to remove confusion.

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!

Remote Access v19.30.5.21 embed Connection Client V127 which now sign RDP file used to start the connection to your server, whether from a .connect file, or by selecting the “remoteapp“ display mode from your Remote Access web portal.

This RDP signing mechanism has been added to comply with Microsoft new security policy regarding un-signed RDP usage (more information here: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/understanding-security-warnings), showing 2 new warning popups otherwise.

However, simply signing the RDP file to be used is not enough to remove these warnings, as you will also need to:

• install our new RDP signing certificate in the "Trusted Root Certification Authorities" store

• register the thumbprint of the certificate as a trusted .rdp publisher (this requires to be an admin)

Both action are done by the Connection Client setup via the following new page, when clicking on the “Configure now (requires admin)“ button.

This configuration only needs to be done once.

You won’t be asked to install the certificate next time you install the Connection Client, unless we renewed our RDP signing certificate, which should be every 5 year.

Important:

• The RDP signing certificate installation page does not appear when you install the connection client "for all users" since this mode starts the setup as an admin, making us able to automatically install and register the certificate without needing to ask the user to elevate as an admin.

• The .rdp file signing processing, done the first time a new .connect is launched, is done remotely by our licenseapi.dl-files.com server.

• The certificate itself is also being downloaded by the setup connectionclient on https://licenseapi.dl-files.com/cert/signer.crt

As a result, your workstation must be allowed to contact licenseapi.dl-files.com on port 443.

Have an idea or issue? To ensure your feedback is properly tracked and addressed, please use our dedicated channels: Support for issues and Feedback for feature requests. Thank you for helping us improve!