Jump to content

verus

Members
  • Posts

    49
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by verus

  1. I opened a ticket but no reaction yet from support@mgk.lu Never had a good experience with them. Any other support I can contact?
  2. Hi, I have the following installation: ESET Security Management Center (Server), Version 7.0 (7.0.577.0) ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) But when I check the installed applications I see this: ESET Endpoint Antivirus ESET, spol. s r.o. 6.1.2109.0 1 ESET Endpoint Antivirus ESET, spol. s r.o. 6.1.2222.0 16 ESET Endpoint Antivirus ESET, spol. s r.o. 6.1.2227.0 2 ESET Endpoint Antivirus ESET, spol. s r.o. 6.2.2021.0 13 ESET Endpoint Antivirus ESET, spol. s r.o. 6.2.2033.0 1 ESET Endpoint Antivirus ESET, spol. s r.o. 6.4.2014.0 6 ESET Endpoint Antivirus ESET, spol. s r.o. 6.5.2094.0 11 ESET Endpoint Antivirus ESET, spol. s r.o. 6.5.2107.1 3 ESET Endpoint Antivirus ESET, spol. s r.o. 6.5.2132.2 2 ESET Endpoint Antivirus ESET, spol. s r.o. 6.6.2052.0 1 ESET Endpoint Antivirus ESET, spol. s r.o. 6.6.2072.4 5 ESET Endpoint Antivirus ESET, spol. s r.o. 6.6.2078.5 2 ESET Endpoint Antivirus ESET, spol. s r.o. 7.0.2073.1 4 ESET Endpoint Antivirus ESET, spol. s r.o. 7.0.2091.0 3 ESET Endpoint Antivirus ESET, spol. s r.o. 7.0.2100.4 15 ESET Endpoint Antivirus ESET, spol. s r.o. 7.1.2045.5 89 ESET Endpoint Antivirus ESET, spol. s r.o. 7.1.2053.0 8 ESET File Security ESET, spol. s r.o. 6.4.12002.0 1 ESET File Security ESET, spol. s r.o. 6.5.12010.0 1 ESET File Security ESET, spol. s r.o. 7.0.12018.0 6 ESET Management Agent ESET, spol. s r.o. 7.0.553.0 45 ESET Management Agent ESET, spol. s r.o. 7.0.577.0 129 ESET Remote Administrator Agent ESET, spol. s r.o. 6.1.265.0 1 ESET Remote Administrator Agent ESET, spol. s r.o. 6.1.365.0 6 ESET Remote Administrator Agent ESET, spol. s r.o. 6.1.444.0 1 ESET Remote Administrator Agent ESET, spol. s r.o. 6.2.190.0 1 ESET Remote Administrator Agent ESET, spol. s r.o. 6.5.522.0 13 ESET Remote Administrator Mobile Device Connector ESET, spol. s r.o. 6.1.402.0 1 ESET Remote Administrator Server ESET, spol. s r.o. 6.1.365.0 1 ESET Rogue Detection Sensor ESET, spol. s r.o. 1.0.817.0 1 ESET Rogue Detection Sensor ESET, spol. s r.o. 1.1.693.0 1 ESET Security Management Center Mobile Device Connector ESET, spol. s r.o. 7.0.416.0 1 ESET Security Management Center Server ESET, spol. s r.o. 7.0.577.0 1 Why is server version 6.1 in this list? I already upgraded to the latest version (Management center server 7.0.577.0). Also, in the gui when I click HELP ==> UPDATE PRODUCT, I get: Failed to create task: The referenced repository package is not available And when I check the changelog in that update window, I get: Version 6.5.34.0 (compared to 6.5.31.0 released on March 14,2017) Changed: New Apache Tomcat 7.0.82 that includes fixed security vulnerabilities Changed: New Apache HTTP Proxy 2.4.28.0 that includes fixed security vulnerabilities Changed: New Mirror Tool that allows creation of mirror for ESET Endpoint Security and ESET Endpoint Antivirus 6.6 Changed: Increased the maximum number of concurrent ESET Virtualization Security connections to 200 Fixed: ESET Mobile Device Connector to ERA Server connectivity issues (when mobile devices were functioning correctly, however connection to ERA server was interrupted, and data in ERA Web Console was not updated) Fixed: Rare database write failures when the database server is overloaded Fixed: Increase in MultiAgent startup time Fixed: False MultiAgent overload report What is wrong here? Do I have the latest version or not? This is so unclear in ESET....
  3. @ESET, The link doesn't work and if I search for it I get this: hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3734 That is for Remote Administrator SERVER but is there an article for UPGRADING the AGENT on all the clients ? Is so, what is the link ? thanks.
  4. Hi, I have ESET 6.1.282.0 with policies for my users and in that policy I have a profile MY PROFILE (the default one you can't delete or rename...) and I want to make another profile so that my users can CHOOSE what profile they want to use but this seems impossible. When I EDIT the list of profiles and I add another one, then the "selected profiles" and "list of profiles" selection gets APPLIED and as soon as it is APPLIED, the user can't choose a profile. So I disagree and I push the BIN icon and then I select my new profile and push FINISH. After that when I edit this policy again and I check the profiles, they are all gone/deleted. 1) It should be possible to make SLECTABLE profiles 2) Profiles shouldn't be deleted automatically if you UN-APPLY I don't think it is possible to do what I want so (1) looks like a conceptional error and (2) looks like a bug or is there another way ?
  5. Hi, This is still not working for me and it is configured as explained in this topic so there is no fault in the configuration. screenshots of my configuration are attached (I placed a follow up number like (1) (2) (3) etc... in the pics because the uploader mixes the order) Is there anyone who configured this and has this working ? Setting up different profiles for users so that they can choose another profile doesn't work too because as soon as you make a new profile it is APPLIED and the users can't choose another one but I will make another post for that. @ ESET, please support on this specific topic since it is NOT working as it should. Philippe.
  6. I try to update outside the network with the configuration settings as explained and I get a connection error message. Is there a log where I can find information about this ?
  7. thanks, about the APPLY setting and the profiles, that is not logical that as soon as you work with multiple profiles the settings are applied and can't be overruled by an admin on the client itself. Is that a bug or still incomplete because that would be desirable.
  8. When you choose to work with these profiles, the APPLY setting is automatically set and when you remove it, the profiles are also removed. When the apply is set, then it is not possible anymore on the client to overrule the setting, there is a lock icon. This seems unlogical, it should be possible to overrule this on the client if I want to do that. Also, when you edit the profiles and you remove the "My profile" (I don't like the name), then all other profiles are also removed and when you only have the "my profile" and you remove it and you add another one like test (or whatever), then you get an error: Failed to get values, path plugins.01000400.profile.profile.1.settings That's buggy behavior...
  9. Hi, Thanks for the feedback. I configured it as you say and I will test it this evening with my computer. One more question about the "USE PROXY SERVER" in the TOOLS section. Is the "use proxy server" in the tools section used when the UPDATE section proxy mode is set as USE GLOBAL PROXY SERVER SETTINGS or else why is there a proxy setting in tools if there is already a proxy setting in update ? thanks, Ph.
  10. Hi, I configured the settings so that the clients get their updates via the HTTP proxy server but a lot of our users work also outside or from home. So I want that ESET updates directly from internet when the internal network with the HTTP proxy server is unavailable. How can I do that ? thanks, Philippe.
  11. Hi, A few days ago I updated our ESET server according the following procedure hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3668&locale=en_US After the update, the administrator agent service on the clients crashed after a reboot or after a manual service restart. Hereby the status log after the installation: status_log_first_install.png And also the log after a reboot or service restart: status_log_administrator_agent_service_restart.png After a reboot the service doesn't start anymore and a message in the windows event log is generated. It's a message without any useful information (%%70 error). I don't find a lot of information in the trace.log after the first installation and the trace.log after a reboot or manual restart of the service (which fails) doesn't give me any newsbreaking facts also. When I install admin agent version 6.1.265.0, everything works fine. The agents were upgraded to the latest version and in that task, the correct certificate was chosen so I had no idea why this fails and I thought it was the new agent since it works with the old agent. The clients have some policies and one of those policies is that the agent on the administrator agent client checks every x minutes with the server. If you check those settings, there is a "connection" section and in that connection section, there is a CERTIFICATE setting and that setting was empty. When I edit that setting and I select the current certificate and I redeploy the agent to that computer, everything works fine and I have no more errors and service starts up as it should. Strange since that worked perfectly with the previous version. Maybe someone else is also helped with this explanation. regards, Ph.
  12. Do you have to revoke the certificates when using new ones or can you just leave them as they are (even if they have the same name but of course another serial) ?
  13. I reinstalled the server, new certificates and agent 6.1.365.0 crashes on all computers (service crash). Version 6.1.265.0 works (at least it doesn't crash and I can restart the service).
  14. I have this same error and ESET agent crash on another computer with windows 8 also now.
  15. But what about the certificates if you update the server ? So first you update the agent via a task ? And when you want to update the server ? Then you have to create new certificates and redeploy the agent to the clients with this new certificate ? Even if they have the newest administrator agent version because else they will not communicate with the new server with its new certificates ? Ph.
  16. According to the following post you have to uninstall everything (hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3668&locale=en_US) What happens if you install the new version while the old version is still running ? Is there a reason why that is not supported ? Then you don't have to reinstall the agent on all computers again. Or can you use the same certificates ? Reinstalling the agent on all computers is a job which can give you other problems too. There will always be client computers who don't reinstall normally like client computers who connect over VPN, 3G, not in the office for a while etc... I worked with other brands of AV before and never had to uninstall the whole package for a minor update. Very unhappy with this and all the other problems I have with ESET 6.
  17. The dump folder is empty. I will send the ESET log collector log via a message to you. Thanks, Ph.
  18. Hi, I installed ESET administrator agent on a windows XP computer (push install via server) and the first time the agent worked but after reboot, the administrator agent doesn't start anymore. In the windows event logs I get this: De ESET Remote Administrator Agent-service is gestopt met de specifieke servicefout 70 (0x46). Zie Help en ondersteuning op hxxp://go.microsoft.com/fwlink/events.aspvoor meer informatie. It's in dutch but it says that de service stopped because of fault 70 (0x46). No Idea what that means. The status log shows this: Peer certificate | 2015-Mar-10 13:04:29 | Error: No such node (result.strIssuer) trace.log: 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Starting module NetworkModule 2015-03-10 13:04:29 Information: CAgentSecurityModule [Thread f0]: Checking agent peer certificate expiration in 30 days 2015-03-10 13:04:29 Information: SchedulerModule [Thread 5e0]: Received message: RegisterSleepEvent 2015-03-10 13:04:29 Information: Kernel [Thread ef0]: Initiating crash dumps sender for directory: "C:\Documents and Settings\All Users\Application Data\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Dumps\" 2015-03-10 13:04:29 Error: Service [Thread dc4]: Kernel start: Last starting module failed with: No such node (result.strIssuer) 2015-03-10 13:04:29 Information: Service [Thread dc4]: Preparing to stop 2015-03-10 13:04:29 Error: CAgentSecurityModule [Thread f0]: No such node (result.strIssuer) 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Used memory before modules shutdown is 48100 KB 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CUpdatesModule 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CSymbolsModule 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CDatabaseModule 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CAgentSecurityModule 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: SchedulerModule 2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Stopping crash dumps sending thread 2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CUpdatesModule 2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CSymbolsModule 2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CDatabaseModule 2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CAgentSecurityModule 2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: SchedulerModule 2015-03-10 13:04:30 Information: Service [Thread dc4]: Kernel shut down nicely 2015-03-10 13:04:30 Information: AutomationModule [Thread dc4]: Facade: All triggers have been unloaded. 2015-03-10 13:04:30 Error: Service [Thread dc4]: Kernel start failed any idea ? thanks.
  19. Hi, I have ESET 6 and the time on the server (windows) is correct, the time on the client also (windows) but when I check the time in the status.html from the agent, it is one hour behind. I saw that with the installation of a new agent that the "Last replication time" was one hour behind when it was just installed (installation was done at 11.00AM, client time is 11.00AM, server time is 11.00AM and last replication time is 10.00AM) The time in the trace.log on the client is also one hour behind. Any reason why ? thanks, Ph.
  20. I get the same error on some clients (client deoployed from the server). certificate created by ESET. 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Started module ERAG1ClientConnector (used 0 KB) 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Starting module CMDMCoreConnectorModule 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Started module CMDMCoreConnectorModule (used 0 KB) 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Starting module CVAHCoreConnectorModule 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Started module CVAHCoreConnectorModule (used 0 KB) 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Starting module AgentToProxyConnectorModule 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Started module AgentToProxyConnectorModule (used 0 KB) 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Starting module CRDSensorConnectorModule 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Started module CRDSensorConnectorModule (used 0 KB) 2015-03-04 15:03:41 Information: Kernel [Thread 3f0]: Used memory after modules start-up is 33036 KB 2015-03-04 15:03:41 Error: NetworkModule [Thread 83c]: Receive: NodSslWriteEncryptedData: Handshake failed to complete., ResolvedIpAddress:192.168.xx.xx, ResolvedHostname:, ResolvedPort:2222 2015-03-04 15:03:41 Error: NetworkModule [Thread 83c]: Protocol failure for session id 1, error:Receive: NodSslWriteEncryptedData: Handshake failed to complete. 2015-03-04 15:03:41 Error: CReplicationModule [Thread 1860]: CReplicationManager: Replication (network) connection to 'host: "xxxx.xxDOMAIN.local" port: 2222' failed with: Receive: NodSslWriteEncryptedData: Handshake failed to complete. 2015-03-04 15:03:46 Error: NetworkModule [Thread 83c]: Receive: NodSslWriteEncryptedData: Handshake failed to complete., ResolvedIpAddress:192.168.x.x, ResolvedHostname:, ResolvedPort:2222 2015-03-04 15:03:46 Error: NetworkModule [Thread 83c]: Protocol failure for session id 2, error:Receive: NodSslWriteEncryptedData: Handshake failed to complete. 2015-03-04 15:03:46 Error: CReplicationModule [Thread 1860]: CReplicationManager: Replication (network) connection to 'host: "xxxx.xxDOMAIN.local" port: 2222' failed with: Receive: NodSslWriteEncryptedData: Handshake failed to complete. 2015-03-04 15:04:48 Error: NetworkModule [Thread 83c]: Receive: NodSslWriteEncryptedData: Handshake failed to complete., ResolvedIpAddress:192.168.xx.xx, ResolvedHostname:, ResolvedPort:2222 2015-03-04 15:04:48 Error: NetworkModule [Thread 83c]: Protocol failure for session id 3, error:Receive: NodSslWriteEncryptedData: Handshake failed to complete. 2015-03-04 15:04:48 Error: CReplicationModule [Thread 1ffc]: CReplicationManager: Replication (network) connection to 'host: "xxxx.xxDOMAIN.local" port: 2222' failed with: Receive: NodSslWriteEncryptedData: Handshake failed to complete.
  21. Hi, I have the version of december 2014 installed and now I want to upgrade to the latest version for the server, webconsole etc... (on windows server). I can download the single packages and server install works but I don't know how to update the web console and other packages (and if it is necessary). When I download the full package I get the error that some components are already installed and I have to uninstall them first ??? Hello ESET ?? I assume you guys understand that it is necessary for existing installations to update and to make some documentation about it ?
×
×
  • Create New...