Jump to content


ESET Staff
  • Content Count

  • Joined

  • Days Won


Posts posted by MichalJ

  1. If you have added the license to your security admin account / ESET Business Account, and you add the credentials, does it work? Does your environment have connectivity to edf.eset.com?

    Do you have the original license key? (XXXX-XXXX-XXXX-XXXX-XXXX).Can you add the key directly? 

  2. Hello Jirka,

    For the first problem, I would first apply "reset the RD sensor database" task, to validate whether the white-list is working (as once reported the data are kept, even in case the RD sensor whitelist is actually working). Alternatively, I would uninstall the RD sensor at all, if it reports too many false positives.

    With regards to the second problem, I would recommend to contact your customer care, as the error is generic, and does not give is exact reasoning for what might be the failure. 



  3. I am not completely able to understand, what you are trying to achieve. Most probably, it´s about the policy inheritance. In general, the policy set for "secondary" should overwrite the settings from "all", however settings from "all" should not be set to "force" (as that prevents overwriting). 

    However, the best thing I would do is to contact our ESET Portugal, they should be able to help you in the local language. 

    They should be accessible here: http://eset.pt/suporte/

  4. Hello,

    ESMC itself does need a license only for the need of updating it´s modules (translator, configuration engine module). And for that purpose, it needs to obtain a silent license, which will include its update credentials, that will unlock access to ESET servers. You can alternatively do it in a way, that you import just the product licenses, converted into the offline files.  Please note, that you will have to update your ESMC server then from the offline mirror created by the mirror tool, otherwise it won´t get the latest modules, and won´t be for example able to configure newest settings in newest products. 

    In general, a better approach would be to allow access to ESET licensing server, via some proxy, and then use it for activation. 

  5. @OrthoC Than you for your feedback. Indeed, you are right, that´s the long term goal to achieve completely "careless" environment for our customers. As of now, the ecosystem consist of three components: 

    1. ECA server - we care about the upgrades
    2. ECA Management Agent - there is a task to initiate an upgrade of the agent, when a new version is available. This one can be easily triggered from the main dashboard, by clicking on the "red" portion of the chart, or from the dashboard "installed applications"
    3. Security Product - as Marcos correctly stated, there is a "micro PCU" functionality implemented, that we will be enabling soon. You can configure it for Windows Endpoints here in the policy, and that would mean, the moment we release, we will automatically either download or download and update the Endpoint program. 

    Long term goal is to remove also the point number 2 and let agents automatically update to the latest version as well. 



  6. Can you please let us know, how are you updating the modules? Are they updated: 

    • Directly from ESET servers 
    • From ESET servers, via HTTP Proxy
    • From offline mirror? 

    Thank you. However it looks to us, that the translator module is the latest, however for whatever reason the configuration engine module failed to update. That would require customer care ticket. 

  7. You are right, the policy is "buggy", as it by default it includes also default rules (when you click on the " Show built in (predefined) rules" checkbox in the bottom they will be shown). I will ask our team to change it.

    As a quick workaround, you should either edit the policy, and move the rules to the top (above the default ones). Or disable the predefined rules. I am sorry for the inconvenience. 

  8. Hi @Slawek Zarod some of the settings are not applicable for server products, as there is no such functionality in our server products. Some of them which are available on the client, and are not seen in the settings on the console are related to the asynchronous configuration engine module release procedure. We are aware of those issues, and will work on addressing them both in the form of another CE module release, and also in bigger process changes. 

  9. You are running a version of ERA server, which is almost 5 years old, and is not even supported for direct upgrades for the newest version. The best suggestion I would have is to attempt to rebuild your environment, for the ESMC V7, which is much more robust, stable and improved. For the license itself, the PLID XXX-XXX-XXX and the public IP address for your computer will be required. I would recommend to contact your local customer care, that should file a ticket for you. 

  10. @pps that is not a correct statement. regardless what is the ERA version, if your configuration module update is updated, you can connect and manage also Endpoints v 7.1. There is forward compatibility. 

    Your setup might result in those errors. As the logic is, that the first profile tries, then fails (triggers message) and then uses the second profile. 

  11. How are your updates configured? Theoretically this happens in case, when the Endpoint client is unable to communicate with the update server (it´s set to update from Mirror, or it is trying to communicate via proxy, with "fallback" disabled).

    This error will be written to log, if you want to suppress the interactive notification (valid for V7): 

    module update error.png

  • Create New...