Jump to content


  • Posts

  • Joined

  • Last visited

About razec06

  • Rank

Profile Information

  • Location

Recent Profile Visitors

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

  1. So the ESA Server can be detected through the public, but when trying to install ESA on workstations through invite, the installation just rolls back.
  2. 2023-01-24 15:54:39.0179 ERROR EIP.Core.Services.InvitationService Certificate info from url 'https://IPADDRESS:8001' cannot be retrieved. Unable to connect to the remote server I am also having this error when adding it to the server access.
  3. Hi, I am trying to configure the ESET Secure Authentication to be accessible on the public network. I have replaced the certificate with a new one that will connect to the Public IP, but when I try to attempt to add a machine, the machine is unable to find the ESA Server through the Public IP even though the needed port is now open on the public. Only when the private IP can be detected during enrollment. Any ideas on what I can do or other procedures to be done? I have followed every step on the knowledgebase but still I failed to configure it properly. https://help.eset.com/esa/30/en-US/replacing_the_ssl_certificate.html#idpcertificate
  4. Hi @Kstainton, Thank you for this. This cleared up my concern in using EFDE.
  5. Hi, I have a question, I don't know if it would fall under this forum and I apologize in advance. I was reading the the guide for the EFDE about the Decryption/Uninstallation. I would like to ask what if the device is not manageable on the ESET PROTECT Console. Like a scenario where the Agent was uninstalled and the device was removed from the ESET PROTECT Console, only the EFDE is retained then a problem where the device needs to be decrypted and the device can't get pass the Pre-boot login. Do I still need to use the ESET Recovery Media Creator without having to generate the efderecovery.dat?
  6. Thanks for this. I can now activate my endpoints.
  7. I am having the same issue. I followed all the procedures https://support.eset.com/en/kb6996-resolve-act-or-ecp-errors-during-activation-business-users, but all else fails. So I think there is an issue with the activation servers, even the trace logs shows no sign of blockings from the network side.
  8. What I meant to say was, what if I have a GPO policy for USB Access applied to a machine that has a ESET security installed that also has a ESET policy for Device Control applied. Will the machine read the GPO policy first then ESET policy? Sorry if confusing, my mind got confused with domain and GPO.
  9. Sorry if its not clear. What if I have a workstation that has a domain policy applied to it and ESET policy applied to it also. Assuming that the domain policy configuration is for device control and same with ESET policy. What will the workstation follow? Will it follow the domains policy or will it follow ESET's policy? Will there be a conflict on the domains policy and ESETs policy if applied on the same workstation?
  10. Hi, If I have a domain on my network and have configurations made for all the workstations and I will intend to install ESET Endpoint that has also configurations made for all the workstations. What will the computer follow first? Will it be the domains configuration or ESETs configuration? Sorry about a somewhat stupid question.
  11. Yep, you can just install the latest version over the older version.
  12. Hi, I would like to know the newly release version 9.0.2046 for ESET Endpoint on Windows. I need to know the part for: FIXED: CVE-2021-37853 FIXED: CVE-2022-27167 What does these have to do with the ESET Endpoints? Thank you for the clarification and info.
  13. Hi, I would like to ask if there will be plans to support openSUSE for ESET Endpoint for Linux. The legacy version of ESET Endpoint for Linux (NOD32) supports this environment. Will there be a timeline on when this will be supported? Thank you.
  14. I have a workaround on this without having to reboot the device. I have tried the disabling and re-enabling of advanced scanning of browser scripts but its not successful. What I did is to disable and re-enable the advanced scanning via AMSI by policy. And most of the workstations AMSI error disappeared. I don't know if this is ideal but it works,
  • Create New...