Peter Randziak

Hello, @timse201 the increased memory pool consumption is not caused by our product, not directly for sure as there are not any huge allocations made by our components. It is probably result of Windows caching, the same allocations would be probably caused by going through all files on the disk and by reading them. P.R.

Hello, The solution would be to add the license directly to the SW install task. Or you can create dynamic group for non-activated products and execute the activation above this dynamic group. P.R.

Hello, thank you for your report, we will check it. P.R.

Hello Morisato, updfiles - it is a cache of downloaded update files, you can clear it (manually or by Clear update cache), but the following update may be larger. backup - the files for update rollback feature, in case you think you do not need it, you can disable it to save some space. P.R.

Hello, @Baltagy, thank you for the dumps a created a ticket for the Devs to check it. @timse201 Please download Poolmon utility and run it with this command: "poolmon.exe -u -e -r –n", it will create poolsnap.log, which is required for analysis so please send it to me with output from ESET log collector via private message. Thank you. P.R.

Hello, the service release is planned for the end of Q2 of 2015, but no promises everything depends on development, localization and testing resources. Regards, P.R.

O.K., thank you. Please let it leak for a while, it is much more easy to find what is leaking when the leaked allocated memory is really over standard size. P.R.

Hello, sorry for our late response, are you still seeing high memory consumption by ekrn? Thank you. P.R.

Hello Baltagy, can you please wait until the memory consumption is over 400-500 MB and than create a memory dump via Procdump utility (this is important especially on x64 systems), pack the dump with SysInspector log and send it to me via private message? Thank you. P.R.

Hello, as Marcos said, try to disable it as you are not able to remove system apps. P.R.

Hello, we reproduce the issue in-house and created a bug report for the Dev team to check. Thank you letting us know about this issue. P.R.

Hello, can you please submit the logs to your local support for detailed analysis with output from ESET Log Collector attached? The web interface is not able to show the details because the installation logs are not fetched to the server. Thank you. P.R.

Hello, the in-product upgrade should be available in upcoming days, if there will be no serious negative feedback from users, who updated manually already. P.R.

Hello, I spoke about this with a colleague and we found out that you have ticket opened for this with us, right? If yes can we continue with the solution via the ticket? Can you please share the solution with the community here once successfully solved? Thank you. P.R.

Hello Renato, can you please send me export of the endpoint's settings and network communication captured by Wireshark during unsuccessful update attempt? We will check it. P.R.

Hello, the easiest way would be to use the proxy not directly so not to chain it. If you need to have one proxy behind another you can configure it not to request authentication from the other one. P.R.

Hello, can you please set the logging verbosity to diagnostics, reproduce the issue and send me the tracelogs to check? P.R.

Hello Ted, yes this is an issue with the product and it will be fixed in future versions. P.R.

Hello, I would recommend you to create dynamic group for computers, where the ESET product is not installed and deploy on members of that group. By this you can automatize the deployment. P.R.

Hello Dave, I would recommend you to password protect the settings so the users shouldn't switch it off. There is an issue with it with the current build, but in the next which will be released it should work flawlessly. P.R.

Hello, that is really interesting deployment scenario. You should run reset cloned agent task. The new ERA does not use such identifiers as the old one, each agent has it's unique ID. You can check the license usage in ela.eset.com portal. P.R.

Hello, we will have to think how to handle such environments. But you shouldn't have issues with the activation nor the updating. The ESET product is installed on the image before the deployment, right? Regards, P.R.

Hello, yes you can update the system, but I would really recommend to create a snapshot before update, just to be sure. P.R.

Hello, this will be fixed in upcoming hot-fix release of the ERA. P.R.

Hello, yes we plan to implement it in future versions of the ERA. P.R.