Ekran System Help File

Size: px
Start display at page:

Download "Ekran System Help File"

Transcription

1 Ekran System Help File

2 Table of Contents About... 9 What s New System Requirements Updating Ekran to version Program Structure Getting Started Deployment Process Working with Application Server and Database About Database Types Comparison Installing/Uninstalling/Updating the Server Installing the Server Adding Server Executable to Windows Firewall Using an External/Cloud-Based Server Computer Updating the Server Uninstalling the Server Server Tray Database Management About Database Cleanup Shrinking MS SQL Database Firebird Database Optimization Deleting the Client Moving the Server Database Moving Binary Data to Shared Folder Management Tool About Management Tool Installation Prerequisites Prerequisites Overview Turning on Internet Information Service (IIS) Turning on IIS for Windows 8, Windows 7, and Windows Vista Turning on IIS for Windows Server 2008 and Windows Server 2008 R

3 Turning on IIS for Windows Server Installing.NET Framework Configuring Internet Information Service (IIS) Using Certificates Generating Self-Signed Certificate Exporting Self-Signed Certificate Importing Trusted Certificate Adding Certificate to Trusted Root Certification Authorities Setting HTTPS Binding for a Default Web-Site Installing/Uninstalling/Updating the Management Tool Installing the Management Tool Adjusting Computer for Remote Access Updating Management Tool Uninstalling Management Tool Opening Management Tool Management Tool Interface Changing Password for Logged in User Licensing General Licensing Information About Subscription Viewing License State Activating Serial Keys Online Adding Activated Serial Keys Offline Deactivating Serial Keys Client License Management User and User Group Management About Viewing Users and User Groups User Management Adding Users Editing Users Deleting Users User Group Management Adding User Groups Editing User Groups Deleting User Groups

4 Permissions About Administrative Permissions Client Permissions Permission Example Windows Clients About Monitoring via Windows Clients Installing Windows Clients About Setting up Environment for Remote Installation Windows Client Installation Prerequisites Disabling Simple File Sharing in Windows XP Disabling Sharing Wizard in Windows 8.1, Windows 8, and Windows Checking System Services Setting up Windows Vista, Windows XP, and Windows Server 2003 Firewall Setting up Firewall for Windows 8.1, Windows 8, Windows 7, Windows Server 2012, Windows Server Installing Windows Clients Remotely via the Management Tool About Selecting Computers Remote Windows Client Installation Process Remote Installation from an Existing.INI File Installing Windows Clients Locally About Windows Client Installation Package Generating Windows Client Installation Package Installing Windows Clients Locally with Custom Monitoring Parameters Downloading Windows Client Installation File (.exe) Installing Windows Clients Locally without.ini File Installation via Third Party Software Cloning a Virtual Machine with Installed Client Unassigning License on Virtual Machine Shutdown Updating Windows Clients Reconnecting Windows Clients to Another Server Uninstalling Windows Clients

5 About Client Uninstallation Key Uninstalling Windows Clients Remotely Uninstalling Windows Clients Locally Viewing Windows Clients Windows Client Description Windows Client Configuration About Protected Mode Parameter Client Tray Icon Parameter Screen Capture Creation Parameters Keystroke Logging Parameters Monitoring Log Parameter URL Monitoring Parameters Application Filtering Parameters User Filtering Parameters Forced User Authentication Parameter Additional Message on User Login Parameter Editing Windows Client Configuration Viewing Windows Client Configuration Defining Client Configuration for All Windows Clients in a Group Forced User Authentication on Clients About Enabling Forced User Authentication on Client Granting the User Permission to Log In Logging In Informing about Monitoring About Enabling Displaying Additional Message Enabling Displaying Client Tray Icon Logging In Linux Clients About Monitoring via Linux Clients Installing Linux Client About

6 Downloading Linux Client Installation File Installing Linux Clients Uninstalling Linux Clients Viewing Linux Clients Linux Client Description Client Group Management About Client Groups Adding Client Groups Editing Client Groups Deleting Client Groups Alerts About Viewing Alerts Alerts Management Adding Alerts Rules Rule Examples Enabling/Disabling Alerts Editing Alerts Assigning Alerts to Clients Deleting Alerts Defining Global Alert Settings Receiving Information on Alert Events Advanced Reports About Report Types Report Limitations Scheduled Reports About Adding Report Rules Editing Report Rules Deleting Report Rules Generating Reports from the Scheduled Report Rule Frequency and Time Interval for Report Creation Viewing Logs Report Generator

7 About Report Parameters Generating Report Creating a Scheduled Report Rule from the Report Generator Page USB Monitoring & Blocking About Monitored Devices USB Monitoring Rules About Adding USB Monitoring Rules Editing USB Monitoring Rules Deleting USB Monitoring Rules Defining Exceptions for USB Rules Viewing Device Hardware ID Configuration Defining Sending Settings Viewing Monitored Data Session List About Sessions Monitored Sessions List Filtering Sessions Filtering via Searching Filtering by Column Grouping and Sorting Sessions Playing Sessions About Session Viewer Interface Session Player Magnifier Getting Data URL Metadata Grid Player and Metadata Synchronization Filtering Data Grouping and Sorting Data Live Sessions Windows Client Sessions

8 Playing Windows Sessions Viewing Keystrokes Viewing USB Device Info Viewing URLs Viewing Idle State Linux Client Sessions Playing Linux Sessions Filtering EXEC Commands Forensic Export About Exporting Session Fragment Exporting Full Session Viewing Forensic Export History Playing Exported Session Validating Exported Data Troubleshooting Quick Access to Log Files Database/Server Database/Server Related Issues Database/Server Related Error Messages Management Tool Management Tool Related Issues Management Tool Error Messages Viewing Monitored Data Windows Client Checking that the Client Is Installed Clients Installation/Uninstallation Issues and Error Messages Possible Problems with Receiving Data from Clients Possible USB Monitoring Problems Linux Client Possible Problems with Receiving Data from Clients Checking the State of the Linux Client Restarting Linux Client

9 About About Welcome to Ekran System! Ekran System is an application that allows you to record the activity of the target computers with installed Clients and to view the screen captures from these computers in the form of video. 9

10 What s New What s New Ekran System v. 4.1 introduces the following changes: USB monitoring and blocking: Now you can detect that a USB device is plugged into the computer on which the Client is installed. You can view the detected devices in the Session Viewer, receive notifications when a device is connected to the Client computer, and block the device from using. It is also possible to create a list of exceptions of devices not to be monitored or blocked. USB report: A new report type that contains the information on all USB-device-related events detected via the USB rules is introduced. Client Tray Icon: You can optionally enable displaying the tray icon notifying a user of the monitored computer that all his actions are being monitored by Ekran Client. The database structure has been modified for overall performance improvement. Alert notifications stability has been improved. Usability enhancements. 10

11 System Requirements System Requirements Ekran System claims different system requirements for each of its components. Make sure your hardware and software meet the following system requirements to avoid possible component malfunctions. Server requirements: 2 GHz or higher CPU 1024 MB or more RAM Enterprise-level Ethernet card Minimum 1 Gbit/s network adapter Windows Server 2012 and 2008 R2 (x64 platform)..net Framework 4.5 NOTE: If the Server and the Management Tool are to be installed on the same computer, make sure you turn on the Internet Information Service before the installation of.net Framework 4.5. [When using MS SQL Database]: Full edition of MS SQL Server 2008 or higher. Standard license or higher is required. Management Tool requirements: 2 GHz or higher CPU 1024 MB or more RAM 100 Mbit/s network adapter Windows 8.1, Windows 8, Windows 7 (any edition except Home), Windows Vista; [recommended] Windows Server 2012 and Windows Server 2008 R2 (starting from SP2 version). Both x86 and x64 platforms are supported..net Framework 4.5 IIS 7.5 or higher with enabled ASP.NET support [For accessing the Management Tool locally or remotely] One of the following browsers: Google Chrome 37 or higher Mozilla Firefox 32 or higher Internet Explorer 10 or higher Safari S6 and Safari S5 Opera 15 or higher NOTE: The Management Tool might be opened in other browsers, but its compatibility with other browsers is not guaranteed. 11

12 System Requirements Windows Client requirements: 1 GHz or higher CPU 512 MB or more RAM 100 Mbit/s network adapter Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows XP SP2; Windows Server 2012, Windows Server 2008 and Windows Server Both x86 and x64 platforms are supported. It is recommended to have not less than 500MB of free space on the disk where the Client is installed to save data during the offline session. Ekran System Linux Client requirements: 1 GHz or higher CPU 512 MB or more RAM 100 Mbit/s network adapter Linux Kernel and higher It is recommended to have not less than 500MB of free space on the disk where the Client is installed to save data during the offline session NOTE: When the Client is installed to the terminal server, hardware requirements depend on the number of active user sessions and may increase drastically. For example, hardware requirements for the Client deployed on the terminal server hosting 10 active user sessions will be as follows: Intel Core i3 or similar AMD CPU 2048 MB RAM 12

13 Updating Ekran to version 4.1 Updating Ekran to version 4.1 The updating of the Server is performed via the installation file of a newer version. Please note that when the Ekran Server is updated to version 4.1, the database is being restructured for performance improvement resulting in the size of the metadata database increasing times. However, afterwards its overall size is not going to increase for some time. The process of database updating runs in the background and takes some time. After the Server is updated to version 4.1, some older sessions might be temporarily unavailable in the Session Viewer. Such sessions are marked with a special icon. 13

14 Program Structure Program Structure Ekran System is an application specially designed to control user activity remotely. Ekran System includes the following components: Ekran System Server (further referred to as Server): It is the main part of the Ekran System used for storing the screen captures and associated information received from the Clients. The work of the Server can be started or stopped via Server Tray. Ekran System Management Tool (further referred to as Management Tool): It is a central administrative unit that allows you to control and manage Clients, Users, Alerts, Server database, and Serial Keys. You can have access to the Management Tool from any computer in the network without having to install it on this computer. Starting from version 4.0, Ekran System Monitor functionality is added to the Management Tool. A new Ekran System Session Viewer provides a usable interface for quick review of the monitored data received from the Windows and Linux Clients. Ekran System Windows Clients (further referred to as Windows Clients): Being hosted on the remote computers, Windows Clients create screen captures of certain quality and defined frequency and send them to the Server. Managing the remote Windows Clients configuration and settings is performed via the Management Tool. Ekran System Linux Clients (further referred to as Linux Clients): Being hosted on the remote computers, Linux Clients capture input/output terminal data (including all executed commands) and send this interactive data to the Server. Ekran System Tray Notifications application (further referred to as Tray Notifications application): This application allows receiving notifications on alert events on Clients. 14

15 Getting Started Getting Started Deployment Process The Ekran System installation consists of several steps: 1. Installing the Server: To deploy the system, first of all you need to install the Server. The Server is used to store and process all records sent by the Clients hosted on the remote computers. During the Server installation you can select the type of the database and define administrator credentials. 2. Completing Management Tool installation prerequisites: To install and run the Management Tool, you need to turn on the Internet Information Service on your computer, add the selfsigned or trusted certificate to the Trusted Root Certification Authorities and set HTTPS binding for a default web site (or any other IIS site). 3. Installing the Management Tool: The Management Tool is used to manage Users, Clients, Alerts, and Database, as well as to view the monitored data received from Clients. Connection with the Server is required for the Management Tool to operate. 4. Activating serial keys (adding activated serial keys): To be able to receive data from the Clients, you need to license the Clients by activating purchased serial keys. 5. Installing Clients: Installing Windows Clients: The Windows Clients are usually installed remotely via the Management Tool. A Windows Client can be installed on any computer in the network. The Windows Clients collect user activity data and send it to the Server. Please note that several conditions have to be met for successful remote Client installation. Installing Linux Clients: The Linux Clients are installed locally. The Linux Clients capture input/output terminal data (including all executed commands) and send this interactive data to the Server. 6. Installing the Tray Notifications application: The Tray Notifications application can be installed on any computer and as long as there is connection to the Server; the Tray Notifications application displays notifications on all alert events received from Clients. For more information, see the Tray Notifications application help file. After installing all the system components, Ekran System is considered deployed and all its features become available. 15

16 Getting Started Working with Application The work with the application includes the following options: 1. Assigning licenses to the Clients: An available license is automatically assigned to the Client (both Windows and Linux) during its first connection to the Server. If the license hasn t been assigned to the Client, you need to assign it manually. 2. Adding Client Groups: Client Groups allow you to grant access to several Clients at the same time to your users without the necessity to grant them access to all the Clients. 3. Adding Users/User Groups and defining their permissions: To allow others to work with the Management Tool, you can create new users and define their permissions in the Management Tool. 4. Defining Windows Client configuration: The configuration allows you to manage the Windows Client monitoring parameters, such as screen capture creation, keystroke logging, protected mode, displaying Client tray icon, application filtering, user filtering, monitoring logs, forced user authentication, and additional message on user login. 5. Creating Alerts: Alerts are used to notify the investigators of a specific activity (potentially harmful/forbidden actions) on the target computers on which Clients are installed. 6. Viewing monitoring results in the Management Tool: The monitored data received from the Client computer can be viewed in the Session Viewer part of the Management Tool. 7. Receiving Alert notifications: The notifications on the alert events are received via the Tray Notifications application. The notifications are displayed in the Windows notification area. 8. Generating reports: The user activity can be analyzed with the help of reports generated via the Management Tool. You can schedule the reports to be generated and sent via at the specified time or generate the reports manually via Report Generator. 9. Managing database: Not to run out of space on the Server computer, it s recommended to clean up the database periodically removing old unnecessary screenshots or enable the automatic clean-up. You can also remove unnecessary uninstalled Clients from the database. 16

17 Server and Database Server and Database About The Server is the main component of the system, which provides interaction between other components. The Server stores all monitored data, user accounts, and system settings in the database. Database Types Comparison When installing the Server, you can choose between the two types of databases (MS SQL database and Firebird database). These databases have the following differences: Feature MS SQL Database Firebird Database Free No (has a limited free version) NOTE: Using MS SQL Express does not guarantee the stable work of the Server. Yes Processing speed High Low Remote access to database Yes No Requires additional software installation Yes No Security High Low 17

18 Server and Database Installing/Uninstalling/Updating the Server Installing the Server To install the Server, do the following: 1. Run the EkranSystem_Components.exe installation file. 2. Click Next on the Welcome page. 3. Carefully read the terms of the End-User License Agreement and click I Agree. 4. On the Choose Components page, do one of the following and click Next: In the drop-down list, select Ekran System Server. Select Ekran System Server in the box. 5. On the Choose Install Location page, enter the installation path or click Browse to navigate to the Server installation folder. Click Next. On the Database Type page, select the type of the database you want to use for storing data. Click Next. For more information see the Database Types Comparison chapter. 18

19 Server and Database 7. If you have selected MS SQL Server, on the MS SQL Server Database Configuration page, define the connection parameters and then click Next. Define the MS SQL Server instance name, which is the instance name assigned to the TCP/IP port. Define the Database name for the database. Define the User name and Password of a user account via which the connection to the Server will be established. 19

20 Server and Database 8. If you have selected Firebird database, on the Database Location page, enter the database path or click Browse to navigate to the database installation folder. Click Next. 9. If you already have a database created during the usage of previous program versions, you will be offered to re-use it. If you want to use the existing database, click Yes. In other case, click No and the new database will be created. NOTE: If you click No, the existing database will be deleted. On the Administrator password page, define the password for the administrator (the default user of Ekran System with login admin and full permissions). Click Next. 20

21 Server and Database 10. On the Client Uninstallation Key page, enter the key that will be used during the Client local uninstallation and click Next. By default, the Uninstallation key is allowed. You will be able to change this key via the Management Tool any time later. 11. On the Choose Start Menu Folder page, define the name of the folder in the Start menu to which the shortcuts will be placed. Click Install. 21

22 Server and Database 12. The installation process starts. Its progress is displayed on the Installing page. 13. After the end of the installation process, click Finish to exit the wizard. 14. In Windows Firewall, you must allow the Server executable to accept TCP connections via ports 9447 (for the connection between the Server and the Clients) and (for the connection between the Server and the Management Tool). These rules will be added to Windows Firewall automatically if Windows Firewall is enabled during the Server installation. Adding Server Executable to Windows Firewall Please note that Windows Firewall will be adjusted automatically if it is enabled during the Server installation. If you use any other Firewall, it should be adjusted as well. To add the Server executable to the Windows Firewall, do the following: 1. In the Control Panel, select System and Security > Windows Firewall. 2. In the Windows Firewall window, click Advanced settings. 22

23 Server and Database 3. In the Windows Firewall with Advanced Security window, right-click Inbound Rules and select New rule. 4. The New Inbound Rule Wizard opens. 5. On the Rule Type page, select Program and click Next. 23

24 Server and Database 6. On the Program page, select This program path, then click Browse and navigate to the Server executable. The default path is "C:\Program Files\Ekran System\Ekran System\Server\EkranServer.exe ". Click Next. 7. On the Action page, select Allow the connection and then click Next. 24

25 Server and Database 8. On the Profile page, select the profile of the network used for connecting remote computers and the Server. Click Next. 9. On the Name page, define the Name of the rule. Click Finish. 10. The rule is created for the Server application. By default, the rule allows any connections via all ports. 11. To define the protocol and ports, double-click the created rule. The Properties window opens. 25

26 Server and Database 12. In the Protocols and Ports tab, do the following: In the Protocol Type list, select TCP. In the Local port list, select Specific Ports. Type the following port numbers in the box below: o 9447 (for the connection between the Server and the Clients) o (for the connection between the Server and the Management Tool) 13. Click Apply to save changes. Click OK. 14. Close the Windows Firewall window. Using an External/Cloud-Based Server Computer If your Server is not in the same network as Clients or the Management Tool, do the following: 1. Make sure your Server has a unique external IP address. 2. Specify this address when installing the Management Tool and installing the Client. Updating the Server The updating of the Server is performed via the installation file of a newer version. During an update you may select to update the existing database to a newer version or simply reinstall it. To update the Server, do the following: 1. Run the EkranSystem_Components.exe installation file. 26

27 Server and Database 2. On the Welcome page, click Next. 3. On the Already Installed page, select Update/Add/Remove components and click Next. 4. On the Choose Components page, select Ekran System Server in the box and then click Next. 27

28 Server and Database 5. On the Database Update page, if you want to keep the existing database, select Update database to a new version, otherwise select Reinstall the database. Click Next. NOTE: To change the type of the database, you need to reinstall the whole system. 6. On the Administrator password page, define the password for the administrator (the default user of Ekran System with login admin and full permissions). Click Next. 28

29 Server and Database 7. The update process starts. 8. After the end of the update process, click Finish to exit the wizard. Uninstalling the Server NOTE: Before uninstalling the Server, make sure you have uninstalled all the Clients from the remote computers. If you do not uninstall the Clients, they will remain installed on the remote computers and collect the data locally. It will be impossible to remove them in a common way. To uninstall the Server from the local computer, do the following: 1. Run the EkranSystem_Components.exe installation file or click Uninstall/Change on the Ekran System application in the Programs and Features window of the Windows Control Panel. 2. The setup wizard opens. 3. Click Next on the Welcome page. 4. On the Already Installed page, select Uninstall and click Next. 29

30 Server and Database 5. On the Uninstall Ekran System page, click Uninstall. 6. If you want to delete the database, click Yes in the confirmation message. In other case, click No and you will be able to use the saved database during the next installation of the program. 30

31 Server and Database 7. Wait for the uninstallation process to complete. Server Tray The Server Tray application informs you about the Server state. This application is installed on the computer where the Server is installed. It also automatically restarts the Server in case of its failure. The first three times the restart is performed automatically. The user is informed about the Server failure in the notification area. If the Server fails for the fourth time, it does not restart. You can start/stop the Server or hide the icon from the notification area. If you want to contact the Support, you need to collect the Server log (<Server installation folder>\serverservice.log) and attach it to the request. Database Management About Database management is performed via the Management Tool by the user with the administrative Database management permission. During the database management process you can delete monitoring data collected by the Clients, delete offline or uninstalled Clients and shrink the database depending on its type. Database Cleanup There are two ways to perform the Server database cleanup: 31

32 Server and Database Manually: allows you to define the date interval for which the data is to be removed from the database. Automatically: allows you to define the period during which sessions will be stored in database and cleanup start time. The automatic database cleanup will be performed on a daily basis at a specified time and all old sessions of Clients will be deleted. To delete data from the Server manually, do the following: 1. Log in to the Management Tool as a user with the administrative Database management permission. 2. Click the Database Management navigation link on the left. 3. On the Database Management page, select the Database Cleanup tab. 4. On the Database Cleanup tab, enter the Start Date and End Date within which the monitoring data will be removed from the database. NOTE: Only the whole sessions, i.e., the sessions whose start and end dates are within the defined period, will be removed. 5. Click Start Cleanup. To enable automatic database cleanup, do the following: 1. Log in to the Management Tool as a user with the administrative Database management permission. 2. Click the Database Management navigation link on the left. 3. On the Database Management page, select the Automatic Cleanup Settings tab. 4. On the Automatic Cleanup Settings tab, select the Enable automatic Server database cleanup check box. 5. Define the following options: 32

33 Server and Database Leave sessions in database (days): The number of days to store data before deleting. Start database cleanup at: The time to execute the clean-up operation. 6. To select the Clients whose monitoring data will not be deleted during automatic cleanup, click Add Exceptions. 7. On the Adding Exceptions page, select the necessary Clients and then click Add selected to add the Clients to the automatic cleanup list. Use filters to find a specific Client. 8. When all cleanup settings are defined, click Save. 33

34 Server and Database Shrinking MS SQL Database The database shrinking feature allows you to shrink the size of the MS SQL database to the actual amount of the data stored in it by cutting the space reserved by the database, but which is not used by it. NOTE: The database shrinking procedure may take some time (up to several hours) and cause performance slowdown. To shrink a database, do the following: 1. Log in to the Management Tool as a user with the administrative Database management permission. 2. Click the Database Management navigation link on the left. 3. On the Database Management page, select the Database Options tab. 4. On the Database Options tab, click Shrink database. NOTE: The progress of the database shrinking process is not displayed in the Management Tool and there is no indication of the process finishing. Firebird Database Optimization When using the Firebird database it is recommended to perform the Update statistics procedure at least every two months in order to optimize the database and increase the speed of reports generation. To perform the Update statistics procedure, do the following: 1. Log in to the Management Tool as a user with the administrative Database management permission. 2. Click the Database Management navigation link on the left. 3. On the Database Management page, select the Database Options tab. 4. On the Database Options tab, click Update statistics. Deleting the Client To delete the Client means to delete it completely from the database with cleaning up all its captured sessions. After this, the Client disappears from the Management Tool and its captured data is not displayed in the Session Viewer. It is possible to delete only offline or uninstalled (both after local or remote uninstallation) Clients. If after deletion the Client connects to the Server again, it will appear in the Management Tool but its deleted data will be unavailable. 34

35 Server and Database To delete one offline/uninstalled Client, do the following: 1. Log in to the Management Tool as a user with the administrative Database management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the needed offline or uninstalled Client from the list and click Edit Client. 4. On the Editing Client page, on the Properties tab, click Delete Client. 5. In the confirmation message, click Delete. 6. The Client is deleted. To delete several offline/uninstalled Clients, do the following: 1. Log in to the Management Tool as a user with the administrative Database management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Delete Clients. 4. On the Client Deletion page, click Add Clients to list. 35

36 Server and Database 5. The Client Deletion from Database page opens. It contains all Clients that can be deleted. NOTE: Only offline and uninstalled Clients are displayed in the list. 6. Select the needed Clients from the list and then click Next. To find a specific Client, enter its name in the Contains box and click Apply Filters. 7. When all Clients are selected, click Delete on the Client Deletion from Database page. 8. The Clients are deleted from the Server (with all captured sessions) and disappear from the Management Tool. Moving the Server Database If you are using an MS SQL database, you can move it to another location on the same computer using SQL Management Studio. If you are using the Firebird database, you can change its location to another disk/directory or rename it. To change the location for the Server Firebird database, do the following: 1. Stop the Server by clicking Stop in the right-click menu of the Server icon in the notification area or find the Server application in the Task Manager and click End task. 2. Open the Windows Registry Editor. 3. In the Registry Editor window, select the HKEY_LOCAL_MACHINE\SOFTWARE\EkranSystem key. 4. Find the Database values (Database and ManagedDatabase) and see where the Database files are located on your computer. 36

37 Server and Database 5. Move the folder with database files to a new location. NOTE: The folder contains the EKRANACTIVITYDB.FDB and MANAGEMENTDATABASE.FDB files and the Cache subfolder (unless your Cache subfolder is stored in the shared folder). 37

38 Server and Database 6. In the Registry Editor window, modify the following values: Database: Enter the full path to the EkranActivityDB.fdb file (including the file name) in its new location and then click OK. Managed Database: Enter the path to the folder with Ekran database in its new location and then click OK. 38

39 Server and Database 7. The Database location is changed. Start the Server to continue working with the program. Moving Binary Data to Shared Folder If necessary, you can store binary data received from Clients in the shared folder on your computer. This might be necessary for storing large amounts of data. This feature has the following limitations: Shared folders on mapped and mounted disks cannot be used for storing binary data. After you select to store binary data in the shared folder instead of MS SQL database, the already existing screenshots will no longer be displayed (only metadata will be available for them). The newly received screenshots will be displayed. To move binary data to the shared folder, do the following: 1. Stop the Server by clicking Stop in the right-click menu of the Server icon in the notification area or find the Server application in the Task Manager and click End task. 2. For a Firebird database do the following: Open the Windows Registry Editor. In the Registry Editor window, select the HKEY_LOCAL_MACHINE\SOFTWARE\EkranSystem key. Find the Database value and check where the Database files are located on your computer. Move the Cache folder with binary file to a new location. 3. In the Registry Editor window, click Edit>New>String value and add a new value: Value type: String Value name: StorageDirectory Value data: Shared folder location as \\<computer IP>\<folder path> or \\<computer name>\<folder path> 39

