Marcos

Now it's been removed from blacklist. Should there be still malware somewhere, it will be detected but I didn't encounter any while browsing the website.

I gather then that the issue has been resolved and you are no longer getting threat detection alerts after removing the malicious JS code.

Please read https://support-eol.eset.com/en/business_managed_remote_va.html for options that you have.

Please provide logs collected with ESET Log Collector.

The detection is correct, however, I was unable to reproduce it.

If the management agent has connected to the ESET PROTECT server recently and there's still a discrepancy in the engine version reported, please raise a support ticket for further troubleshooting of the issue.

You would never give your personal ID to random strangers, right? So why provide the ID of your computer? Unsuspecting users beware, IP grabbers do not ask for your permission.View the full article

Please contact the technical support again. We, the administrators of this forum, are not in direct touch with local distributors and their technical support engineers around the world. If they cannot help resolve a particular issue, they have options to reach out to ESET HQ support and developers for assistance.

Is that more than 24 hours after you've set auto-removal to 7 days?

This will need to be investigated by the technical support. It is not clear to me if the issue occurs even with Endpoint not managed via PROTECT with the same Device Control settings so we can't narrow it down to policies or Endpoint itself.

It doesn't make sense that a policy would stop working after several days if still assigned to the machine or group. Do you mean that if you configure Device Control in the same way on a machine without a management agent installed the Device Control rules will stop working after several days? Please provide your support ticket ID so that I can check the previous communication, especially if your local distributor escalated it to ESET HQ.

Please raise a support ticket. It is not clear if the problem lies in different policies being applied over time or if you are able to reproduce it also on a machine without the management agent.

Yes, there is an issue that we expect to be solved shortly.

The domain was unblocked about 9 hours ago.

This was a false positive, it's already fixed.

The domain will be unblocked.

Agents must be updated via an ESET PROTECT component update task. If this is failing, please raise a support ticket.

ESET Antispam nevyhodnocuje dane emaily ako spam. ESETS_SMFI bol sucastou ESET Mail Security pre Linux, ktoremu podpora skoncila pred niekolkymi rokmi. Aky produkt ESET pouzivate na mail serveri?

We've made some additional changes to the Configuration module to prevent these issues. There's no ETA for release yet, however. but it should not take long. M_CNFENG-1880

The verification email was sent to the license owner's email address sxxxxxxxxxxx6@hotmail.com.

I was unable to find any license registered with your forum email address. Please provide your public license ID in the form of XXX-XXX-XXX. Where did you buy your license from?

The malware seems to have been removed, we'll unblock the website.

Theoretically you could use a Run command task to run an installer from a network share if it supports unattended installation in the local system account.

In EBA you can enable automatic deactivation of clients that have not connected in a specific time period: This will free unused seats that you can use in a software activation task then. E.g. you can create a dynamic group with not activated clients and assign a software installation task to the DG so that clients who will fall in the DG will run the task automatically,

If the detection occurs shortly after the system starts, please create a Procmon boot log and stop logging only after the detection has occurred after a reboot. Then save the log unfiltered in the PML format. Collect fresh logs with ESET Log Collector, add the PML log to the archive and supply it to me.