Peter Randziak

There are pros and cons to everything If there is a gateway in front of the mailbox, and the gateway is out of order for whatever reason, the email may not get delivered at all as it could remain stuck at the gateway and would not be forwarded to the mailbox. On the flipside, with API security solutions, if that solution goes down, the email gets delivered, but it wouldn´t be scanned. Of course this is an edge case, but still something to think about.
I don´t know about our competitors but when we onboard a new tenant (which is extremely easy and short), we only request minimal permissions necessary for ECOS to work. And you can also revoke them at any time if you want.

I am not trying to convince you to choose ESET for your mail security, but I want to make sure you make an informed choice. If you decide to go with a competitor, and we end up releasing a gateway in the future, I hope we can win you back as our customer

You can install the management agent v10.x on Windows 7 SP1.
https://help.eset.com/protect_install/10.1/en-US/?windows.html
The latest version of Endpoint than can be installed is v9.
We strongly recommend upgrading the operating system to one that is fully supported and which receives security updates on a regular basis.

Fixed the issue. PEBKAC! Hostname was typed slightly wrong for the Proxy , and my eyes must be getting worse.
Used KB7848 to check proxy match string in config. Restarted Proxy service and clients started connecting correctly right away.
https://support.eset.com/en/kb7848-write-a-proxymatch-expression-for-configuration-of-apache-http-proxy-with-eset-protect

Hi,
most probably you are experiencing issue with missing compiler. Ubuntu latest released kernel was compiled with gcc-12, but this version isn't by default installed there and it results into issue during our kernel modules compilation. 
Please try to install gcc-12 package (sudo apt install gcc-12) and start again our service. 
Regards,
Kurco

Resolved!
We install the On Prem console only to connect the agents of the hosts with Windows 7(We use version 9.1 for both the console and the agent).

We create a task that redirects those Windows 7 hosts to the Cloud console. Once they are reported to the Cloud console, and we already have management of the Pc with win 7 in this console, we can uninstall the On-Prem console.
 

Correct. ESET doesn't re-compress scanned data prior to passing it to the browser.

Since EPNS does not affect protection whatsoever, we plan to report EPNS issues only if a problem is on user's end, e.g. if a firewall is blocking the communication with EPNS servers.

We're going to adjust the reporting of EPNS so that the notification appears only if there's a problem on user's end (e.g. if the communication with EPNS servers is blocked by a firewall or proxy). EPNS has no effect on protection whatsoever.

Thanks Peter, 
I meant to show that both EEI and EEA installations are missing previous versions. 
I understand that the minor versions usually means no major new features are introduced,
However, in the past I have noticed specific minor version works while another don't. That's why all versions are being tested before mass-deployed. 
In any case, both the repo and the main site did not have versions available except the latest. 
This is the issue I experienced, on both EP and the website. 
That's kinda major, isn't it? 

I had similar issue on my personal laptop even without ESET product installed. Can't remember the exact solution but playing with sign-in options in OS settings (disabling whatever is enabled like auto sign-in after update), solved the issue for me.

Since some time ago (around Win10 RS3), windows automatically logs you in and immediately locks, so you are unlocking your PC not logging in. That could be why the hive is loaded before what you see as login.
@Andrej Kuk @Jamie Reader@hack-the-planet what are the products used and their versions?

Losing FDA during restart of macOS is macOS bug. We did workaround in released latest 7.4 to do not trigger this macOS bug.

A new version of ESET Endpoint Security is planned later this year.

I've heard that you can disable outbound UDP 443 on their firewall of preference, either directly on their desktop OS's via GPO or on their perimeter firewall that this will effectively disable QUIC regardless of the browser settings.

Please check the connection settings in your agent policy and make sure that the server is configured correctly. The message means that agent could not connect using current server settings but the connection was successful when previous server settings were used.

Thanks @Peter Randziak  This issue presents during an upgrade cycle, which we've mostly completed (for now). Support recommended we bump our license purge to 30 days, so most duplicates have cleared by now.
I did share one log file I was able to find, but this instance doesn't look quite the same as what we typically see.

I've been working with support for around 8 months (#00521603) and haven't had much luck with two issues. Posting here in hopes of more visibility and hopefully some options.
Frequently, activated devices in EP Console are not found in EBA Console at all (neither device name, nor seat name). They are clearly activated and are licensed Is there a way to force these clients to update in EBA Console? OS X devices consume multiple licenses when upgraded Many times after and upgrade of either AV or EI Connector, the OS X clients consume a license for the previous version and the new version. So we'll frequently see an OS X device with a 7.3.x license and a 7.4.x license at the same time. So we frequently run out of licenses when upgrading. This is not an issue on Windows devices. Regarding #2, support indicated they were able to reproduce the license issue when upgrading from v6 to v7 and reportedly fixed this for this specific case. However, we found that the problem exists for other upgrade paths, as well, including the EI Connector.
It would make sense that this license issue is not version specific, nonetheless, support wants us to collect logs during the upgrade process. Unfortunately, this is not possible because 1) it is not consistently reproducible and we have no way of knowing what workstation might exhibit this issue, 2) there is no way to remotely start and stop log file creation to capture the process. Interactive login is required for log capture, which is not an option for remote sites and production systems, and 3) frequently systems can't be found in EBA Console so test cases are even more limited as we can't see what licenses are consumed.
I've presented multiple examples of the issue (see below), yet the onus for resolution seems to always be placed on the end-user to reproduce the issue, log the results, provide the log files, etc.
Here is an example of one device consuming 5 licenses for two products:

yes

Clipboard protection ensures that payment data you enter in a secured browser is not modified by malware if running on the machine.

All's well that ends well We are happy that you've made it work and are committed to help anyone who comes across issues while using ESET.

Hello guys,
I can confirm that there is an issue with the quality of service of the ESET Push Notification Service (EPNS).
The teams responsible are on it.
We apologize for the inconvenience caused,
Peter

Just to let you know, the other terminal server got it's update to 2099.7 through the regular channel. All is working well, profiles are removed nicely at logoff. I think you can mark this as solved. To bad @krab is not responding in his own thread.

This worked for me:
- set a system date from before Dec 7
- rebooted the server to ensure that drivers are loaded
- installed EFSW 9.0.12018.0 over 9.0.12013.0
- rebooted the server

Many of our users have probably already updated to the latest v9. It is crucial to keep the product updated, in this case at least to the latest version v9 if not to v10. We had been notifying about the expiring Entrust certificate and the need to upgrade the product and the OS to an ACS-compatible version throughout this year.

You have an older version installed, the latest v9.0.12018 or v10 don't have this problem with Entrust cert. expired on Dec 7 and the server being subsequently rebooted. Do you have v9.0.12013 installed on all servers?
We are preparing a workaround via an automatic module update, however, it will be necessary to upgrade to the latest v9 or v10 afterwards.
You can fix it yourself immediately by:
1, Uninstalling ESET in safe mode using the ESET Uninstall tool and installing the latest v9 or v10.
2, Changing the system date to a day from before December 7, rebooting the server and upgrading to the latest version v9 or v10.