bbahes

Just out of curiosity, which protocol you use to communicate with O365 servers?

Times change, as did ESET Endpoint change over time. For example, v5 did not have anti ransomware module, v6 (guessing) and v7 does. As for Microsoft remark, I would welcome any solution from security vendors, like ESET, that would warn about this activity from Microsoft or any other software vendor and possibly block it on user demand.

Correct me if I'm wrong, but I don't see in KB article, statement that you use DNS for information exchange, only for DNS queries. For example, for ESET Live Grid you only say "These IP addresses need to be enabled for HTTP port 80. Also, an access to your local DNS server is required for DNS queries on UDP port 53." If port 53 or DNS protocol is used for something other than name resolution, that should be noted in that text. I don't see problem in information exchange as long it's transparent and highlighted clearly in documentation. That way we could avoid problems with 3rd party products.

Is this documented?

You are right, SELinux might be main "problem".

1. Is option "Use All Server" selected just above server list? 2. What do you get in File > Edit Connections ?

Only agent. However, there was attempt made to install ESET File Security for Linux/FreeBSD which failed. After that I manually tried to install ESET Antivirus for Linux.

This is test environment. I tried to install it manually, but got error:

Agent did install correctly, but I'm unable to install binary. This is clean virtual machine guest Ubuntu 18.04.1 LTS. I tried pushing ESET Antivirus for Linux 4.0.90.0

Basically it generates bash script inside tar.gz archive?

You could check policy settings: Windows desktop v5 > Personal firewall > Settings > SSL > SSL protocol checking We had similar situation but it was due UTM settings.

Thanks for sharing info. Out of curiosity, did you investigate UTM logs for this issue or used packet capture tool on server and client?

We've had situations where ESET had problems with antivirus database (usually many false positives with web filtering) where we had to revert to previous version. However, that was not main focus for us since fix was delivered in few hours, but we had quick overview of what clients had which version in comparison to ESET server or ERA server.

If you use v5 there is Tab "Advanced setup" (Windows desktop v5 > Personal firewall > Settings > Rule setup) where you uncheck "Allow remote desktop in the Trusted zone". Did you try unchecking this option?

No. Unfortunately Windows Defender deleted it completely.

UPDATE: After deleting and recreating installer in Installers I was able to download normally installer without virus warning.

I was testing new virtual appliance instance today and I got the same error. However I was able to resume after I clicked link again "Download 64 bit version". After that I got message from Windows Defender that it detected virus: @MartinK @Marcos

You are right. As soon as I tried in different browser with https://<hostname> initial wizzard started. Thank you both for quick response!

Hi! Testing ESMC v7 and after reverting to previous checkpoint in Hyper-V I get error:

In my organization we also use v5 and plan to move to v7. Reading forum and documentation (Migration assistant vs Migration Tool) we plan have virtual appliance of ESMC and move manually one client at the time. Basically you have 3 options: 1. Migration scenario 1 - Migration to ESMC 7.x running on a different computer than ERA 5.x. 2. Migration scenario 2 - Migration to ESMC 7.x running on the same computer as ERA 5.x. 3. Migration scenario 3 - Migration to ESMC 7.x where endpoints connect to old ERA 5.x until the ESET Management Agent is deployed by ESMC 7.x. https://help.eset.com/esmc_install/70/en-US/migration_from_era5.html?migration_tool.html Regarding your problem with internal server error, did you use virtual appliance for ESMC deployment or did you use Windows Server? As for upgrading your current era server, unfortunately this may be possible for short time. Since the plan is to have it EOL by december this year https://support.eset.com/kb3592/#era

For some strange reason, editor did not post entire message. I also added that you post feature request on https://forum.eset.com/topic/14271-future-changes-to-eset-remote-administrator/ I would only add to your request for scheduled scan, option to scan PST/OST when PC is in idle state.

This helped us on v5. Please do test this and if possible report back.

Description: Agent logs in Endpoint productDetail: It would be practical to have agent log in Endpoint product Log Files for easier export and review.

I was asking for situation where you upgraded from v5 to v6. Was this Windows server? We need to jump from v5 to v7.