MichalJ

I would like to inform you, that we have silently released ESET Remote Administrator 6.4. It is available in the download section on eset.com Please note, that the full global release will happen on Tuesday, July 19, 2016. Till then the repository is not available, meaning that you won´t be able to: Generate agent live installers Generate package installers of Agent / Endpoint Perform remote deployment task of ERA agent Perform component upgrade task from the previous version of ESET Remote Administrator (6.1.28+) Regards, Michal

Please note, that repository for ERA 6.4 is not yet updated. It will be updated on Monday, approx noon CET. So till then remote agent deployment / agent live installer generation / package generation won´t work. We are sorry for inconvenience. Also, the component upgrade task will be enabled next week, together with the repository update.

I guess that it is from the "client" that is trying to get updated from the mirror. I am not fluent in Spanish, but it seems to me it says "unauthorized access". First think that popped to my mind is that you should configure an username & password, to access the computer, from which the files are downloaded (as it requires some sort of authentication).

Business products are working in a way, that when you install a product a "seat" is taken from your license. When you uninstall (the standard way, not by formatting), the seat is automatically "released". If you format the computer, and reinstall again on the same computer, it won´t take a new seat, as ESET uses hardware fingerprint for seat identification. Only exception might be a virtual machine, where HWF is always allocated from a pool of resources, so it might be identified as a new seat. Then, you can free the seat using ESET License Administrator. Second option is, that if you are managing computers using ERA V6, prior to removing the computer entry in ERA V6 (delete computer), after it was formatted, you can before deletion trigger context menu action "deactivate products", which will perform the deactivation automatically (will contact the licensing server, and return the seat to the pool). Hope that this helps.

What you are doing wrong is, that you are not editing "Server Settings", but you are creating a policy for Remote Administrator Server. Please proceed according to the screenshots below:

Have you anyhow modified the file? Opened it / saved it as? Because the license filename is not a standard one.

Those requests are representing state, when product "asks" ESET cloud servers, about any configuration changes (in case of consumer products, it is related to antitheft, parental & my.eset.com integration), in case of business, it is related to the new licensing system (product is asking, if the license was not changed, or if the seat was not renamed in the license administrator). However, in general, it should trigger max 20 requests per 4 hours ideally, so it would be very good, if you send us the "seat ID" that you see in the "about" window of your ESET Endpoint Security, so we can find those specific requests and let you know, what have triggered them. You can send me the SeatID in the private message.

Hello, response to this is in the other forum topic, here: https://forum.eset.com/topic/8904-fail-to-add-setup-file-in-package-in-era-5/ However, what you have to do, is to adjust server setting" Maximum size of install package" to more than 150 MB, as installer for the latest EES is bigger. You can do it in ERA configuration editor, here:

Hello, you should change the preferences of your ERA server settings, and increase the maximum size of the installation package. Details are in this post: https://forum.eset.com/topic/8905-package-create-issue-for-windows-nt-64-bit-systems-version-5022650/?p=47070

What I would suggest is to: - Login to ESET License Administrator with your license key & ELA password (if you do not have your license key, please convert it using the ESET License Administrator conversion page: https://ela.eset.com/LicenseOwner/Converter, you will need your ESET license Username & Password for that. - Download the license file from there - by clicking the download icon for the license file, opening a dialog and downloading (name of the file should be like the one in the attachment).

Hello cbrasga, Thank you for your constructive feedback. I have to tell you, that your list of suggested improvements somehow copies the backlog of items that we would like to / are going to implement. As of now, the confirmed items are : 3 (ERA 6.5), 6 (ERA 6.5 / EP 6.5), 7 (ERA 6.5, already implemented in developments builds, however as of now only in "computer details") 9 (backlog item, without a target version yet, requires more complex adjustments of the threat handling process), 10 (backlog item, without a target version yet, but might be 6.5), 11 (ERA 6.5) Concerning the other items, we do have improvements tracked for 1, 2, 5 & 13 without target version. We will track new improvements for item 8 (should be easy to do). Item 12 might be partially solved in ERA 6.4, where we have enabled deselecting in case of "select all" functionality. So you select all items on the screen, and the deselect undesired items.

We will be adding the 64-bit native scanning core to the Endpoint V7, however road-map for that one is not yet set properly. The only thing I can say is, that it would not be this year. But as Marek stated, the level of protection is the same, core protection features are the same. Of course, there are some differences from the feature perspective, and the business products are remotely manageable, which is not the case of the consumer editions.

Hello, we have postponed the release of ESET Remote Administrator 6.4 by a week, initial release date was July 12, as of now we do expect that the release will occur next week, starting July 18 (our aim is to have it available on next Tuesday, July 19).

I would recommend using the "On-demand computer scan" client task, from ESET Remote Administrator. There this option is present.

Hello, ESET Endpoint Security 6.4 was released on June 7, 2016. Concerning the release of ESET Remote Administrator 6.4, which was planned for today, we have identified one issue, that we have decided to fix before the 6.4 is released. Therefore, the launch date will be postponed by one week, with currently anticipated date set to next Tuesday, July 19, 2016. We want to spare our users from any unnecessary upgrades of their infrastructure. I want to apologize for not providing correct information before, however the decision to postpone the release was made just today.

Hello, basically, you have two ways how threats are reported: Threats "TAB" (menu item in the left-side menu in ERA). This one is basically "threat log" meaning, all detection are transferred here, with there respective time stamp. Only way how to "get rid of the alert" from this part, is to manually mark those as resolved. That will decrease the "unresolved threat" count in the computers TAB, and also the alert counter in the threats tab If you then execute another on demand scan, it won´t trigger another entry in the Threats TAB. Active Threats report / dynamic group (this one is reporting the last state of the particular threat) Only way how to "get rid of the alert" from this report / computer presence in dynamic group, is to trigger an in-depth scan with strict cleaning. You can adjust your scanning profile by the steps provided by Marek above. If you then execute this on-demand scan, the threats will be removed from the report, and also computer will not be present in the dynamic group "active threats" But what I have understood from what you were writing in your post, you want to get rid of the alerts from the "Threats Tab", so the first 2 steps are valid for you.

Sorry for maybe a duplicate question, but what you basically want, is to create a one bigger report, assembled from multiple report templates in ERA 6, ideally combined into one .pdf output. Is this correct? That is not possible as of now, as the generate report task, is to able to include only a one report template at a time into the output. We are however planning to change the behavior, so you will be able to receive multiple reports at once (this is currently estimated for ERA 6.5 in December).

Hello, as of now, there is no option to manually reset Agent ID. The only way, is to use the "reset cloned agent task". Concerning the options, how to embed the agent in a n image is, to follow these steps: 1) Create the template image and install the agent and Endpoint on it. 2) Let the agent connect to ERAS (at least once) 3) Create an image of the disk. IMPORTANT: This computer (image) must not connect to ERAS again, otherwise this will execute the task and will prevent from executing it again. 4) For this computer entry in ERA, create a "Reset cloned agent" for the agent with trigger "ASAP" and no expiration so that anytime computer with the same Agent UUID connects, the task will be executed. 5) Image other computers using the prepared image. The "Reset cloned agent" task will change the unique ID so that the server can distinguish between the clients. We are currently working hard, to solve the issues with supporting pooled environments. We aim to have fix available in ESET Remote Administrator 6.5, which is planned for release in December 2016.