40 Server and Database 4. Start the Server to continue working with the program. 40

41 Management Tool Management Tool About The Management Tool is the component for managing the whole system and viewing monitored data received from Clients. It can be installed on any computer, but a network connection to the Server is required for the Management Tool to operate. There can be several computers with the installed Management Tool in the system. The work with the Management Tool is performed via your browser. Management Tool Installation Prerequisites Prerequisites Overview The following prerequisites are necessary for successful installation of the Management Tool. For Windows 7, it is important that you follow these steps in the correct order. To be able to install the Management Tool, you need to: 1. Turn on the Internet Information Service. 2. Install.NET Framework Configure the Internet Information Service. 4. Generate a self-signed certificate or import a purchased SSL certificate issued for the computer on which the Management Tool will be installed. 5. Add the certificate to the Trusted Root Certification Authorities on the computer on which the Management Tool will be installed. Otherwise a certificate error will be displayed in your browser when opening the Management Tool. 6. Set HTTPS binding for a default web site (or any other IIS site). NOTE: If you already have a certificate generated for the computer on which the Management Tool will be installed, you can skip certificate generation step and use an existing certificate. 41

42 Management Tool Turning on Internet Information Service (IIS) Turning on IIS for Windows 8, Windows 7, and Windows Vista To turn on the Internet Information Service for Windows 8, Windows 7, and Windows Vista, do the following: 1. Select Control Panel > Programs and Features (Program uninstallation). 2. Click the Turn Windows features on or off navigation link. 3. The Windows Features window opens. 4. In the features tree-view, select the Internet Information Services check box. 5. Click OK. 42

43 Management Tool Turning on IIS for Windows Server 2008 and Windows Server 2008 R2 To turn on the Internet Information Service for Windows Server 2008 and Windows Server 2008 R2, do the following: 1. In the Start menu, select All Programs > Administrative Tools > Server Manager. 2. In the navigation pane, select Roles, and then click Add Roles. 3. The Add Roles Wizard opens. 4. On the Before You Begin page, click Next. 5. On the Server Roles page, select Web Server (IIS), click Next, and then go to the Role Services page to start configuring Web Server (IIS). 43

44 Management Tool Turning on IIS for Windows Server 2012 To turn on the Internet Information Service for Windows Server 2012, do the following: 1. In the Start menu, select Server Manager. 2. In the navigation pane, select Dashboard, then click Manage > Add roles and features. 3. The Add Roles and Features Wizard opens. 4. On the Before You Begin page, click Next. 5. On the Installation type page, select Role-based or feature-based installation, and then click Next. 6. On the Server Selection page, select Select a server from the server pool, select your server from the Server Pool list, and then click Next. 44

45 Management Tool 7. On the Server Roles page, select Web Server (IIS), click Next and then click Add Features to start configuring Web Server (IIS). 45

46 Management Tool Installing.NET Framework 4.5 NET Framework 4.5 is usually installed on Windows 8.1, Windows 8, and Windows Server 2012 by default. If you are using Windows 7, Windows Vista, Windows Server 2008, or if there is no.net Framework 4.5 on other Windows versions, you can download it from the Microsoft official website and run the installation file on your computer. Configuring Internet Information Service (IIS) Windows 8 Make sure that all the following check boxes are selected in the Windows Features window and then click OK:.NET Framework 3.5 and.net Framework 4.5 Advanced Services; Internet Information Services > Web Management Tools > IIS Management Console; Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 3.5 and ASP.NET 4.5; Internet Information Services > World Wide Web Services > Common HTTP Features > Static Content. Windows Make sure that all the following check boxes are selected in the 46

47 Management Tool Vista/Windows 7 Windows Features window and then click OK: Internet Information Services > Web Management Tools > IIS Management Console; Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET; Internet Information Services > World Wide Web Services > Common HTTP Features > Static Content. Windows Server In the Add Roles Wizard window, on the Role Services page, make sure that the following check boxes are selected: Common HTTP Features > Static Content; Application Development > ASP.NET. 2. Click Next and then click Add Required Role Services. 3. On the Role Services page, make sure that the following check boxes are selected: Management Tools > IIS Management Console. 4. Click Next and then click Install. 5. After the end of installation, click Close. Windows Server In the Add Roles and Features Wizard window, on the Server Roles page, make sure that the Web Server (IIS) check box is selected and then click Next. 47

48 Management Tool 2. On the Features page, make sure that the following check boxes are selected:.net Framework 3.5 Features (Installed) >.NET Framework 3.5;.NET Framework 4.5 (Installed) > ASP.NET Click Next. 3. On the Web Server Role IIS page, click Next. 4. On the Role Services page, select the ASP.NET 4.5 check box (under Application Development). 5. Click Next and then click Add Features. 6. On the Role Services page, make sure that the following check boxes are selected: Application Development >.NET Extensibility 4.5 > ASP > NET 4.5 > ISAPI Extensions > ISAPI Filters. 7. Click Next and then click Install. 8. After the end of installation, click Close. 48

49 Management Tool Using Certificates Generating Self-Signed Certificate To generate a self-signed certificate on the machine on which you will install the Management Tool, do the following: 1. Open the Internet Information Service Manager: For Windows 8 or Windows 7: Open Computer > Manage > Services and Applications > Internet Information Services (IIS) Manager. For Windows Server 2012 or Windows Server 2008: Press Windows+R, enter inetmgr in the Run window and then press Enter. NOTE: Using the inetmgr command is a common way of opening the Internet Information Service Manager for any version of the Windows operating system. 2. Click the main node in the Connections tree-view and then double-click the Server Certificates item under the IIS category. 3. The Server Certificates pane opens. 4. On the Actions pane (to the right), click Create Self-Signed Certificate. 49

50 Management Tool 5. The Create Self-Signed Certificate window opens. 6. Enter the name for a certificate in the Specify a friendly name for the certificate box and select Personal in the Select a certificate store for the new certificate drop-down list. Click OK. 7. The certificate is created. 50

51 Management Tool Exporting Self-Signed Certificate To export self-signed certificate, do the following: 1. In the Internet Information Service Manager, on the Server Certificates pane, select the generated certificate and click Export on the Actions pane or in the certificate right-click menu. 2. In the Export Certificate window, define the location and password for the certificate. Click OK. 3. The certificate is exported and can be added to the Trusted Root Certification Authorities. Importing Trusted Certificate To import a purchased certificate issued for the computer, do the following: 1. Open the Internet Information Service Manager: For Windows 8 or Windows 7: Open Computer > Manage > Services and Applications > Internet Information Services (IIS) Manager. For Windows Server 2012 or 2008: Press Windows+R, enter inetmgr in the Run window and then press Enter. NOTE: Using the inetmgr command is a common way of opening the Internet Information Service Manager for any version of the Windows operating system. 2. Click the main node in the Connections tree-view and then double-click the Server Certificates item under the IIS category. 3. The Server Certificates pane opens. 4. On the Actions pane (to the right), click Import. 51

52 Management Tool 5. In the Import Certificate window, click the dots ( ) to browse for the file of the purchased certificate and enter its password in the Password field. 6. Click OK. 7. The certificate is imported and displayed on the Server Certificates pane of the Internet Information Services (IIS) Manager. Adding Certificate to Trusted Root Certification Authorities Before adding the self-signed certificate to the Trusted Root Certification Authorities, it should be exported. For purchased certificates that were issued for your computer this procedure is not needed. To add the certificate to the Trusted Root Certification Authorities, do the following: 1. Press Windows+R, type mmc in the Run text box and press Enter. 2. In the opened User Account Control window, click Yes. 3. In the Console window, select File > Add/Remove Snap-in. 52

53 Management Tool 4. In the opened Add or Remove Snap-ins window, select Certificates > Add. 5. In the opened Certificates snap-in window, select Computer account and click Next. 6. In the opened Select Computer window, select Local computer: (the computer this console is running on) and click Finish. 7. In the Add or Remove Snap-ins window, click OK. 53

54 Management Tool 8. In the Console window, expand the Certificates (Local computer) node. 9. In the Certificates (Local computer) tree-view, find the Trusted Root Certification Authorities node. 10. In the right-click menu of the Trusted Root Certification Authorities node, select All Tasks > Import. 11. The Certificate Import Wizard opens. 12. On the Certificate Import Wizard Welcome page, click Next. 54

55 Management Tool 13. On the File to Import page, click Browse to find the certificate to be imported and then click Next. 14. On the Private key protection page, enter the certificate password and then click Next. 55

56 Management Tool 15. On the Certificate Store page, click Next. 16. On the last page of the Certificate Import Wizard, click Finish. 17. In the confirmation message, click OK. 56

57 Management Tool 18. The certificate is imported and is displayed in the Console window in the Certificates node. Please note that the Issued To field contains the name of the computer on which the Management Tool will be installed in the format that will be used when opening the Management Tool. 19. Close the Console window. 57

58 Management Tool Setting HTTPS Binding for a Default Web-Site To set HTTPS binding for a default web-site, do the following: 1. Open the Internet Information Service Manager: For Windows 8 or Windows 7: Open Computer > Manage > Services and Applications > Internet Information Services (IIS) Manager. For Windows Server 2012 or Windows Server 2008: Press Windows+R, enter inetmgr in the Run window and then press Enter. NOTE: Using the inetmgr command is a common way of opening the Internet Information Service Manager for any version of the Windows operating system. 2. Expand the node with the name of the target computer in the central pane. 3. Expand the Sites node. 4. Select the Default Web Site. NOTE: If there is no such site in the Internet Information Services (IIS) Manager of your computer, you can select any other site (the name of the site does not matter). 5. Click the Bindings navigation link on the right. 6. The Site Bindings window opens. 58

59 Management Tool 7. If there is no binding of HTTPS type in the Site Bindings window, click Add. 8. The Edit Site Binding window opens. 9. In the Type box, select https. 10. Next to the SSL certificate drop-down list, click Select. 11. The Select Certificate window opens, where the list of existing certificates is displayed. 12. In the Select Certificate window, select the certificate generated for the Management Tool and then click OK. 13. In the Add Site Binding window, click OK. 14. In the Site Bindings window, click Close. 15. Now the Internet Information Service is fully adjusted and you can start installing the Management Tool. Installing/Uninstalling/Updating the Management Tool Installing the Management Tool To install the Management Tool, do the following: 1. Run the EkranSystem_ManagementTool.exe installation file. 2. On the Welcome page, click Next. 59

60 Management Tool 3. Carefully read the terms of the End-User License Agreement and click I Agree. 4. On the Connection Settings page, do the following and then click Next: In the Server address box, enter the name or IP address of the computer on which the Server is installed. In the URL address field enter the folder where the Management Tool will be located within IIS. This URL will be used when opening the Management Tool. 5. On the Choose Install Location page, enter the destination folder in the corresponding field or click Browse and in the Browse For Folder window, define the destination folder. Click Install. 60

61 Management Tool 6. The installation process starts. Its progress is displayed on the Installing page. 7. After the end of the installation process, click Close to exit the wizard. 8. The Management Tool is displayed as an application of a default web site or any other site with https connection in the Internet Information Services (IIS) Manager. 9. Now you can open the Management Tool via your browser from the same computer or a remote one. 61

62 Management Tool Adjusting Computer for Remote Access If you want to open the Management Tool from the computer different from the one where the Management Tool is installed, you need to adjust Firewall settings to be able to access this computer. If the users access Management Tool only from computers where it is installed, there is no need to configure Firewall. To adjust Firewall on the computer where the Management Tool is installed, do the following: 1. In the Control Panel, select System and Security > Windows Firewall. 2. In the Windows Firewall window, click Advanced settings. 3. In the Windows Firewall with Advanced Security window, right-click Inbound Rules and select New rule. 4. The New Inbound Rule Wizard opens. 5. On the Rule Type page, select Predefined and then select Secure World Wide Web Services (HTTPS) in the list. Click Next. 6. On the Predefined Rules page, select the World Wide Web Services (HTTPS Traffic-In) check box. Click Next. 62

63 Management Tool 7. On the Action page, select Allow the connection. Click Finish. 8. The new inbound rule for Firewall is created. Updating Management Tool To update the Management Tool, do the following: 1. Run the Management Tool installation file (EkranSystem_ManagementTool.exe) of a newer version. 2. On the The program is already installed page, select Update and then click Next. 63

64 Management Tool 3. Follow the installation instructions. 4. The Management Tool will be updated to the new version. Uninstalling Management Tool To uninstall the Management Tool, do the following: 1. Open the Programs and Features window of the Windows Control Panel. 2. In the Programs and Features window, find the Ekran System Management Tool application. 3. In the right-click menu of the application, select Uninstall. 4. The setup wizard opens and starts the uninstallation process. 5. When the process is completed, click Close to exit the setup wizard. 6. The Management Tool is uninstalled and removed from the Internet Information Service (IIS). Opening Management Tool To open the Management Tool, do the following: 1. Open the browser and enter https://<name of the computer or IP on which the Management Tool is installed>/<url address that has been specified during the Management Tool installation> in the address line. 64

65 Management Tool For example, https://john-pc/mymonitoringsystem. NOTE: If the certificate is not added to the Trusted Root Certification Authorities or the name of the computer entered in the browser address does not match the subject (Issued To field) of the certificate, your browser will display a certificate error when opening the Management Tool. 2. The Management Tool opens. 3. Enter the credentials of the existing user added to the system: For an internal user, enter the login and password defined during user creation. For a Windows user, enter the login in the form <domain name>\<user name> and Windows authentication password. Please note, if the Active Directory user group has been added to the system, the users belonging to it can login using their Windows credentials. 4. The Management Tool Home page opens. If you encounter any problems when opening the Management Tool, see the Troubleshooting chapter. 65

66 Management Tool Management Tool Interface The Management Tool interface is divided into the following areas: Navigation pane Data View pane Filtering pane Toolbar Panes The Navigation pane The Navigation pane allows you to navigate between different sections of the Management Tool and consists of the following navigation links: Home: Opens the page on which the information about the number of used Licenses and installed Clients is displayed. Monitored Sessions: Displays the list of all monitored sessions received from Clients to users that have View monitoring results permission. Forensic Export History: Displays the list of sessions exported via Forensic Export from the Session Viewer. A user can download any exported session and validate the already exported session. Report Generator: Opens the Report Generator page on which the user can generate the report of the required type by defined parameters and then save it or print it. Client Management: Displays the information about all Clients in the system. The number of Clients displayed on the page depends upon permissions given to users that log in to the Management Tool. User Management: Displays the information about all Users in the system and is available for users that have the User management permission. Alert Management: Displays the information about alerts assigned to your Clients. USB Monitoring Management: Displays the list of all USB monitoring rules for all the Clients in the system and is available for the users with the administrative Client installation and management permission. Scheduled Reports: Opens the Scheduled Reports page on which the user can view and manage report generation rules, and view rule logs. Database Management: Opens the page with Manual Cleanup and Auto Cleanup options used for deleting the data from your Database by users that have the Database management permission. Serial Key Management: Displays the information about your Serial key and contains keys activating/deactivating options and is available for users that have the Serial keys management permission. 66

67 Management Tool Diagnostics: Provides quick access to Server and Management Tool log files for users that have the Database management permission. The Data View pane The Data View pane contains a grid with the information about your Clients, Users, Alerts, database, and Serial keys. The Filtering pane The Filtering pane allows you to filter the Clients, Users, and Alerts by keywords of their names and hide offline/online/uninstalled/licensed/windows/linux Clients. Toolbar The Toolbar of the Management Tool allows you to perform basic actions with Clients, Users, and Alerts. The options of the Toolbar are the following: For Client Management: Add Client Group, Install Clients, Manage Licenses, Edit Uninstallation Key, Uninstall Clients, and Delete Clients. For User Management: Add User and Add User Group. For Alert Management: Add Alert and Global Alert Settings. For USB Monitoring Management: Add Rule. For Scheduled Reports: Add Rule. For Forensic Export: Validate Export Results. Changing Password for Logged in User Internal users, including the Built-in administrator, can change their password after logging in to the Management Tool. This action is not available for Active Directory users. To change your password, do the following: 1. Click your user name in the upper right corner of any Management Tool page. 2. The Manage account page opens. 3. In the Current password box, type your current password. 4. In the New password box, type the new password. 5. Re-enter the password in the Confirm password box. 67

68 Management Tool 6. Click Change password. 7. Your password is changed. You will need to use it on the next log in. 68

69 Licensing Licensing General Licensing Information To start receiving information from the Clients, you have to assign licenses to them. Three types of licenses are available: Workstation license: Clients with this license monitor only one session, either remote or local, on the investigated computer. NOTE: Licenses of the workstation type cannot be assigned to a computer with Server OS. Server license: Clients with this license monitor unlimited number of remote sessions and any local sessions on the investigated computer. Remote sessions include Remote Desktop sessions, terminal sessions, etc. Linux license: Linux Clients with this license monitor unlimited number of terminal sessions on the investigated computer. Each Client can have only one license assigned. During the first connection to the Server, the license corresponding to the Client computer operating system is automatically assigned to a Client. If the license has not been automatically assigned, then you will have to assign the license to the Client manually. When you log into the Management Tool for the first time, you can request a trial serial key which allows you to use 5 workstation licenses, 3 Linux licenses, and 1 server license for 30 days. The trial serial key will be sent to the address you specify in the request form. To use the system permanently and with a greater number of licenses, you have to license it with purchased serial keys on a computer with the installed Server. NOTE: After activation of any serial key, the embedded trial key expires. Two types of serial keys are available: Standard serial keys: These keys allow you to use licenses they contain during the unlimited period of time and allow you to update the product during 12 months from activation. Trial serial keys: These keys allow you to use the licenses they contain during 30 days from activation and update the product during this period. Each serial key contains the following data: Subscription period Server licenses for the Clients Workstation licenses for the Clients Linux licenses for the Clients 69

70 Licensing Once you have purchased serial keys, you can either activate serial keys online or add activated serial keys if you have no Internet connection on a computer with the installed Server. Contact your vendor for information on purchasing serial keys. You need the administrative Serial keys management permission to activate serial keys. Please note, after the activation, serial keys are bound to a specific computer and cannot be used on another computer. About Subscription A subscription is a period that defines what updates can be applied to your copy of the product. Updates are defined by their release date. After the subscription expires, you can still assign licenses to Clients, but you will be unable to update the System to versions released after the subscription expiration date. The subscription end date is defined during the serial key activation (either via the Management Tool or on the vendor s site). It is calculated using a serial key with the longest subscription period. Example: If you activate two keys, one with a 30 days subscription period and one with a 12 months subscription period, simultaneously, the subscription end date will be set to 12 months from the activation date. When a new serial key is being activated, the subscription period is prolonged accordingly. Please note, if the current subscription period is longer than the one of a key being activated, current subscription period does not change. For example, if you activate a key with 12 months subscription period after a key with 30 days subscription period, the subscription end date will be set to 12 months since the activation date. But if you activate a key with 30 days subscription period after a key with 12 months subscription period, the subscription end date will not change. If your subscription expires, you can purchase a special subscription extension serial key, which does not contain any keys, but extends your subscription period, or you can activate any other serial key. Viewing License State You can view the information on serial keys you have activated or added and license details on the Serial Key Management page in the Management Tool. 70

71 Licensing To view the license state, open the Management Tool and click Serial Key Management navigation link on the left. The following information is displayed on the Serial Key Management page: Subscription end date: The subscription end date is calculated basing on dates of serial keys activation and their subscription periods. Workstation licenses used: The number of workstation licenses used out of total number, which is summed up from all activated serial keys. Server licenses used: The number of server licenses used out of total number, which is summed up from all activated serial keys. Linux licenses used: The number of Linux licenses used out of total number, which is summed up from all activated serial keys. Not licensed Clients: Displays the number of installed Clients with no licenses assigned. The following information is displayed in the Serial Key Management table: o Serial key o Activation date o Deactivation date (for deactivated keys only) o Number of server licenses o Number of workstation licenses o Number of Linux licenses o Key state: activated/deactivated/expired. For a trial serial key, an expiration date is displayed near the key state. Activating Serial Keys Online To activate purchased serial keys online, do the following: 1. Make sure you have an active Internet connection on the computer with the installed Server. 2. Log in to the Management Tool as a user with the administrative Serial keys management permission. 3. Click the Serial Key Management navigation link on the left. 4. On the Serial Key Management page, click Activate keys online. 71

72 Licensing 5. In the Serial Key Activation window, enter serial keys to be activated separating them with semicolons or paragraphs and click Activate. 6. The activated keys will appear on the Serial Key Management page. 7. The number of available server, workstation, and Linux licenses and the subscription end date change. Adding Activated Serial Keys Offline If you have no Internet connection on a computer on which the serial keys are to be activated, you can activate them on the license site and then add the activated serial keys offline. For more information, send an to To activate serial keys offline on the license site, do the following: 1. On the computer with the installed Server, start the UniqueIdentifierGenerator.exe file, which you can find near the Server installation file. 2. The Unique Identifier Generator window opens. 3. Click Generate to generate a unique identifier for your computer. 4. When a unique identifier for your computer is generated, it will appear in a text box under the Unique Identifier group of options. 5. Copy the unique identifier from the text box to a text file on a removable drive. 6. Go to the license site. 7. Enter the generated unique identifier in the Unique Identifier box. 8. Copy and paste the purchased serial keys to the Serial Keys box separating them with paragraphs or spaces. 9. Enter the CAPTCHA text in a text box near the CAPTCHA image. 10. Click Activate. 11. The activatedkeys.txt file will be generated. Save the file on a removable drive. 12. Copy the file to the computer on which you will open the Management Tool. NOTE: Please do not edit the generated file activatedkeys.txt. 72

73 Licensing To add activated serial keys in offline mode, do the following: 1. Log in to the Management Tool as a user with the administrative Serial keys management permission. 2. Click the Serial Key Management navigation link on the left. 3. On the Serial Key Management page, click Add activated keys. 4. On the Activated Serial Key Adding page, click Choose File and navigate to the activatedkeys.txt file with activated serial keys. 5. Click Add. 6. The newly added serial keys appear on the Serial Key Management page. 7. The number of available server, workstation, and Linux licenses and the subscription end date change. 8. If there are both licensed and unlicensed Clients in your network and you want to license the rest of Clients with a purchased key, you will have to assign the license to the remaining unlicensed Clients manually. Deactivating Serial Keys If for some reason you decide to discontinue using Ekran System, you can deactivate serial keys. To deactivate a serial key, do the following: 1. Make sure you have an active Internet connection on the computer with the installed Server. 2. Log in to the Management Tool as a user with the administrative Serial keys management permission. 3. Click the Serial Key Management navigation link on the left. 4. On the Serial Key Management page, select a serial key to be deactivated and click Deactivate selected. NOTE: Expired serial keys can t be deactivated. 5. In the confirmation message, click Deactivate. 6. The deactivated serial key is marked as Deactivated in the State column of the Serial Key Management page. 7. The number of available server, workstation and Linux licenses and the subscription end date change. 73

74 Licensing Client License Management The Client license management is performed in the Management Tool by the user with the administrative Client installation and management permission. You can assign a license to a Client or unassign it manually any time. The license can be assigned to an offline Client, and it will be applied after the Client is online. If the Client is uninstalled, its license becomes free and can be assigned to another Client. NOTE: When a trial serial key expires, the corresponding number of licenses is automatically unassigned from Clients. Information about the number of used and free licenses of each type is displayed on the Serial Key Management page in the Management Tool. To assign the license to one Client, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the needed Client from the list and then click Edit Client. 4. On the Editing Client page, on the Properties tab, in the License box, select the type of license you want to assign to the Client. 5. Click Finish. 6. The license is assigned to the Client. To manage the licenses to several Clients, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Сlick the Client Management navigation link on the left. 3. On the Clients page, click Manage Licenses. 4. On the License Management page, select the Clients to which the licenses should be assigned. To find a specific Client, enter its name in the Contains box and click Apply Filters. 5. When the Clients are selected, click one of the following: Assign workstation license: Assigns licenses to the selected Windows Clients installed on the computers with not Server operating system. Assign server license: Assigns licenses to the selected Windows Clients installed on the computers with Server operating system. Assign Linux license: Assigns licenses to the selected Linux Clients. Assign recommended license: Automatically defines the type of the licenses to be assigned basing on the operating system of the computers on which the Clients are installed. 74

75 Licensing Unassign license: Removes licenses from the selected Clients. NOTE: To change the Client license type, you do not need to unassign the current license. This will be done automatically. 75

76 User and User Group Management User and User Group Management About By default, there is one administrator in the system, whose login is admin and whose password is defined during the Server installation. The administrator has all the rights for work in the system. In order to grant others access to the system, you can add users and define their permissions. There are two types of users: Internal users Active Directory Users (Windows domain users) To define permissions for users, you can create user groups. One user can belong to several user groups. When the user is added to a group, he/she inherits all permissions from a group. If the user inherited some permissions from a group, these permissions can be removed only by removing the user from this group. Apart from permissions received from the group, you can assign other permissions to a specific user. By default, there are three user groups in the system: All Users: A group that contains all created users. Administrators: A group of users that can perform administrative functions within the system. If a user is added to this group, he/she receives all administrative and Client permissions within the system. This user group corresponds to the Administrator role in the earlier versions of the application. Supervisors: A group of users that perform major investigative work with the Clients. If a user is added to this group, he/she receives the Viewing monitoring results permission for All Clients. This user group corresponds to the Supervisor role in the earlier versions of the application. You can also add other custom user groups and manage them yourself. Please note, user and user group management is allowed only to the users with the administrative User management permission. Viewing Users and User Groups The Users and User Groups are displayed on the User Management page in the Management Tool. Users are grouped by the User Groups which they belong to. The lists of Users contain the following information: User Name First Name Last Name 76

