Jump to content

MichalJ

ESET Staff
  • Content Count

    2,099
  • Joined

  • Last visited

  • Days Won

    63

MichalJ last won the day on January 13

MichalJ had the most liked content!

2 Followers

About MichalJ

  • Rank
    Expert

Profile Information

  • Gender
    Male
  • Location
    Slovakia
  • Interests
    customer problems, but besides that cycling, architecture, and everything that rides, flies or floats (transportation industry)

Recent Profile Visitors

8,237 profile views
  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.
×
×
  • Create New...