Peter Randziak

Hi all,
The ESET online shop fixed the problem on their end - I would say the changed email address was the cause here.
The license is now shown as valid for another 3 years and also with the expected 3 PCs.
many thanks for everyone's help!
 
M

If someone has the same issue, maybe you are using auditbeat from Elastic. You cannot use at the same time ESET and auditbeat
From @Peter Randziak : auditbeat sets kernel probe on SyS_exeve what prohibits us to hook on this syscall and scan executed files...

i received a reply now 
CASE:64149

Any chance changing "legacy" filter in packages table helps? Also I would recommend to check ESMC's trace.log for possible synchronization (network) or database related errors. It is possible that repository synchronization is failing and list is not updated correctly.

What about leaving IMAP scanning enabled but disabling integration with MS Outlook? Do you have a lot of emails directly in the Inbox folder? If so, how many approximately?

I have not had chance to check yet, had the Mail server developer on the system all day.
Add to that the latest Office 365 version of Outlook does not seem to be creating a IMAP debug log when debugging is switched on, so MS is looking at that one also.
Will be back with some more details as soon as I can.

A month after installing 6.8.455, and the issue mentioned above still has not manifest itself.
Seems to have solved the problem for me.

TLS connection is actually initiated by ODBC driver installed in system, so it is not in ESMC control. Could you please check what ODBC driver is actually used by ESMC and possibly install latest version. My best guess is that older version is used, which has no support for TLS 1.2. Also it seems that SQL Server 2014 in latest version you are using is supposed to fully support TLS 1.2: just for information, with recent versions we are installing SQL Server 2019 + all-in-one installer do even support upgrade of database server is supported by operating system, but ODBC driver is not installed nor upgraded.
In order to check or change ODBC driver used by ESMC, please check DB connection string file as described in documentation. In referenced article, relevant parameter is Driver=SQL Server, i.e. in example, very old ODBC driver is used. In case it is also in your case, I would recommend to upgrade to Microsoft ODBC Driver 17 for SQL Server. It will also require to modify ESMC DB connection string, probably to Driver=ODBC Driver 17 for SQL Server, where exact name can be verified in ODBC Data Source control panel:

Happy to report the update has successfully installed after upgrading the ODBC driver and modifying the ESMC DB connection string as per your instructions. Thanks for all your help, it's much appreciated!
Just wondering if it is possible to upgrade the SQL Server to 2019 without having to reinstall ESMC?
 

mxp provided me with the requested data so we are checking it with the devops team.
Peter
P_EMA2-3538

Thanks for your answer, indeed I am running a company and indeed I have multiple licenses BUT i don't use the business version because it does not suit my needs, I don't need a central location to manage the different installations but I need that on each machine the main reason being technically advanced users that need to handle the AV themselves (and we are just 3 with 6 machines). 
 
I tested the business version as it looked very interesting on paper... BUT it has its glitch as well... 
- First the GUI is just used for notifications, there is no GUI nor possibility to use without ESMC
- "/var/run" which is a system file/directory is included in your rpm for no reason, that can lead to serious issue
- The kernel module had troubles to find the Linux sources...
- The application is hardly linked to openssl v1.0.2 wich is a complete non sens (can not work with greater/lower versions of openssl)  
 
 
I don't have the time for the moment to reinstall and troubleshoot the new version, and i can not send back global logs, the bug is clearly introduced by the new change to your library libesets_pac.so 
I'll post back some logs if I have the time to test that on a vm  

Cool, thanks for that - it identifies the 'supposedly invalid tasks OK (they're all "Software Installation (ESET Endpoint Security) - via context menu") but when I drill down they're all finished successfully. Seems like a glitch in the system - at least I can delete the 'problematic' tasks from this. Thanks again...

Hello @leoo1231,
It may, make sure that the product is able to access edf.eset.com, for details see https://support.eset.com/en/kb332-ports-and-addresses-required-to-use-your-eset-product-with-a-third-party-firewall
Peter

Thanks a lot @Peter Randziak

Okay, I'll setup a test machine with ESET and Teams only to isolate the problem and run the steps you listed ASAP.
 

Besides edf.eset.com, it's also important that clients can connect to pki.eset.com as well to perform activation.

Thanks @Peter Randziak. We added license already.

Hi Marcos & Peter Randziak,
Absolutely correct, even i didnt notice the update mirror was enabled causing heavy update, it works like charm after disabling it
Thank you very much

Hello @Ricky Martin
I would bet, you have the "Create update mirror" option enabled, causing the update to be so large.
Disable that option and the download will be significantly smaller.
Note that the initial download will still be quite large, but the incremental ones will be very small, as Marcos already mentioned.
Peter

Thank you @Peter Randziak
Everything is still normal so far. If it happens again I will let you know.

If you are interested, in about a month we should be able to provide you with ECA with MDM enabled and a 3-month trial license in exchange for feedback.

I found a solution.
Downgrading to  mysql-connector-odbc                                 5.3.14-1.el7 
All is displayed correctly.
I think you guys and girls in ESET are doing a good job but please fix that damn ODBC-Connector.
That is second time something is wrong because of this.

Cloud MDM for management of Android devices is planned for December 2020

Thanks, it appears to be FP made by Augur the machine-learning system which blocked the file in LiveGrid. The file has now been removed from the blacklist. We're investigating why it happened to prevent such FP in the future.

The initial scan run after installation scans all files on local disks and cleans detected files. While malware, adware and riskware is cleaned automatically, potentially unwanted and unsafe applications require the user to select an action at the end of the scan.
We've run a test and files were cleaned and quarantined alright. Please collect logs with ESET Log Collector and upload the generated archive here for perusal.