77 User and User Group Management Description NOTE: For Active Directory users, their first name and last name will be filled automatically after the first log in to the system. To find a required User, enter a part of his/her user name, first name, last name or description in the Contains box and click Apply Filters. On the User Management page, you can add new Users/User Groups and edit existing Users/User Groups (including deleting). User Management Adding Users To add a new user, do the following: 1. Log in to the Management Tool as a user with the administrative User management permission. 2. Click the User Management navigation link on the left. 3. On the Users page, click Add User. 4. On the User Type tab, select the type of the user you want to add: Click Add an Internal user to create an internal application user. Click Add an Active Directory user/user group to add an existing Windows user/user group. 77

78 User and User Group Management 5. On the User Details tab, do one of the following and click Next: For an internal user, define user credentials and additional information about the user. NOTE: Login and password are required. The password must be at least 6 characters long. The maximum length of the first name, last name, and description is 200 characters. For an Active Directory user, enter User login and Domain. 78

79 User and User Group Management 6. On the User Groups tab, select the user groups to which the user will belong. To find a specific group, enter its name in the Contains box and click Apply Filters. Click Next. NOTE: The user is automatically added to the default All Users group and can t be removed from it. 7. On the Administrative Permissions tab, select administrative permissions that will be given to the user. Click Next. NOTE: If the user has inherited some permissions from user groups, you can only add new permissions. To remove permissions inherited from user groups, you need to remove the user from these groups. 79

80 User and User Group Management 8. On the Client Permissions tab, do the following: Select the necessary Client/Client Group. To find a specific Client/Client Group, enter its name in the Contains box and click Apply Filters. Click Edit Permissions and then, in the Client Permissions/Client Group Permissions window, define the Client permissions which will be given to a user for the corresponding Client/Client Group. When the permissions are defined, click Save to close the Client Permissions/Client Group Permissions window. 9. Click Finish. 10. The user is added and displayed on the Users page. NOTE: For an Active Directory user, the first name and last name properties will be automatically filled after the user s first login to the system. Editing Users To edit an existing user, do the following: 1. Log in to the Management Tool as a user with the administrative User management permission. 80

81 User and User Group Management 2. Click the User Management navigation link on the left. 3. On the Users page, click Edit User for the required user. 4. Edit user properties and permissions on the corresponding tabs in the same way as when adding a new user. NOTE: Click Next or Finish to save the changes on each tab. 5. The user is edited. New permissions will be applied to him/her in minutes. Deleting Users Deleting a user means that a user will not be able to use the system. If you delete the user who is logged in the Management Tool, the Management Tool will become unavailable for the user at once and none of its pages will be displayed. To delete a user, do the following: 1. Log in to the Management Tool as a user with the administrative User management permission. 2. Click the User Management navigation link on the left. 3. On the Users page, click Edit User for the required user. 4. On the User Details tab, click Delete User. 5. In the confirmation message, click Delete. 6. The user is deleted. User Group Management Adding User Groups To add a new user group, do the following: 1. Log in to the Management Tool as a user with the administrative User management permission. 2. Click the User Management navigation link on the left. 3. On the Users page, click Add User Group. 4. On the Group Properties tab, define the name for the user group and optionally define its description. Click Next. NOTE: The maximum length of the group name and description is 200 characters. 5. On the User Management tab, select users that will belong to the user group. To find a specific user, enter its name in the Contains box and click Apply Filters. Click Next. 6. On the Administrative Permissions tab, select administrative permissions that will be given to all users belonging to this user group. Click Next. 81

82 User and User Group Management 7. On the Client Permissions tab, find the Client/Client Group for which permissions are to be defined. To find a specific Client/ Client Group, enter its name in the Contains box and click Apply Filters. Click Edit Permissions and then, in the Client Permissions/ Client Group Permissions window, define the Client permissions which will be given to a user for the corresponding Client/Client Group. After you have defined all Client permissions, click Save to close the Client Permissions/ Client Group Permissions window. 8. On the Client Permissions tab, click Finish. 9. The user group is added. Editing User Groups To edit an existing user group, do the following: 1. Log in to the Management Tool as a user with the administrative User management permission. 2. Click the User Management navigation link on the left. 3. On the Users page, click Edit User Group for the required user group. 4. Edit user group properties and permissions on the corresponding tabs in the same way as when adding a new user group. NOTE: Click Next or Finish to save the changes on each tab. 5. The user group is edited. Deleting User Groups Deleting a user group does not delete users belonging to it. If the group is deleted, its users no longer have permissions given by this user group unless these permissions are inherited from another user group. NOTE: The user group All Users cannot be deleted. 82

83 User and User Group Management To delete a user group, do the following: 1. Log in to the Management Tool as a user with the administrative User management permission. 2. Click the User Management navigation link on the left. 3. On the Users page, click Edit User Group for the required user group. 4. On the Group Properties tab, click Delete Group. 5. In the confirmation message, click Delete. 6. The user group is deleted. Permissions About The permissions allow you to define which functions a user will be able to perform with the system and Clients. There are two types of permissions: administrative permissions and Client permissions. Administrative permissions define actions that a user can perform with the whole system. Client permissions define actions that a user can perform with selected Clients. The permissions can be defined during user and user group adding/editing. After editing, new permissions are applied to the user with a timeout up to 30 minutes. If you define permissions for the group, any user belonging to this group inherits these permissions. To remove permissions inherited by the user from a group, you need to remove the user from a group. Apart from permissions inherited from the group, you can assign a user his/her own permissions. Administrative Permissions The following administrative permissions are available: Serial keys management: Allows a user to activate and deactivate serial keys. User management: Allows a user to add, edit, delete Users/User groups and define permissions for them. Client installation and management: Allows a user to install Windows Clients, assign licenses to Windows Clients, add, edit, and delete Client groups, manage alerts, define alert settings, create and manage scheduled report rules, view report logs, and define sending settings, and create and manage the USB monitoring & blocking rules. Database management: Allows a user to get information on the database, perform database cleanup, delete Clients from the database, and download Server and Management Tool log files. 83

84 User and User Group Management Client Permissions Client permissions define which actions a user will be able to perform with the Clients. If a user does not have the administrative Client installation and management permission, in the Management Tool he/she will see only those Clients for which he/she has at least one Client permission. NOTE: Client permissions are defined for each Client or Client Group individually. The following Client permissions are available: Client configuration management: Allows a user to define Client configuration. Viewing monitoring results: Allows a user to: o View the results of Client monitoring and Forensic Export results in the Management Tool. o View Windows and Linux Client configuration. o Generate reports in the Management Tool. [Windows Clients] Viewing keystrokes: Allows a user to view keystrokes recorded during Client monitoring [Windows Clients] Client uninstallation: Allows a user to uninstall a Client. [Windows Clients] Login to Client computer: Allows a user to log in to the Client computer with enabled forced user authentication and is available only for the Client with server operating system. Permission Example You can define the permission for a user, by selecting the Edit User option and selecting the check box next to the required permission on the Administrative Permissions tab. If the user belongs to several Groups, he/she will inherit all the permissions defined for them. For example: There is a user Joe who belongs to Group 1 and Group 2 user groups. Besides, there are Client 1 and Client 2 that belong to All Clients group. The following permissions are given to the user Joe, Group 1, and Group 2 by the administrator: User/User Group Administrative Client permissions permissions Permission For Group 1 User management Client uninstallation Client 1 Group 2 Serial keys management Viewing monitoring Client 2 results User Joe Client installation and Viewing monitoring Client 1 84

85 User and User Group Management management Serial keys management results Client configuration management All Clients As a result, the user Joe will have the following permissions: Administrative o User management permission (Because he belongs to Group 1). o Serial keys management permission (Because he belongs to Group 2. But he also has his own Serial keys management permission, and thus will have it even if Group 2 is deleted or its permissions are edited). o Client installation and management permission (He will have this permission irrespective to user groups which he will be added to). Client permissions for Client 1 o Client uninstallation permission (Because he belongs to Group 1). o Viewing monitoring results permission (Because it is his own permission and he will have it irrespective to user groups which he will be added to). o Client configuration management permission (Because the Client belongs to All Clients group). 85

86 User and User Group Management Client permissions for Client 2 o Viewing monitoring results permission (Because he belongs to Group 2). o Client configuration management permission (Because the Client belongs to All Clients group). 86

87 Windows Clients Windows Clients About Windows Client is a program that can be installed on the target computers to monitor the activity of their users. The monitored data is sent by the Windows Client to the Server and can be viewed in the Management Tool. Depending upon his/her permissions, a user can install/uninstall Clients remotely, manage their configuration, and manage Client groups. Monitoring via Windows Clients The Windows Clients work as follows: Each Windows Client starts automatically on computer start. A licensed Windows Client performs the monitoring of both remote and local sessions. Clients with a server license can monitor many sessions simultaneously. Clients with a workstation license monitor only one session (local or remote). Every time the computer is restarted, the Windows Client starts recording screen captures in a new session. The maximum duration of one session can be 24 hours. At 00:00 all live sessions are terminated. After their termination (their status changes from live to finished), new live sessions automatically start. If a user works with several monitors, the Windows Client creates screen captures from all of them. The Windows Client sends its monitoring results to the Server. If there is no connection with the Server, the Client stores the monitored data and automatically sends it to the Server when the connection is renewed. The data is stored in the in TempWrite.dat file in the Client folder, which is located here: C:\Program Files\Ekran System\Ekran System\Client. The screen capture creation frequency of the Windows Client is the following: o If the user is typing the text, the screen capture is created once in 10 seconds. o If the user clicks a mouse, the screen capture is created once in 3 seconds. o If the user changes an active window, the screen capture is created once in 3 seconds. Screen capture creation triggers usually influence each other, though the average screen capture creation frequency is higher. If the Capture screen on each event without timeout parameter is selected for the Windows Client, screen captures are created on each mouse click or keyboard key pressing without using data sending time out. WARNING! The Capture screen on each event without timeout option affects CPU usage on the Client computer and database size. It is not recommended to use this option for a great number of Clients and for a long period of time. 87

88 Windows Clients Installing Windows Clients About During the system deployment, remote installation of the Windows Clients is used. Remote installation of the Clients is performed via the Management Tool. To ensure successful remote installation of the Windows Clients, you have to set up the network environment beforehand. If your computers belong to a workgroup but not a domain, you need to know the administrator account credentials for each remote computer. Otherwise, knowing the domain administrator credentials is enough. The Windows Clients can also be installed locally via the installation package generated in the Management Tool. Thus you can distribute the installation package of the Client with predefined settings among the network computers and install it. This kind of installation is useful when you experience difficulties with installing the Clients remotely via the Management Tool, or the computers in your network are a part of a workgroup and do not have the same administrative account for each computer. Setting up Environment for Remote Installation Windows Client Installation Prerequisites The majority of Windows Client installation/uninstallation issues are caused by incorrect system or network settings. The following conditions have to be met for successful Windows Client installation: The remote computer has to be online and accessible via network. Shared folders have to be accessible on the remote computer. Simple file sharing (Sharing Wizard) has to be disabled if the computer is in a workgroup (for domain computers this requirement can be skipped). You need to know the domain administrator or local administrator account credentials for the remote computer. The Server and the Remote Procedure Call (RPC) system services have to be running on the remote computer. Windows Vista and Windows XP Firewall has to be properly set up on the remote computer during the Clients remote installation. In Windows 8, Windows 7, Windows Server 2012 and Windows Server 2008 Firewall, inbound connections have to be allowed in the Remote Service Management (RPC) rule for the remote computers and the File and Printer Sharing option has to be enabled (in this case it is not necessary to disable Windows Firewall). In Windows Firewall on the Server side, allow the Server executable to accept TCP connections via ports 9447 (for the connection between the Server and the Clients). 88

89 Windows Clients NOTE: These rules will be added to Windows Firewall automatically if Windows Firewall is enabled during the Server installation. Make sure the conditions mentioned above are met to avoid possible problems with Client remote installation. Disabling Simple File Sharing in Windows XP To disable simple file sharing in Windows XP, do the following: 1. Open My Computer. 2. Select Tools > Folder Options in the menu. 3. In the Folder Options window, select the View tab. 4. Clear the Use simple file sharing check box. 5. Click Apply and OK to close the window. 89

90 Windows Clients Disabling Sharing Wizard in Windows 8.1, Windows 8, and Windows 7 To disable the Sharing wizard in Windows 8.1, Windows 8, and Windows 7, do the following: 1. Open the Folder options window: For Windows 8.1/Windows 8: Open the Control Panel and then select Appearance and Personalization. For Windows 7: Open Computer and then select Organize > Folder and search options. 2. In the Folder Options window, select the View tab. 3. Clear the Use Sharing Wizard check box. 4. Click Apply and OK to close the window. Checking System Services To check that the Server and Remote Procedure Call (RPC) system services are running: 1. Right-click Computer and select Manage. The Computer Management window opens. 90

91 Windows Clients 2. Expand the Services and Applications node and select Services. To quickly access Windows Services, press Windows+R, type services.msc in the Run text box and press Enter. 3. Find the Server service and the Remote Procedure Call (RPC) service in the list of services. Make sure both services are running (their status is displayed as Started). 4. If one or both services are not running, start them manually. To start the service, right-click it and select Start from the context menu. The selected service is started. Setting up Windows Vista, Windows XP, and Windows Server 2003 Firewall It is not necessary to disable the Firewall in Windows Vista, Windows XP, and Windows Server For successful remote installation of the Clients, you have to enable the File and Printer Sharing option. To set up Windows Vista, Windows XP, and Windows Server 2003 Firewall, do the following: 1. Select Start > Control Panel > Windows Firewall. 91

92 Windows Clients 2. In the Windows Firewall window, select the Exceptions tab. 3. On the Exceptions tab, select the File and Printer Sharing check box. 4. Click OK. 92

93 Windows Clients Setting up Firewall for Windows 8.1, Windows 8, Windows 7, Windows Server 2012, Windows Server 2008 It is not necessary to disable the Firewall in Windows 8.1, Windows 8, Windows 7, Windows Server 2012, and Windows Server For successful remote installation of the Clients, you have to allow inbound connections in the Remote Service Management (RPC) rule for the remote computers and enable the File and Printer Sharing option. To enable inbound connections for the Remote Management Service (RPC), do the following: 1. Select Control Panel > System and Security > Windows Firewall. 2. In the Windows Firewall window, click Advanced settings. 3. In the Windows Firewall with Advanced Security window, click Inbound Rules and then double-click the Remote Service Management (RPC) rule in the rules list. 4. The Remote Service Management (RPC) Properties window opens. 5. In the General tab, select Enabled under General and click Allow the connection under Action. 93

94 Windows Clients 6. In the Advanced tab, under Profiles, select the profile of the network used for connecting remote computers and the Server. 94

95 Windows Clients 7. Click Apply and then OK to save the settings and close the Properties window. 8. Close the Windows Firewall window. To enable the File and Printer Sharing option, do the following: 1. Select Control Panel > System and Security > Windows Firewall. 2. In the Windows Firewall window, click Allow an app or feature through Windows Firewall. 3. In the opened Allowed apps window, click Change settings. 95

96 Windows Clients 4. Select the File and Printer Sharing check box. 5. Click OK. 96

97 Windows Clients Installing Windows Clients Remotely via the Management Tool About You can install the Windows Clients remotely via the Management Tool. This way of installation is very convenient if all computers in your network have the same domain administrator credentials. Remote Windows Client Installation is performed by a user who has the Client installation and management permission in two steps: 1. Selecting computers on which Clients will be installed. 2. Defining installation parameters and installing the Clients. Selecting Computers To select the computers for Client installation, do the following: 1. Log in to the Management Tool as a user with the Client installation and management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Install Clients. 4. The Computers without Clients page opens. On this page, you can see the computers for which the previous installations failed. 5. Select how you would like to search for computers where the Windows Clients will be installed: To select computers from the list of all computers in your network, click Deploy via network scan. To select computers by IP range (IPv4 or IPv6 addresses), click Deploy via IP range. 97

98 Windows Clients To select computers by their names, click Deploy on specific computers. 6. In the Choose search results window: Click Start new search to look for computers with defined parameters. Click Previous search results to choose the computers found in the previous search. If you have not performed any searches yet, this option will be absent. 7. If you have selected the Deploy via IP range option, the Computers Scan page opens. In the From Address and To Address boxes, enter the IP range (either IPv4 or IPv6) for which the network should be scanned. To find only one computer, enter the same IP address in both boxes. Click Scan. 8. If you have selected the Deploy on specific computers option, the Adding Computers page opens. Enter the names of computers on which Windows Clients must be installed in the box Name and click Scan. Use semicolon to separate computer names. Please note that you should enter the full name of the computer. 9. The scanning process starts. The list of found computers will be updated automatically. If it is not updated, click Refresh. 10. When the scanning process finishes, select check boxes next to the computers that you want to install the Clients on. Click Next. 98

99 Windows Clients 11. The selected computers are added to the list on the Computers without Clients page. 12. If you want to remove some computers from this list, click Remove from list next to the selected computer. Remote Windows Client Installation Process When all computers for Windows Сlient installation are selected, you are ready to start installation. Please make sure that all selected computers are correctly adjusted. To install the Windows Clients remotely, do the following: 1. On the Computers without Clients page, click Install. 2. On the Client Configuration page, define the name/ip of the Server to which the Windows Clients will connect, and define the Client configuration for the Clients you are installing. Click Next. NOTE: The Server IP address has to be static for Clients to connect to it successfully. Unique external IP addresses should be used for cloud-based Servers. 3. On the Installation credentials page, enter the credentials of a user with administrator permissions on the target computers for Client installation and then click Next. If the computers are in a domain, enter the domain name and domain administrator account credentials. If the computers are in workgroup, enter the credentials of a local administrator for target computers. 99

100 Windows Clients If you leave the Domain box empty, the entered credentials will be used as the credentials of a local user of a target computer and the Client will be installed under the <target PC name>\<user name> account. NOTE: All workgroup computers must have the same administrator account credentials. Otherwise use installation via installation package method to deploy the Clients. 4. The installation process starts. The progress of installation will be updated automatically on the Client installation page. If it is not updated, click Refresh. 5. After the end of the installation, the installed Clients will appear on the Clients page in All Clients group. If the installation of some Clients fails, these computers will remain in the Computers without Clients list and you can click Retry to start the installation again. Remote Installation from an Existing.INI File If you already have an.ini file with defined settings generated in the Management Tool and saved to your computer, you can use it for installing the Windows Clients. To install the Windows Clients remotely using an existing.ini file, do the following: 1. On the Computers without Clients page, click Install using existing.ini file. 2. On the INI file selection page, click Choose file to select the.ini file that will be used for configuration of new Clients. Please note, if any parameter except RemoteHost is absent or not valid, its value will be set to default. The RemoteHost parameter is ignored in this type of installation. The Windows Client will connect to the Server to which the Management Tool is connected. 100

101 Windows Clients 3. Once the.ini file is chosen, click Next and continue the installation the same way as when installing the Clients remotely in a common way. Installing Windows Clients Locally About You can install the Windows Clients locally using the Client installation file generated in the Management Tool. You have two options for downloading the Client installation file from the Management Tool: Generate the installation package and set the Windows Client configuration during generation. Use Client installation file (.exe) to install the Client with default parameters. Windows Client Installation Package The installation package consists of 2 components: A signed agent.exe installation file. An agent.ini text configuration file that contains the Windows Client installation parameters defining the Server to which the Client will connect, and the Client configuration. The table below lists all the Windows Client installation parameters. If any parameter except RemoteHost is absent or not valid, its value will be set to default. NOTE: The Forced User Authentication parameter can be set only during Client editing. Parameter Description Default Value RemoteHost ColorDepth A name or IP address of the computer on which the Server is installed. NOTE: The Server IP address has to be static for Clients to connect to it successfully. Unique external IP addresses should be used for cloud-based Servers. A color scheme used for screenshots saving. 7 4 bits (Grayscale), 8 8 bits, bits. No 7(4 bits (Grayscale)) 101

102 Windows Clients EnableTimer Timer EnableActivity EnableWndNmChanges SmoothMode Screenshots will be created with a certain time interval. If the value is 1, the option is enabled, if the value is 0 disabled. A period of screenshot creation in seconds. This period can t be less than 30 seconds. This parameter is needed if the EnableTimer parameter is set. A screenshot creation when an active window is changed. If the value is 1, the option is enabled, if the value is 0 disabled. A screenshot creation when a window name is changed. If the value is 1, the option is enabled, if the value is 0 disabled. A screenshot creation on each event without timeout. If the value is 1, the option is enabled, if the value is 0 disabled. WARNING! This parameter affects CPU usage on the Client computer and database size. Disabled 30 Enabled Enabled Disabled DisplayClientIcon The Client tray icon displaying. If the value is 1, the Client tray icon is displayed, if the value is 0 hidden. Disabled EnableKBandMouse EnableProtectedMode EnableKeystrokes A screenshot creation on clicking and a key pressing. If the value is 1, the option is enabled, if the value is 0 disabled. The mode of Client work. If the value is 1, the protected mode is enabled, if the value is 0 disabled. Logging of a keystroke. If the value is 1, the option is enabled, if the value is 0 disabled. Enabled Disabled Enabled URLMonitoring Monitoring of URL addresses. If the value is 1, the option is enabled, if the value is 0 disabled. Enabled MonitorTopDomain Monitoring of top and second-level domain names. If the value is 1, the option is enabled, if the value is 0 disabled. NOTE: This parameter works only if URLMonitoring=1. Enabled 102

103 Windows Clients FilterState FilterAppName FilterAppTitle UserFilterState UserFilterNames MonLogging LogPath Application filtering during monitoring. If the value is disabled, the application filtering is disabled and all applications are monitored. If the value is include, the application filtering is enabled in the Include mode, and only applications listed in FilterAppName or FilterAppTitle are monitored. If the value is exclude, the application filtering is enabled in the Exclude mode, and only applications not listed in FilterAppName or FilterAppTitle are monitored. The list of application names separated with comma (e.g., word.exe, skype.exe). Names are combined with OR logic; the LIKE operator is applied to names (e.g., if word.exe is written then winword.exe will be monitored). The list of application titles separated with comma (e.g., Facebook, Google). Names are combined with OR logic; the LIKE operator is applied to titles (if Facebook is written, then Facebook-Messages will be monitored). User filtering during monitoring. If the value is disabled, activity of all users is monitored. If the value is include, the user filtering is enabled in the Include mode, and only activity of users listed in UserFilterNames is monitored. If the value is exclude, the application filtering is enabled in the Exclude mode, and only activity of users not listed in UserFilterNames is monitored. The list of user names separated with a semicolon (e.g., work\jane;work\john). Names are combined with OR logic. Using asterisk (*) as name/domain mask is allowed (e.g., *\administrator or *\admin*). Creation of monitoring logs on the Client computer. 0 - monitoring logs creation is disabled, 1 - monitoring text log will be created in the LogPath location. The path to the monitoring logs location. Using environment variables (%appdata%, Disabled Empty Empty Disabled Empty Disabled C:\ProgramDat a\ekran 103

104 Windows Clients %temp%, etc.) is allowed. System\MonLo gs EnableForcedAuth NotificationMessage Additional identification of users that log in to the Client computer with server operation system. If the value is 1, the option is enabled, if the value is 0 disabled. The message that is displayed on user login to the system. Disabled Disabled Generating Windows Client Installation Package To generate an installation package, do the following: 1. Log in to the Management Tool as a user with the Client installation and management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Install Clients. 4. On the Computers without Clients page, click Download installation file. 5. On the Installation File Download page, click Generate Client installation package (*.ini + *.exe). 6. On the Generate Installation Package page, define the name/ip of the Server to which the Clients will connect, and define the client configuration to be applied to the Client and then click Next. NOTE: The Server IP address has to be static for Clients to connect to it successfully. Unique external IP addresses should be used for cloud-based Servers. 7. The installation package is successfully created and downloaded to your computer. The download settings depend upon the settings of your browser. Installing Windows Clients Locally with Custom Monitoring Parameters To install the Windows Client locally using the installation package, do the following: 1. Copy the package (the agent.exe installation file and the agent.ini file) to the target computer. 2. Start the agent.exe installation file under the administrator account on the target computer. 3. After the package is deployed, the name of the required computer appears on the Client Management page in the Management Tool. 104

105 Windows Clients Downloading Windows Client Installation File (.exe) To download the file for Windows Client installation, do the following: 1. Log in to the Management Tool as a user with the Client installation and management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Install Clients. 4. On the Computers without Clients page, click Download installation file. 5. On the Installation File Download page, click Download default Client Installation (*.exe). 6. File downloading starts. The download settings depend upon the settings of your browser. Installing Windows Clients Locally without.ini File This type of installation allows you to install the Windows Clients with the default configuration. This way you will need only an agent.exe file for Client installation. The agent.ini file with the default parameters will be generated automatically. To install the Windows Client locally using the installation package on the target computer: 1. Copy the downloaded agent.exe file to the target computer and do one of the following: Start the agent.exe installation file under the administrator account on the target computer. Then in the opened window, enter the name or IP address of the computer on which the Server is installed and after that click Install. In the Command Prompt (cmd.exe) started under administrator, enter agent.exe /ServerName=<Server Name>. 2. After the package is deployed, the installed Client appears in the list on the Client Management page in the Management Tool. 105

