TomasP

Hello Omni, Sorry for the delayed response. I would like to ask you to create a support ticket via https://www.eset.com/int/support/contact/ and our technicians will look right into the issue and suggest a solution for you. Thank you

Hello, this was resolved earlier today, thank you for your reports. Tomas

Hello guys, according to our forum backend provider, this was supposed to be fixed already. But I can confirm I see the issue as well. I raised it with them and hopefully this will be resolved soon. Tomas

...I meant the server cache, not your local cache. It had to be fixed on the server.

Thank you for pointing this out, last time it was an issue with a cache, we reported this again to the service provider, so hopefully it will be resolved soon. Tomas

Hello mimn2g, To analyze the activation issue, we would need to check the specifics of the situation, including the license details. Please, contact us via http://www.eset.com/int/support/contact/ and we will look into this. Regards, TomasP

Hello, this has now been fixed, you should be able to see all online users again.

Hi guys, I can see the same. I will check this on Monday.

Hello Howard, We are indeed in the process of switching from 32-bit modules to 64-bit modules. The 64-bit module are being tested and will be released via an update soon, so currently the app runs 32-bit modules, but there is full compatibility and full protection even on 64-bit systems and thus nothing to worry about. Now why you saw "64-bit" in the about screen earlier - this was simply a bug, which instead of the modules showed the bit-ness of the system. We fixed the bug in the latest release and now it correctly shows the bit-ness of the modules. Regards, Tomas

Hello @EdwardTus, it is against rule 19 to ask for other users' logs. @Rami While you are free to discuss such matter in a private conversation, please keep in mind that by providing such logs, the user may get various kinds of sensitive information about your system.

Please keep the topic technical and leave any personal hassles out of it. As the correct response has been given by several users throughout the topic and it has now turned into an exchange of personal insults and mockery, we are locking it for further responses. @novice Please refer to rules 23 and 24 and follow them in all your future posts.

So, the explanation is simpler than it seemed. The landing page you're seeing is hosted on the server, so everybody has the new design on it already. The rest of the pages are served by the module and thus only people with version 1147 have those in the new design as of now. So the behavior is correct, there is no glitch or bug.

Thanks, will check with the development team.

That is not possible - being an Insider means downloading and installing a specific build of the product, it is not a switch on our side that we could switch on your behalf. Maybe there is some glitch that causes to show some limited parts of the new design in the previous version of the module as well, we will need to look into it. Can you please send me an output of ESET Log Collector via a private message? Thanks

Hi @itman, this wasn't a pre-release update, but rather an update for the Insiders installations. However, the screens should be consistent. Can you please reboot the PC, then check the module version and the design of the respective screens? Thanks

On April 11, 2019 May 29, 2019, Google is replacing the Google Cloud Messaging (GCM) service with the Firebase Cloud Messaging (FCM) service. (Google has deprecated GCM since April 2018). GCM communication protocol is currently used by ESET Remote Administrator / ESET Security Management Center Mobile Device Connector component for management of Android devices. The GCM successor – FCM – is supported only by Mobile Device Management v7.0+ and ESET Endpoint for Android 2.2.x+. What does this mean? Communication between MDM v6.x and managed Android devices will not stop after April 11, 2019 May 29, 2019, but will no longer be guaranteed on the same level as it was up to this date. For users of either MDM version lower than v7.0 or ESET Endpoint for Android lower than 2.2.x, the following article explains all the ways to upgrade and to resolve any issue during upgrading: https://support.eset.com/kb7092/. --- Google moved the deadline to May 29, 2019. The post has been edited accordingly.

On April 11, 2019 May 29, 2019, Google is replacing the Google Cloud Messaging (GCM) service with the Firebase Cloud Messaging (FCM) service. (Google has deprecated GCM since April 2018). GCM communication protocol is currently used by ESET Remote Administrator / ESET Security Management Center Mobile Device Connector component for management of Android devices. The GCM successor – FCM – is supported only by Mobile Device Management v7.0+ and ESET Endpoint for Android 2.2.x+. What does this mean? Communication between MDM v6.x and managed Android devices will not stop after April 11, 2019 May 29, 2019, but will no longer be guaranteed on the same level as it was up to this date. For users of either MDM version lower than v7.0 or ESET Endpoint for Android lower than 2.2.x, the following article explains all the ways to upgrade and to resolve any issue during upgrading: https://support.eset.com/kb7092/. --- Google moved the deadline to May 29, 2019. The post has been edited accordingly.

Hello @lvl1k0n, Just to let you know, our development team analyzed the calls and the implementation on the websites you mentioned and came up with a fix for this issue that will be a part of a future application update. Regards, T.

I see where you're coming from. Most of the claims you listed can subjectively be understood in several ways, but in general, they are not false, nor misleading - e.g. the product is indeed built on NOD32 technology, as it uses the same malware detection engine, the same database, etc. I also checked the product's online help pages and they only mention HTTP, POP3 and IMAP protocols, but nevertheless, I will ask our documentation team to include an explicit mention of no support for encrypted protocols at this time, to make it even clearer and more transparent - thank you for the feedback.

Thank you for your comment. To be honest, I don't recall a situation when a customer contacted us believing the SSL scanning feature was present when it actually wasn't - seldom customers asked whether it is included or not, but I don't think I remember someone actually being misled. Can you please point me to the marketing material that made you believe SSL scanning was a part of the product? If there is a misinformation somewhere, we can certainly have it fixed! Thank you.

I understand your concern and I don't disagree that each protection level is important, as it hardens the security, however, it is equally necessary to point out that the users are not left unprotected, because if a piece of malware theoretically makes it in via HTTPS, POP3S, or IMAPS, it will still face the Real-time file system protection.

Hello bld, The ports used for SSL communication were added both to HTTP and POP3/IMAP scanners in order to facilitate blocking feature - without seeing the encrypted content, we can still perform basic decisions based on the available information about the connection (mainly applicable in the HTTP scanner). Rest assured we did not forget the request for SSL scanning - however, we analyze and prioritize new features based on many criteria, both from the users and the market in general and we strive to create a product with features that the majority of our user base will find useful in their everyday online activities. With that being said, full HTTPS and POP3S/IMAPS scanning has now been confirmed, is already in the works and will be coming, as Marcos said above. Regards, Tomas

Hi, public release for Endpoint products 7.1 is planned for Q2 of this year.

Hello @brandobot, I will contact you via a personal message with further instructions.

Great seeing you back here! Get well soon!