Terminal Services Log 3.5 is out with major new features

It has been almost a year since we first launched the completely redesigned, almost built from scratch, version 3.0. There have been numerous enhancements and new features since the launch, but today we are happy to present the biggest upgrade among 3.X versions – Terminal Services Log 3.5.

Split reports on published applications and server desktops

All users connecting to Remote Desktop Services can be divided into two main groups – ones that use applications directly on the server (published apps in XenApp or RemoteApps in Remote Desktop Services) and others who have their full server desktops.

When one analyzed users and application activity with the previous version of Terminal Services Log, one could see the overall stats filter by certain criteria, but was not able to split the ones that use published apps or server desktops.

Not only that the newest Terminal Services Log  can split and filter the results, but it can also automatically detect all published applications and server desktops. That makes the new feature easy to use allowing you to filter only the sessions that use published apps.

Published apps filter
Split report per Server desktop and Published apps only

Private and Global report views

Our customers wanted to create a predefined set of filters that would define servers as a logical farm, users as a logical organization et cetera. Such views could be save but every time you had to choose particular servers or users  yourself.

Any combination of users and servers can now be saved and deployed as Private or Global view. Global view is available for all reports while private view is available only for the selected reports.

Session count and views

 New Session count report and Private/Global views allow you to create personalized views

User management like Remote Desktop Manager and Citrix AppCenter

Your are familiar with the Remote Desktop Manager or Citrix AppCenter. They enable you to manage users and applications, and we decided to implement some of their functionalities and enhance them in Terminal Services Log, making TSL more than a reporting software only.

Session management implemented in Terminal Service Log 3.5. lets you assist end users, help them use remote desktop and terminate applications on a single and group level. It provides much more flexibility than RD Manager or Citrix AppCenter by enabling you to filter only a few users, applications or servers and perform session log off on the server/group level or, for example, kill all Internet Explorers in your farm.

Session management

Session management allows you to manage al users and application across almonitored servers

Click here to download new release.

Product version:
Build number: 41101
Database version:
Release date: Monday, November 7, 2011

Other new features

  • Session count report provides the same data as the Dashboard, counting all users across all servers displaying load per sessions in your farm.
  • Performance report that allows you to monitor hard disk utilization.
  • Merged report that combines user activities and applications in one place.
  • Ability to configure a real-time alert when servers go offline.
  • Option to select one e-mail to be sent daily/weekly/monthly/quarterly with a single schedule.
  • Choose which day of the week will be your starting day for receiving weekly reports.
  • Configurable empty e-mail, sent if there was no activity on the servers.
  • Check all server statuses at once with the server tab.
  • Warning about exceeding the database limit on Microsoft SQL Express.

Bug fixes

  • XLSX formatting was in a number format.
  • Adding users from the domain was slow, now there is a progress bar with import status.
  • Sometimes user activity would be zero.
  • You couldn’t import users that had special characters in the name.
  • You couldn’t search in OUs that had special characters in the name.
  • Anonymous sessions wouldn’t work correctly in the Professional Edition.
  • Export to Excel pivot in custom reports with time spent had issues.
  • CPU utilization sometimes was over 100% because of the bug in Windows performance counters.
  • Huge SQL database would sometimes timeout  on upgrade.
  • When you disabled a  job, the  job would actually .
  • Session type filter was not working on the Dashboard.

Click here to download new release.