igi008

Thank you very much for your valuable feedback. I absolutely agree with you. It is our goal to improve this situation and have all necessary components and tools in one installer/agent, with components enabled based on your license.
Currently, we are making efforts to introduce more improvements that enhance the experience of easily enabling additional protection layers. We are striving to achieve this through an installer that installs all components based on your license across all platforms. By expanding ESET Solutions, we allow for the easy enablement of additional protection layers via a context menu over a single computer or groups of computers. The license is preselected automatically, and everything necessary is enabled or installed on the endpoint.
We also aim to expand a dedicated section in the menu titled "ESET Solutions" where we are adding support for more and more protection layers. In this section, it is easy to distinguish where a protection layer is enabled and where it is missing.
If a customer does not have a sufficient license, they can request a trial and try an additional protection layer like LiveGuard directly from this section.

Hello, thank you very much for this feedback, we plan to improve it, and every table should be sortable in the future.

Hello, many thanks for this idea.
Actually we have something like you mentioned in our EDR layer (ESET Inspect), which provides better visibility in your network and helps you identify suspicious behavior.
For example, these rules related to this MITRE ATT&CK Technique: https://attack.mitre.org/techniques/T1219/ can be helpful.

However, including other conditions in such rules is a quite interesting idea.

Hello @LesRMed
I have opened this up with our QA department and this is what they came up with: 
In case you enable the setting that allows appending the globally set exclusions to the local list, it will enable you to add the local ones. However, what you need to do first on the endpoint side, is to adjust the "combo box" to "show local exclusions". Once this is done, the add button will enable, and allow you to enter the exclusion locally. 
I have filed an improvement request, to change this behavior, as it is considered as not intuitive. 


 

Thank you very much for your suggestion. We also have a negative filter in your backlog. We plan to pilot it on the computer screen with a new Filter Advisor (planned in H1/2022). Please stay tuned

Hello,
Manny, thanks for your suggestion. We have in the backlog the reworking dynamic groups or, better say, enriching them to be possible to consider also data on the server (console).
For now, you can try a workaround (but not ideal) to filter servers based on OS name and exclude domain controllers by the "Not equal" condition for specific machines.

In the future, we will try to extend Dynamic groups / Dynamic group Templates to better-fitting this kind of need.

Hello,
Manny, thanks for your suggestion. We have in the backlog the reworking dynamic groups or, better say, enriching them to be possible to consider also data on the server (console).
For now, you can try a workaround (but not ideal) to filter servers based on OS name and exclude domain controllers by the "Not equal" condition for specific machines.

In the future, we will try to extend Dynamic groups / Dynamic group Templates to better-fitting this kind of need.

Hi Bob,
By default, we're sending to EDTD only documents with active content (e.g. Macro) and not standard documents.
However, it's possible, that e.g. an ordinary document would be send to ESET LiveGrid Feedback system (not EDTD) in case this document would be downloaded from URL/domain, which is considered as dangerous based on historic data for further inspection (should not normally happen).
That means, probability of sending an ordinary document to ESET which you receive e.g. from customer with sensitive data is close to zero.

Hello, thank you very much for reminding those things. Yes, we are also tracking these various smaller improvements. Unfortunately, capacity is limited, and we need to solve a lot of things with higher priority with broader business impact. However, do not worry. We have it in the backlog, and I hope that some of them will be able to address in the upcoming release.
# 1 Uptime
There was a tricky part how often to synchronize. We are considering adding it, but not sure if directly to the main computer table, maybe under details and sync it in some time intervals.
# 2 Service pack / OS version
It is problematic because it is impossible to guarantee that MS won't bring some ServicePack for Win 10. Now is possible to parse this information from the "OS version" in ESET PROTECT (that is technically the OS build). However, is good to consider creating a new field "OS build" and report version (e.g., 20H2) to "OS version", but it needs to be analyzed cross-platform.
# 3 Network adapters
Now we are reporting more physical adapters also wireless.
Yes, the problem with duplicity (IPv4 and IPv6) is not fixed yet, but it is planned.
Many thanks for your patience, I hope you have found other interesting improvements in ESET PROTECT 9.0.
And of course, we will also try to move forward the smaller improvements suggested in this forum thread, but in some cases, we need more time due to other priorities.
 

