6/12/2023 0 Comments Eset endpoint security key 2014You can use any of the following methods to activate ESET Endpoint Security: To activate your copy of ESET Endpoint Security directly from the program, open the ESET Endpoint Security main program window and in the main menu, click Help and support > Activate product or Protection status > Activate product. Availability of a particular activation scenario in the activation window may vary depending on the country, and the means of distribution (ESET web page, installer type. There are several methods for activating your product. I don't see anything related with my problem here? I hope that I've described my situation (I'm working in mixed environment - the computers that are not on AD but are on the Local Area Network are seen on the dashboard as unmanaged, but computers that are connecting trough VPN (they are not on the AD too) are not seen even as Unmanaged).After installation is complete, you will be prompted to activate your product. Performance Indicator Value Up time 1679:15:49 Kernel time 13627 sec., 0.2 % of up time User time 16650 sec., 0.3 % of up time Memory private usage 267 MB Memory working set 245 MB Memory peak working set 474 MB Available physical memory 3779 MB Total I/O reads 40499290 KB Total I/O writes 39466283 KB Total I/O others 4183104 KB Agent peer certificate with subject 'CN=Agent at *, OU=Intercomgroup, O=Intercomgroup, L=bg, S=Bulgaria, C=BG' issued by 'CN=Server Certification Authority, OU=Intercomgroup, O=Intercomgroup, L=bg, S=Bulgaria, C=BG' with serial number '01047e142548244f9db379482c8c52e4a501' is and will be valid in 30 days.Status log Scope Time Text Last replication 2016-Oct-18 15:55:33 OK Last successful replication 2016-Oct-18 15:55:33 OK As I'm still trying and learning ERA6 is this the status.html you meant? "C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html" My guess would be, that a wrong "public" hostname was entered, or your "public" hostname is not correctly set in your server certificate. The error should tell you, what is the issue with replication. What you should do, is to check the "status.html" located in ESET RemoteAdministrator folder of Program Data / ESET. That would explain that nothing gets applied, and that they are not visible on the dashboard when they are synced from AD / imported they are seen as "unmanaged" (unmanaged = without ERA agent). Hello, it seems to me, that your ERA agents are not connecting to the server, in case they are connected via VPN. Has someone interracted with this situation? When I add the remote computer to the All Computers group manually it adds, but I cannot see no details of it and even if I try to create task to deploy agent (even that with the custom made installer it is already installed) it fails. I have generated an installer with my custom settings in it (get updates from the era server and some other stuff), which works fine on the computers connected to the LAN network - setting are applying, but when I run the same installer on a computer connecting trough VPN to the LAN network where the Era server is located, none of my settings applies, neither updating trough the Proxy server (the Era server). All of the computers that are on the DC have appeared on the dashboard of Era Console, but none of the computers that are connecting to the Era Server trough VPN's are on the dashboard. We're working in mixed environment (Domain controller and non managed computers). Please excuse me if there's an answer of this, but I have the following problem.
0 Comments
Leave a Reply. |