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
Hardware requirements are same as the requirements for the underlying operating system. Our application consumes minimal memory and CPU time.
The application is easy to install, the installation wizard will guide you through it. See the Terminal Services Log User Manual for instructions.
You will need to purchase additional license keys for each server. Contact us for volume discounts.
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.
Yes, our application allows you to monitor both Citrix and Terminal Services users.
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.
You can use both options.
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.
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.
Yes.
Yes, you can run our application from a USB stick. Please feel free to contact us for more details.
Please contact our support department to obtain a fix for your regional settings.
The Microsoft baseline security policy locks down certain items and you will have to allow the account the aforementioned permission.
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.
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.
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.
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() );
Please contact us to free your Terminal Services Log license.
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.
Please contact us to obtain trial extender for Terminal Services Log.
Terminal Services Log requires around 30MB of disk space for installation.
Terminal Services Log generates around 20MB monthly per server.
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.
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.
Terminal Services Log does not support Microsoft SQL 2000 server. Please use at least Microsoft SQL 2005 server.
Delete Terminal Services Log shortcut and create it again.
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.