psilva 0 Posted May 3, 2016 Share Posted May 3, 2016 Hi! I'm trying to remotely install the endpoint antivirus, using the ERA Server, but the task is scheduled and not executed, i don't know if the server need some patch or the procedure is inconrrect, attach the trace file for your information. Thanks in advance Pablo EraServerInstaller.log last-error.html status.html trace.log.gz Link to comment Share on other sites More sharing options...
psilva 0 Posted May 3, 2016 Author Share Posted May 3, 2016 Hi Again! Some information about the server: ESET Remote Administrator (Server), Version 6.3.148.0ESET Remote Administrator (Web Console), Version 6.3.114.0Copyright © 1992-2016 ESET, spol. s r.o. All Rights Reserved. CentOS (64-bit), Version 7.2.1511 License used for module updates of this ERA: Public ID: 33D-83R-RAEExpires: 2037 Dec 31 09:00:00 Connected Clients: 1Active Licenses: 1 Installed Components Update module1062 (20151228) Translation support module1479 (20160422) Configuration module1238B (20151204) SysInspector module1257 (20151113) We don't have Active Directory.. Regards, Pablo Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 430 Posted May 3, 2016 ESET Staff Share Posted May 3, 2016 Just to be sure, have you install ERA agent on the target system before attempting to execute a software install task? Software install task is executed by ERA agent, not by ERA server, you have to deploy the agent firs. Link to comment Share on other sites More sharing options...
psilva 0 Posted May 3, 2016 Author Share Posted May 3, 2016 Hi ESET Staff! Yes my first step was install Era Agent to Windows 10 Client by using Era Server, was successfully, but when the folowing step I use Era server for to install Antivirus , only the task is planned but never executed.., whats wrong with the server?, I've attached the log server on my first post. Thanks in advance! Pablo Link to comment Share on other sites More sharing options...
Administrators Marcos 4,720 Posted May 3, 2016 Administrators Share Posted May 3, 2016 If you check client details in the web console, do you see that the client (agent) has recently connected to ERAS? Link to comment Share on other sites More sharing options...
psilva 0 Posted May 3, 2016 Author Share Posted May 3, 2016 Hi Eset Moderators! The information in client details, said never...., what the next? Thanks in advance! Pablo Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 430 Posted May 3, 2016 ESET Staff Share Posted May 3, 2016 You should check the era agent trace logs on the target computer. Ideally send us both status.html and era agent trace log, to be able to analyze why the computer is not connecting. Link to comment Share on other sites More sharing options...
psilva 0 Posted May 3, 2016 Author Share Posted May 3, 2016 Dear Eset Staff: Only i can find in the server those log files , but in the target nothing there isn't a log file, can you tell me the path inside the target for to find it, please? Thanks in advance! Pablo last-error.html status.html trace.log Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted May 3, 2016 ESET Staff Share Posted May 3, 2016 Dear Eset Staff: Only i can find in the server those log files , but in the target nothing there isn't a log file, can you tell me the path inside the target for to find it, please? Thanks in advance! Pablo Please check C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html on target computer (client computer). It should highlight most significant error. Link to comment Share on other sites More sharing options...
psilva 0 Posted May 3, 2016 Author Share Posted May 3, 2016 Dear Eset Staff: Here the target files, perhaps the error is can't resolve EraServer name, look at in zip file, it was maked by Diagnostic.exe tool inside the target, in dns server i get the following configuration: eraserver A 10.200.200.145 _era._tcp.eraserver IN SRV 0 5 2222 eraserver.areaprod.b2b. How i can resolve this error? Thanks in advance Pablo last-error.html status.html trace.log RemoteAdministratorAgentDiagnostic20160503T194141.zip Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted May 4, 2016 ESET Staff Share Posted May 4, 2016 Dear Eset Staff: Here the target files, perhaps the error is can't resolve EraServer name, look at in zip file, it was maked by Diagnostic.exe tool inside the target, in dns server i get the following configuration: eraserver A 10.200.200.145 _era._tcp.eraserver IN SRV 0 5 2222 eraserver.areaprod.b2b. How i can resolve this error? Thanks in advance Pablo So there are two errors: Replication (network) connection to 'host: "EraServer" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2af9), Host desconocido caused by EraServer to be not resolvable by AGENT. Could you try to ping this host from client machine? Maybe problem is different case (EraServer != eraserver). There is also another error: Certificated user verification failed with: VerifyDnsSubjectAltName: Certificate SubjectAltName extension does not have any supported records after a minute gap in trace log. this indicates wrong certificate has been used to install AGENT, have you been doing some kind of repair? Link to comment Share on other sites More sharing options...
Solution psilva 0 Posted May 4, 2016 Author Solution Share Posted May 4, 2016 Solved! The problem was no clean install + DNS configuration, now all works in centos 7. Please update the documentation, because in Centos 6 have severals problems with samba version, especific with: net -i -k rpc service You can resolve if you use samba4, but you can't use mount -t cifs, by incompatible install versions. [root@ERAServer ~]# yum install cifs-utilsComplementos cargados:fastestmirrorConfigurando el proceso de instalaciónLoading mirror speeds from cached hostfileepel/metalink | 2.8 kB 00:00* base: centos.secrel.com.br* epel: mirror.cedia.org.ec* extras: centos.secrel.com.br* updates: centos.secrel.com.brbase | 3.7 kB 00:00epel | 4.3 kB 00:00epel/primary_db | 5.9 MB 00:02extras | 3.4 kB 00:00mysql-connectors-community | 2.5 kB 00:00mysql-tools-community | 2.5 kB 00:00mysql56-community | 2.5 kB 00:00updates | 3.4 kB 00:00Resolviendo dependencias--> Ejecutando prueba de transacción---> Package cifs-utils.x86_64 0:4.8.1-20.el6 will be instalado--> Procesando dependencias: libwbclient.so.0()(64bit) para el paquete:cifs-utils-4.8.1-20.el6.x86_64--> Ejecutando prueba de transacción---> Package samba-winbind-clients.x86_64 0:3.6.23-30.el6_7 will beinstalado--> Procesando dependencias: samba-winbind = 3.6.23-30.el6_7 para elpaquete: samba-winbind-clients-3.6.23-30.el6_7.x86_64--> Ejecutando prueba de transacción---> Package samba-winbind.x86_64 0:3.6.23-30.el6_7 will be instalado--> Procesando dependencias: samba-common = 3.6.23-30.el6_7 para el paquete:samba-winbind-3.6.23-30.el6_7.x86_64--> Ejecutando prueba de transacción---> Package samba-common.x86_64 0:3.6.23-30.el6_7 will be instalado--> Procesando conflictos: samba4-common-4.2.10-6.el6_7.x86_64 choca consamba-common < 3.9.9--> Procesando conflictos: samba4-winbind-4.2.10-6.el6_7.x86_64 choca consamba-winbind < 3.9.9--> Procesando conflictos: samba4-winbind-clients-4.2.10-6.el6_7.x86_64choca con samba-winbind-clients < 3.9.9--> Resolución de dependencias finalizadaError: samba4-winbind conflicts with samba-winbind-3.6.23-30.el6_7.x86_64Error: samba4-common conflicts with samba-common-3.6.23-30.el6_7.x86_64Error: samba4-winbind-clients conflicts withsamba-winbind-clients-3.6.23-30.el6_7.x86_64Podría intentar utilizar el comando --skip-broken para sortear el problemaPodría intentar ejecutar: rpm- Va --nofiles --nodigest Link to comment Share on other sites More sharing options...
Recommended Posts