Jump to content

MichalJ

ESET Staff
  • Content Count

    1,971
  • Joined

  • Days Won

    59

Everything posted by MichalJ

  1. Per what I see, the license is overused - meaning more units are activated than the license is actually issued for. When you mouse-over the red triangle, it should give you a popup with explanation.
  2. I am not sure we understand each another. It might be not related to just permission sets, but to the fact that table column " resolved" is not displayed in a default view for a newly created user. You can edit "columns" and add column "resolved", it might help, as AFAIK, resolving of threats should not be (or at least was not) tight to the group all.
  3. Hello, per my knowledge, it could be related to the fact, that column "resolved" is not present in default view, and we have a bug that when this is hidden, the option is greyed out. Can you please confirm?
  4. Hello, per the information from our tech support teams, they are aware of the issue and are working on it.
  5. Hello, important is the message about BIOS and not UEFI. In case the computer does not have modern type UEFI, but uses old BIOS, EFDE will not work.
  6. @Lockbits Hello. Per my knowledge, if the agent was not the exact same version, it would first perform "upgrade" and on the second attempt it would perform "repair". So it might be required that you deploy the agent twice, in order to make it connect to the new server. Also, what are the errors in the local agent trace log? They might explain if the problem is in the cert, or in anything else.
  7. Hello @Camilo Diaz Even though task is called "Security management center components upgrade task", it´s client task. Client task means, that the task is executed by ESET Management Agent (=client). Server task means, that it is executed by server (sync against AD, push deployment, or generate report are examples of this). So to upgrade ESMC Server, you actually need to run a client "components upgrade task" targeted to the machine where ESMC server is running. What will happen is, that ESMC agent will contact ESET repository, and download newer versions of server, console and agent, and install them one by one. NOTE: Please note that ESMC 7.1 is only 64-bit, so in case the older install of either server, or any related components is 32-bit, it might fail.
  8. Hello @Nightowl those types of errors are likely to happen in case when a secure boot is enabled. However, as I am not a Linux expert, I would recommend you to open a ticket with ESET customer care. @tbsky per my knowledge, it should work OK, alternatively you can use older ESET File Security V4, as update mirror for V4 clients. And yes, it´s more than probable that this legacy product will reach EOL in the near future, as replacement solution, that you are eligible to use is now being available. We will be updating the EOL policy information on the web soon.
  9. Hello @tbsky, yes, that is correct. Endpoint Antivirus for Linux was developed for the managed (controlled from ESMC) environments, and for the power Linux users. From our POW, there is no practical need by a standard LInux user might want any level of local management of AV product installed on his Endpoint. As of now, we are not planning to bring back the full blown UI.
  10. Hello @Camilo Diaz, in this case, I would suggest to use task "security management center components upgrade". This can be targeted to a dynamic group. Deployment task is a server task (executed by ESMC server), and as DG membership is evaluated by agent, it can´t utilize this concept.
  11. Thanks for the information. I will report this to my colleagues. What you can use as a workaround is to apply a policy to a reference static group (group all) or the group, where the machine would report after being connected first time to ESMC server. Policy will be applied after first replication, so basically the same result will be achieved.
  12. Hello @tbsky, just to double check. Do you talk about the password to protect Endpoint from being uninstalled / from local users to access settings, or some other password (update one?). Also, can you please state the : Version of your ESMC server / ESMC console and its platform (Linux / Windows) Version of the Endpoint that you are trying to install / activate
  13. And if you apply policy with other settings than the password, does the problem still persist?
  14. Hello, we have verified this by our QA, and no such behavior was detected. What are the settings you set by policy? Maybe, that can be the root cause, but without more information, we won´t be able to provide further assistance.
  15. If you apply this logic, then yes, it would be correct.
  16. Maybe you have identified a bug in the implementation. What I would recommend is to perform "reactivation" using the product activation task from the ECA console. After task being performed, can you double-check the machine? What I am thinking of, is that the "managed" is written there in case when the computer has been activated by agent, which is not the case in case when the installer has been generated from the console, but only on case when it was performed via task. Please note, that this is just my assumption. You can run the task on all of your clients, then we will know for sure (all should be marked as "managed". Thank you, Michal
  17. Hello @tmuster2k. I was searching for the term "EDR compliance" and was not able to find any results. Do you know, what exactly he means with this term, as it obviously not refers to any standard like PCI/DSS, HIPAA or other compliance standards, which have direct implications on how the Endpoint solution is being used. So therefore, please check with the customer, what he means with that, as it is no official term (at least not known to us before). Standard endpoint AV is not an EDR solution, meaning it only blocks the known malicious activity, and does allow "back to the root" analysis, like it´s possible with EDR solution.
  18. @Jenova Thank you for your feedback. We are currently tracking such environment. I have asked the responsible PM for comments. Internal reference P_ESSW-827
  19. Can you share screenshot of the "malfunctioning" client task configuration? The one which is intended for the activation of the offline seats? Also, please note, that even when activated using offline file, client still tries to connect to ESET licensing servers, and in case it succeeds it will report license misuse/ violation on ELA / EBA and prevent generation of further offline licenses. You have to either reactivate such clients with online license, or manually restrict communication with ESET license servers on such computers.
  20. Basically in this case you need to do the following: Execute "rename computers task" on the group where the rename computers are present. This will change the ESMC name to the name in your domain. Execute the "static group synchronization task", with correctly set extinction / conflict resolution handling (AFAIK it should be "move"). This will prevent creation of a duplicated entry. There is no linkage between the computer name and the license consumption. When you rename the computer, it will still consume the same license as license consumption is bond to a specific hardware fingerprint, not a computer name. With regards to the ESMC, computer name is a property stored on server, created upon first connection. So even when computer is renamed, without executing the computer rename task, computer will keep connecting to ESMC under it´s original name (when you have renamed it, it should have kept connecting to ESMC).
  21. When you generate the installer from the ESMC console, you can select the group and it is included in the agent.sh.
  22. Hello, are you interested in knowing the command line parameters? As if you specify the group in the wizard, and then extract the installer, it will be automatically placed in the desired static group.
  23. Hi @Carl S - when you just delete both entries, the one that has agent, and is correctly connecting will reappear in the ESMC server, however it will be placed into the ESMC group. Such situation might happen, when the system / agent was reinstalled, so it connects to the server with a newer ID. In general, you did nothing wrong, deleting machines will however wipe their previous data history of tasks, and reported detections.
  24. Hello @Piter - yes, when you renew your license, you will just have to generate a new offline file with the ESMC token, and then create a product activation task, that will deploy the license to your clients. It should work without any issues, if the license is generate for the correct application (offline files are application specific, so if you use EEA, you need file for EEA, etc.).
  25. If you are using the "EFDE" managed via ESMC / ECA, you need to decrypt it by assigning a policy that sets the encryption to "disabled". Then it will be possible to initiate the decryption on the laptop itself.
×
×
  • Create New...