Peter Randziak

Hello siobhan, no there is not an option to protect the settings by password directly. Settings are stored in esets.cfg file (protected by standard system permissions). They can be edited directly or via web interface, which has to have the password set. Regarding the notifications please see daemon_notification_script or notifications in general in the manual The configuration file is stored in /etc/opt/eset/esets and there are stored the settings even set via the web interface. So you can do the setup on one box, test it and than just replace the config file after the deployment on a new system. P.R.

Hello, thank you for sharing the solution with us. P.R.

Hello Elkar, sorry my fault. On pre-release there is 1080, which does contain the bug, we are testing new module with more changes so it has't been released yet. The solution for you is to switch to the regular update channel, there is Internet protection module 1173B.2 (for v.8), which does not contain the bug. I'm sorry for the confusion. P.R.

Hello, you may add e-mail addresses to the blacklist as shown on the screenshot, but I do not suppose that the spammers are sending it from the same addresses (which may be spoofed as well). Can you please resend the samples not detected to spam@eset.com as an e-mail attachment so we can analyze them? Thank you. P.R.

Hello, the GPO will not check if the SW is already installed. I would suggest you to deploy all Endpoints with the same method or to split them into some logical groups and deploy on the groups based on the method, which is more feasible for the particular group.

Hello, the list of ports used by default is available in our online help here. P.R.

Hello yesnoo, please try pre-release updates where new version of Internet protection module is available to check if it helps. Please let us know if it helped. P.R.

Hello Elkar, also new arriving messages are getting large? Which version of Internet protection module do you have? P.R.

Hello, the best option is to submit the samples / false positives as described in this KB article. So if you did it there is no need to do something else. P.R.

Hello, we haven't received the logs to check, yet. You can send them to me via private message. By the way do have ERA v.5 installed by any chance on the system? Or services registered with name "EraMDMCoreSvc" or "ESET Remote Administrator Mobile Device Connector" P.R.

For the user you specify for the ERA to connect to the database. P.R.

Hello, please send me a logs via private message with a reference to this thread, we will check it. Thank you. P.R.

Hello, go to the Details you should be able to see there all the reported issues. Is the client connecting to the server (see last connected column)? P.R.

Hello, there is no need to uninstall all the components just follow steps described here. In the KB article there are actually 2 ways how to do it, you should follow the one for advanced users. P.R.

Hello, is the Kerberos working on the server? P.R.

Hello, all installation pushed are with quiet parameter, that is by design.

Hello, a fix is planned for the next release so the agent restart will not be required. P.R.

Hello, in case you would like to solve threat related issue (and zero the counter) you need to run In-depth scan of all targets from the ERA (this is required to reset the counter). P.R.

Hello, the issue is solved by Internet protection module 1173B.1 available on update servers since yesterday. P.R.

Hello, the issue is already fixed for v.8 as well. Just check if you have Internet protection module 1173B.1 released today. We have confirmed from some customers reporting it that the update solved it. V.7 and lower hasn't been affected as far as they didn't get the module containing the bug. We are sorry for the inconvenience caused by this issue. P.R.

Hello, KB team prepared an article How do I install ESET Remote Administrator on Microsoft Small Business Server? (6.x) Please let us know your feedback in case you encounter any issues with installation when following steps in this article. Thank you. P.R.

Hello, we have a response from the Dev team, it is an confirmed issue on our side. This issue will be addressed in future releases of the product. Workaround for this issue is to change default language for the user which you use to connect to the database from your default to English via Management studio. Please let us know how it went in case you decide to try this workaround. Thank you. P.R.

Hello, promised KB articles: How do I upgrade ESET Remote Administrator 6.1.21 to version 6.1.28? (Windows) How do I upgrade ESET Remote Administrator 6.1.21 to version 6.1.28? (Linux) Please let us know if there is a scenario not described or something what does not work as described or expected. Thank you. P.R.

Hello, promised KB articles: How do I upgrade ESET Remote Administrator 6.1.21 to version 6.1.28? (Windows) How do I upgrade ESET Remote Administrator 6.1.21 to version 6.1.28? (Linux) Please let us know if there is a scenario not described or something what does not work as described or expected. Thank you. P.R.

Hello, promised KB articles: How do I upgrade ESET Remote Administrator 6.1.21 to version 6.1.28? (Windows) How do I upgrade ESET Remote Administrator 6.1.21 to version 6.1.28? (Linux) Please let us know if there is a scenario not described or something what does not work as described or expected. Thank you. P.R.