Yes, ESET Remote Administrator 6.3 is compatible with ESET Endpoint Antivirus / Security 6.4. 6.4 was basically only a service release, with supporting functionality needed for soon-to-be-release ESET Remote Administrator 6.4 (as of now planned for July 12) and couple of bugfixes. You can check the full changelog on eset.com.

You have to go to "Policies", create a new policy for "ESET Rogue Detection Sensor", configure the details (check tooltips for the correct option) and then assign it to the computer where RD sensor is running.

Hello, It seems to be a problem (known issue) which is specific to the ERA appliance. Please follow the steps in this forum post, to resolve it: https://forum.eset.com/topic/8061-workstations-showing-up-as-unmanaged-in-era-63-and-task-timing-issue/?p=43028 Also, please be aware, that agent - server communication is always initiate by agent, so it´s the agent who connects. Issue could be fixed by the restarting the server, as then, the webconsole data showing "last connected time" gets updated.

Hello, Unfortunately this is not possible in the current implementation. It´s saved in "current user keys" in registry, which are different per each user.

Hello mackintire, All three of your suggested steps / fixes are already on the road-map for the future ERA versions. First issue was for a longer discussion with Legal, due to possibilities of EULA changes between product versions. This will be solved by the step you have suggested (invalidation of task & notification tight to that one). We are in the process of designing another way, how EULAs are handled, which will allow us to deliver "always use the newest" version. Secondly, we will provide local repository for ERA, where you will have full control, over the versions (this one is coming together with the EULA change) in ERA 6.5 (December 2016). On top of that, we are going to adjust our internal processes, related to repository updates, so we will keep at least 2 versions (newest + one older) of a specific product version in the online repository of ERA, so the older version is not automatically removed, as soon as the newer one is released. As I have explained in the other thread, this time we have removed the 6.3 packages due to planned release of ERA 6.4, which will bring long awaited "package generation option", however that would be supported only with the Endpoint 6.4 and not older. We are sorry for that.

If you click "manage policies" on a client, it shows you only the policies assigned to the particular client, not the ones, that are inherited from the group. Important is, if you click on "manage policies" on a client, or on a "group". On a "group" you manage only assignments for that group, on a "client" only the ones for that client. You can however click on the "client details" (opens a popup), where in the tab "configuration" you see all of the policies, that are either inherited or applied directly on the client, in the order they are applied. However, when you click "manage policies" again, you are managing only the ones, that are directly applied to a client. We are currently designing a way, that would improve this behavior, so the answer for your question is, that it was not yet implemented.

Basically, the entire idea of ERA 6.5 release, is focused on support for multi-tenant usage of ESET Remote Administrator. We will bring the new security model, allowing data isolation + we will work hard on further database performance optimizations / performance increase, which will make ERA 6 well suitable for the use-cases described above (one ERA used to host multiple customer entities). Other functionality tailored for this, is planned as well, including for example management of installer packages (new deployment option, that will be added to ERA 6.4 and others). Concerning the AVG Cloud Care, were those customers also using the subscription licensing model (monthly billing). Is the customer actively using ESET MSP Program? If yes, there are a lot of improvements planned for MSP Administrator as well, however with a slightly different time-frame.