The web-based client (v8.88+) now supports raw HTTP traffic for specific web paths and improved TLS traffic forwarding, making it easier to integrate with complex network architectures.
Administrators will appreciate the improved algorithm for publishing specific applications rather than full desktops. Version 17.10.2.20 reduces the overhead per published application by roughly 15%, which is particularly beneficial when hosting demanding software like CAD tools or ERP systems.
For the first time in the 5.5 series, database connection settings can be edited directly through the user interface, removing the need for manual config file manipulation. TSplus 17.10.2.20 - Server Monitoring 5.5.219.1...
No modern update is complete without addressing security. This version includes patches for minor vulnerabilities identified in the web interface and the administration console. By closing potential attack vectors, TSplus ensures that the "gate" to the corporate network remains secure against unauthorized access attempts.
Additionally, the monitoring agent now encrypts its traffic back to the TSplus console using AES-256. This prevents anyone sniffing network packets from seeing which servers are critical or what resources they have. The web-based client (v8
When deployed together, these two versions create a robust ecosystem for remote work:
One of the most persistent headaches in RDS environments is printer mapping. Drivers conflict, spoolers crash, and printers disappear without warning. This specific build addresses several edge-case bugs regarding printer redirection. It improves the way the TSplus Universal Printer handles PDF conversions and streamlines the communication pipeline for local printers mapped to remote sessions. Additionally, improvements have been noted in the redirection of smart cards and specialized peripherals, which is vital for healthcare and financial sectors. For the first time in the 5
You can now set granular alerts per server. For example:
: Historical data from previous monitoring versions is not migrated due to database schema changes. This is a one-time event. Set a new baseline by giving the tool 24 hours to collect fresh metrics.
Ensure systems run on supported x86 or x64 architectures before deployment.
With Remote Access 17.10's security fixes (like preventing multiple HTML5 server launches) and Server Monitoring's real-time alerts for disk usage or CPU spikes, the risk of downtime is significantly minimized.