Ekran System FAQ

System requirements

You are able to use Ekran System with the free embedded Firebird database. We recommend choosing that option during the Ekran System Server installation.

It is recommended to have 100 MB of free disk space for correct Ekran System Client installation.

According to our experience, 2 TB HDD is enough to save records of 100 workstations for up to six months, without your having to perform database cleanup and archiving.

Ekran System supports different database configurations, so you can use SQL to save metadata and NAS to save binary data. This configuration is recommended for large installations.

Ekran System infrastructure is free, and you can deploy several Ekran System Servers and connect multiple Clients to them.

The recommended configuration of the Ekran System Server can support recording 100 sessions simultaneously under embedded Firebird and 250 under MSSQL for up to six months, without you having to perform database cleanup and archiving. A single installation of Ekran System can support monitoring of thousands infrastructure servers with low activities.

Yes, after installation you should delete the unique Client GUID from the registry. After the first connection, each new computer will receive a unique ID and will be monitored as a separate instance.

The Ekran System Server supports Windows Server 2008 and Windows Server 2012 (both x64 and x86). The Ekran System Management Tool supports Windows 8.1, Windows 8, Windows 7 (any edition except Home), Windows Vista; [recommended] Windows Server 2012 and Windows Server 2008 (starting from SP2 version) (both x64 and x86). The Ekran System Client supports Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows XP SP2; Windows Server 2012, Windows Server 2008 and Windows Server 2003 (both x64 and x86).

The Ekran System Linux Client supports all Linux systems with Linux Kernel 2.6.16 and higher.

Ekran System supports full edition of MS SQL Server 2008 or higher. Standard license or higher is required.

Ekran System functioning

Ekran System records all types of user activities. Due to the ability to set the periodicity of screen captures making, you will receive records regardless system events or user action context.

The Ekran System Client uses not more than 5% of CPU in the period of activity (screen capture creation). When there is no activity, the Ekran System Client doesn’t use CPU at all.

 The Ekran System Client uses approximately from 20 MB to 25 MB of memory.

Yes, it is possible to export screen captures of the separate session in the video format to your computer. In the Web-based Management Tool, right-click the target session and select Export video file. The video is exported in the *.avi format.

The size of one screen capture depends on its bit depth and display resolution on the investigated computer. In average, the size of 4 bits screen capture with 1280*1024 display resolution is 10 KB.

Yes, the maximum duration of one session is 24 hours. After that the current session is terminated and a new live session starts automatically.

There are two main reasons for the live session termination:

  • Each live session is automatically terminated at 00:00. After its termination, the new live session automatically starts.
  • If the user turns off the PC with the Ekran System Client installed, the live session is automatically terminated.

Ekran System has a set period of 3 seconds for creating screen captures on mouse click. That is why you always receive a balanced number of screen captures.

If there is no connection with the Server, the monitoring continues: data is saved on the Client computer, and as soon as the connection to the Server is restored, all captured data is sent to the Server.

Ekran System uses its own format to save binary data. To open monitored data from another location, you should export it from the web-based Session Player.

Each Server installation has its own unique key. The exported files can be validated to guarantee that these files have been created by this Server and their integrity has not been violated.

Ekran System Windows Clients capture screenshots together with the following types of metadata: user name, host name, keystrokes, application name, active window title, and activity time. Optionally, you can also capture visited URLs. Using this metadata, you are able to quickly find the needed information. Ekran System Linux Clients additionally capture entered exec* and sudo Linux commands with all their parameters.

There are two possible reasons:

  • If a user types something continuously, stops typing, and then switches to desktop after the 3-second period, the keystrokes will be attached to a blank screen capture.
  • If a user accesses the Client computer via the Remote Desktop Protocol (RDP) and minimizes the Remote Desktop Connection window, a blank screen capture is created.

Ekran System installation & licensing

Use the Getting Started guide or a manual for instructions on quick Ekran System deployment.

A new version of Ekran System installs over the previous version. All configuration remains the same. After you update the Ekran System Server, Ekran System Clients will be automatically updated.

Yes. You can backup Ekran System data by means of the MS SQL Server or the Firebird database.

You can quickly unassign a license from one Client and assign it to another one in two mouse clicks. No limitations.

You should install a Client on each virtual machine on hypervisor. Ekran System records all connections to virtual machines including the ones through VMware remote console, Hyper-V console, etc.

It is recommended to have 100 MB of free disk space for the correct Ekran System Client installation.

After the Client is installed, its activity has little to no effect on the computer productivity. The Ekran System Client uses not more than 5% of CPU in the period of activity (screen capture creation). When there is no activity, the Ekran System Client doesn’t use CPU at all.

The Ekran System Client uses approximately 20 to 25 MB of memory.

No. The license is assigned to a physical computer. A Client with the server license monitors unlimited number of sessions on the computer.

Ekran system configuration & privacy settings

If you have changed Ekran System configuration parameters, new parameters are applied immediately.

Ekran System allows you to enable the protected mode on the Client, which makes it impossible for the user to edit Client log files, monitored data, Client settings in the registry, delete Client files and the Client itself.

Application filtering allows you to reduce the amount of information received from the Client by defining applications whose data will be skipped during the monitoring.

Ekran System allows you to enable the additional message which pops-up on user login to the system. It informs the user that the session is being monitored and can also contain information on the important issues related to the corporate policy or the country laws.

You can set screen captures color depth parameters in the Management Tool by selecting the necessary bit depth (4 bits (Grayscale), 8 bits, and 24 bits) when installing the Client or editing its configuration.

Additionally, you can define the screen capture making triggers by selecting the necessary options. There are the following triggers: screen capture making frequency, active window change, window title change, mouse-clicking or key-pressing.

No. The Ekran System Client makes screen captures only on the certain user actions you are able to define. Moreover, the Client is able to detect the computer being in idle state, which is taken into account during reports generation.

Ekran System has the Forced User Authentication option to control who can access which computer. We can also integrate Ekran System with the access management system you use in your company.

The identification can be performed by means of Forced User Authentication that requires the user to enter additional credentials in the pop-up dialog after logging in. Thus, as soon as the user starts working with the system and the Client starts monitoring, the username will be displayed in the Management Tool as follows: ().