Walter Vergara

Thanks for your response Mark! We will be attentive to help generate possible continuous improvements in products. Yes, maybe change the nomenclature, but the option was super useful to see one alert above others

Hello Team, we see that since the update of the EP cloud console in version 5.4.7.1 we no longer have the filter option due to a problem of worse functionality. We attach a screenshot of two different consoles, the On prem console does have it and the cloud does not. Is it possible that this is so? Can something be done to add it again? Thanks!

HI Marcos, We already created the ticket, if there is a solution I will share it here.

Hi team, Since the last update of the console (Version 11.1.14.0), we can see that from the DEVICES-->search engine section: when viewing the devices, in some cases where the device has the IPV4 and IPV6 protocol enabled at the OS level, The EP console only shows the primary IP under the IPV6 protocol. It would be extremely useful to add both protocols in the search engine. For our part, we verified that in this section you can only add or modify the columns, and that in IP Address you CANNOT modify/choose between ipv4 or ipv6. Unlike the REPORTS section where we can discriminate between ipv4 and ipv6 If we are wrong or there is a possibility If you want to modify it, please tell us how to do it.

I found the solution, although the ESET Help specifies the migration of devices from the ON PREM console to CLOUD through the option: quick links, download migration policy, this option is viable for this case: migrating devices from a CLOUD console to another Cloud console (even if it is from different EBA/USERS) We set up a laboratory and created the environment to carry out the test from a Trial license to another license and the result was satisfactory: the equipment on console 1 was migrated to console 2. You must download the migration policy for console 2 (console to which we want to migrate the equipment) and import it to console 1 (console from which we want to remove the equipment to assign it to the other console) For this you must go to Policies-- actions--import

Clarification of the case: the client at a commercial level has already unified the license and expanded it to cover the other licensing, in this way the idea is to go from two licenses and two cloud consoles to one license and cloud console obviously expanding the license to cover the other

Hi, I have a question, If a client had two different licenses and needs to unify them (both ESET Protect Cloud consoles), so that all computers can be managed from a single console (console 1), a migration policy can be used (option in the ESET Protect console: Download migration policy) to migrate to console 2 ESET Protect CLOUD, so that in this way the two licenses that a client has can be unified and send the computers from console 2 to report to console 1 and manage all the computers from console 1.

Resolved! We install the On Prem console only to connect the agents of the hosts with Windows 7(We use version 9.1 for both the console and the agent). We create a task that redirects those Windows 7 hosts to the Cloud console. Once they are reported to the Cloud console, and we already have management of the Pc with win 7 in this console, we can uninstall the On-Prem console.

Sorry Admins for creating the forum thread in the General Section, it should go in ESET Business User Products->PROTECT Cloud. If it necessary you can move it.

Hello, we have a potential client who wants to implement ESET on more than 100 computers that have the Windows 7 SP1 version. The client does not have an Active directory or On-premise console: uses the CLOUD version of ESET Protect to manage the ESET solution. According to the official ESET website and forums, the latest version of ESET for said OS is version 9.1 The problem is that it is impossible to change the ESET agent+client installer on this type of console. It could only be done in the On premise Console. Is there any WorkAround to try to implement what is required? The only way we can think of to carry out this implementation is to install EP ON PREMISE, install the agents on the endpoints with the client in its version compatible with Windows 7 and then migrate that same Console to EP Cloud. Is there an easier way to implement this from the EP Cloud Console? Perhaps by modifying the installer path from the Cloud console, to the installer compatible with Windows 7 (version 9.1). Or, could you install Agent 9 manually and point it to the cloud instance and then assign an EBA username and password during the installation? I hope you can help me. Thank you.

Hello, here again. The client was able to remove the encryption with the pendrive tool after trying several times. Thank you very much for all the help provided!

Thank you for your help, the energy you give is admirable! and sorry for the insistence!

That would be very helpful to me, it is not a problem to send the logs. Here I send you the Recovery logs (https://support.eset.com/en/kb7894-eset-encryption-recovery-utility-diagnostics#SearchForMeta) *In addition, I place the respective logs and prints separately in the process 1 and 2 folders. Thank you for your Help Kieran! Recovery logs.rar Process 1.zip Process 2.zip

790856 It is from ESET latam, they escalated it to the company developers.

Yes its all ready scaled by a ticket , Thanks for your help. I will share information about how its going.