Jump to content

greyjoy99

Members
  • Posts

    23
  • Joined

  • Last visited

About greyjoy99

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Slovenia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello, I would like to gather diagnostic logs from our devices. If the file is larger than 15mb, I can find it on the ESMC server disk on C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Data\RemoteDiagnostics But I cannot find files smaller than 15mb, can you please tell me where they are located on the disk? Regards, G
  2. Dear all, I am able to deploy ESET Management Agent as an individual application with SCCM using .msi file and the exported script from ESCM. The issue occurs when I include the same application in the Windows OS deployment task sequence (PXE boot). The Agent is installed successfully, but it is not configured and consequently computer can't connect to our ESMC server. Does anyone know what to do? Thanks. Kind Regards, M
  3. Hi @larzillo I don't recommend you exposing ESMC on the internet since it is quite a dangerous tool. If you have to do it for some reason, open firewall port to allow access to your web console.
  4. Actual software version which was installed is ESET Endpoint Antivirus 7.2.2055.0. "Security product" is only information under product column. @Rami I haven't, since we don't force restarts on users computers/servers. I will try that. I am worried what will happen when I push the upgrade task to remaining 2000+ computers including production servers. Will ESET product on half of them just stop working and will require instant reboot?
  5. Hi everyone, an error is showing up on several computers (200+) after ESET Management Agent on the computers has been upgraded to 7.1.717.0 via ESMC. The issue is present on different operating systems (from Windows 7 to 10 & from Winserver 2008 to 2019), and on computers with different ESET Products (from Endpoint Antivirus 6.5.x to 6.6.x & ESET File Security from 6.5.x to 7.1.x). I do not understand why this happened so I was hoping maybe someone can help me out? Thank you. Regards, M
  6. Hi Marcos, thank you for your answer. No, I cannot see any progress, when I click download nothing happens for a while and then error message pops out. Today I cannot even get all packages from repository - I only get some of them (none of them is for Windows Desktop). I have captured PCAP logs, please tell me how can I send it to you. Thank you. Regards, M
  7. Hello, everyone, since I updated ESMC version to 7.1.717, I have had problems downloading installers. I can create packages, but I get an error every time I try to download them. This was working normally before the upgrade. Please help. Regards, M
  8. Hi, any update on this issue? Apache logs are still filled with failed connection attempts. Thank you.
  9. Several computers are attempting to communicate ( 583 unique ones in the last hour ). LG feedback was always disabled, however, until 5 hours ago, there were settings for Submission of Samples enabled and greyed out (screenshot attached). Charon folder contains cache.ndb file only. All clients are activated and don't have problems with updates.
  10. Hi all, I have a question regarding ESET Live Grid Feedback system. Anonymous reporting is disabled by our policy which is forced to all computers, however Apache HTTP Proxy Logs are showing connection attempts to ESET's threat lab servers all the time. Do we have to disable anything else to avoid this? No connection could be made because the target machine actively refused it. : [client xx.xx.xx.xx] AH00939: CONNECT: attempt to connect to 91.228.166.150:443 (ts.eset.com) failed No connection could be made because the target machine actively refused it. : [client xx.xx.xx.xx] AH00939: CONNECT: attempt to connect to 91.228.167.146:443 (ts.eset.com) failed No connection could be made because the target machine actively refused it. : [client xx.xx.xx.xx] AH00939: CONNECT: attempt to connect to 91.228.167:151:443 (ts.eset.com) failed No connection could be made because the target machine actively refused it. : [client xx.xx.xx.xx] AH00939: CONNECT: attempt to connect to 91.228.166.11:443 (ts.eset.com) failed Thanks. Regards, M
  11. Hi @Peter Randziak, is there mabye any new information regarding this issue? Regards, M
  12. Hi Peter, thank you for your reply. Yes it is the similar issue, but... Our computers have installed only ESET Management Agent v 7.0.577.0 via SCCM and they need just ESET Endpoint Antivirus. So .msi package from ESET website does not do the trick for me. Especially because we need Endpoint Antivirus version 6.6.2089.2 (newer versions are not compliant with Cisco Anyconnect hostscan check).
  13. Dear all, installation of All-in-one package (ESET Endpoint Antivirus + Management Agent) fails with error message: The installation was not completed successfully. This happens on all computers with ESET Management Agent already installed on. I have tried different versions (also with AV remover tool included) but the result is the same every time. We install ESET Agent via SCCM on every domain computer to avoid having computers without Antivirus product, so basically this problem affects every computer. Thank you for your help. Regards, M
  14. We have our ESMC server in DMZ. Ports 2222 & 3128 are open but secured enough.
  15. Dear all, I have migrated ESMC server to another machine with different IP address and hostname. Now the new server still shows old hostname (when creating installers, reports, ...). I am wondering if is it ok if I change the name of the server in ERA sql database (server_identificator), as I guess it should solve the problem? Thank you. Regards, M
×
×
  • Create New...