106 Windows Clients Installation via Third Party Software If you want to install the Windows Client via a third-party tool (e.g., via System Center Configuration Manager, Active Directory, etc.), download the Client installation file and use the following command: agent.exe /ServerName=<Server Name>. The Client will be installed with a default configuration. Cloning a Virtual Machine with Installed Client Each Windows Client has its own unique ID, which it receives when it connects to the Server. When you prepare a virtual machine which is to be monitored, for cloning, you need to remove the Client ID to ensure the proper Client connection to Server. To remove the Client ID, do the following: 1. Make sure the Client is offline (does not have any connection with the Server). 2. Open the Windows Registry Editor. 3. In the Registry Editor window, select the following key HKEY_LOCAL_MACHINE\SOFTWARE\EkranSystem\Client. 4. Double-click the AgentGUID value, or select it and click Modify in the right-click menu. 5. Remove the ID from the Value Data box. 6. Click OK. NOTE: You will not be able to edit the registry values in the Protected Mode. Unassigning License on Virtual Machine Shutdown If Ekran Windows Client is used on virtual machines, in some cases the master image might be used multiple times. To prevent wasting Client licenses when this occurs, you can configure the Client license to be unassigned on the virtual machine shutdown. Before configuring a virtual machine image, you have to create a cmd file (for example, uninstall_client.cmd) containing the following command-line command: start /wait <path to EkranClient.exe> -uninstwl <uninstallation key> For example (default installation parameters used): start /wait C:\Progra~1\EkranS~1\EkranS~1\Client\EkranClient.exe -uninstwl allowed To configure the image of the virtual machine with the Client for the license to be unassigned on shutdown: 106

107 Windows Clients 1. Start your virtual machine image. 2. Configure the system and install the necessary software. 3. Install Ekran Client (via remote installation or locally) with the Protected Mode option disabled. 4. Open the Windows Registry Editor. 5. In the Registry Editor window, select the following key HKEY_LOCAL_MACHINE\SOFTWARE\EkranSystem\Client 6. Double-click the AgentGUID value, or select it and click Modify in the right-click menu. 7. Remove the ID from the Value Data box. 8. Click OK. 9. Copy uninstall_client.cmd to the target folder on your virtual machine. 10. Run the Command Prompt (cmd.exe) as administrator. 11. Enter the gpedit command. 12. In the Local Group Policy Editor window, select Computer Configuration -> Windows Settings -> Scripts (Startup/Shutdown) -> Shutdown 13. In the Shutdown Properties window, click Add and select the uninstall_client.cmd file. 14. Click OK. 15. Create the master snapshot (gold image). 16. From now on, whenever you start the virtual machine using this image, the Client is going to connect to the Server as a new Client and get a license assigned to it. Whenever the virtual machine is shutdown, the license is going to be unassigned from the Client. NOTE: If you need the license to be unassigned on Logoff, you have to edit the Logoff script in a similar way in the Local Group Policy Editor (User Configuration -> Windows Settings -> Scripts (Logon/Logoff) -> Logoff -> Properties). Updating Windows Clients The Client updating is performed automatically when a Windows Client connects to the Server of a newer version. When the Windows Client is updated, you will still be able to access its monitored data that was received before the update. NOTE: During the Windows Client updating, the Client status in the Management Tool is offline. In some cases, if you install a newer version of the Server, Windows Clients of very old versions will not be able to update. In this case you need to uninstall the old Client and install a new version of a Client manually. 107

108 Windows Clients Reconnecting Windows Clients to Another Server If you want to reconnect the Windows Clients to another Server, start the remote installation from that Server. The Clients will be reconnected. Please note that this way of reconnection can be used only for the Clients that work in the nonprotected mode. If your Clients work in the protected mode, first disable the protected mode and then reconnect the Clients. Uninstalling Windows Clients About Windows Clients can be uninstalled locally or remotely. It is possible to uninstall the Windows Client locally only with the help of the Uninstallation key. After remote uninstallation, the Client stops sending its data to the Server, but its data is not deleted from the Server and the Client is displayed in the Management Tool. After local uninstallation, the Client stops sending its data to the Server, but the Client is not marked as uninstalled on the Server. That is why the Client status in the Management Tool becomes offline after local uninstallation. To delete the Client from the Server (with all its captured data) and from the Management Tool, follow the steps described in the Deleting the Windows Client section. Client Uninstallation Key During the Server installation, it is possible to define the Client Uninstallation key. By default, this key is allowed. The Client Uninstallation key is used during the local Client uninstallation. The user is able to view or change the Client Uninstallation key in the Management Tool. If you change the Uninstallation key, the Windows Client will receive it after connection to the Server. If the Client has not connected to the Server yet, then its Uninstallation key is allowed. If the Client has not connected to the Server after the Uninstallation key has been changed, the Client has to be uninstalled with the help of an old Uninstallation key. To change the uninstallation key, do the following: 1. Log in to the Management Tool as a user with the Client uninstallation permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Edit Uninstallation Key. 108

109 Windows Clients 4. On the Custom Uninstall Key page, enter the new uninstallation key in the New Key field. 5. Re-enter the new uninstallation key in the Confirm Key field and then click Save. 6. The uninstallation key is changed. Uninstalling Windows Clients Remotely To uninstall a Windows Client, do the following: 1. Log in to the Management Tool as a user that has the Client uninstallation permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the Client you want to uninstall and click Edit Client. 4. On the Editing Client page on the Properties tab, click Uninstall Client. NOTE: This option is not displayed if the Client is already uninstalled or you do not have the Client uninstallation permission for it. 5. In the confirmation message, click Uninstall. 6. The Client is uninstalled. To uninstall several Windows Clients, do the following: 1. Log in to the Management Tool as a user with the Client uninstallation permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select Uninstall Clients. 4. On the Client Uninstallation page, click Add Clients to list. 5. The page with the Clients for which you have the Client uninstallation permission opens. 6. Select the Clients that you want to uninstall and click Next. To find a specific Client, enter its name or a part of its name in the Contains box and click Apply Filters. 7. Make sure you have added all necessary Clients to the uninstallation list and click Uninstall. 8. The selected Clients are uninstalled. Uninstalling Windows Clients Locally It is possible to uninstall the Windows Client locally only with the help of the Uninstallation key that is defined during the Server installation or in the Management Tool. To uninstall the Windows Client locally, do the following: 1. Run the Command Prompt (cmd.exe) as administrator. 109

110 Windows Clients 2. In the Command Prompt, go to the Client installation folder. By default, it is located here: C:\Program Files\Ekran System\Ekran System 3. Enter the following command: UninstallClient.exe /key=<uninstallation key>. 4. Press Enter. 5. The Client is successfully uninstalled. Viewing Windows Clients Windows Clients are displayed in groups on the Client Management page. If the user has an administrative Client installation and management permission, he/she will see all Clients. In other case, the user will see only those Clients for which he/she has at least one Client permission. The lists of Clients contain the following information: Client name Status Domain IPv4 IPv6 Description Please note, if there are several network cards on the Client computer, only those IPv4 and IPv6 addresses used by Windows Clients will be displayed in the Management Tool. You can filter Windows Clients in the following ways: To sort Clients by operating system, click the OS column header. To find Windows Clients only, select the Hide Linux Clients checkbox and click Apply Filters. To find Clients by their host name or description, enter the name/description or a part of it in the Contains box and click Apply Filters. To hide offline/online/uninstalled/licensed Clients, select the corresponding option in the Filtering pane and click Apply Filters. On the Client Management page you have the following options: Add Client Group, Install Clients, Manage Licenses, Edit Uninstallation Key, Uninstall Clients, Delete Clients, Edit client configuration and Edit Client Groups. The number of available options depends upon permissions. 110

111 Windows Clients Windows Client Description Client description is used as additional information about your Windows Clients, which makes it easier to find a specific Client. You can filter your Clients by their descriptions as well as by their names. Client description can be defined on the Editing Client page on the Properties tab. To edit the description for the Windows Client, enter it in the Description box and click Finish. Windows Client Configuration About Windows Client Configuration includes its monitoring parameters (screen capture creation, keystrokes logging, Client mode, etc.). The Client configuration can be defined in the.ini file, which is included to the installation package. You can set the Client configuration during remote installation and during Client editing. NOTE: The Forced User Authentication parameter can be set only during Client editing. Protected Mode Parameter The Windows Client can work in two modes: Non-protected mode: a regular mode without enhanced Client security. Protected mode: a mode with enhanced Client security: the user is not able to edit Client data (log files, generated screen captures), edit Client settings in the registry, edit/remove/modify/rename Client files (*.exe and *.dlls). The protected mode can be enabled when installing, updating, or editing the Client. If the protected mode is enabled during Client installation, this change will come into effect immediately. If the protected mode is enabled during Client editing, this change will come into effect after the computer is rebooted. NOTE: It is impossible to reconnect the Client working in protected mode to another Server. In such situation, you will have to uninstall the Client locally or change its mode to nonprotected. 111

112 Windows Clients Client Tray Icon Parameter The Client tray icon is displayed to notify the users that their actions are being monitored when they log into the Client computer and while they are working on it. This feature can be enabled during Clients installation and editing in the Management Tool. If the Display Client tray icon option is selected in the Management Tool, the licensed Client will display a tray notification to inform the logged-in users that they are being monitored by a Server. Screen Capture Creation Parameters Screen captures are the main result of the Windows Client monitoring activity. You can define the following parameters of Client screen captures: Screen capture color settings: By default, screen captures are grayscale with 4 bit color depth. This guarantees the smallest database size with a normal screen capture quality. You can also set color depth to 8 bits or 24 bits. Screen capture creation frequency: These options allow you to define how often the screen captures on the Client computer will be created. Screen capture creation can be initiated by one of the following triggers: o Time interval: Screen captures are created with a certain time interval, irrespective to whether something changes on the screen or not. The minimal time interval is 30 seconds. o Active window change: Screen captures are created on the change of the active window. For example, a new window opens (program starts), a new tab in the browser opens, any secondary window opens, etc. (influences the keystroke logging as well). o Active window title change: Screen captures are created on the change of the name of the active window (influences the keystroke logging as well). o Clicking or key pressing: Screen captures are created on each mouse click or keyboard key pressing. Please note, the screen captures in this mode are sent not oftener than once in 3 seconds to avoid affecting the performance of the Client computer and database size increasing. o Each event without timeout: Screen captures are created on each mouse click or keyboard key pressing without using data sending time out. WARNING! The Capture screen on each event without timeout option affects CPU usage on the Client computer and database size. It is not recommended to use this option for a great number of Clients and for a long period of time. Keystroke Logging Parameters If keystroke logging is enabled, the Windows Client logs keystrokes along with the screen capture creation. 112

113 Windows Clients The Windows Client logs the following types of keystrokes: Character keys: Keys that contain alphabet symbols (upper or lower case), numerals (0-9), all kinds of punctuation symbols, and space. Modifiers: This group of keys includes Control key, Shift key, Alt key, and Windows key. Navigation and typing modes: The arrow keys, Home/End, Page Up/Page Down, Tab, Insert, Delete/Backspace, Enter, and Lock keys (Num Lock, Scroll Lock, and Caps Lock). System commands: Print Screen, Menu, Escape, and Break/Pause key. Function keys: Keys that perform some functions, such as printing or saving files. Usually, they are labeled as F1- F12 and are located along the top of the keyboard. Monitoring Log Parameter Monitoring logs are text files created on the Client computer. Monitoring logs can be of two types: User actions log: The log name is Client_<yyyy_mm_dd>.log. The log includes information on all monitored activities on the Client computer. The following information is written to this log: Activity time, Session ID, Client computer name (Host name), User name, Activity title, and Application name. User logging in log: The log name is Login_<yyyy_mm_dd>.log. The log includes information on all user logs in on the Client computer. The following information is written to this log: Login time, Client computer name (Host name), and User name. NOTE: The monitoring log feature can be used for the integration with SIEM systems (e.g., ArcSight). Both logs are created in the user defined location. You can use the environment variables (%appdata%, %temp%, etc.) when defining the path. If this location is not accessible or write-protected, logs are saved to <systemdisk>\programdata\ekran System\MonLogs. If you change the log files location via the Management Tool, the new log files will be created in the defined location and the old log files (if any) will remain in the previous location. NOTE: Please do not confuse monitoring logs with Client activity logs (service logs for internal use) stored in <client installation folder>\activitylogs. 113

114 Windows Clients Parameters examples:.ini File Parameters Parameters Set in Management Tool Do not create monitoring logs [ActivityLogsParameters] MonLogging=0 LogPath= On the Monitoring options tab, make sure that the Enable creating log files of the monitored events check box is not selected. Create monitoring logs in the default location %ProgramData%\EKRAN\MonLogs [ActivityLogsParameters] MonLogging=1 LogPath= On the Monitoring options tab, make sure that the Enable creating log files of the monitored events check box is selected. Create monitoring logs in the C:\1\Logs folder [ActivityLogsParameters] MonLogging=1 LogPath=C:\1\Logs On the Monitoring options tab, do the following: 1. Select the Enable creating log files of the monitored events check box. 2. In the Log files creation field, type C:\1\Logs. Create monitoring logs in the <current user profile>\appdata\ekran_logs [ActivityLogsParameters] MonLogging=1 LogPath=%AppData%\EKRAN_Logs On the Monitoring options tab, do the following: 1. Select the Enable creating log files of the monitored events check box. 2. In the Log files creation field, type =%AppData%\EKRAN_Logs. URL Monitoring Parameters The URL monitoring option enables recording the text entered in the browser address line at the moment of screen capture creation and allows the investigator to receive information about websites visited by the user of the Client computer. This feature also allows you to set an alert to send notifications each time when the user opens the forbidden URL. The monitored URL addresses are displayed in the Management Tool on the Session Viewer page in the URL column and in the Details pane. There are several restrictions for the URL monitoring option in the current version of the program: 114

