Jump to content


ESET Staff
  • Posts

  • Joined

  • Days Won


Everything posted by MichalJ

  1. Please note, that you have to verify it in a way, that you set the severity to "warning", then connect the device. It will not work "backwards", only forwards. So only newly connected devices will be shown in the report.
  2. Hello, it´s possible that your instance has not yet been upgraded to the latest version (upgrades are pending now as we speak). In that case, you can find this "ESET Solutions" tab within "preview features", which is located in the "quick links" menu in the top bar of ESET PROTECT Cloud Instance.
  3. "ESET Solutions" tab is located directly in ESET PROTECT Cloud, in the menu on the left hand side of the screen.
  4. Hello, the issue should be fixed, and you should see all of the details in EBA. Per the developers, it was a manifest of an older issue, that is fixed already.
  5. Hello. Currently, it is a bit difficult, to determine, which computer has EDTD activated and working. Your are right, that in the past, it worked in the following way: You enabled EDTD via policy If the EDTD was "not activated" on a particular machine, it reported an error Based on this error, you can group such machines in a dynamic group You can have set "activated EDTD" task on top of such dynamic group that will enable it Currently, the "error" state was removed, and EDTD does not report that type of error it is not activated. Per my knowledge, this was due to some architectural changes, and moving towards "more proper" reporting of feature states. Last update I got from the developers was, that we are working on a better way, that will be most likely implemented in next releases. One IDEA is use "ESET Solutions" tab, and over there you will see, how many have EDTD active, and how many does not have it active. You can click "Deploy", which should do both the enabling, and activation in one step. Sorry for the inconvenience, and stay tuned for the updates, when the proper solution gets implemented.
  6. Hello. I have forwarded this info to our release manager, as I do agree, that every release post / info / metadata should include also the release date, for simpler orientation.
  7. Hello, if you want to apply the change in "bulk" you can configure all parameters of ESET software using "policies". Just navigate to "policies" tab in ESET PROTECT / PROTECT Cloud, and adjust the following settings: - Endpoint for Windows / Tools / Microsoft Windows Update - ESET Management Agent / Advanced Settings / Report if operating system is not up-t-date + you have also there setting for firewall issues reporting
  8. The best way to handle this (at least from my point of view) is to enable automatic product updates. The main benefit is, that in case this feature is active, it will automatically download and prepare the update, and will apply it upon computer reboot. However, reboot is not required, computer is working normally with the previous version. This is a major change compared to "traditional" way of doing updates, where you install the new update over the old binary, and after this the restart is required (as the previous version drivers are still hooked into the system). This functionality currently applies to the Windows machines only, and only to clients newer than version 8.1.
  9. That´s indeed a good question. My assumption is, that the product is functional, however older version of modules are loaded, meaning the highest level of protection, that will be achieved with newer modules is not ensured. As in some cases we bring new detection functionality along the way. But I will double check with the teams responsible.
  10. Hello. This is a new / adjusted status. As Dynamic group automation works on a concept of Agent being explicitly aware of the status types, following the change on the Endpoint side, we will reflect the change in the upcoming release of ESET PROTECT coming later this year. Please note, that for proper operations, both server / agents will have to be updated to the latest version. We are sorry for the inconvenience.
  11. @mgfeal you can login to ELA using the license key, and in that case, you should be able to see and deactivate all of the seats. You will need your license key, and ELA password to enter it. Alternative approach is to setup ESET Business Account, and add there the license.
  12. If you have installed just the endpoint using the "offline installer", you are missing an ESET Management Agent, which is the component that communicates with the protect console. You should generate a new installer from protect console, that includes "agent only" and try to install it. If it fails, it means it can´t download the required components, and it might be a network issue. EBA sees the device as it reports just the information from the licensing server, and uses different channel for communication than ESET PROTECT.
  13. I would add, that ESET Internet Security (as it includes firewall and antispam) is functionality-wise closer to ESET Endpoint Security. ESET Endpoint Antivirus is functionality-wise comparable with ESET NOD32 Antivirus (consumer product)
  14. Hello, recommended approach would be to use the dashboard / reporting functionality for it. You can navigate to the tab "ESET applications", where you can see which are outdated and even list count of all outdated versions. Then you can initiate upgrade by "one click" from there, for a particular version, you seek to upgrade to a newest version.
  15. Hello, we will need to see more details configuration of the notification, to verify, whether it is setup properly. I Would suggest you create a support ticket, so we can check, whether that notification has some issues, or there is some generic problem with sending/receiving emails from Protect Cloud (you can verify that, by trying to send an installer download link, via ESET PROTECT Cloud UI).
  16. Hello, per the knowledge I have, our PM / Dev teams are currently looking on a way how to precisely monitor "functionality statuses" of products / features. When done, it should resolve also this issue, that OK state will be reported as well.
  17. Hello @BrianMorris One "workaround" is that if you click on a particular computer, navigate to computer details and in the overview section, you look at the "ESET Dynamic Threat Defense " TAB, there is a button to open "submitted files". That button will filter out the submitted files screen filtered out for that particular computer. However I do agree that having a direct visibility in the form of a separate tab is a good idea, and we will track it as an improvement towards future versions.
  18. Hello, The only current way how to verify if EDTD is "enabled" is to check whether a corresponding policy that enables it is applied to a client + if a correct EDTD license is present. The second one can be done by a dynamic group, that will filter computers having a particular license, based on a product type / PLID. The first one, only by policies assignments checking.
  19. Hello, we are currently starting a closed early access phase with selected customers, and proceeding towards the global availability of our cloud EDR solution during H1/2022. I would suggest that you follow standard announcement channels for more news. If you share with me your license details (PLID XXX-XXX-XXX) I can check for your eligibility, and provide further details.
  20. Yes, but your ESET PROTECT Cloud instance will be later on shut down, as you will no longer be entitled to use it. But your endpoints will run, after you manually replace the license.
  21. Hello @Romain Dheilly, even if you have just used the software install task, the application should work in a way, that it will keep the license (even if no license was selected in the software install task). I will check with the teams here, whether they have witnessed similar behavior from the other customers. One of the things that I know tends to happen is, when customer accidentally installs EES and his license is for EEA, that will result in products being not activated, as the license and product do not match. When you have attempted the manual reactivation (vie the software install task), what was written in the task details / executions history? What was the reason for it to fail?
  22. Hello, The paid license that you have bought does not allow you to use ESET PROTECT Cloud. You should have purchased "ESET PROTECT Entry" without the "on-prem", as that is only limited to use on-prem deployed ESET PROTECT console. Unfortunately you will have to upgrade your license. Regards, Michal
  23. Hello, I was trying to contact colleagues that has a deeper knowledge about this topic, but we might require some additional data, about what is the problem. There were recently some modifications in the last iteration of ESET PROTECT, so it might require an update. I would recommend that you create an official ticket, and it will get to our devs, who will respond.
  24. @BrianMorris you can easily use "dashboards" for this. Over there, you can filter out the computers, which have either not latest version of agent, or security product. Especially in EPC, we have implemented agent auto update, so in foreseeable future, all machines will be automatically running the latest compatible version. So column would not be required anymore.
  • Create New...