Cyclope Clients Deployment |  |
For this version of Cyclope there are 3 different client applications: CyclopeClient (the setup is located in \Setups\CyclopeClient\CyclopeClientSetup.exe folder) CyclopeDLLClient (the setup is located in \Setups\CyclopeClient\CyclopeDLLClientSetup.exe folder) CyclopeNETClient (executable file in located in the \Setups\CyclopeClient\CyclopeNetClient.exe folder). All client applications have the same monitoring features but there are differences in the deployment manner. The CyclopeClient and CyclopeDLLClient must be installed on each machine you want to monitor using the setup CyclopeClientSetup.exe or CyclopeDLLClientSetup.exe. The NET Client CyclopeNETClient.exe can be included in the network logon scripts. More details about this are available on this page. CyclopeClient The setup file can be copied on a removable storage or a network share from where the administrator can install it on the computer that you want to monitor. After you run the setup you must agree to install Cyclope Client, The Welcome Dialog - you must press Next button in order to continue. You can select the Installation Folder (default C:\Program Files\Cyclope Client). Now the setup is ready to install Cyclope Client - you must press Install button in order to continue. Setup will run in a few seconds and at the end Cyclope Client Configuration will be launched (please do not uncheck this check box). Press Finish button and the Cyclope Client Configuration will be launched. Configure Cyclope Client There if only a mandatory field that you must complete - The name of the server or the IP address of the server - on which you have installed Cyclope Server on Step 1. The Server Port default value is 7879. Test if the client can connect to the server by pressing Test Server Connection button. You should obtain this message. Monitoring Precision means how often the client application is logging user activity and Server Connectivity means how often the client application sends the user activity report to the server. The default value for Monitoring Precision is 3 (seconds) but you can change it to 1 (second) if you want the highest precision. The default value for Server Connectivity is 10 (minutes) but you can change it to 1, 2 or 3 (minutes) for a better connectivity. The Automatic Run at Start Up option is default checked and starts Cyclope Client each tine the machine restarts or there is a user switch (a new log on). In order to verify this you can run Manager and view the list of processes. There should be a process named CyclopeClient.exe like in the image attached. CyclopeDLLClient The setup file can be copied on a removable storage or a network share from where the administrator can install it on the computer that you want to monitor. The CyclopeClient and CyclopeDLLClient are identical. The deployment method is the same and the parameters for configuring the monitoring options are also similar. The difference is that CyclopeDLLClient is using the RunDll32 to run, like in the picture below: We use this technique for “hiding” the client application. Since CyclopeClient.exe is a detectable by the users in Task Manager. The RunDll32 is less known by users and also there is the chance that other applications are running using this RunDll32. Basically it is up to you to decide which version of the Cyclope Client you want to deploy. CyclopeNETClient There is a set of parameters that must be used with the NET client in order to configure it with the monitoring values you want. The parameters are: "-cfg=[srv=CYLOPE_SERVER&srvport=CYLOPE_SERVER_PORT&pre=PRECISION&conn=CONNECTIVITY]" Those parameters are identical with the one used by Cyclope Client Configuration. The CyclopeNETClient may be started each time a user logs on, by using a GPO (Group Policy Object). To create this: 1) A GPO has to be linked to an OU (Organizational Unit). - In Active Directory Users and Computers, right click the OU and select Properties. - In the group Policy Tab a new GPO may be created for the OU or an existing unlinked Gpo may be linked to the current OU. 2) Click Edit to edit the GPO Properties or open a MMC with the wanted Gpo snap-in. 3) Under User Configuration, expand Windows Settings, click Scripts (Logon/Logoff) and double click Logon. 4) Click Add.. and Browse to a script (from a share or from the local computer) that starts an application. The script is written in Windows Script Host. Each time a user that has the GPO – linked, logs on, the application is started. Example of the script: winScript.vbs Set WshShell = Wscript.CreateObject(“Wscript.Shell”) WshShell.run "\\NetworkShare\CyclopeNETClient.exe "-cfg=[srv=CYLOPE_SERVER&srvport=CYLOPE_SERVER_PORT&pre=PRECISION&conn=CONNECTIVITY]"" CyclopeNETClient.exe si located in Setups/CyclopeClient Folder.