115 Windows Clients Only URLs from the standard browsers (Firefox, Chrome, Opera, and Internet Explorer) are monitored. URLs from Metro versions of browsers Chrome/Internet Explorer are not monitored. URLs entered in web anonymizers are not monitored. Please note that proxy server anonymizers are supported. If there is no address line in the browser (e.g., due to user s settings), URLs are not monitored. Unicode symbols in domain names (e.g., Russian) are not monitored. If the Enable URL monitoring option is selected in the Management Tool, you can also select the Monitor top and second-level domain names only option. In this case only the main part of the URL (e.g., example.com) will be monitored. Parameters examples:.ini File Parameters [AgentParameters] URLMonitoring=0 MonitorTopDomain=0 [AgentParameters] URLMonitoring=1 MonitorTopDomain=0 [AgentParameters] URLMonitoring=1 MonitorTopDomain=1 Parameters Set in Management Tool On the Editing Client page, on the Monitoring Options tab, clear the Enable URL monitoring check box. On the Editing Client page, on the Monitoring Options tab, select the Enable URL monitoring check box. On the Editing Client page, on the Monitoring Options tab, select the Enable URL monitoring check box, then select the Monitor top and second-level domain names only check box. Example of monitored data (activity title) John Doe - Google Chrome John Doe - Google Chrome (URL: https://facebook.com/ John.doe) John Doe - Google Chrome (URL: https://facebook.com) 115

116 Windows Clients Application Filtering Parameters Application filtering allows you to reduce the amount of information received from the Windows Client by defining applications whose data will be skipped during the monitoring. The Application filtering can be in one of three states: Disabled: User activity in all applications is monitored (screen captures are created and keystrokes are logged). Include: User activity in predefined applications is monitored. Information on all other activity is skipped. This mode allows you to enable monitoring only of the important applications. Exclude: User activity in all applications except predefined ones is monitored. This mode allows you to skip information about user activity in non-suspicious applications (for example, Word). The applications are identified by name or window title. Both parameters are combined with OR logic, i.e., if activity meets at least one of conditions, it s recorded in the Include mode or skipped in the Exclude mode. Parameters examples:.ini File Parameters Parameters Set in Management Tool Monitor all data without applying filters [FilterParameters] FilterState=disable FilterAppTitle= FilterAppName= On the Application Filtering tab, in the Filter State box, select Disabled. Monitor only data from all applications containing Facebook or Gmail in the title [FilterParameters] On the Application Filtering tab, do the 116

117 Windows Clients FilterState=include FilterAppTitle=Facebook,Gmail FilterAppName= following: In the Filter State box, select Monitor only activity matching defined parameters. In the Active window title contains box, type Facebook, Gmail. Monitor only data from all applications containing Firefox or Internet in the application names [FilterParameters] FilterState=include FilterAppTitle= FilterAppName=Firefox,Internet On the Application Filtering tab, do the following: 1. In the Filter State box, select Monitor only activity matching defined parameters. 2. In the Application name contains box, type Firefox, Internet. Monitor only data from applications containing Firefox, Chrome or Internet in the application names (any title) and applications with the Facebook word in the title (any name) [FilterParameters] FilterState=include FilterAppTitle=Facebook FilterAppName=Firefox,Chrome,Internet On the Application Filtering tab, do the following: 1. In the Filter State box, select Monitor only activity matching defined parameters. 2. In the Active window title contains box, type Facebook. 3. In the Application name contains box, type Firefox, Chrome, Internet. Monitor all data except data from applications containing words Work or Doc in the title [FilterParameters] FilterState=exclude FilterAppTitle=work,doc FilterAppName= On the Application Filtering tab, do the following: 1. In the Filter State box, select Monitor all activity except. 2. In the Active window title contains box, type Work, doc. Monitor all data except data from applications containing words Word or Excel in the application names [FilterParameters] FilterState=exclude FilterAppTitle= On the Application Filtering tab, do the following: 1. In the Filter State box, select Monitor all activity except. 117

118 Windows Clients FilterAppName=word,excel 2. In the Application name contains box, type Word, Excel. Monitor all data except data from applications containing the Word word in the application name or the doc word in the title [FilterParameters] FilterState=exclude FilterAppTitle=doc FilterAppName=word On the Application Filtering tab, do the following: 1. In the Filter State box, select Monitor all activity except. 2. In the Active window title contains box, type doc. 3. In the Application name contains box, type Word. User Filtering Parameters User filtering allows you to reduce the amount of information received from the Windows Client by defining computer users whose data will be skipped during the monitoring. User filtering affects both primary and secondary users. The User filtering can be in one of three states: Disabled: Activity of all users is monitored. Include: Activity of predefined users is monitored. Information on the activity of all other users is skipped. Exclude: Activity of all users except predefined ones is monitored. This mode allows you to skip information about the activity of particular users (for example, administrator). 118

119 Windows Clients You can define user names for filtering entering them manually or by clicking Add Users and selecting users from the list. When you enter user names manually, they must be entered as <domain name>\<user name> and separated with comma (,), semicolon (;), paragraph, or space. You can also use asterisk (*) as name/domain mask (e.g., *\administrator or *\admin*). When you click Add Users, the Adding Users page opens. Please note, only those users whose activities have already been monitored are listed. Select the user names to be added and click Add selected. NOTE: If you select a user with the Forced User Authentication on the Adding Users page e.g., WORK\janet (jan), you need to change parentheses in the User names box to semicolon, i.e., WORK\janet;jan. Parameters examples:.ini File Parameters Parameters Set in Management Tool Monitor all user activity without applying filters [FilterParameters] UserFilterState=disable UserFilterNames= On the User Filtering tab, in the Filter State box, select Disabled. Monitor only the activity of the janet user or joe user in the work domain 119

120 Windows Clients [FilterParameters] UserFilterState=include UserFilterNames=WORK\janet;WORK\joe On the User Filtering tab, do the following: In the Filter State box, select Monitor only activity of selected users. In the User names box, enter work\janet,work\joe manually or select the users from the list. Monitor the activity of all users except the users with administrator login (both local and domain) [FilterParameters] UserFilterState=exclude UserFilterNames=*\administrator On the User Filtering tab, do the following: In the Filter State box, select Monitor activity of all users except. In the User names box, enter *\administrator, using asterisk (*) as a name/domain mask Monitor only the activity of the janet Ekran system user name used for secondary authentication [FilterParameters] UserFilterState=include UserFilterNames=WORK\janet;janet On the User Filtering tab, do the following: In the Filter State box, select Monitor only activity of selected users. In the User names box, enter work\janet;janet manually or select the user from the list. Forced User Authentication Parameter Forced User Authentication provides a method for an additional identification of users that log in to the Client computer. This feature can be enabled only for Clients installed on computers with server OS and it cannot be set during Client installation. If the Enable secondary user authentication on log-in option is selected in the Management Tool, the Client will display the additional login window on the user login to Windows. NOTE: Forced User Authentication can only be set during Client editing in the Management Tool. 120

121 Windows Clients Additional Message on User Login Parameter Additional message on user login allows you to inform the user that his/her session is monitored and also inform him/her about the important issues related to the corporate policy or the country laws. If the Enable displaying additional message option is selected in the Management Tool, the Client will display the additional notification message on the user login to Windows. After the user confirms acknowledging the message, he/she will be allowed to log in and continue working. For more information, see the Additional message on user login chapter. Editing Windows Client Configuration You can edit the Client configuration for online and offline Clients. The configuration for online Clients will be applied immediately. The configuration for offline Clients will be applied as soon as the Client is online. To edit the Windows Client configuration, do the following: 1. Log in to the Management Tool as a user with the Client configuration management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the Windows Client for which you want to edit the configuration, and click Edit Client. To find a specific Client, enter its name in the Contains box and click Apply Filters. NOTE: If you do not have the Client configuration management permission for this Client, the configuration options will be disabled. 4. On the Editing Client page, on the Properties tab, define the description for the Client (optionally). Then select the Enable protected mode check box if you want to enable protected mode and the Display Client tray icon check box if you want to display the Client tray icon to the user. NOTE: The Client mode will be changed after reboot of the Client computer. 121

122 Windows Clients 5. On the Screen Capture Options tab, define the required screen capture quality and screen captures creation frequency. WARNING! The Capture screen on each event without timeout option affects CPU usage on the Client computer and database size. It is not recommended to use this option for a great number of Clients and for a long period of time. 6. On the Monitoring Options tab, do the following: Select the Enable keystroke logging check box to enable the keystroke logging. Select the Enable creating log files of the monitored events check box to enable creation of monitoring logs on the Client computer and define log files location. Select the Enable URL monitoring check box to receive information about websites visited by the user of the Client computer. Select the Monitor top and second-level domain names only check box to monitor only the main part of the URL (e.g., example.com). 122

123 Windows Clients 7. On the Application Filtering tab, define the application filtering parameters for the Client. 8. On the User Filtering tab, define the user filtering parameters for the Client. 123

124 Windows Clients 9. On the Authentication options tab, do the following: For Clients installed on the computer with server operation system, select the Enable secondary user authentication on log-in check box if you want to enable the additional authorization for users that log in to the Client computer. Select the Enable displaying additional message check box if you want to enable additional message on user login, and then enter the message to be displayed to a user. 10. After defining the configuration, click Next to proceed to defining Client Groups to which the Client belongs and permissions on working with it or click Finish to except changes. 11. A new configuration will be immediately applied to the Client. Viewing Windows Client Configuration The Windows Client configuration can be viewed by a user that has an administrative Client installation and management permission or any Client permission. To view the Windows Client configuration, do the following: 1. Log in to the Management Tool. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the required Client and click Edit Client. 4. In the opened window you will see the tabs with the corresponding configuration parameters. Defining Client Configuration for All Windows Clients in a Group Client configuration can be changed for all Windows Clients in the group simultaneously. These settings will change the current settings of Clients but will not be applied to any new Clients added to the corresponding group. NOTE: If the Client group contains both Windows and Linux Clients, only Windows Clients configuration will be changed. To change Client configuration for All Clients in a Group, do the following: 124

125 Windows Clients 1. Log in to the Management Tool as a user with the Client configuration management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the required Client Group and click Edit Client Group. 4. On the Group Properties tab, click Configure Clients in group. 5. Edit configuration to be applied to all Clients in the group on the corresponding tabs in the same way as when editing configuration for one Client. 6. When all configuration parameters are defined, click Finish. 7. A new configuration will be immediately applied to all Clients in the group. Forced User Authentication on Clients About If the Client is installed on the computer with a server operating system (Windows Server 2012, Windows Server 2008, or Windows Server 2003) and several users may use the same account to log in to this computer, it is important to identify the person using the account. The identification can be performed by means of Forced User Authentication, which requires the user to enter additional credentials in the pop-up dialog after logging in. The secondary login will then be displayed in the Monitored Sessions list in brackets next to the primary login under which the user is logged in to Windows. The forced user authentication feature works only if there is a connection between the Client computer and the Server computer. If the connection with the Server computer is lost (the Server is unavailable), the pop-up dialog for entering secondary credentials will not be displayed. NOTE: In some situations (e.g., after the forced restart) the Client service does not start during one minute after the computer turning on. In these situations forced authentication will not work. Enabling Forced User Authentication on Client The Forced User Authentication parameter can be set only during Client editing and is available only for the Clients installed on the computers with server operating system. To enable Forced User Authentication on the Client, do the following: 1. Log in to the Management Tool as a user with the Client configuration management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the Client for which you want to enable Forced User Authentication, and click Edit Client. To find a specific Client, enter its name in the Contains box and click Apply Filters. 125

126 Windows Clients 4. On the Editing Client page, on the Authentication options tab, select the Enable secondary user authentication on log-in check box. 5. Click Finish. 6. If the Client is installed on Windows Server 2003, the computer must be restarted after enabling or disabling the forced authentication mode. On Windows Server 2012 and Windows Server 2008, the forced authentication mode is enabled immediately. Granting the User Permission to Log In To grant a user a permission to log in to the Client computer with a server operating system and enabled forced user authentication, do the following: 1. Log in to the Management Tool as a user with the administrative User management permission. 2. Add the Active Directory or internal user which will log in to the Client computer, to the system. 3. Click the User Management navigation link on the left. 4. On the Users page, click Edit User for the required user. To find a specific user, enter its name in the Contains box and click Apply Filters. 5. Open the Client Permissions tab and click Edit Permissions for the required Client. To find a specific Client, enter its name in the Contains box and click Apply Filters. 6. In the opened Client Permissions window, select the Login to Client computer check box and then click Save. 126

127 Windows Clients Logging In If the Enable secondary user authentication on log-in option is selected for the Client in the Management Tool, only users with the Login to Client computer permission will be able to work on the Client computer. The process of logging in to the Client computer with enabled forced user authentication is performed as follows: 1. The user logs in to Windows in a common way (locally or remotely). 2. On the user login to Windows, the Client displays the secondary authentication window requesting a user to enter his/her credentials. 3. The user enters the credentials of the user created in the Management Tool that has a Login to Client computer permission. 4. These credentials are sent to the Server and the Server returns the response on whether the access to this computer is allowed. If the user has the required permission and his/her entered credentials are correct, the user is allowed to continue working with the System. In other case, the user will receive a corresponding message. 5. As soon as the user starts working with the system, the Client will start writing his/her activity and the user s name will be displayed in the Management Tool on the Monitored Sessions page in the User name column in brackets: <logged in Windows user> (<forced authentication user>). Informing about Monitoring About If you want the user to be informed that his/her session will be monitored, you can enable displaying the Client tray icon option in Management Tool. You can also enable the additional message option to set the message to be displayed to a user, who must confirm acknowledging the message in order to log in to the computer. The additional message is displayed when: Windows is started, restarted, or shut down. The user gets logged out or switched. The user logs in via the remote connection. If both forced user authentication and additional message features are enabled for the Windows Client, the additional message will be displayed after the user enters his/her additional credentials in the secondary authentication window. The Client tray icon is always displayed to the user. The tray notification is displayed when: The user logs in. The user clicks on the icon. NOTE: The additional message and Client tray icon are not displayed for unlicensed Windows Clients. 127

128 Windows Clients Enabling Displaying Additional Message The additional message displaying can be enabled when editing Client/Client Group configuration and defining the Client settings during the remote installation or Client installation package generation for local installation. By default, the additional message text is: According to company policy you must agree to the terms in order to continue working on this computer. You can enter the custom message to be displayed to users. NOTE: The message can be up to symbols. To enable displaying the additional message when installing the Windows Client, select the Enable displaying additional message check box on the Client configuration page (if the Client is to be installed remotely) or on the Generate Installation Package page (if the Client is to be installed via the installation package). When the Client is installed, the user will receive the default notification message on his/her login until the text of the message is changed when editing the Client. To enable displaying the additional message when editing the Windows Client, do the following: 1. Log in to the Management Tool as a user with the Client configuration management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the Client for which you want to edit the configuration, and click Edit Client. To find a specific Client, enter its name in the Contains box and click Apply Filters. 4. On the Authentication options tab, select the Enable displaying additional message check box, and then optionally enter the message to be displayed to a user. 5. Click Finish. Enabling Displaying Client Tray Icon The Client tray icon displaying can be enabled when editing Client/Client Group configuration and defining the Client settings during the remote installation or Client installation package generation for local installation. When the option is enabled, the Client icon is displayed in the notification area of the Client computer. When the user clicks the icon, the notification displayed is the following: Your actions are being monitored by <Server name> To enable displaying the Client tray icon when installing the Windows Client, select the Display Client tray icon option on the Client configuration page (if the Client is to be installed remotely) or on the Generate Installation Package page (if the Client is to be installed via the installation package). 128

129 Windows Clients When the Client is installed, the notification message will be displayed to the user after his/her login. To enable displaying the Client tray icon when editing the Windows Client, do the following: 1. Log in to the Management Tool as a user with the Client configuration management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, select the Client for which you want to edit the configuration, and click Edit Client. To find a specific Client, enter its name in the Contains box and click Apply Filters. 4. On the Properties tab, select the Display Client tray icon check box. 5. Click Finish. The Client tray icon will be displayed on the next user login. Logging In The process of logging in to the Windows Client computer with enabled additional message option is performed as follows: 1. The user logs in to Windows in a common way (locally or remotely). 2. On the user login to Windows, the notification message is displayed. 3. If the user clicks I Agree, he/she is allowed to continue working with the system. If the user clicks Cancel, he/she returns to the Windows login screen. NOTE: If the user logs in to the computer with Server operation system on which forced user authentication is enabled, he/she enters credentials in the additional authentication form and then the additional message is displayed. 4. If the Client tray icon displaying option is enabled for the Client, the tray notification is displayed to the user. 129

130 Linux Clients Linux Clients About The Linux Client is a program that can be installed on the target computers to monitor the activity of their users in the terminal. The monitored data is sent by the Linux Client to the Server and can be viewed via the Session Viewer in the Management Tool. Monitoring via Linux Clients The Linux Client monitors the following actions: 1. User actions (input commands and responses from the terminal) 2. System calls in: SSH (local and remote) Telnet (local and remote) Local terminal sessions A Client with a Linux license can monitor multiple sessions simultaneously, both remote and local. A new monitoring session is created each time the terminal is opened. There is no time limitation for a Linux Client session. The session status becomes Finished whenever the terminal is closed or the Linux Client is disconnected from the Server. Whenever the Linux Client reconnects to the Server, the session status changes from Finished back to Live. Installing Linux Client About You can install the Linux Clients locally from the command line using the linux_agent_.tar.gz package, respectively: linux_agent_x64.tar.gz for the 64-bit system linux_agent_x86.tar.gz for the 32-bit system Downloading Linux Client Installation File To download the file for Linux Client installation, do the following: 1. Log in to the Management Tool as a user with the Client installation and management permission. 2. Click the Client Management navigation link on the left. 130

131 Linux Clients 3. On the Clients page, click Install Clients. 4. On the Computers without Clients page, click Download installation file. 5. On the Installation File Download page, click Download Linux x86 Client Installation (.tar.gz) or Download Linux x64 Client Installation (.tar.gz). 6. File downloading starts. The download settings depend upon the settings of your browser. Installing Linux Clients This type of installation allows you to install the Linux Clients locally from the command line using the downloaded linux_agent_.tar.gz package. To install the Linux Client on the target computer with a Linux operating system from the command line: 1. Copy the installation package to any folder. Make sure you use the correct installation package (x64 or x86). 2. Run the command-line terminal. 3. Using the terminal, go to the folder with the installation package by entering the following command: $ cd path/to/folder 4. Unpack the installation package using the following command: $ tar xvfz <installation package name> 131

132 Linux Clients 5. Go to the unpacked EkranClient folder using the following command: $ cd EkranClient. 6. The EkranClient folder contains the install.sh script used to install the Client. 7. Run the Linux Client installation script specifying the Server name or Server IP address and the port used for connection to the Server (9447 is recommended): $ sudo./install.sh <server_name/ip> <Agent_port>. 8. After the Client is installed, it starts monitoring the new terminal sessions. If you want to monitor the older terminal sessions, restart them. 9. The installed Linux Client appears in the list on the Client Management page in the Management Tool. Uninstalling Linux Clients To uninstall the Linux Client from the command line, do the following: 1. Run the command line terminal. 2. Navigate to the folder with the Linux Client by entering the command: $ cd /opt/.ekran 3. The.Ekran folder contains the uninstall.sh script used to uninstall the Client. 4. Run the uninstallation script by entering the following command: $ sudo./uninstall.sh and press Enter. 5. Enter the password of the superuser. 6. Linux Client is successfully uninstalled. Viewing Linux Clients The Linux Clients are displayed in the Management Tool in the Clients list along with the Windows Clients. If the user has an administrative Client installation and management permission, he/she will see all Clients. In other case, the user will see only those Clients for which he/she has at least one Client permission. The lists of Clients contain the following information: Client name Status IPv4 132

133 Linux Clients IPv6 Description The Domain column is empty for Linux Clients. Please note, if there are several network cards on the Client computer, only those IPv4 and IPv6 addresses used by Linux Clients will be displayed in the Management Tool. You can filter Linux Clients in the following ways: To sort Clients by operating system, click the column header. To find Linux Clients only, select the Hide Windows Clients checkbox and click Apply Filters. To find Clients by their host name or description, enter the name/description or a part of it in the Contains box and click Apply Filters. To hide offline/online/uninstalled/licensed Clients, select the corresponding option in the Filtering pane and click Apply Filters. Linux Client Description Client description is used as additional information about your Linux Clients, which makes it easier to find a specific Client. You can filter your Clients by their descriptions as well as by their names. Client description can be defined on the Editing Client page on the Properties tab. Only users with the Client configuration management permission can edit the Linux Client description. To edit the description for the Linux Client, enter it in the Description box and click Finish. 133

134 Client Group Management Client Group Management About Client Groups Client Groups allow you to grant access to several Clients at the same time to your users without the necessity to grant them access to all the Clients (both Windows and Linux). By default, there is one Client Group in the system, which contains all installed Clients. You cannot remove Clients from this group. NOTE: One Client can belong to several groups. Adding Client Groups To add a new Client Group, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Add Client Group. 4. On the Group Properties tab, define the name for the Client Group and optionally define its description. Click Next. NOTE: The maximum length of the Client Group name and description is 200 characters. 5. On the Client Management tab, select the Clients that will belong to the Client Group and then click Next. To find a specific Client, enter its name in the Contains box and click Apply Filters. 6. On the Permissions tab, select users/user groups which will have access to the Client Group and define their permissions: To find a specific user/user group, enter its name in the Contains box and click Apply Filters. To define user/user group permissions, click Define Permissions for the required users/user groups and select the check boxes near the corresponding permissions in the opened Client Permissions window. After you have defined all permissions, click Save. NOTE: Permissions inherited by the user from user groups to which he/she belongs are displayed as disabled check boxes with a user group name near them. 7. When permissions for all users are defined, click Finish on the Permissions tab. 8. The Client Group is created. 134

135 Client Group Management Editing Client Groups To edit an existing Client Group, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Edit Client Group for the required Client group. 4. Edit Client Group properties and permissions on the corresponding tabs in the same way as when adding a new Client group. NOTE: Click Next or Finish to save the changes on each tab. 5. The Client Group is edited. Deleting Client Groups If you delete a Client group, the Clients belonging to it will not be deleted, but the permissions of users defined for the deleted Client Group will change. The All Clients group cannot be deleted. To delete a Client Group, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Client Management navigation link on the left. 3. On the Clients page, click Edit Client Group for the required Client group. 4. On the Group Properties tab, click Delete Client Group. 5. In the confirmation message, click Delete. 6. The Client Group is deleted. 135

136 Alerts Alerts About Alerts are instances that notify the investigator of a specific activity (potentially harmful/forbidden actions) on the target computers on which Clients are installed and allow the investigator to respond to such activity quickly without performing searches. The notifications can be received via or in the Tray Notifications application. Besides, monitored activity associated with alert events is marked as alert in the Session Viewer. Alert system can be used for two purposes: Immediate response: This allows the investigator to get immediate information about the forbidden action and respond to it quickly (almost at once). Delayed response: This allows the investigator to get information on a batch of forbidden actions on multiple Сlients, analyze them, and then respond. Viewing Alerts The alerts are displayed on the Alert Management page in the Management Tool. The list of alerts contains the following information: Name Description Clients/Client Groups to which the alert is assigned Alert State: Indicates if the alert is enabled. Notification Type: Indicates how the investigators are notified about alert events (by s or via Tray Notifications application). Recipient: The address of the investigator who will be notified about alert events. To find a required alert, you can use a filtering option on the top of the page. On the Alert Management page, you can add new alerts, edit existing alerts (including deleting), and define Global Alert Settings. 136

137 Alerts Alerts Management Adding Alerts To add an alert, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Alert Management navigation link on the left and click Add Alert. 3. On the Add Alert page, on the Alert Properties tab, enter a unique name for the created alert and then optionally enter its description and select the Enabled check box. Click Next. 4. On the Alert Rules tab, define the rules to be applied and then click Next: Select the Parameter of the rule. Select the Comparison operator. Enter the Value to which Parameter will be compared. Click Add to create one more rule. To delete a rule, clear its Value box. 137

138 Alerts 5. On the Assigned Clients tab, select the Clients/Client Groups to which the alert will be assigned and click Next. To find specific Clients/Client Groups, enter their names in the Contains box and click Apply Filters. 6. On the Notification Options tab, select how you would like to receive the alert notifications: In the s field, enter the address to which the notifications will be sent. You can enter several addresses, separating them with semicolon. NOTE: To receive notifications correctly, make sure that Sending Settings contain correct parameters for sending. Select the Show warnings in Tray Notifications application check box to activate the tray notifications. The alert notifications will then pop up from the tray. 138

139 Alerts 7. Click Finish to save the created alert. 8. The alert is added. Rules Alert rules allow you to determine what events on the investigated computer will be considered an alert. Each alert has to have at least one rule. Each rule consists of the Parameter, Comparison operator, and Value, to which the Parameter will be compared. The following parameters are available for rules: Parameter Description Example Parameters applied to both Windows and Linux Clients Username The name of the user whose work is to be monitored. Set this parameter type for alert to be activated whenever the specified user uses the computer on which the Client is installed. If forced user authentication is enabled and the secondary user login matches the user name alert parameter, the Client marks corresponding events as an alert. For example: The alert parameter is Login LIKE John. The user logs in to Windows as Guest and then enters John as the secondary login. Screen captures from this user (Guest (John)) are marked as alert. John 139

140 Alerts Parameters applied to Windows Clients Application Title/URL The name of the started application on the investigated computer. Set this parameter type for alert to be activated whenever the specified value is identified as the name of a launched application. The name that appears in the title of a window. Set this parameter type for alert to be activated whenever the specified value is identified in any title on the screen. If the URL monitoring option is enabled for the Client, the Title/URL parameter will be applied not only to window titles, but also to URL addresses. skype.exe My document or facebook.com Parameters applied to Linux Clients Command Parameter The command entered in the Linux terminal. Set this parameter type for alerts to be activated whenever the specified command is entered. The parameter of the entered Linux command. Set this parameters type for alerts to be activated when the user enters the command with specified parameters. sudo ImportantDocu ment Comparison operators: Equal to: The defined value fully corresponds to the found result (e.g., John will find John, but will not find Johny) Like: The found result includes the defined value (e.g., John will find Johny, Johnatan, but will not find Johan) Rules defined for Windows and Linux parameters do not influence one another. Thus you can have rules for Windows and Linux clients defined in one alert and the alert will work correctly. For example: Rule 1. Command is su. Rule 2. URL is facebook.com. The alert will be triggered by user entering the su command in the Linux terminal or visiting the facebook.com site from the computer with Windows operating system. When several rules are defined for the same parameter within one alert, the alert will work if the conditions of at least one rule are met. 140

141 Alerts For example: Rule 1. Application name is skype.exe Rule 2. Application name is winword.exe The alert will be triggered by user launching either Skype or Word. When the rules are defined for the different parameters within one alert, the alert will work if the conditions of all the rules are met. For example: Rule 1. Application name is skype.exe Rule 2. User name is Nancy The alert will be triggered by launching Skype by the user Nancy. When you have multiple rules defined for one parameter and one rule defined for the other parameter, the alert will work if conditions of any rule from the first group and the conditions of the rule defined for a different parameter are met. For example: Rule 1. Application name is skype.exe Rule 2. Application name is winword.exe Rule 3. User name is Nancy The alert will by triggered by user Nancy launching Skype or Word. Rule Examples 1. To set up the alert notification about any user opening the facebook.com site on the investigated computer, select the Title/URL parameter and, in the Value field, enter facebook.com. NOTE: URL monitoring must be enabled. 141

142 Alerts 2. To set up the alert notification about a specific user (e.g., Stefan) opening Facebook on the investigated computer, enter the following parameters: If you enter more than one name, the alert notification will then appear if any of them (Stefan or Rick) opens Facebook. 142

143 Alerts 3. To set up the alert notification about any user launching skype.exe application on the investigated computer, enter the following parameters: 4. To set up the alert notification about a specific user (e.g., Stefan) opening facebook.com in Chrome, enter the following parameters: 143

144 Alerts 5. To set up the alert notification about entering any command with sudo or a command su, enter the following parameters: Enabling/Disabling Alerts If you do not need to receive notifications on a specific alert which you do not want to delete, you can disable it in the Management Tool by clearing the Enabled check box on the Alert Properties tab of the Edit alert page. This option can be enabled again later, by selecting the Enabled check box on the same page. 144

145 Alerts Editing Alerts To edit an alert, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Alert Management navigation link on the left. 3. Click Edit alert for the required alert. 4. Edit alert properties and rules on the corresponding tabs in the same way as when adding a new alert. NOTE: Click Next or Finish to save the changes on each tab. 5. The alert is edited. Assigning Alerts to Clients To assign an alert to a specific Client, do the following: 1. Log in to the Management Tool as a user with an administrative Client installation and management permission. 2. Click the Alert Management navigation link on the left. 3. Click Edit alert for the required alert. 4. On the Assigned Clients tab, select the Client to which the alert will be assigned and click Next. To find specific Client, enter its name in the Contains box and click Apply Filters. 5. Click Finish to save the changes. 6. The alert is assigned to the selected Client. Deleting Alerts To delete an alert, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Alert Management navigation link on the left. 3. Click Edit Alert for the required alert. 4. On the Alert Properties tab, click Delete Alert. 5. In the confirmation message, click Delete. 6. The alert is deleted. 145

146 Alerts Defining Global Alert Settings Global Alert Settings allow you to define notification settings for all alerts. Their editing is available for users with the administrative Client installation and management permission. These settings are applied to all alerts. To define Global Alert Settings, click Global Alert Settings on the Alert Management page. Frequency Settings The Frequency settings group allows you to define how frequently the alert notifications will appear in the Tray Notifications application and be sent via . Minimal interval between notifications sent for the same alert event. This option defines how frequently the notifications about the same alert event will appear. For example, if this parameter is set to 10 minutes and a user has started Skype and works in it, the investigator will receive one notification every 10 minutes instead of receiving 10 notifications every minute or even more. Define how often the notification will be sent: - Send notifications on every alert event option allows you to notify the investigator on every alert event. - Send batch notification every (min) option allows you to notify the investigator about all alert events that occurred during defined time interval. Time counting starts when the Server starts if this option is selected. Notifications are then sent with the defined frequency. Player Link Settings This option allows you to define the Management Tool domain name that will be used in the link to the Session Viewer in alert notifications in Tray Notifications application journal and s. The domain name must be entered in the following format: https://<management Tool computer name or IP>/EkranSystem. Receiving Information on Alert Events You can receive information on alert events in three ways: In the Session Viewer, the alert events are marked with a special icon. If notifications are enabled in the Alert Parameters, the information on alert events will be sent to defined recipients. To receive notifications via , define Sending Settings. Each contains metadata of the alert event (user name, Client name, time, application name, and activity title) and the link for viewing this alert in the Session Viewer. 146

147 Alerts If the tray notifications are enabled in the Alert Parameters, the information on alert events will be sent via Tray Notifications component. To receive alert notifications in the Tray Notifications, do the following: 1. Install the Tray Notifications on the computer where alert notifications are to be received. 2. Log in to the Tray Notifications as a user of the Ekran System. 3. Start receiving alert notifications in the Windows Tray. 4. Use the Tray Notifications journal to view the history of received tray notifications and get more information on the alert event by opening the session in the Session Viewer. See the Tray Notifications application help file for more information. 147

148 Advanced Reports Advanced Reports About The user activity can be analyzed with the help of reports generated via the Management Tool. These reports allow you to receive the information on the activity of multiple Clients, alert events, detected URLs, and executed Linux commands, and get statistics on time spent by the user in each application or on each web-page. You can schedule the reports to be generated and sent via at the specified time or manually generate the reports, which can be saved or printed, via Report Generator. The reports can be generated in any of the following formats: PDF (*.pdf), Web Page (*.html), Single File Web Page (*.mht), Rich Text Format (*.rtf), Plain Text (*.txt), Excel Workbook (*.xlsx), Excel Workbook (*.xls), XPS Document (*.xps), and CSV Document (*.csv). Report Types The following types of reports are available in the Management Tool: Grid reports Report type Contains the information about Consists of the following columns Contains the information on Alert Grid Report All alert events on all selected Clients for the defined users and defined time interval. Activity time Alert name Activity title Application name Keystrokes Clients and users of Client computers Linux Grid Report (for Linux Clients) All commands executed on Linux Clients. Time Command Parameters Clients and users of Client computers USB Grid Report All USB-device-related events detected by the USB rules. Time Rule Name Action (Blocked/Detected) Device Class Device Details Clients and users of Client computers 148

149 Advanced Reports Summary reports Report type Contains the information about Consists of the following columns Contains the information on Activity Summary Report (for Windows Clients) URL Summary Report (for Windows Clients) Time spent by the user in each application (by application name) for the defined users and defined time interval. Idle time. Time spent by the user on each site (by domain name) for the defined users and defined time interval. Application Time spent (hrs) URL only the main part of the URL (e.g., example.com) will be added to the report. Time spent (hrs) Clients and users of Client computers Clients and users of Client computers Chart reports Report type Contains Consists of the following data Contains the information on Activity Chart Report (for Windows Clients) The same information as in the Activity Summary Report, but in the form of a bar chart. Application title Total time spent (minutes) Users of Client computers Activity Pie Chart Report (for Windows Clients) The same information as in the Activity Summary Report, but in the form of a pie chart. Application title Time spent in the application (%) Users of Client computers URL Chart Report (for Windows Clients) The same information as in the URL Summary Report, but in the form of a bar chart. URL only the main part of the URL (e.g., example.com) will be added to the report. Total time spent (minutes) Users of Client computers URL Pie Chart Report (for Windows Clients) The same information as in the URL Summary Report, but in the form of a pie chart. URL only the main part of the URL (e.g., example.com) will be added to the report. Time spent on the website (%). Users of Client computers 149

150 Advanced Reports Report Limitations 1. Any user activity that lasts less than 10 seconds will not be included into the report. 2. The time spent by the user on a certain site or in a certain application is calculated basing on the time difference between the screen capture with the current user activity and the screen capture with another user activity. To enhance the accuracy of time calculation, disable the application filtering option and make sure that all screen capture options are selected in the Management Tool. 3. Linux reports include only exec* and sudo commands. Scheduled Reports About The Management Tool allows creating reports via Report Scheduler and sending them the defined addresses with the defined time interval. The reports creation is available to the user with the administrative Client installation and management permission. The report creation and sending options are defined in rules, which include the following parameters: rule name and description, report type and format, state (enabled or disabled), generation frequency (daily, weekly, or monthly), Windows Clients/Client groups, and Users on Clients to which the rule must be applied. The created rules are displayed on the Scheduled Reports page in the grid with the following columns: Name Description Assigned To Monitored Users State Frequency Recipients Adding Report Rules To add a rule, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Scheduled Reports navigation link on the left and click Add rule. 150

151 Advanced Reports 3. On the Add rule page, on the Rule Properties tab, enter a unique name for the created rule and then optionally enter its description and select the Enable scheduled report generation check box. Click Next. 4. On the Report Options tab, do the following and then click Next: Select one or several Report Types. Define the Report Parameters: o In the Report format field, select the format for the report. o In the Generate report filed, select the frequency of report generation (Daily, Weekly, or Monthly). o In the Start report generation at field, define the time at which the report generation must be started. NOTE: Depending upon the Server load, the report generation can start a few minutes later than the set time. You can select the value from the drop-down list and edit it manually if you need to set your own number of minutes. If the Weekly parameter is selected in the Generate report field, select the day of the week on which the report will be generated in the Day of week drop-down list. If the Monthly parameter is selected in the Generate report filed, select the day of the month on which the report will be generated in the Day of month dropdown list. NOTE: If the Monthly parameter is selected and you want the report to be generated on the 31 st day of the month, it will be generated only in those months where there are 31 days. Define the custom header and footer for the report in the Header text and Footer text fields (the maximum length of the header and footer text is 1000 symbols). Enter the addresses to which the report will be sent in the s field. NOTE: Define the Sending Settings to receive the scheduled reports via On the Assigned Clients tab, select the Windows Clients/Client Groups to which the rule will be applied and click Next. To find specific Windows Clients/Client Groups, enter their names in the Contains box and click Apply Filters. 6. On the Monitored Users tab, define the users whose activity will be included in the report. To select a certain user, click Add Users, then on the Adding Users page, select the check boxes next to the corresponding users and click Add selected. NOTE: Only those users whose activities have already been monitored are listed on the Adding Users page. 7. Click Finish. 8. The rule is added. NOTE: The scheduled report rule can also be created by clicking Create Scheduled Report Rule on the Report Generator page. Editing Report Rules To edit a rule, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 151

152 Advanced Reports 2. Click the Scheduled Reports navigation link on the left. 3. Click Edit Rule for the required rule. 4. Edit rule properties, report options, and define assigned Windows Clients and monitored users on the corresponding tabs in the same way as when adding a new rule. NOTE: Click Next or Finish to save the changes on each tab. 5. The rule is edited. Deleting Report Rules To delete a rule, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Scheduled Reports navigation link on the left. 3. Click Edit Rule for the required rule. 4. On the Rule Properties tab, click Delete Rule. 5. In the confirmation message, click Delete. 6. The rule is deleted. Generating Reports from the Scheduled Report Rule Once the scheduled report rule is created, you can generate a report from the Rule Properties tab any time. To generate a report from the Scheduled Report Rule, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Scheduled Reports navigation link on the left. 3. Click Edit Rule for the required rule. 4. On the Rule Properties tab, click Generate Report. 5. The generation of the report starts. 6. The report can be viewed on the Scheduled Reports Generation Log page as soon as it is generated. If the s field contains one or more addresses defined in the rule, the report will be sent to those addresses. NOTE: If the generated report is not displayed on the Scheduled Reports Generation Log page, it is still being generated. Reload the page by pressing the F5 key until the report is displayed. Frequency and Time Interval for Report Creation The time interval of the data that is added to the report depends upon the report generation frequency. 152

153 Advanced Reports If the report is generated on a daily basis, it will include the data that was monitored starting from the specified time of the previous day up till the specified time of the current day. For example: If the Daily parameter is set and the report is to be generated on June, 13, at 17:00, the time interval of the data for this report will start on June, 12, at 17:00 and end on June, 13, at 17:00. If the report is generated on a weekly basis, it will include the data that was monitored starting from the specified time and day of the previous week up till the specified time and day of the current week. For example: If the Weekly parameter is set and the report is to be generated on Monday at 18:00, the time interval of the data for this report will start on Monday of the previous week at 18:00 and end on Monday of the current week at 18:00. If the report is generated on a monthly basis, it will include the data that was monitored starting from the specified time and day of the previous month up till the specified time and day of the current month. For example: If the Monthly parameter is set and the report is to be generated on January, 20, at 19:00, the time interval of the data for this report will start on December, 20, at 19:00 and end on January, 20, at 19:00. NOTE: If the Monthly parameter is selected and you want the report to be generated on the 31 st day of the month, it will not be generated in those months where there are 30 days or less. If the monthly report is set to be generated on the 31 st day of month, but there were less than 31 days in the previous month, the time interval of the data for this report will start on the last day of the previous month and end on the 31 st day of the current month. For example: If the report is generated on March, 31, the time interval of the data for this report will start February, 28, or February, 29, and end on March, 31. If the report is generated from the scheduled report rule, the time interval of the data for the report will depend upon the current date and time. For example: If the Daily parameter is set in the rule and the Start report generation parameter is set to 15:00, and you want to generate the report at 14:00, the time interval of the data for the report will start from 14:00 of the previous day and end at 14:00 of the current day. If the Weekly parameter is set in the rule and the Day of week parameter is set to Wednesday, and you want to generate the report on Friday at 12:00, the time interval of the data for the report will start from Friday of the previous week at 12:00 and end on the current day at 12:

154 Advanced Reports If the Monthly parameter is set in the rule and the Day of month parameter is set to the 15 th day of month, and you want to generate the report on May, 10, at 10:00, the time interval of the data for the report will start from April, 10, at 10:00 and end on the current day at 10:00. NOTE: If there are too many activities in the defined time interval, the report may become too large. The generated report file cannot exceed the size of allowed SMTP server attachments. Viewing Logs For each rule, the user can see the log which contains the information on time when the report was generated, report name (file name) and type, report generation result (status), number of results in the report, and the s to which the report was sent. NOTE: Only 100 last records are stored. To view the logs, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the Scheduled Reports navigation link on the left. 3. Click View Log for the required rule. 4. On the Scheduled Reports Generation Log page the logs are displayed in the grid with the following columns: Generated (Time when the report was generated) File Name (Report name) Report Type Status (Finished, In Progress, or an error reason in case the error occurred during report generation) Results Count (Number of results in the report) Sent To 5. Click the Download link to download the report to your computer. 6. Click the Delete link to delete the report from the log and from the Server. Report Generator About The reports can be generated on the Report Generator page by the user with the Viewing monitoring results permission and can be previewed before printing. 154

155 Advanced Reports The main difference between Report Scheduler and Report Generator is that Report Generator allows you to create reports for the time interval of any length. Though it may take you much time to generate a report for a long time interval and for a big number of Windows Clients. NOTE: You can generate only one type of report at a time via Report Generator. Report Parameters The following parameters are defined in the Management Tool when creating a report: 1. Report parameters This option allows you to select the type of the report and enter its custom Footer text and Header text. 2. Date filters This option allows you to define the time interval for which the report will be generated. 3. Clients This option allows you to select the Clients/Client groups, whose monitored data will be added to the report. NOTE: Only Clients for which the user has the Viewing monitoring results are displayed. 4. Users This option allows you to select the users of Client computers whose activity will be included in the report. Generating Report To generate a report, do the following: 1. Log in to the Management Tool as a user with the Viewing monitoring results permission. 2. Click the Report Generator navigation link on the left. 3. Define the report parameters: Select the type of the report and enter its Footer and Header text. In the From and To fields, enter the dates and time within which the data of the monitored Clients should be added. Click Add Clients and on the opened Adding Clients page select the check boxes next to the corresponding Clients/Client groups. Once the Clients are selected, click Add selected. Define the users whose activity will be included in the report: o Select the Any user option if you do not need to specify the user whose activity will be added. 155

156 Advanced Reports o In other case, select the Selected users option, click Add Users, and then select the check boxes next to the corresponding users on the opened page. Once the users are selected, click Add selected. NOTE: Only those users whose activities have already been monitored are listed. 4. Click Generate Report. 5. On the opened Report Preview page, click the corresponding icons located on the toolbar above the report to perform the following actions: Display the search window Print the report Print the current page Export a report and save it to the disk Export a report and show it in a new window when this icon is clicked, the report is opened in a new window, from which it can be saved to the disk, printed, or zoomed. You can also navigate between the pages of the report by clicking the blue arrows and choose the format of the report by clicking the black arrow that opens a drop-down list with all supported formats. Creating a Scheduled Report Rule from the Report Generator Page Once the parameters for the report are defined, you can create a scheduled report rule basing on the defined parameters. To create a rule, do the following: 1. Log in to the Management Tool as a user with the Viewing monitoring results permission. 2. Click the Report Generator navigation link on the left. 3. Define the report parameters. 4. On the Report Generator page, click Create Scheduled Report Rule. 5. The Editing Rule page opens. 6. On the Rule Properties tab, enter a unique name for the created rule and then optionally enter its description. The default name of the rule is GeneratorRule<number of rule>. 7. Click Next. 8. On the Report Options tab, enter the corresponding values in the Report Parameters fields and the s field the same as when adding a new report rule. The other parameters like Report Type, Header and Footer text, Clients, and Users were defined in Report Generator, but you can edit them if you want. 9. Click Finish. 156

157 USB Monitoring & Blocking USB Monitoring & Blocking About The USB Monitoring option allows you to detect that the USB device is plugged into the computer on which the Client is installed. When the USB device is plugged in, the Client sends information on it to the Server. The following actions with the plugged in devices are available for a user: Monitoring allows you to view information on the detected devices in the Session Viewer. Sending notifications allows you to receive notifications (by or in the Tray Notifications app) when a new device is connected to the Client computer. Blocking allows you to block the USB device from using. In this case, the user may be informed that the device on his computer is blocked with a balloon notification in the system tray. It is also possible to create a list of exceptions of devices that must not be monitored or blocked. WARNING! It is recommended to add all the allowed USB devices to exceptions in order not to block them from using accidentally. Monitored Devices Monitored Devices, a list of devices that can be monitored/blocked/alerted, includes the following classes: Mass storage devices external magnetic hard drives, external optical drives (including CD and DVD reader and writer drives), portable flash memory devices, solid-state drives, adapters between standard flash memory cards and USB connections, digital cameras, digital audio and portable media players, card readers, PDAs, and mobile phones. Windows portable devices audio players, phones, and other devices that use nonstandard identifier. Wireless connection devices Bluetooth adapter, Microsoft RNDIS. Modems and Network adapters network interface controllers. Audio devices speakers, microphones, sound cards, MIDIs, etc. Video devices web cameras. Human interface devices keyboards, computer mouse devices, joysticks. Printer devices laser printers, inkjet printers, CNC machines. Composite devices devices that consist of one or a few more devices (e.g. keyboards with USB ports). Vendor-specific devices devices which require vendor-specific drivers and whose class is defined by the vendor. 157

158 USB Monitoring & Blocking WARNING! When this class is selected, a device of any type might get blocked. Each class has its own name (e.g., 00, 01, 02, etc.), which can be viewed in the device properties. The name of class allows you to define to what class the detected device belongs. For more information, check these links: To view the name of the USB device class, do the following: 1. Plug the device into your computer. 2. Right-click Computer and select Manage. 158

159 USB Monitoring & Blocking 3. The Computer Management window opens. 4. Expand the Device Manager node. 5. Expand the node with the name of the computer in the central pane. 6. Select the Universal Serial Bus controllers node in the list and expand it. 7. Find the device, the class of which you want to view, right-click it and select Properties. 8. In the opened window, select the Details tab, then select Compatible Ids in the Property drop-down list, and view the necessary information in the Value field. 9. Click OK or Cancel to close the window. USB Monitoring Rules About In order to monitor and block the devices which are plugged into the computer, the user needs to create rules in the Management Tool. The rules can be created and assigned to the Clients by the user with the administrative Client installation and management permission. The created USB Monitoring rules are displayed on the USB Monitoring Management page in the Management Tool in a grid with the following columns: Name Description State Action Assigned to (Clients group) Adding USB Monitoring Rules To add a new rule, do the following: 1. Log in to the Management Tool as a user with the Client installation and management permission. 2. Click the USB Monitoring Management navigation link on the left. 3. On the USB Monitoring Management page, click Add Rule. 159

160 USB Monitoring & Blocking 4. On the Add USB Rule page, on the USB Rule Properties tab, enter a unique name for the created rule and then optionally enter its description and select the Enable USB rule check box. Click Next. 5. On the Rule Conditions tab, do the following: Add the classes of devices to be monitored to the Monitored Devices list. Define the exceptions for the devices to be skipped while monitoring. 6. On the Action tab, define what happens when a device from the list of monitored devices is used on target computer by selecting the following check boxes: Block USB device allows you to prevent the user from using the USB device from the Monitored Devices list on the target computer. This option affects all the users, regardless of the user filtering settings. Notify the user on target computer about device blocking allows you to define the custom text to be displayed in a balloon notification on the Client computer (maximum 250 characters). Send notification to allows you to receive an alert notification on USB device detection via . NOTE: Define the Sending Settings to receive notifications on USB device detection via . Display tray notification allows you to receive an alert notification on USB device detection via the Tray Notification app. If you do not select any of the actions, the detected USB devices will be monitored and displayed in the Session Viewer only. 160

161 USB Monitoring & Blocking 7. On the Assigned Clients tab, select the Clients/Client Groups, to which the rule will be applied, and click Next. To find specific Clients/Client Groups, enter their names in the Contains box and click Apply Filters. 8. Click Finish. 9. The rule is added. 161

162 USB Monitoring & Blocking Editing USB Monitoring Rules To edit a rule, do the following: 1. Log in to the Management Tool as a user with the Client installation and management permission. 2. Click the USB Monitoring Management navigation link on the left. 3. On the USB Monitoring Management page, click Edit Rule for the required rule. 4. Edit rule properties on the corresponding tabs in the same way as when adding a new rule and click Finish. 5. The rule is edited. NOTE: The existing rules can also be edited by a user with the Client configuration management permission. Deleting USB Monitoring Rules To delete a rule, do the following: 1. Log in to the Management Tool as a user with the administrative Client installation and management permission. 2. Click the USB Monitoring Management navigation link on the left. 3. On the USB Monitoring Management page, click Edit Rule for the required rule. 4. On the USB Rule Properties tab, click Delete Rule. 5. In the confirmation message, click Delete. 6. The rule is deleted. In case some plugged-in devices were blocked in accordance with the rule, the user will have to remove the devices and plug them back in. Defining Exceptions for USB Rules The list of exceptions for USB devices includes the devices are not monitored or blocked. Unlike the Monitored Devices list that contains the classes of devices, the exceptions include the separate devices added individually. The exceptions can be added on the Rule Conditions tab when adding or editing the rule. In case you want to block vendor-specific devices, make sure you have added all allowed user devices to the list of exceptions. To add an exception, do the following: 1. On the Rule Conditions tab, click Add. 2. On the Add Exception page, select one of the following radio buttons: Quick selection allows you to enter your Device Hardware ID. Custom selection allows you to enter the Vendor ID (VID), Product ID (PID), Revision, and Serial in the corresponding fields. NOTE: The Vendor ID (VID) and the Product ID (PID) are required fields, Revision and Serial are optional fields. 162

163 USB Monitoring & Blocking 3. Optionally, enter a description in the Description field. 4. Click Add and then click Finish. 5. The exception is added. Viewing Device Hardware ID To view the Device hardware ID, do the following: 1. Plug the device into your computer. 2. Right-click Computer and select Manage. 3. The Computer Management window opens. 4. Expand the Device Manager node. 5. Expand the node with the name of the computer in the central pane. 6. Select the Universal Serial Bus Controllers node in the list and expand it. 7. Find the device, the information of which you want to view, right-click it and select Properties. 8. In the opened window, select the Details tab, then select Hardware Ids in the Property drop-down list, and view the necessary information in the Value field. 9. Click OK or Cancel to close the window. 163

164 Configuration Configuration Defining Sending Settings sending settings allow you to define the options of sending notifications for all alerts, USB monitoring, and receiving reports via . Their editing is available for users with the administrative Client installation and management permission. To define sending settings, click the Configuration navigation link to the left and open the sending settings tab. The settings include: 1. Connection Settings Server: This option allows you to define an existing SMTP mail server. NOTE: The delivery of notifications via mail servers with only NTLM authentication, such as Microsoft Exchange Server, is not supported. Port: This option allows you to define the server port number via which the s will be sent. Encrypted connection type: This option allows you to define the type of encrypted connection via which the notifications will be sent. You can choose between: - None - SSL - TLS 2. Connection Credentials This option allows you to define the login details (User and Password) of an existing account from which the notifications will be sent. If the mail server does not require entering any credentials, you can select the No authentications check box. 3. Connection Test This option allows you to send a test to a specified address to check if all connection settings are correctly defined. 164

165 Viewing Monitored Data Viewing Monitored Data Session List About Sessions Monitored data received from Windows and Linux Clients is organized in the session. The Windows Client session includes screen captures and metadata associated with them (application name, activity title, captured keystrokes, and URLs). Windows Clients start recording screen captures in a new session every time the computer is restarted. The maximum duration of one session can be 24 hours. At 00:00 all live sessions are terminated. After their termination (their status changes from live to finished), new live sessions automatically start. The Linux Client session contains the list of executed commands and their parameters. Linux Clients start recording a new monitoring session each time the terminal is opened. There is no time limitation for a Linux Client session. Monitored Sessions List To view monitored sessions, click the Monitored Sessions navigation link on the left. The Monitored Session page is divided into two panes: Search pane Sessions grid The search pane allows you to perform search in the session data. The list of all sessions is displayed in the form of grid. The grid includes the following information: Play: Allows opening a session in the Session Player to view monitored data in the form of video. User name: Displays the name of the user logged in to the Client computer. NOTE: If Forced User Authentication is enabled on the Client installed on the computer with Windows Server operating system, the user name is displayed in the User name column in brackets as follows: <logged in Windows user> (<secondary authentication user>). If there has been no secondary authentication, there are no brackets. Client Name: Displays the name of the computer on which the Client is installed. OS: Displays the operating system type (Windows or Linux). Type: Displays the session type (Live or Finished). Start: Displays the date and time when the session started. Last Activity: Displays the date and time of the last made screen capture or executed Linux command. 165

166 Viewing Monitored Data Finish: Displays the date and time when the session finished. If the session has the Live status, this field is empty. IPv4: Displays the address used to connect the Client to the Server. IPv6: Displays the address used to connect the Client to the Server. Domain: Displays the name of the domain to which the Client belongs. Client Description: Displays the custom Client description. Client Group: Displays the name of the Client Group to which the Client belongs. If the Client belongs to the All Clients group only, the column is empty. Filtering Sessions A user can filter the session by metadata on the Monitored Sessions page in one of the following ways: Via searching in the session data Via filtering by column Filtering via Searching This type of filtering is the analog of the Simple search in the Monitor version 3.3 and lower. The Search field allows you to find sessions containing search expression (keyword) in: User Name Client Name [Windows] Application Name [Windows] Activity Title [Windows] Keystrokes [Windows] USB Device Information [Windows] URL [Linux] Executed Command [Linux] Command Parameters To find the required session, enter the required keyword into the Search field. The metadata in the Sessions grid is filtered according to the search expressions. If you click Play for the filtered session, data in it will automatically be filtered according to entered search expression to display only records corresponding to the search expression. You can enter several keywords separating them with space ( ), comma (,), colon (:), period (.), or slash (/). NOTE: The system searches for each part of the URL separately. For example, if the search request is google.com, the system will show results with google and com separately, i.e., the system will find google.com, facebook.com, google.co.uk, etc. 166

167 Viewing Monitored Data Filtering by Column You can filter sessions using the dropdown menu near the column header in the Sessions grid. To filter sessions by the not date field (Client name, OS, User name, etc.), click required column name, select one or several check boxes, and then click OK. near the To filter sessions by the date field (Start, Last Activity, or Finish), click near the required column name, select the From and To dates in the dropdown menu, and then click OK. You can filter sessions by multiple fields. Grouping and Sorting Sessions To group sessions in the Sessions grid, drag any column header to the group pane. You can group using several parameters. To sort sessions in the Session grid, click the required column header. You can change column sort order from ascending to descending, and vice versa. To do this, click the Sort arrow near the column header. If the data is not sorted by this column, the Sort arrow is hidden. 167

168 Viewing Monitored Data Playing Sessions About The Session Viewer is a part of the Management Tool that provides the possibility to view monitored data within one selected session. To open the Session Viewer, select one of the sessions in the Sessions grid on the Monitored Sessions page and click. Session Viewer Interface By default, the Session Viewer interface is divided into the following areas: Session Player pane: Allows viewing screen captures made from the computer on which the Windows Client is installed, or visually recreated interactive data of the recorded Linux terminal (input and output as the user sees them in the terminal). The navigation section allows you to manage the playback of the video of screen captures or commands. [Windows Client] Details pane: Allows you to view the keystrokes associated with the selected screen capture, USB device information, and URL addresses of websites visited by a user. Metadata pane: Displays the session data in the form of grid, which includes: o Activity time, Activity title, Application name, Keystrokes, and URLs for Windows Clients; o Activity time, Command, Function, and Parameters for Linux Clients. 168

169 Viewing Monitored Data Session Player The Session Player allows viewing screen captures made from the computer on which the Windows Client is installed, or graphic representation of the recorded Linux terminal (input and output as the user sees them in the terminal). You can view them separately by selecting the required record from the Metadata grid or play all monitored data in the form of video. The following actions are available: To play/pause the video playback, click Play/Pause. To move from one record to another, click To the beginning, To the end, Previous, or Next. To open the Player to the full-screen mode, double-click the Player or. To return from the full-screen mode, double-click the Player or. You can define the speed with which monitored data will change in the Player area. To do this, click second.. The available speed options are 1/2/4/8/16 frame(s) per To receive the link to a certain position in the session, click. Magnifier If you need to view data displayed in the Player in detail, use the Magnifying Glass option. To enlarge the certain part of the played data, do the following: 1. Click the Magnifying Glass. 2. The Magnifier window opens on the right. 3. Move the rectangle across the displayed data. To turn off the Magnifying Glass, click the Magnifying Glass again. Getting Data URL The Get data URL feature allows receiving the link of the certain position of the session. You can use this URL to: Open the Session Viewer for playing the required session from the same position; Bookmark certain position in the session using the browser bookmarking mechanism. 169

170 Viewing Monitored Data To get data URL, do the following: 1. Click on the Navigation pane under the Player. 2. The URL Data window opens. 3. Copy the URL and click Close. 4. Enter the copied URL into the browser address bar. 5. The Session Viewer opens. NOTE: If you are logged out, the login page opens before Session Viewer. 6. The Player starts playing records from the selected position in the session. Metadata Grid Metadata grid is located to the right of the Player. It contains detailed information on monitored user activity. Information is displayed in the grid with the following columns: [Windows Client] o Activity Time: Displays the date and time when the screen capture was executed. o Activity Title: Displays the name of the active window that is associated with the screen capture. o Application Name: Displays the name of the application started on the Client computer. o URL: Displays the URL of the visited web resource. o Keystrokes: Displays the keystrokes typed by the user. o Alert/USB: Displays the indication whether the screen capture was triggered by an alert event. o Rule Name: Displays the name of the name of the rule according to which the alert event was identified. [Linux Client] o Activity Time: Displays the date and time when the command was executed. o Command: Displays the command being executed. o Function: Displays the system call made. o Parameters: Displays the full parameters of the executed command. o Alert: Displays the indication whether the activity has triggered an alert event. Data is sorted by the time of the Activity Time by default. You can change the order and size of the columns. 170

171 Viewing Monitored Data Player and Metadata Synchronization The Session Viewer can work in two modes: In the Synced View mode, data in the Metadata grid and Player are synchronized while session playing, i.e., metadata associated with the data being currently played is highlighted in the Metadata grid. This mode is available unless any filtering, searching, or grouping is performed in the Metadata grid. In the Filtered View mode, data in the Metadata grid and Player are not synchronized while session playing. In this mode, the Player displays all data in the session, whereas data is Metadata grid is being filtered, searched, or grouped. After selecting the session on the Monitored Sessions page without previous searching, the Player opens in the Synced View mode. As soon as you perform any filtering, grouping or searching, the Synced View mode is automatically changed to the Filtered View mode. To switch the modes, click Back to Synced View/Back to Filtered View above the Metadata grid. Filtering Data You can filter the metadata in the Metadata grid on the Player page in one of the following ways: Via searching Via filtering by column After data filtering, the Session Player switches to the Filtered View mode. Filtering via searching The Search field allows you to find metadata containing search expression in: Activity title Application Name Keystrokes USB Device Info URL Linux Command Linux Command Parameters Linux Functions To find the required metadata, enter the keyword into the Search field and press Enter. Data in the Metadata grid is filtered according to the search expressions. 171

172 Viewing Monitored Data Filtering by column You can filter the metadata using the dropdown menu near the column header in the Metadata grid. To filter metadata by the Activity Time field, click near the column name, select the From and To dates in the dropdown menu, and then click OK. To filter metadata by any other field, click several check boxes, and then click OK. near the required column name, select one or Grouping and Sorting Data To group metadata in the Metadata grid, drag any column header to the group pane. You can group using several parameters. To sort metadata in the Metadata grid, click the required column header. You can change column sort order from ascending to descending, and vice versa. To do this, click the Sort arrow near the column header. If the data is not sorted in this column, the Sort arrow is hidden. Live Sessions The Session Viewer allows you to view Client Live sessions in the real time, i.e., while the monitoring of the Client computer is still in progress. To play a live session: 172

173 Viewing Monitored Data 1. Click Play for the session with the type Live in the Monitored Sessions grid. 2. The Session Player opens in the full screen mode. The Metadata grid is hidden. 3. Data in the Player will be refreshed as soon as new monitored data is received from the Client. 4. To stop playing the Live session, click. After this, data stops auto-updating and the session can be played the same as Finished sessions. 5. To resume playing the Live session, click. NOTE: If you are viewing the session of the Windows Client with the enabled Capture screen on each event without timeout option, it may affect CPU usage and cause performance slowdown due to the great number of received screen captures. Windows Client Sessions Playing Windows Sessions A user starts playing Windows Session by clicking Play on the Monitored Sessions page. The session is opened in the new tab or new window depending on your browser settings. While playing Windows sessions, you can view screenshots in the Player pane and associated metadata (Application name, Activity title, URL, and keystrokes) in the Metadata grid. If data containing keystrokes is selected in the Metadata grid, the detailed information on keystrokes is displayed in the Details pane. Viewing Keystrokes Viewing keystrokes is available only to the users with the Viewing keystrokes permission for the Client. When you select a screen capture or a row in the Metadata grid, the keystrokes associated with it are displayed in the Details pane below the Player pane. By default, only text characters are displayed. You can enable displaying all keystrokes logged (e.g., navigation keys, functions keys, etc.) by clearing the Show only text characters check box. Then any other keys and key combinations will be displayed in square brackets. If a key was pressed repeatedly, it will be displayed with an "x" sign and the number of reiterations (e.g., [F12 x 24]). If the user types the text, using arrows (left/right) and Backspace or Delete keys, these keys are processed by the system to edit the logged keystrokes. When the keystrokes are edited, only the end result of text that was meant to be typed by the user is displayed in the Details pane. To see this result, the Show only text characters check box must be selected. For example: If the user types Helo and then uses the left arrow to go back and correct the word by typing another l, the word Hello will be displayed in the Details pane, with Helol. 173

174 Viewing Monitored Data Presentation of keystrokes with the selected Show only text characters check box. Presentation of keystrokes with the unselected Show only text characters check box. Please note that if the SmoothMode parameter (a screenshot creation on each event without timeout) is enabled for the Client, the keystrokes are not edited. If the user corrects the word using a mouse, the keystrokes are not edited. For example: If the user types Fried and then uses the mouse to go back and correct the word by typing letter n, the word Friedn will be displayed in the Details pane, instead of Friend. 174

175 Viewing Monitored Data If the user types the text in different applications, the logged keystrokes are split according to screen captures. For example: If the user types Hello in Skype and then opens Word and types Ok, the word Hello will be displayed next to the screen capture associated with Skype, and the word Ok will be displayed next to the screen capture associated with Word, instead of HelloOk. NOTE: If the Enter key was pressed during input, the log will be split in the list of screen captures. Though to maintain text integrity, in the keystrokes box, the keystrokes lines having the same Title-Application pair will be put together. Viewing USB Device Info If there are any USB Monitoring rules according to which the devices are detected or blocked, each time the alert event occurs, a screen capture is created. In the Metadata grid, this is indicated by the icon in the Alert/USB column. When you select a USB-device-related screen capture or a row in the Metadata grid, the USB device info associated with it is displayed in the Details pane below the Player pane. If the device was blocked, it is marked as BLOCKED in the parentheses. Viewing URLs If the URL monitoring option is enabled for the Windows Client, then each time the screen capture is created while the user is working in the browser, the URL address is saved and displayed in the URL column in the Metadata grid. If there are several screenshots created while the user is viewing one page on a certain website, then all of them contain the same URL information. NOTE: As getting a URL address to be monitored may take about 600 milliseconds, there is a possibility that the screen capture and its activity title along with URL address may be not properly synchronized in the Session Viewer (e.g., the user may see a screen capture with a URL address that belongs to the previous one). 175

176 Viewing Monitored Data Viewing Idle State Windows Client activity will be marked as Idle if there has been no activity on the target computer for a long time. The activity is displayed as Idle in the Metadata grid in two cases: On computers with Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2012, and Windows Server 2008: If the user is inactive for more than 15 minutes, computer is in sleep or hibernation modes, or the screen is set to be turned off automatically. On computers with Windows XP and Windows Server 2003: If the computer is in sleep or hibernation modes, or the screen is set to be turned off automatically. Linux Client Sessions Playing Linux Sessions A user starts playing Linux Session by clicking Play on the Monitored Sessions page. The session is opened in the new tab or new window depending on your browser settings. While playing Linux sessions, you can view all visually recreated interactive data in a form of a video in the Player pane and executed commands with parameters in the metadata grid. Filtering EXEC Commands By default, the commands are filtered by exec function to display only the command executed after user input. To display the list of all commands, including system ones, discard the filtering by clearing the Show only execution commands checkbox. 176

177 Forensic Export Forensic Export About Forensic Export allows exporting the session in the encrypted form for viewing monitored session on any computer, even without access to the Management Tool. The session is exported into the signed executable file, which contains the embedded player for displaying graphical information and metadata. The validity of forensic export results can be checked via Management Tool. The results of export are stored on the Server until you delete them. Exporting Session Fragment To export the session fragment, do the following: 1. Open the Session Viewer page for the selected session. 2. In the Player, select the start point of the session fragment. 3. Click Session Forensic Export under the Player. 4. The Session Forensic Export window opens. 5. Select the Export session fragment from current Player position option and enter the required fragment length in minutes. 6. Click Export. 7. The Forensic Export History page opens, displaying export progress. 8. As soon as export process finishes, the resulting file become available for downloading. 9. Click Download to download the file with Forensic Export results. Exporting Full Session To export the session, do the following: 1. On the Session Viewer page for the selected session, click Session Forensic Export under the Player. 2. The Session Forensic Export window opens. 3. Select the Export full session option and then click Export. 4. The Forensic Export History page opens, displaying export progress. 177

178 Forensic Export 5. As soon as export process finishes, the resulting file become available for downloading. 6. Click Download to download the file with Forensic Export results. Viewing Forensic Export History The Forensic Export History page displays the grid with all results of export for Clients you have permissions for. You can see exports performed both by you and other users. The Forensic Export History grid contains the following information: Export Date: Displays the date and time when the session was exported. Client Name: Displays the name of the computer on which the Client is installed. User: Displays the name of the user logged in to the Client computer. Session Start Date: Displays the date and time when the session started. Session End Date: Displays the date and the time when the session finished. Export Type: Displays the export type: Full (for the full exported session) or the time interval (From To) included in the exported session. Status: Displays the status of session export (Generated or Generation failed). Full Size: Displays the size of the resulting file (n/a for failed session exporting). To download the exported session, click Download in the Forensic Export History grid. To delete the exported session from Server, click Delete in the Forensic Export History grid. Playing Exported Session To view exported data, download it and start the downloaded executable file. NOTE: To view exported data on computers with Linux or Mac operating system, you need to install Mono Framework on them. Follow the instructions at to install Mono Framework on your computer. Sessions are played in the Forensic Export Player. 178

179 Forensic Export The Forensic Export Player interface is divided into the following parts: Player pane: Allows viewing screen captures made from the computer on which the Windows Client is installed, or visually recreated interactive data of the recorded Linux terminal (input and output as the user sees them in the terminal). The navigation section allows you to manage the playback of the video of screen captures or commands. [Windows Client] Details pane: Allows you to view the keystrokes associated with the selected screen capture, USB device information, and URL addresses of websites visited by a user. Metadata pane: Displays the session data in the form of grid, which includes: o Activity time, Activity title, Application name, Keystrokes, and URLs for Windows Clients; o Activity time, Command, Function, and Parameters for Linux Clients. NOTE: If the user performing export does not have the Viewing keystrokes permission for this Client, Forensic Export results will contain no keystrokes. You can do one of the following while viewing: To play/pause the video, click Play/Pause in the Player pane. To move from one record to another, use the control buttons in the Player pane. To open the monitored data to the full-screen mode, double-click the monitored data in the Player pane or. You can define the speed with which monitored data will change in the Player pane. To do this, click. The available speed options are 1/2/4/8/16 frame(s) per second. To enlarge a certain part of the played data, click the Magnifying Glass. 179

180 Forensic Export Validating Exported Data Using Management Tool, you can check that exported data is valid and its integrity has not been altered. Please note that data validity must be checked only in the Management Tool connected to the Server via which data has been exported. Any other Server will consider data not valid. To validate exported data, do the following: 1. Click the Forensic Export History navigation link on the left and then click Validate Export Results. 2. On the Forensic Export Results validation page, click Choose File to select the.exe file with forensic export results. 3. The file is uploaded to the Server and validated. 4. If file validity is confirmed, you will see a message: The file is validated successfully! 180

181 Troubleshooting Troubleshooting Quick Access to Log Files Log files contain information that might be useful for administrator for detecting problems in the system if any. Whenever there is some kind of Server or Management tool error, a warning icon is displayed next to the Diagnostics navigation link to the left. It is no longer displayed after the log files are downloaded. You can either analyse the log files yourself to get more information on what is happening in your system or send them to the Support team to help them in detecting the source of problems in your system. To download the Server log file, login as the user with the Database Management permission, click the Diagnostics navigation link to the left and then click Download Server log file. The log file will be downloaded to your computer. To download the Management Tool log file, login as the user with the Database Management permission, click the Diagnostics navigation link to the left and then click Download Management Tool log file. The log file will be downloaded to your computer. Database/Server Database/Server Related Issues Issue I cannot start the Server from the Server tray. There are too many records in the database. I have defined a new database, what happened to the old one? I need to transfer the data from an old database to a new one/i want to change the type of the database without losing data. I have transferred the SQL database to Cause/Solution To start the Server, the Server tray service must be started under the administrator account. Use the automatic or manual database cleanup feature to remove the old records from the database. To do this, in the Management Tool, click the Database Management navigation link and define the cleanup settings on the corresponding tabs. The old database remains in place and is not changed. Unfortunately, the data cannot be transferred from one database to another. Unfortunately, you can t relocate the SQL database to another computer. Though you can move it to 181

182 Troubleshooting another computer. I have changed the location of the Firebird database. I have installed a new version of the Server and I want to use the old database. I have used the database cleanup feature, but the size of the database didn t change. I have accidentally removed the database from the MS SQL Server. another location on the same PC with SQL means. To redefine the location of the Firebird database, move it to another location and change its values in the Windows Registry Editor. See Moving the Server Database chapter for more details. If you have updated the Server, your old database will remain. If you have reinstalled the Server, you need to use a new database. The cleanup feature only removes data from the database, but does not change the size reserved by it. To reduce the size of the database, click Shrink database on the Database Options tab on the Database Management page of the Management Tool. You need to define a new database. To do this, you need to reinstall the Server. I cannot shrink the database: the Shrink database button is absent in the Management Tool on the Database Options tab. Make sure you use the MS SQL Server database. The shrinking cannot be performed if the cleanup procedure is in progress. My anti-virus blocks the Server uninstallation/update. Due to the uninstaller specifics some anti-viruses might detect it as a false positive during virus scan. In this case, it is recommended to disable your antivirus during Server uninstallation/update. Database/Server Related Error Messages The following table provides the list of error messages related to databases and the Server and their causes and possible solutions. These messages may appear in the Management Tool, from the Server tray service, or during the installation of the Server. Message Cause/Solution If you get the following message in the Management Tool: "Connection with MS SQL database is lost. Please check that the database is accessible and try again." The Server has lost the connection to the MS SQL Server. Please make sure that the MS SQL Server is running and it is online and accessible. To check that the MS SQL Server computer is accessible, enter the following command in the Windows command 182

183 Troubleshooting line: ping <name of the MS SQL Server computer> The connection to the MS SQL Server is blocked by the Firewall. Try disabling the Firewall on the MS SQL Server side. If you get the following message when trying to restart the Server service: Not enough permissions to restart the Server. You can restart the Server service only under the administrator account. If you get the following error while trying to clean up the database: "Error occurred while clearing the database. Please try again." If you get the following message from the Server tray service: "The Server connection with the database has been lost. Click to view logs." The program encountered an unexpected error while trying to clear the database. Try clearing the database again. Make sure the Server service is running. There was a problem with connection to the database. Please make sure that the computer on which the database is installed is online and accessible. To check that the computer is accessible, enter the following command in the Windows command line: ping <name of the computer with installed database> If the problem comes up again, please, send us logs (the Server Service file), which you can find in the Server subfolder of the Ekran System installation folder. The Server has lost the connection to the database. Please make sure that the computer on which the database is installed is online and accessible. To check that the computer is accessible, enter the following command in the Windows command line: ping <name of the computer with installed database> If the problem comes up again, please, send us logs (the Server 183

184 Troubleshooting If you get one of the following messages while trying to perform an action with database: "An error occurred when shrinking database. Please try again." "Error occurred while retrieving database info. Please try again." Service file), which you can find in the Server sub-folder of the Ekran System installation folder. The program encountered an unexpected error while trying to perform an action with database. Please try performing the action again. There was a problem with connection to the database. Please make sure that the computer on which the database is installed is online and accessible. To check that the computer is accessible, enter the following command in the Windows command line: ping <name of the computer with installed database> If the problem comes up again, please, send us logs (the Server Service file), which you can find in the Server sub-folder of the Ekran System installation folder. Management Tool Management Tool Related Issues Issue HTTP 500 Internal Server error is displayed when I try to connect to the Management Tool. Cause/Solution For Windows 7, follow these instructions: 1. Make sure that all the following check boxes are selected in the Windows Features window: Net Framework 3.5> Windows Communication Foundation HTTP Activation and Windows Communication Foundation non-http Activation. 2. Run the Command Prompt (cmd.exe) as administrator: Enter %windir%\microsoft.net\framework\v4.0.xxxxx\ aspnet_regiis.exe iru (for 32 bit machine) or %windir%\microsoft.net\framework64\v4.0.xxx xx\aspnet_regiis.exe iru (for 64 bit machine). 184

185 Troubleshooting Example: C:\Windows\Microsoft.NET\Framework64\v \aspnet_regiis.exe iru 3. Press Enter. For Windows 8.0 or 8.1, make sure that all the following check boxes are selected in the Windows Features window: Net Framework 3.5> Windows Communication Foundation HTTP Activation and Windows Communication Foundation non-http Activation. The license management function is unavailable and I cannot add server/workstation licenses to Clients. I have no Internet connection on the computer with the installed Server and cannot activate serial keys. Make sure you have the administrative Client installation and management permission. If you have this permission, but the license management function is still unavailable, then your copy of the program is not licensed. Please purchase serial keys and activate them online or activate them on your vendor s license site and add them offline. You can activate the serial on the license site of your vendor and then add activated keys on the computer with the installed Server. I have reinstalled/updated the Server and now there are no activated serial keys in it. If you activated serial keys online, after you reinstall or update the Server, activated serial keys will be automatically synchronized. For this purpose, you need to have an active Internet connection during the first start of the Server. If you used an offline activation (added activated serial keys), you need to add them in the Management Tool again. The list of the domain computers is empty during the Client installation. The list of the domain computers is not complete during the Client installation. This problem can be caused by network or Windows issues (e.g., your computer cannot connect to the local network). If there are no network problems, try searching for computers via the Add computers by IP option. To install Clients in such a way, on the Computers without Clients page click Add computers by IP. Ekran System obtains the list of domain computers using standard Windows methods, which do not always provide the full list of computers. 185

186 Troubleshooting The target computer is out of the domain. I have assigned a server license instead of a workstation license to the Client or I have assigned a license to the wrong Client. There are some Clients that I did not install. I do not receive notifications, although the parameters are correct. Some of the Management Tool functions are unavailable. I do not want to provide the user with access to all Clients. I forgot the password of the internal user. The user is able to perform actions that are supposed to be prohibited for him/her (e.g., the user sees the Clients that he/she does not have a permission for). I haven t received any reports or alert notifications by . If DNS settings of your computer network allow, you can: Search for computers using the Add computers by IP option. To install Clients in such a way, on the Computers without Clients page, click Add computers by IP. Create an installation package and install a Client locally on the target computer. To generate an installation package, on the Computers without Clients page, click Download installation file and then select the type of the installation file you want to download. When the installation file is downloaded to your computer, you can start the installation process. Any license can be unassigned from a Client anytime. These may be old Clients that were installed earlier. You can uninstall them remotely via the Management Tool or locally on the Client computer. Make sure you do not use Microsoft Exchange Server 2010, which is not supported. Make sure that you have the corresponding permissions for these functions. By defining the Client permissions for the user in the Management Tool, you can define which Clients the user will have the access to. Contact the administrator and ask him/her to change the password. Check the groups which the user belongs to. He/she might have inherited some new permissions from these groups. Check the Spam folder. 186

187 Troubleshooting Management Tool Error Messages The following table provides the list of error messages that you may see while working in the Management Tool and their causes and possible solutions. Message If you get the following message when trying to connect to the Management Tool: Server is unavailable. Please contact administrator. If you get the following message when trying to connect to the Management Tool: Wrong password or username. Cause/Solution The program encountered an unexpected error while trying to perform an action. Please refresh the Management Tool. Please make sure that the Server is running. Please restart the Server and try again. If the problem comes up again, please contact the support. Please make sure that your login and the password are correct. If you are logging in as a Windows user, do not forget to enter <domain name>\<login>. Viewing Monitored Data Issue Cause/Solution I have successfully logged into the Management Tool but I cannot see any captured data from the Windows Client. An alert event does not trigger an alert notification and is not displayed as alert in the Management Tool. Please check the section Possible Problems with Receiving Data from Clients. Contact the administrator and check if you have the Viewing monitoring results permission for the Client. Please check that the defined alert parameters are correct on the Alert Rules tab on the Edit alert page of the Management Tool (e.g., Process name may be defined instead of Window title). To do this, open the Alert Management page of Management Tool, click Edit alert for the required alert and select the Alert Rules tab. The alert might be disabled. Please make sure the alert is enabled on the Alert properties tab in the Management Tool. I don t receive alert notifications about Please check the Minimal interval between 187

188 Troubleshooting all the events that correspond to notification settings. notifications sent for the same alert event parameter. If less time than defined in the settings has passed since the moment when the last notification for the same alert event had been received, you will not receive the notification. Some screen captures are blank. If a user types something continuously, stops typing, and then switches the window during the 3 seconds 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. Some screen captures look like they consist of two parts. There are two monitors on the Client computer and you see the screen captures from both of them. The Keystrokes field is empty, although the text was entered on the Client computer. Check that you have Viewing keystrokes permission for this Client. Please check that you have enabled the keystroke logging in the Client configuration. The keystrokes are logged only after the user presses Enter or switches to another window. So they might be attached to another screen capture. The screen captures are sent more frequently than I defined. Screen capture image is blurry. The screen capture image is black and white. The screen capture time does not correspond to time on my computer. The screen capture time does not correspond to the time that should be displayed on Client computer. If in the Client configuration you have enabled options other than Capture screen periodically, the screen captures may be created more frequently depending on the user activity. Check the Client configuration. The Client computer may have smooth interface animation the screen capture may have been taken when the animation was in progress. The Client is configured to capture screen in greyscale images. Please check the Client configuration in the Management Tool. The screen capture time corresponds to the time displayed on the Client computer. Please check that the Client computer time settings have not been changed. 188

189 Troubleshooting Windows Client Checking that the Client Is Installed If the Client is successfully installed, it will appear on the Clients page of the Management Tool in the Data View pane. If there is no Client in the Management Tool, you have to check whether the Client has been installed. You can check if the Client is installed on the investigated computer in one of the following ways: The EkranService.exe process is running. The EkranClient and EkranController services are started. There is a <system disk>:\program Files\Ekran System\Ekran System\Client\ folder with executable files. 189

190 Troubleshooting The HKEY_LOCAL_MACHINE\SOFTWARE\EkranSystem\Client key has the following values: 190

191 Troubleshooting Clients Installation/Uninstallation Issues and Error Messages The common reasons of issues with remote installation or uninstallation of Clients are the inadequate network configuration or system settings. If you are sure that a user has administrative rights on the Client computer, please check whether all of the conditions for successful installation are met. Remote Installation Error Messages During remote Client installation you can get the following error messages: The user does not have enough permission on the remote host. The network name cannot be found. Client machine must be rebooted before agent installation. The host is unavailable now or turned off. Try again later. Solving Remote Installation Issues If you receive the following error message during the remote Client installation: The User doesn t have enough permission on the remote host, as a rule, such issue may be caused by the following reasons: There is no access to network shares. DNS service is unavailable. UAC is enabled (Windows 7/8/Vista). Errors in Active Directory. Issues with the Service Principle Name for the domain. Two computers have the same computer name. Issue: There is No Access to Network Shares For successful remote installation, Ekran System needs to access the administrative shares on the target computers. At first, please check that you have access to administrative shares and if there is no access, enable it. How to Check: To check the administrative shares availability, do the following: 1. Open Windows Explorer. 2. In the address bar type \\<target_computer_ip/name>\admin$ and press Enter. 191

192 Troubleshooting 3. When the Enter Network Password window opens, enter administrator credentials and click OK. 4. If the login credentials are accepted, the system folder opens (by default, C:\Windows). If you get an error after performing step 2, try the following: Open the Command Prompt (cmd.exe). Enter and execute the ping <target_computer_name or IP> command. Check the following: 1. If you do not get ping replies, network may be down. Check the network connection and try again. 2. If the network is up, but you do not get the ping reply, check the firewall on the remote computer. Disable the firewall on the target remote computer. If you are receiving ping replies, but the administrative share is still unavailable, check that the Sharing Wizard or the Simple file sharing are disabled. If you are receiving ping replies and the sharing options are good, but you still cannot access the administrative shares, check that the Server system service is running on the remote computer. If you get a login error after performing step 3, try the following: Make sure that the credentials you enter are correct. You have to enter the credentials of a domain administrator or a local administrator account on the remote computer. Verify that the account password is not empty. Accounts with empty passwords cannot be used for remote connection. Try typing the username as <domain_name>\<username> if the remote computer is in a domain, or <computer_name>\<username> if the PC belongs to a workgroup. 192

Desktop Surveillance Help

Desktop Surveillance Help Desktop Surveillance Help Table of Contents About... 9 What s New... 10 System Requirements... 11 Updating from Desktop Surveillance 2.6 to Desktop Surveillance 3.2... 13 Program Structure... 14 Getting

More information

Ekran System v.4.4 Getting Started

Ekran System v.4.4 Getting Started Ekran System v.4.4 Getting Started About Table of Contents About... 4 System Requirements... 5 Program Structure... 7 Getting Started... 8 Server and Database... 9 Installing the Server... 9 Database Types

More information

Issue Tracking Anywhere Installation Guide

Issue Tracking Anywhere Installation Guide TM Issue Tracking Anywhere Installation Guide The leading developer of version control and issue tracking software Table of Contents Introduction...3 Installation Guide...3 Installation Prerequisites...3

More information

User Manual. Onsight Management Suite Version 5.1. Another Innovation by Librestream

User Manual. Onsight Management Suite Version 5.1. Another Innovation by Librestream User Manual Onsight Management Suite Version 5.1 Another Innovation by Librestream Doc #: 400075-06 May 2012 Information in this document is subject to change without notice. Reproduction in any manner

More information

System Administration Training Guide. S100 Installation and Site Management

System Administration Training Guide. S100 Installation and Site Management System Administration Training Guide S100 Installation and Site Management Table of contents System Requirements for Acumatica ERP 4.2... 5 Learning Objects:... 5 Web Browser... 5 Server Software... 5

More information

USER GUIDE WEB-BASED SYSTEM CONTROL APPLICATION. www.pesa.com August 2014 Phone: 256.726.9200. Publication: 81-9059-0703-0, Rev. C

USER GUIDE WEB-BASED SYSTEM CONTROL APPLICATION. www.pesa.com August 2014 Phone: 256.726.9200. Publication: 81-9059-0703-0, Rev. C USER GUIDE WEB-BASED SYSTEM CONTROL APPLICATION Publication: 81-9059-0703-0, Rev. C www.pesa.com Phone: 256.726.9200 Thank You for Choosing PESA!! We appreciate your confidence in our products. PESA produces

More information

WhatsUp Gold v16.1 Installation and Configuration Guide

WhatsUp Gold v16.1 Installation and Configuration Guide WhatsUp Gold v16.1 Installation and Configuration Guide Contents Installing and Configuring Ipswitch WhatsUp Gold v16.1 using WhatsUp Setup Installing WhatsUp Gold using WhatsUp Setup... 1 Security guidelines

More information

Getting Started Guide

Getting Started Guide GFI MailArchiver for Exchange Getting Started Guide By GFI Software Ltd. http://www.gfi.com Email: info@gfi.com Information in this document is subject to change without notice. Companies, names, and

More information

Dovico Timesheet v12 INSTALLATION GUIDE

Dovico Timesheet v12 INSTALLATION GUIDE v12 TABLE OF CONTENTS System Requirements... 1 NEW INSTALLATION... 2 UPGRADE from a previous version of Dovico Timesheet 5 System Requirements Deployment Options Either installed on your server or use

More information

File Share Navigator Online 1

File Share Navigator Online 1 File Share Navigator Online 1 User Guide Service Pack 3 Issued November 2015 Table of Contents What s New in this Guide... 4 About File Share Navigator Online... 5 Components of File Share Navigator Online...

More information

Enterprise Manager. Version 6.2. Installation Guide

Enterprise Manager. Version 6.2. Installation Guide Enterprise Manager Version 6.2 Installation Guide Enterprise Manager 6.2 Installation Guide Document Number 680-028-014 Revision Date Description A August 2012 Initial release to support version 6.2.1

More information

WhatsUp Gold v16.3 Installation and Configuration Guide

WhatsUp Gold v16.3 Installation and Configuration Guide WhatsUp Gold v16.3 Installation and Configuration Guide Contents Installing and Configuring WhatsUp Gold using WhatsUp Setup Installation Overview... 1 Overview... 1 Security considerations... 2 Standard

More information

Installation Guide for Pulse on Windows Server 2012

Installation Guide for Pulse on Windows Server 2012 MadCap Software Installation Guide for Pulse on Windows Server 2012 Pulse Copyright 2014 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software

More information

Installation Instruction STATISTICA Enterprise Server

Installation Instruction STATISTICA Enterprise Server Installation Instruction STATISTICA Enterprise Server Notes: ❶ The installation of STATISTICA Enterprise Server entails two parts: a) a server installation, and b) workstation installations on each of

