Learn more Download free trial Buy now!

FAQ

1. What is the recommended Terminal Services Log host requirement?

Terminal Services Log runs on all versions of Microsoft® Windows® server operating systems including Windows Server 2008!
Required operating systems:
* Windows Server 2000 x86
* Windows Server 2003 x86 and x64
* Windows Server 2003 R2 x86 and x64
* Windows Server 2008 x86 and x64
* Windows Server 2008 R2 x64

2. What are the hardware requirements for Terminal Services Log?

Hardware requirements are same as the requirements for the underlying operating system. Our application consumes minimal memory and CPU time.

3. How difficult is it to setup Terminal Services Log?

The application is easy to install, the installation wizard will guide you through it. See the Terminal Services Log User Manual for instructions.

4. How do I buy additional software licenses for different servers?

You will need to purchase additional license keys for each server. Contact us for volume discounts.

5. How many licenses do I need to purchase for 3 servers?

You will have to purchase 3 licenses because our application is licensed per-server. If you have more than one server we would recommend purchasing the Professional edition that allows monitoring of server farms. Contact us for volume discounts.

6. Can I monitor Citrix Presentation server users?

Yes, our application allows you to monitor both Citrix and Terminal Services users.

7. I am receiving a 2103 error code during installation. How to I fix it?

In order to install Terminal Services Log you will have to log on with Administrators rights on the server you plan to install our software on.

8. Should this program only be opened on the server console or is it ok to also access it through Terminal Service?

You can use both options.

9. What databases does TSL support, and where is the database installed?

Terminal Services Log database is located in the application folder. For single server environments we recommend Microsoft SQL Compact database to minimize the impact on the server performance.
If you are running Terminal Services Log in a farm you can install the Terminal Services Log database on Microsoft SQL Server 2005 or 2008. We also support Microsoft SQL Server Express, which is free. You can download it here.

10. Can this product be used on local workstations too? Or is it for servers running Terminal Services only?

Our product only monitors a server running Terminal Services or Citrix. If your workstation is running on top of Windows Server 2003 or Windows Server 2008 you will be able to monitor it. However there is no reporting functionality for Windows XP or Vista.

11. Can I customize the account for the service that will be running on the host?

Yes.

12. Can I run Terminal Services Log from a USB drive? I cannot install software on the production server due to our company installation policy.

Yes, you can run our application from a USB stick. Please feel free to contact us for more details.

13. I am using a localized version of Windows and it seems idle time does not get recognized correctly.

Please contact our support department to obtain a fix for your regional settings.

14. Why must the Service account have Allow logon as a service permission on the terminal server?

The Microsoft baseline security policy locks down certain items and you will have to allow the account the aforementioned permission.

15. I am getting Cannot start TSLService on computer '.'. What is wrong?

Try first to return with back button to the page before and then click next again, service installation will be restarted and service will start.
In case service fails again start service TSLService manually from Administrative tools > Services. If there are further issues contact us.

16. On Windows server 2008 with UAC enabled (User Access Control) I am unable to run TSL front end, I am getting strange error.

Locate TSL installation directory in Program Files and find TSL.Analytics.exe file. Then create shortcut of that file on the desktop. Now execute application by right click and then choose run as administrator. UAC will prompt you to run as admin and TSL will work OK.
Note you are required to create shortcut directly from the file in installation directory, not from the file in the Start menu.

17. On XenApp (Presentation server) when users are connecting through Web Interface / am getting strange client name, something like WI_s9wV-5sHAM7mCoWhF, I want to display real client name.

This is releated to the Citrix XenApp webinterface configuration. To get real client name please follow this steps:
Add the ClientName tag in the default.ica file to return the client name or machine name:
\Inetpub\wwwroot\Citrix\Metaframe(or XenApp)\conf\default.ica
[WFClient]
Version=2
ClientName=
Save file, and reconnect your client.

18. How to Configure Web Interface to Return the Client IP Address through a Secure Gateway 3.0 Connection

If you are using Citrix Secure Gateway 3.0 to connect to your Citrix published applications through Web Interface 4.0 then by default you will see the client’s IP address as the IP address of the Secure Gateway and not the actual client’s IP. To overcome this issue pleas make the following changes:
On the Web Interface server, modify the following files:
· In the %WEBROOT%/Citrix/MetaFrame/site/serverscripts/include.cs script please change the following lines of code:

/**
* Returns the IP address of the client.
*/
public string getClientAddress() {
return Request.ServerVariables["REMOTE_ADDR"];
}
To the following: (Also note that if the Secure Gateway is not installed on the Web Interface server, replace 127.0.0.1 with the real IP address of the Secure Gateway server.)
/**
* Returns the IP address of the client.
*/
public string getClientAddress() {
if (!(Request.ServerVariables["HTTP_X_FORWARDED_FOR"] == null) && (Request.ServerVariables["REMOTE_ADDR"] == "127.0.0.1"))
{
return Request.ServerVariables["HTTP_X_FORWARDED_FOR"];
} else {
return Request.ServerVariables["REMOTE_ADDR"];
}
}

· In the %WEBROOT%/Citrix/MetaFrame/site/serverscripts/session.cs script please change the following lines of code:
deviceInfo.setDetectedAddress( Request.UserHostAddress );
To the following:
deviceInfo.setDetectedAddress( getClientAddress() );

19. I would like to migrate Terminal Services Log to the new server or I have reinstalled my server but I am unable to activate again

Please contact us to free your Terminal Services Log license.

20. I’ve installed the Enterprise edition. It is showing as Online with Monitoring Enabled and yet it does not appear to be returning any data. An error says that “TSL Service is not running on this computer”.

In the Enterprise edition Terminal Services Log service is installed only on one server in the farm. Then Terminal Services Log will remotely connect to the servers without installing any agent or services on the remote servers.

21. I would like to extend Terminal Services Log evaluation license

Please contact us to obtain trial extender for Terminal Services Log.

22. How much hard disk space is needed to install?

Terminal Services Log requires around 30MB of disk space for installation.

23. How much data does Terminal Services Log generate?

Terminal Services Log generates around 20MB monthly per server.

24. Does it require Active Directory to function?

Terminal Services Log does not require AD to function correctly. TSL is able to work in workstation environment with SQL server authentication. However AD integration is recommended where possible.

25. I would like to resolve public IP of the client to geo location.

Export IP addresses and client names to XLS format. Public IP names will be in C column. Insert behind C new empty column and in D2 enter following formula:
=HYPERLINK("http://www.maxmind.com/app/locate_ip?ips="&C2; "Resolve IP" ) or
=HYPERLINK("http://www.geoiptool.com/en/?IP="&C2; "Resolve IP" )
This formula will create automatic hyperlink to the webpage where you will be able to see IP state and city. This way you will now exact location of every user that is logging on to your server.

26. I am getting Incorrect syntax near '(' when trying to install on Microsoft SQL 2000 server.

Terminal Services Log does not support Microsoft SQL 2000 server. Please use at least Microsoft SQL 2005 server.

27. I am getting Problem with shortcut. The parameter is incorrect error.

Delete Terminal Services Log shortcut and create it again.

28. How can I check what database Terminal Services Log is using.

In the TSL Analytics select Help > About and then you will get something like:
Database type: SQL
Integrated security: Yes
Database version: 2.6.5.30205
Edition: Professional
License: Licensed
This means TSL is using SQL server with Windows integrated authentication. Just paste this data to us when we request you to do so.