Panagiotis Goudas 0 Posted March 19 Share Posted March 19 Hello. I was wondering if there is any way to quarantine/delete files that were detected and retained by ESET PROTECT without connecting to this pc. Is there any way to achieve this through ESET Console? Thanks in advance for your answer. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,273 Posted March 19 Administrators Share Posted March 19 Files are typically retained if you run a scan without cleaning. Files are not quarantined unless cleaned so further clarification and ideally logs collected with ESET Log Collector from the machine in question will be needed. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted March 21 ESET Staff Share Posted March 21 Also note that there is a set of quarantine management tasks available in the PROTECT console (see: https://help.eset.com/protect_admin/11.0/en-US/client_tasks_quarantine_management.html) which enables console user to remotely perform specific actions. But I am not sure it covers required scenarios as it is not clear to me what is the usecase - but as already mentioned, objects are quarantined automatically, and it is not possible to just request to quarantine specific file. Link to comment Share on other sites More sharing options...
RobertEDS 0 Posted April 7 Share Posted April 7 This is the most common result on 99.99% of scan with cleaning in eset protect cloud. I have hundreds of end points in protect cloud and we do monthly scans with cleaning on them. Almost always results in detections retained. Constantly I see folks here saying it is due to scan without cleaning but this is not true. Would be nice to see this issue actually addressed by eset. It is annoying. The things detected are real problems and should be cleaned especially when the task is scan with cleaning. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,273 Posted April 8 Administrators Share Posted April 8 9 hours ago, RobertEDS said: This is the most common result on 99.99% of scan with cleaning in eset protect cloud. I have hundreds of end points in protect cloud and we do monthly scans with cleaning on them. Almost always results in detections retained. Constantly I see folks here saying it is due to scan without cleaning but this is not true. Would be nice to see this issue actually addressed by eset. It is annoying. The things detected are real problems and should be cleaned especially when the task is scan with cleaning. Please raise a support ticket. A detected file can be retained also in case when it's a driver that is always loaded at system startup. Link to comment Share on other sites More sharing options...
Recommended Posts