More information

WhatsUp Gold v16.2 Installation and Configuration Guide

WhatsUp Gold v16.2 Installation and Configuration Guide WhatsUp Gold v16.2 Installation and Configuration Guide Contents Installing and Configuring Ipswitch WhatsUp Gold v16.2 using WhatsUp Setup Installing WhatsUp Gold using WhatsUp Setup... 1 Security guidelines

More information

PC Monitor Enterprise Server. Setup Guide

PC Monitor Enterprise Server. Setup Guide PC Monitor Enterprise Server Setup Guide Prerequisites Server Requirements - Microsoft Windows Server 2008 R2 or 2012-2GB RAM - IIS 7.5 or IIS 8.0 (with ASP.NET 4.0 installed) - Microsoft SQL Server 2008

More information

Installation and Deployment

Installation and Deployment Installation and Deployment Help Documentation This document was auto-created from web content and is subject to change at any time. Copyright (c) 2016 SmarterTools Inc. Installation and Deployment SmarterStats

More information

Intelligent Power Protector User manual extension for Microsoft Virtual architectures: Hyper-V 6.0 Manager Hyper-V Server (R1&R2)

Intelligent Power Protector User manual extension for Microsoft Virtual architectures: Hyper-V 6.0 Manager Hyper-V Server (R1&R2) Intelligent Power Protector User manual extension for Microsoft Virtual architectures: Hyper-V 6.0 Manager Hyper-V Server (R1&R2) Hyper-V Manager Hyper-V Server R1, R2 Intelligent Power Protector Main

