Jump to content

MichalJ

ESET Staff
  • Content Count

    2,099
  • Joined

  • Last visited

  • Days Won

    63

Everything posted by MichalJ

  1. Hello, yes, it´s a limitation of the database structure. Do you have a set of particular useful reports, that would be relevant for being added?
  2. Hello @NvD Can you please share the details about the affected license? PLID would suffice, we will check it in our systems. Thank you.
  3. Hello, You have to execute either a component upgrade task, targeted to the machine where your ESET PROTECT Server / Console is installed. If that would not work, alternatively download an all in one installer, and try to execute it manually. It should update the webconsole as well.
  4. Notification was configured to be generic, and just drive the attention to the existence of a problem, not a particular problem. I do agree, that it would be better, if we would reference a particular task entry (or entries, in case there are multiple invalid items), and try to list the reasons for the issue. I will report this to our product managers, so they can track an improvement towards future versions. Please note that it does not say "configuration failed", but that "one of the tasks has invalid configuration and will fail / won´t be executed".
  5. Hello @Nono this particular notification means, that one of your client tasks (as shown on the "tasks" screen) in ESET Protect server, has invalid configuration (references invalid repository package, expired license, or non-existing computer). You can easily identify such task, by using filter "is valid" in this particular screen (invalidated items, are highlighted in yellow color, and the same logic is used in other screens, like installers / certificates / notifications ...) :
  6. Hello @rockshox, than you for your feedback and patience with this. The actual product usage between EBA and license screen in EP should match. Does it "correct" if you click "Synchronize licenses" in EP license screen? In this case 238 / 250 should be present in both. Also, when you count the number of actually connected computers in your EP server (not in the license screen, but the amount of devices you manage, what is the total count? Is it more, or less than those 238 reported in EBA ? I am forwarding this information to the responsible team, it might be worth, if you shar
  7. And if you attempt to install File Security via "software install task", what is the reported error (as I assume, that such attempt would fail). What I would do in this case, is try to login to the affected machine in safe mode, and execute eset uninstaller, to remove any remains of EFSW installation, and also the EEI, and once the system is "clean", reinstall those components from scratch. It might indicate a corrupted EFSW install. Also, is this machine reporting any events to EEI server, or reporting any functionality problems in EP console?
  8. If the mask is present, that would indicate, that there is EFSW installed. Did you check the machine itself? As per my knowledge, it should not be possible to install EEI agent, when there is no Endpoint / File Security product. Also, to activate EEI Agent, security product is needed, as it handles the activation of the EEI. Can you maybe post a screenshot from one of the affected machines, from the "computer details", first screen (tiles with installed apps, activated licenses, and the overall status of the machine)?
  9. I will discuss it with our tech teams here what might be the issue as I am personally out of ideas now. Is there any additional info you can share about those devices? Type of hardware, dock, etc. Also, what versions of applications are being used? Per my knowledge, newer versions of Endpoints (7.3 / 8.0) should have improved the HWF logic, so could eventually improve the situation. Btw, if you do a manual count of the devices managed via ESET Protect, and the count of devices used per EBA, does this match, or you have -5 entries, as those 6 devices are counted as one?
  10. My suggestion would be to "deactivate" the grouped entry, and then reactivate the devices, once they are connected outside of the dock. In case you are managing your devices using ESET Protect / Security Management Center, you can create a dynamic group for "not activated computers", that will reactivate them upon detecting the status. And indeed, it is most likely caused by the dock, that has been in use.
  11. Hello @SvenS, this information was not known to our devs / operations team. I have forwarded the message to them. Can you please describe, how are those notifications configured? Also, provide at least some of the EPC instance IDs, so we can double check their health? Is everything else working OK?
  12. Hello, yes, local caching is working the same, as the scanning core is shared between EP 7.x and EFS 7.x
  13. Hello, as this is issue is unknown to the forum staff, the only suggestion I have is to contact your official ESET distributor and open a support ticket. Maybe, trying a different browser might help. Also provide details, about the version of the console, server, and underlying operating system when opening a ticket.
  14. Hello, changing of data format displayed in ESMC is currently not possible.
  15. Hello, ESET Shared Local Cache is no longer being developed. Due to the recent changes in the way how the local caching works, in case you use latest versions of Endpoint products, meaning EP 7.x and 8.x using ESLC became redundant, and therefore the component is obsolete.
  16. Hello @WillB by "License owner password", we mean not the password for your EBA account, where you have e-mail + user defined password, but instead the password that was provided to you upon license purchase in a separate e-mail. If you remove the license from ELA / delete ELA account, it should be possible to add such license in your ESET Business Account.
  17. Hello, this functionality is currently missing in ESET MSP Administrator 2, however we are tracking it in the backlog, and plan to implement it in the future.
  18. @wgriffi There is a possibility for you, as in this documentation: https://help.eset.com/protect_cloud/en-US/cloud_migration.html
  19. When creating a new client task, in ESMC / ESET PROTECT, you can choose "security product / modules update" and then within the settings, you can check the box "clear update cache". That should do the trick.
  20. Hello, if the agent is not communicating with the server, you can check the reason on the client computer. Non existence of such folder might indicate, that the agent is actually not installed / is not running. Are you able to find it in "installed application", or is it among currently running services?
  21. Just a note. We have just released a hotfix version of ESET Protect Webconsole, that should address the issue with login, when username / password contains a special characters. You can upgrade the console to the current version by running a component upgrade task on your ESET PROTECT server machine. IT will update the webconsole to the version 8.0.175.0 which should resolve those issues.
  22. Hello @LesRMed as suggested by @emilota, we will have to investigate this info further. Please open a customer care ticket with ESET Support, and provide them information about your MSP company name in MSP Administrator, and also the particular sites / customers that are affected by this issue. We will have to look into it, as this is not a common error per our knowledge.
  23. Hello, What you can do, you can identify such computers in a dynamic group template, with the following conditions. Then, you can configure a notification, that will trigger anytime, when a new computer enters / exists the dynamic group (you can set throttling, so it won´t trigger too often, and spam your inbox). However, EP / ESMC can´t send the notification to every user, that has the reboot pending. What I would suggest, is to use "display message task", that will show a native Windows popup, informing the user about the need for the reboot, as on the last screenshot.
  24. Hello, we have published the following KB article: https://support.eset.com/en/kb7765-does-eset-protect-me-from-the-solarwinds-supply-chain-attack
  25. Hello @beethoven, I will try to provide some insights, to the concepts of ESET Protect / Protect Cloud. Out of the box, ESET applications (Endpoint Security) are configured with defaults. They are automatically updating all of the relevant internal components (modules). The status of your network can be seen on the dashboard, in sections "status overview", "computers" and with regards to the history of scans in the section "Antivirus" (there is a chart / table, showing info about the last scan execution time). You can drill down, to the list of computers from there. If you want to
×
×
  • Create New...