BlueBear

We are receiving the same alert for Win64/Intel.N potentially unsafe application - 9E5FCAEA33C9A181C56F7D0E4D9C42F8EDEAD252.

Hi, We are trying to create a scheduled report of 'Functionality/Protection problems . Problem', however, not all 'problems' are available within the dropdown list when we are choosing 'is not one of'. We have some legacy devices that we want to exclude within our automated problem report. We are specifically looking to exclude 'Missing support for Azure Code Signing'. Could you kindly confirm if this could be added? Thanks,

Thank you @kurco for your swift response and assistance. This has now been resolved. For those that have a similar issue, you can resolve it by following this article https://support.eset.com/en/kb8571-eset-service-fails-to-start-when-installing-eset-server-security-or-eset-endpoint-antivirus-for-linux-on-ubuntu-2204-or-mint-21?ref=esf.

I have sent the logs as requested via a PM. Thanks

Hi Kurco, Sure, shall I generate them through log collection? Thanks,

I forgot to add, this is when trying to run odscan.

Hi, We have been using ESET AV on Ubuntu for a while now, and following a recent re-image of the device, we can no longer get the AV to run. We have deployed the latest Ubuntu desktop with a full install package (all drivers, software etc..) and have managed to deploy the agent and AV via the console, however, when trying to run the AV we get the message "ESET Endpoint Antivirus Error: Cannot connect to Confd: No such device or address". Confd does not exist within the expected folder and confd is not found as package to install via apt-get. We have tried with various versions of ESET AV, including the .bin file from the ESET Download page - all of them do not work. We have seen a similar thread on this forum in the server section but there's no answers there. Any ideas on how to progress please? Thank you

Having the same issue running ESET AV for Linux on the latest Ubuntu Desktop. Agent and AV installed OK but when trying to run a scan, we get the same "Cannot connect to Confd: No such device or address". I've tried installing via the console, the .bin file, ESET download portal, and apt-get. There's no confd on Ubuntu by default by the looks of things. I have had ESET running on Ubuntu for a year or two and only recently started to have these issues following a re-image of the device. Any chance for some guidance please? Thank you

I am OK with the detection alert being sent to the console and display on the endpoint but I want to stop the removals. The description of 'Reporting' states exactly the above, so this configuration should report but not remove the detection. However, even with this configuration it is being reported and the deletion action being performed: Action Performed: Cleaned by deleting Timestamp: 1/11/24, 4:52:30 AM UTC Am I misunderstanding this somehow? Thanks

Hi, We want to disable the protection of PUP but still report as shown below in our configuration. Having checked the policies, it appears to be set correctly and there's no other policy within the hierarchy which I thought could be an issue. However, we are still getting reports for a file by the PUP protection. We have even added explicit exclusions for the file based on the hash and I can see that the exclusion is present within the devices that are detecting the PUP. Any idea as to why this would be happening or where to check next? Thanks, BB

Excellent, many thanks. We will resume with the upgrades to v11 next week.

@Marcos thanks for creating the notification banner explaining this. One thing I would like to ask is, does it look like the resolution for this will be a new ESET Endpoint Security or Agent update, or is it a fix without client software changes?

Is the PNS not responsible for wake-up commands, task status updates etc? We have devices we updated and they have successfully updated to v11 but are not reporting back task status and the wake-up command is not working. They do however communicate at the usual replication interval.

We have the same issue. We have waited to deploy a new version for the last 4 months due to an issue with a previous update that that affected 100 devices and took us 3 weeks to resolve. Unfortunately now we are pushing out this update (luckily to a smaller subset of devices) and we have the same. The warning and wake-up commands and task results are not reporting correctly. Do we have a fix date for this? We will hold off on upgrading the rest of our devices. Thanks, BB