More information

NSi Mobile Installation Guide. Version 6.2

NSi Mobile Installation Guide. Version 6.2 NSi Mobile Installation Guide Version 6.2 Revision History Version Date 1.0 October 2, 2012 2.0 September 18, 2013 2 CONTENTS TABLE OF CONTENTS PREFACE... 5 Purpose of this Document... 5 Version Compatibility...

More information

Installation Guide for Pulse on Windows Server 2008R2

Installation Guide for Pulse on Windows Server 2008R2 MadCap Software Installation Guide for Pulse on Windows Server 2008R2 Pulse Copyright 2014 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software

More information

intertrax Suite resource MGR Web

intertrax Suite resource MGR Web intertrax Suite resource MGR Web Resource Management Installation Guide Version 4 2012 Copyright 2003-2012 by Salamander Technologies, Inc. Protected by US Patents 5,573,278; 5,596,652; 5,793,882; 6,761,312;

More information

Installation Notes for Outpost Network Security (ONS) version 3.2

Installation Notes for Outpost Network Security (ONS) version 3.2 Outpost Network Security Installation Notes version 3.2 Page 1 Installation Notes for Outpost Network Security (ONS) version 3.2 Contents Installation Notes for Outpost Network Security (ONS) version 3.2...

More information

Sharp Remote Device Manager (SRDM) Server Software Setup Guide