Hello, thank you very much for reminding those things. Yes, we are also tracking these various smaller improvements. Unfortunately, capacity is limited, and we need to solve a lot of things with higher priority with broader business impact. However, do not worry. We have it in the backlog, and I hope that some of them will be able to address in the upcoming release.
# 1 Uptime
There was a tricky part how often to synchronize. We are considering adding it, but not sure if directly to the main computer table, maybe under details and sync it in some time intervals.
# 2 Service pack / OS version
It is problematic because it is impossible to guarantee that MS won't bring some ServicePack for Win 10. Now is possible to parse this information from the "OS version" in ESET PROTECT (that is technically the OS build). However, is good to consider creating a new field "OS build" and report version (e.g., 20H2) to "OS version", but it needs to be analyzed cross-platform.
# 3 Network adapters
Now we are reporting more physical adapters also wireless.
Yes, the problem with duplicity (IPv4 and IPv6) is not fixed yet, but it is planned.
Many thanks for your patience, I hope you have found other interesting improvements in ESET PROTECT 9.0.
And of course, we will also try to move forward the smaller improvements suggested in this forum thread, but in some cases, we need more time due to other priorities.
 

Thanks for letting us know. First part is considered as an issue and should be targeted. Second part will be discussed as an possible improvements, which seems to be legit.

Hello, Many thanks for your suggestion.
We will add it also to ESET PROTECT Cloud.
We have it already in the on-prem version. I apologize. It was forgotten in the cloud version.

Thanks everyone at ESET for all of the improvements. I've just been playing some this morning and I see some things that were added/changed that I've been asking for and that have been needed for years.
1 - I can add the file path/name of the detected malware to email alerts
2 - The UI of the customizing of the alert is MASSIVELY improved.
3 - I can UPGRADE a license without needing to suspend, activate, wait for computers to come online, etc. THIS IS HUGE!!!!!!!
4 - EDTD submissions now show on the Computer Detail page
What else will I notice?
 

Hello, Many thanks for your suggestion.
We will add it also to ESET PROTECT Cloud.
We have it already in the on-prem version. I apologize. It was forgotten in the cloud version.

Hello @endpointandcats
You do not have to select the configuration during the installer creation. You can simply assign all of the relevant "policy templates" (or custom made policies) to group all (or any group or even an individual computer), which means that the resulting configuration would be created as a merge of those policies. 
Alternatively, you can create your own custom template, where you configure the product as you want, and then you choose this template during the installer creation process. 
Please note, that there is a difference between a configuration and policy. Configuration sets the values to the desired state, but does not lock them on the client (if the local user has admin rights, he can change the settings). Policy on the other hand, if setting has "apply/force" flags set, would lock the setting, and prevent it from being edited. 
Hope that this helps.
Michal

Currently it is not decided of the future, and even latest version is using CentOS7-based appliance, which is supposed to be supported until 2024 (i.e. much longer than mentioned CentOS8). We currently rely on fact that security patches are available, even for tomcat 7 which is part of official CentOS7 repositories.
Just out of curiosity, what would be your preferred Linux distribution for future? Asking as there is not many "free" distributions guaranteeing reasonably long support and stability of environment for future migrations.

Yes, ECA will be migrated automatically to the new version. It should be released in Q4/20.

Thanks, quite a good idea. We will try to bring it in a service release next year.

Thanks, quite a good idea. We will try to bring it in a service release next year.

Hello @Zen11t, thank you very much for your explanation again. It helps us to understand your needs better.
I hope this trick will help you

You can filter the computers with an outdated version of agents and then click on any item in the table and select "In computer page (all)". It will navigate you to the computers section, where you will have only computers with outdated agents, and here you can also check the last connection status.

Hello @Zen11t, thank you very much for your explanation again. It helps us to understand your needs better.
I hope this trick will help you

You can filter the computers with an outdated version of agents and then click on any item in the table and select "In computer page (all)". It will navigate you to the computers section, where you will have only computers with outdated agents, and here you can also check the last connection status.

Hello, this issue is known, and we plan to fix it in the upcoming service release (currently planned by end of July). 

Hello, this option is already available in ESET Cloud Administrator console. Currently, as agents are updated via "Components upgrade task", which does not differentiate between agents, and other components of the ESMC infrastructure (server / webconsole) this option was disabled. However, in Cloud the server is fully hosted / maintained by ESET, so "one click agent updates" are possible. 
Please note, that for the future releases we work on "automatic agent upgrades", meaning agents would automatically upgrade themselves to the version compatible / matching with the server. 

I think this is resolved in just-released ESMC 7.2 where it look like this:

Hello tbsky, thank you very much for your post, don't worry, we plan to release mentioned versions in the middle of November. Stay tuned!