AgustinSA 0 Posted July 15, 2019 Share Posted July 15, 2019 (edited) Estimados les cuento mi situación. En el lugar donde trabajo tenemos ESET como herramienta de seguridad principal- Tenemos la versión 7.1 corriendo en todas las maquinas del dominio. El problema esta en que el equipo donde teníamos montado la consola de antivirus se quemo, y el personal de infraestructura no había realizado ningún backup de ese equipo, por lo tanto, perdimos el certificado que estaba en ese servidor. Pese a que vino nuestro proveedor de ESET y dejo funcionando un servidor con dicha solución, ninguno de los agentes que están en los equipos que tenemos en el dominio lo reconoce. La operatoria que nos propuso el soporte es ir maquina por maquina, desinstalar el agente (poniendo la clave de seguridad que habíamos configurado por política en el anterior servidor de ESET. Y luego instalar el nuevo agente. Siguiendo esta operatoria no tendríamos que eliminar el antivirus, que es lo mas lento, solamente tendríamos que reinstalar el agente. Mi consulta es ,, , ¿a alguien se le ocurre como puedo crear una GPO que borre el agente (pasando por parámetro la clave que el mismo va a pedir para su correcta desinstalacion? Y una vez hecho esto otra para instalar el agente nuevo? Saludos! Machine translation: Where we work, we have ESET as the main security tool- We have version 7.1 running on all the domain machines. The problem is that the computer where we had mounted the antivirus console was burned, and the infrastructure staff had not made any backup of that computer, therefore, we lost the certificate that was on that server. Despite the fact that our ESET provider came and left a server with this solution, none of the agents that are on the computers that we have in the domain recognize it. The operative that the support proposed to us is to go machine by machine, uninstall the agent (putting the security key that we had configured by policy in the previous ESET server.) And then install the new agent. Following this procedure we would not have to eliminate the antivirus, which is the slowest, we would only have to reinstall the agent. My query is ,, does anyone think of how I can create a GPO that erases the agent (by passing on the key parameter that it will ask for its correct uninstallation? And once done this another to install the new agent? Edited July 15, 2019 by AgustinSA Machine translation added Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted July 15, 2019 ESET Staff Share Posted July 15, 2019 I would recommend to consider following possibilities: in case you have domain, there might be possibility to "repair" connectivity of AGENTs by distribution certificates via domain configuration. This would work in case AGENT are connecting to correct hostname, but they are "rejected" because of wrong certificates. In order this solution to work, you would have to: Import original CA certificate used by previous ESMC installation into new instance. Only public part of CA certificate is required, it is part of all ESMC installers so there is a high possibility you have it somewhere. Distribute new CA certificate (used to sign new ESMC's server certificate) via domain, so that it gets into "local computer" certificate store on each machine with installed AGENT. Another possibility is to use "repair" functionality of ESMC Agent installer. This would enable you to change AGENTs configuration without uninstallation -> you just have to re-run installer of AGENT with new settings and AGENT. It would have to be tested, but this might be possible also via GPO. Ideally exactly the same version of AGENT installer should be used for re-deploy, but latest installers should handle reconfiguration even during upgrade, Link to comment Share on other sites More sharing options...
AgustinSA 0 Posted July 15, 2019 Author Share Posted July 15, 2019 I don't have the old CA certificate, and when I run the new agent, i see this Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted July 15, 2019 ESET Staff Share Posted July 15, 2019 Log indicates that AGENT is missing CA certificate not only for new ESMC Server, but also for itself. Could you specify how it was actually installed? Also what is suspicious there are two different hostnames listed - new ESMC is deployed on different hostname? Link to comment Share on other sites More sharing options...
Recommended Posts