Sharp Remote Device Manager (SRDM) Server Software Setup Guide Sharp Remote Device Manager (SRDM) Server Software Setup Guide This Guide explains how to install the software which is required in order to use Sharp Remote Device Manager (SRDM). SRDM is a web-based

More information

Installing and Configuring WhatsUp Gold

Installing and Configuring WhatsUp Gold Installing and Configuring WhatsUp Gold This guide provides information about installing and configuring WhatsUp Gold v14.2, including instructions on how to run the WhatsUp web interface through an Internet

More information

Dell UPS Local Node Manager USER'S GUIDE EXTENSION FOR MICROSOFT VIRTUAL ARCHITECTURES Dellups.com

Dell UPS Local Node Manager USER'S GUIDE EXTENSION FOR MICROSOFT VIRTUAL ARCHITECTURES Dellups.com CHAPTER: Introduction Microsoft virtual architecture: Hyper-V 6.0 Manager Hyper-V Server (R1 & R2) Hyper-V Manager Hyper-V Server R1, Dell UPS Local Node Manager R2 Main Operating System: 2008Enterprise

More information

Cloud Services ADM. Agent Deployment Guide

Cloud Services ADM. Agent Deployment Guide Cloud Services ADM Agent Deployment Guide 10/15/2014 CONTENTS System Requirements... 1 Hardware Requirements... 1 Installation... 2 SQL Connection... 4 AD Mgmt Agent... 5 MMC... 7 Service... 8 License

More information

ez Agent Administrator s Guide

ez Agent Administrator s Guide ez Agent Administrator s Guide Copyright This document is protected by the United States copyright laws, and is proprietary to Zscaler Inc. Copying, reproducing, integrating, translating, modifying, enhancing,

More information

Table of Contents. Introduction...9. Installation...17. Program Tour...31. The Program Components...10 Main Program Features...11

Table of Contents. Introduction...9. Installation...17. Program Tour...31. The Program Components...10 Main Program Features...11 2011 AdRem Software, Inc. This document is written by AdRem Software and represents the views and opinions of AdRem Software regarding its content, as of the date the document was issued. The information

More information

NETWRIX FILE SERVER CHANGE REPORTER

NETWRIX FILE SERVER CHANGE REPORTER NETWRIX FILE SERVER CHANGE REPORTER ADMINISTRATOR S GUIDE Product Version: 3.3 April/2012. Legal Notice The information in this publication is furnished for information use only, and does not constitute

More information

Table of Contents. CHAPTER 1 About This Guide... 9. CHAPTER 2 Introduction... 11. CHAPTER 3 Database Backup and Restoration... 15

Table of Contents. CHAPTER 1 About This Guide... 9. CHAPTER 2 Introduction... 11. CHAPTER 3 Database Backup and Restoration... 15 Table of Contents CHAPTER 1 About This Guide......................... 9 The Installation Guides....................................... 10 CHAPTER 2 Introduction............................ 11 Required

More information

Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010

Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010 Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010 This document describes the different types of Unisphere management stations and tells how to install

More information

Active Directory Management. Agent Deployment Guide

Active Directory Management. Agent Deployment Guide Active Directory Management Agent Deployment Guide Document Revision Date: April 26, 2013 Active Directory Management Deployment Guide i Contents System Requirements... 1 Hardware Requirements... 2 Agent

More information

[The BSD License] Copyright (c) 2004-2011 Jaroslaw Kowalski jaak@jkowalski.net

[The BSD License] Copyright (c) 2004-2011 Jaroslaw Kowalski jaak@jkowalski.net Software used by portions of this application require the following license statement: [The BSD License] Copyright (c) 2004-2011 Jaroslaw Kowalski jaak@jkowalski.net All rights reserved. Redistribution

More information

NETWRIX PASSWORD MANAGER

NETWRIX PASSWORD MANAGER NETWRIX PASSWORD MANAGER ADMINISTRATOR S GUIDE Product Version: 6.1 February/2012 Legal Notice The information in this publication is furnished for information use only, and does not constitute a commitment

More information

NETWRIX USER ACTIVITY VIDEO REPORTER

NETWRIX USER ACTIVITY VIDEO REPORTER NETWRIX USER ACTIVITY VIDEO REPORTER ADMINISTRATOR S GUIDE Product Version: 1.0 January 2013. Legal Notice The information in this publication is furnished for information use only, and does not constitute

More information

Migrating TimeForce To A New Server

Migrating TimeForce To A New Server Rev. 4/28/14 Migrating TimeForce To A New Server Table of Contents 1. Installation Prerequisites... 2 Required... 2 Recommended... 3 2. Update to a Migration Compatible Version... 3 Determine the Database

More information

XenDesktop Implementation Guide

XenDesktop Implementation Guide Consulting Solutions WHITE PAPER Citrix XenDesktop XenDesktop Implementation Guide Pooled Desktops (Local and Remote) www.citrix.com Contents Contents... 2 Overview... 4 Initial Architecture... 5 Installation

More information

Installing GFI MailSecurity

Installing GFI MailSecurity Installing GFI MailSecurity Introduction This chapter explains how to install and configure GFI MailSecurity. You can install GFI MailSecurity directly on your mail server or you can choose to install

More information

Portions of this product were created using LEADTOOLS 1991-2009 LEAD Technologies, Inc. ALL RIGHTS RESERVED.

Portions of this product were created using LEADTOOLS 1991-2009 LEAD Technologies, Inc. ALL RIGHTS RESERVED. Installation Guide Lenel OnGuard 2009 Installation Guide, product version 6.3. This guide is item number DOC-110, revision 1.038, May 2009 Copyright 1992-2009 Lenel Systems International, Inc. Information

More information

Sophos for Microsoft SharePoint startup guide

Sophos for Microsoft SharePoint startup guide Sophos for Microsoft SharePoint startup guide Product version: 2.0 Document date: March 2011 Contents 1 About this guide...3 2 About Sophos for Microsoft SharePoint...3 3 System requirements...3 4 Planning

More information

CTERA Agent for Mac OS-X

CTERA Agent for Mac OS-X User Guide CTERA Agent for Mac OS-X September 2013 Version 4.0 Copyright 2009-2013 CTERA Networks Ltd. All rights reserved. No part of this document may be reproduced in any form or by any means without

More information

@ptitude Observer. Installation Manual. Part No. 32170700 Revision G

@ptitude Observer. Installation Manual. Part No. 32170700 Revision G Part No. 32170700 Revision G Installation Manual Copyright 2012 by SKF Reliability Systems All rights reserved. Aurorum 30, 977 75 Lulea Sweden Telephone: +46 (0) 31 337 10 00, Fax: +46 (0) 920 134 40

More information

Juris Suite 2.6. Upgrade Guide

Juris Suite 2.6. Upgrade Guide Juris Suite 2.6 Upgrade Guide Table of Contents Introduction... 3 Upgrading Summary... 3 1 Upgrades from MyJuris 1.1 and JurisSuite Pre-2405... 3 Upgrades from 2405 and above versions of JurisSuite...

More information

SafeGuard Enterprise Installation Best Practice

SafeGuard Enterprise Installation Best Practice SafeGuard Enterprise Installation Best Practice Product Version: 7 Document date: December 2014 Contents www.utimaco.c om Introduction... 4 Technical prerequisites... 5 Installation order... 6 1. Installing

More information

Pro-Watch Software Suite Installation Guide. 2013 Honeywell Release 4.1

Pro-Watch Software Suite Installation Guide. 2013 Honeywell Release 4.1 Pro-Watch Software Suite Release 4.1 Installation Guide Document 7-901073V2 Pro-Watch Software Suite Installation Guide 2013 Honeywell Release 4.1 Copyright 2013 Honeywell. All rights reserved. Pro-Watch

More information

Tharo Systems, Inc. 2866 Nationwide Parkway P.O. Box 798 Brunswick, OH 44212 USA Tel: 330.273.4408 Fax: 330.225.0099

Tharo Systems, Inc. 2866 Nationwide Parkway P.O. Box 798 Brunswick, OH 44212 USA Tel: 330.273.4408 Fax: 330.225.0099 Introduction EASYLABEL 6 has several new features for saving the history of label formats. This history can include information about when label formats were edited and printed. In order to save this history,

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

TECHNICAL DOCUMENTATION SPECOPS DEPLOY / APP 4.7 DOCUMENTATION

TECHNICAL DOCUMENTATION SPECOPS DEPLOY / APP 4.7 DOCUMENTATION TECHNICAL DOCUMENTATION SPECOPS DEPLOY / APP 4.7 DOCUMENTATION Contents 1. Getting Started... 4 1.1 Specops Deploy Supported Configurations... 4 2. Specops Deploy and Active Directory...5 3. Specops Deploy

More information

AvePoint Meetings 3.2.2 for SharePoint On-Premises. Installation and Configuration Guide

AvePoint Meetings 3.2.2 for SharePoint On-Premises. Installation and Configuration Guide AvePoint Meetings 3.2.2 for SharePoint On-Premises Installation and Configuration Guide Issued August 2015 Table of Contents About AvePoint Meetings for SharePoint... 4 System Requirements... 5 2 System

More information

GFI Product Manual. Web security, monitoring and Internet access control. Administrator Guide

GFI Product Manual. Web security, monitoring and Internet access control. Administrator Guide GFI Product Manual Web security, monitoring and Internet access control Administrator Guide The information and content in this document is provided for informational purposes only and is provided "as

More information

Magaya Software Installation Guide

Magaya Software Installation Guide Magaya Software Installation Guide MAGAYA SOFTWARE INSTALLATION GUIDE INTRODUCTION Introduction This installation guide explains the system requirements for installing any Magaya software, the steps to

More information

Legal Notes. Regarding Trademarks. 2013 KYOCERA Document Solutions Inc.

Legal Notes. Regarding Trademarks. 2013 KYOCERA Document Solutions Inc. Legal Notes Unauthorized reproduction of all or part of this guide is prohibited. The information in this guide is subject to change without notice. We cannot be held liable for any problems arising from

More information

GUARD1 PLUS SE Administrator's Manual

GUARD1 PLUS SE Administrator's Manual GUARD1 PLUS SE Administrator's Manual Version 4.4 30700 Bainbridge Road Solon, Ohio 44139 Phone 216-595-0890 Fax 216-595-0991 info@guard1.com www.guard1.com i 2010 TimeKeeping Systems, Inc. GUARD1 PLUS

More information

Quick Start Guide for VMware and Windows 7

Quick Start Guide for VMware and Windows 7 PROPALMS VDI Version 2.1 Quick Start Guide for VMware and Windows 7 Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the

More information

Web Deployment on Windows 2012 Server. Updated: August 28, 2013

Web Deployment on Windows 2012 Server. Updated: August 28, 2013 Web Deployment on Windows 2012 Server Updated: August 28, 2013 Table of Contents Install IIS on Windows 2012... 3 Install Sage 300 ERP...16 Create Web Deployment User...17 Sage 300 ERP Services...22 Web

More information

INSTALLING MICROSOFT SQL SERVER AND CONFIGURING REPORTING SERVICES

INSTALLING MICROSOFT SQL SERVER AND CONFIGURING REPORTING SERVICES INSTALLING MICROSOFT SQL SERVER AND CONFIGURING REPORTING SERVICES TECHNICAL ARTICLE November 2012. Legal Notice The information in this publication is furnished for information use only, and does not

More information

STATISTICA VERSION 12 STATISTICA ENTERPRISE SMALL BUSINESS INSTALLATION INSTRUCTIONS

STATISTICA VERSION 12 STATISTICA ENTERPRISE SMALL BUSINESS INSTALLATION INSTRUCTIONS STATISTICA VERSION 12 STATISTICA ENTERPRISE SMALL BUSINESS INSTALLATION INSTRUCTIONS Notes 1. The installation of STATISTICA Enterprise Small Business entails two parts: a) a server installation, and b)

More information

LifeSize Control Installation Guide

LifeSize Control Installation Guide LifeSize Control Installation Guide April 2005 Part Number 132-00001-001, Version 1.0 Copyright Notice Copyright 2005 LifeSize Communications. All rights reserved. LifeSize Communications has made every

More information

STATISTICA VERSION 10 STATISTICA ENTERPRISE SERVER INSTALLATION INSTRUCTIONS

STATISTICA VERSION 10 STATISTICA ENTERPRISE SERVER INSTALLATION INSTRUCTIONS Notes: STATISTICA VERSION 10 STATISTICA ENTERPRISE SERVER INSTALLATION INSTRUCTIONS 1. The installation of the STATISTICA Enterprise Server entails two parts: a) a server installation, and b) workstation

More information

Spector 360 Deployment Guide. Version 7

Spector 360 Deployment Guide. Version 7 Spector 360 Deployment Guide Version 7 December 11, 2009 Table of Contents Deployment Guide...1 Spector 360 DeploymentGuide... 1 Installing Spector 360... 3 Installing Spector 360 Servers (Details)...

More information

Product Manual. Administration and Configuration Manual

Product Manual. Administration and Configuration Manual Product Manual Administration and Configuration Manual http://www.gfi.com info@gfi.com The information and content in this document is provided for informational purposes only and is provided "as is" with

More information

Installing and Configuring vcenter Multi-Hypervisor Manager

Installing and Configuring vcenter Multi-Hypervisor Manager Installing and Configuring vcenter Multi-Hypervisor Manager vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.1 This document supports the version of each product listed and supports all subsequent

More information

Active Directory Management. Agent Deployment Guide

Active Directory Management. Agent Deployment Guide Active Directory Management Agent Deployment Guide Document Revision Date: June 12, 2014 Active Directory Management Deployment Guide i Contents System Requirements...1 Hardware Requirements...1 Installation...3

More information

Juris and Juris Suite 2.5 Service Pack 2. Installation Guide

Juris and Juris Suite 2.5 Service Pack 2. Installation Guide Juris and Juris Suite 2.5 Service Pack 2 Installation Guide Table of Contents Introduction... 2 Planning and Preparation... 2 System Requirements... 2 Server Required Pre-Install Items... 2 Servers Running

More information

DocAve 6 Service Pack 1

DocAve 6 Service Pack 1 DocAve 6 Service Pack 1 Installation Guide Revision C Issued September 2012 1 Table of Contents About the Installation Guide... 4 Submitting Documentation Feedback to AvePoint... 4 Before You Begin...

More information

CTERA Agent for Linux

CTERA Agent for Linux User Guide CTERA Agent for Linux September 2013 Version 4.0 Copyright 2009-2013 CTERA Networks Ltd. All rights reserved. No part of this document may be reproduced in any form or by any means without written

More information

SysPatrol - Server Security Monitor

SysPatrol - Server Security Monitor SysPatrol Server Security Monitor User Manual Version 2.2 Sep 2013 www.flexense.com www.syspatrol.com 1 Product Overview SysPatrol is a server security monitoring solution allowing one to monitor one or

More information

NETWRIX WINDOWS SERVER CHANGE REPORTER

NETWRIX WINDOWS SERVER CHANGE REPORTER NETWRIX WINDOWS SERVER CHANGE REPORTER INSTALLATION AND CONFIGURATION GUIDE Product Version: 4.0 March 2013. Legal Notice The information in this publication is furnished for information use only, and

More information

Live Maps. for System Center Operations Manager 2007 R2 v6.2.1. Installation Guide

Live Maps. for System Center Operations Manager 2007 R2 v6.2.1. Installation Guide Live Maps for System Center Operations Manager 2007 R2 v6.2.1 Installation Guide CONTENTS Contents... 2 Introduction... 4 About This Guide... 4 Supported Products... 4 Understanding Live Maps... 4 Live

More information

Installation Instruction STATISTICA Enterprise Small Business

Installation Instruction STATISTICA Enterprise Small Business Installation Instruction STATISTICA Enterprise Small Business Notes: ❶ The installation of STATISTICA Enterprise Small Business entails two parts: a) a server installation, and b) workstation installations

More information

Quick Start Guide for Parallels Virtuozzo

Quick Start Guide for Parallels Virtuozzo PROPALMS VDI Version 2.1 Quick Start Guide for Parallels Virtuozzo Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the current

More information

NeuralStar Installation Guide

NeuralStar Installation Guide NeuralStar Installation Guide Version 9.8 Release 2 October 2011 1st Edition Preface Software License Agreement Software is defined as the Kratos Technology & Training Solutions, Inc. computer programs

More information

MCTS Guide to Microsoft Windows Server 2008 Applications Infrastructure Configuration (Exam # 70-643)

MCTS Guide to Microsoft Windows Server 2008 Applications Infrastructure Configuration (Exam # 70-643) MCTS Guide to Microsoft Windows Server 2008 Applications Infrastructure Configuration (Exam # 70-643) Chapter Six Configuring Windows Server 2008 Web Services, Part 1 Objectives Create and configure Web

More information

CTERA Agent for Windows

CTERA Agent for Windows User Guide CTERA Agent for Windows May 2012 Version 3.1 Copyright 2009-2012 CTERA Networks Ltd. All rights reserved. No part of this document may be reproduced in any form or by any means without written

More information

PaperPort PSP Server 3 SERVER ADMINISTRATOR S GUIDE

PaperPort PSP Server 3 SERVER ADMINISTRATOR S GUIDE PaperPort PSP Server 3 SERVER ADMINISTRATOR S GUIDE 1. Third party licenses and notices 5 2. Welcome 6 3. Installation requirements 7 3.1. System requirements 7 3.2. Installing prerequisites 7 3.3. Pre-installation

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

TANDBERG MANAGEMENT SUITE 10.0

TANDBERG MANAGEMENT SUITE 10.0 TANDBERG MANAGEMENT SUITE 10.0 Installation Manual Getting Started D12786 Rev.16 This document is not to be reproduced in whole or in part without permission in writing from: Contents INTRODUCTION 3 REQUIREMENTS

More information

Veeam Backup Enterprise Manager. Version 7.0

Veeam Backup Enterprise Manager. Version 7.0 Veeam Backup Enterprise Manager Version 7.0 User Guide August, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may

More information

Sophos Mobile Control Installation guide. Product version: 3.5

Sophos Mobile Control Installation guide. Product version: 3.5 Sophos Mobile Control Installation guide Product version: 3.5 Document date: July 2013 Contents 1 Introduction...3 2 The Sophos Mobile Control server...4 3 Set up Sophos Mobile Control...10 4 External

More information

Installation & Configuration Guide

Installation & Configuration Guide Installation & Configuration Guide Bluebeam Studio Enterprise ( Software ) 2014 Bluebeam Software, Inc. All Rights Reserved. Patents Pending in the U.S. and/or other countries. Bluebeam and Revu are trademarks

More information

NETWRIX ACCOUNT LOCKOUT EXAMINER

NETWRIX ACCOUNT LOCKOUT EXAMINER NETWRIX ACCOUNT LOCKOUT EXAMINER ADMINISTRATOR S GUIDE Product Version: 4.1 July 2014. Legal Notice The information in this publication is furnished for information use only, and does not constitute a

More information

Software Installation Requirements

Software Installation Requirements Software Installation Guide PrintIQ TM Software Installation Requirements Please use the following guide to ensure that you're meeting all requirements prior to installing the PrintIQ TM Xerox Device Agent

More information

Installation Instructions Release Version 15.0 January 30 th, 2011

Installation Instructions Release Version 15.0 January 30 th, 2011 Release Version 15.0 January 30 th, 2011 ARGUS Software: ARGUS Valuation - DCF The contents of this document are considered proprietary by ARGUS Software, the information enclosed and any portion thereof

More information

Quick Install Guide. Lumension Endpoint Management and Security Suite 7.1

Quick Install Guide. Lumension Endpoint Management and Security Suite 7.1 Quick Install Guide Lumension Endpoint Management and Security Suite 7.1 Lumension Endpoint Management and Security Suite - 2 - Notices Version Information Lumension Endpoint Management and Security Suite

More information

Central Management System

Central Management System Central Management System Software Installation Guide Ver. 1.5.0.101115.001 ... ii System Introduction... 3 Client/Server Architecture...3 System Requirements... 4 System Setup...4 Multiple Monitor Configuration...5

More information

Dell SupportAssist Version 2.0 for Dell OpenManage Essentials Quick Start Guide

Dell SupportAssist Version 2.0 for Dell OpenManage Essentials Quick Start Guide Dell SupportAssist Version 2.0 for Dell OpenManage Essentials Quick Start Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer.

More information

Nexio Connectus with Nexio G-Scribe

Nexio Connectus with Nexio G-Scribe Nexio Connectus with Nexio G-Scribe 2.1.2 3/20/2014 Edition: A 2.1.2 Publication Information 2014 Imagine Communications. Proprietary and Confidential. Imagine Communications considers this document and

More information

Konica Minolta s Optimised Print Services (OPS)

Konica Minolta s Optimised Print Services (OPS) Konica Minolta s Optimised Print Services (OPS) Document Collection Agent (DCA) Detailed Installation Guide V1.6 Page 1 of 43 Table of Contents Notes... 4 Requirements... 5 Network requirements... 5 System

More information

NETWRIX EVENT LOG MANAGER

NETWRIX EVENT LOG MANAGER NETWRIX EVENT LOG MANAGER QUICK-START GUIDE FOR THE ENTERPRISE EDITION Product Version: 4.0 July/2012. Legal Notice The information in this publication is furnished for information use only, and does not

More information

SYSTEM REQUIREMENTS...3

SYSTEM REQUIREMENTS...3 Contents INTRODUCTION...1 Web Suite Setup Checklist... 2 SYSTEM REQUIREMENTS...3 SERVER REQUIREMENTS... 3 Hardware Requirements... 3 Software Requirements... 3 CLIENT/WORKSTATION REQUIREMENTS... 5 Hardware

More information

Reconfiguring VMware vsphere Update Manager

Reconfiguring VMware vsphere Update Manager Reconfiguring VMware vsphere Update Manager vsphere Update Manager 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

Remote Drive PC Client software User Guide

Remote Drive PC Client software User Guide Remote Drive PC Client software User Guide -Page 1 of 27- PRIVACY, SECURITY AND PROPRIETARY RIGHTS NOTICE: The Remote Drive PC Client software is third party software that you can use to upload your files

More information

HELIX MEDIA LIBRARY INSTALL GUIDE FOR WINDOWS SERVER 2003 Helix Media Library Version 1.1. Revision Date: July 2011

HELIX MEDIA LIBRARY INSTALL GUIDE FOR WINDOWS SERVER 2003 Helix Media Library Version 1.1. Revision Date: July 2011 HELIX MEDIA LIBRARY INSTALL GUIDE FOR WINDOWS SERVER 2003 Helix Media Library Version 1.1 Revision Date: July 2011 Summary of Contents Summary of Contents... 2 Pre Installation Checklist... 4 Prerequisites...

More information

Velocity Web Services Client 1.0 Installation Guide and Release Notes

Velocity Web Services Client 1.0 Installation Guide and Release Notes Velocity Web Services Client 1.0 Installation Guide and Release Notes Copyright 2014-2015, Identiv. Last updated June 24, 2015. Overview This document provides the only information about version 1.0 of

More information

File Auditor for NAS, Net App Edition

File Auditor for NAS, Net App Edition File Auditor for NAS, Net App Edition Installation Guide Revision 1.2 - July 2015 This guide provides a short introduction to the installation and initial configuration of NTP Software File Auditor for

More information

CTERA Agent for Windows

CTERA Agent for Windows User Guide CTERA Agent for Windows September 2013 Version 4.0 Copyright 2009-2013 CTERA Networks Ltd. All rights reserved. No part of this document may be reproduced in any form or by any means without

More information

Wavecrest Certificate

Wavecrest Certificate Wavecrest InstallationGuide Wavecrest Certificate www.wavecrest.net Copyright Copyright 1996-2015, Wavecrest Computing, Inc. All rights reserved. Use of this product and this manual is subject to license.

More information

Bitrix Site Manager ASP.NET. Installation Guide

Bitrix Site Manager ASP.NET. Installation Guide Bitrix Site Manager ASP.NET Installation Guide Contents Introduction... 4 Chapter 1. Checking for IIS Installation... 5 Chapter 2. Using An Archive File to Install Bitrix Site Manager ASP.NET... 7 Preliminary

More information

GFI Product Manual. Administrator Guide

GFI Product Manual. Administrator Guide GFI Product Manual Administrator Guide The information and content in this document is provided for informational purposes only and is provided "as is" with no warranty of any kind, either express or implied,

More information

Medtech Clinical Audit Tool Installation Guide

Medtech Clinical Audit Tool Installation Guide Medtech Clinical Audit Tool Installation Guide These Release Notes contain important information for all Medtech Users. Please ensure that they are circulated amongst all your staff. We suggest that these

More information