MichalJ

Hello. The licensing is the same for cloud and on prem. So when you have upgraded your license, it has upgraded it on all active endpoints, regardless if they are connected to the cloud version or on premises version. Even if you uninstall ERA from the on-prem server, but do not remove ESET from those other 11 machines, they will continue being counted. The best thing would be to login to EBA, deactivate all devices, and reactivate only the ones connected to ESET PROTECT Cloud, using the console activation task. Unless you have some more machines to migrate.

Hello, there will be soon a new version of the virtual appliance, that will be based on the Rocky Linux 9.

It´s actually pretty simple. ESET PROTECT Is built with concept of "task reusability" in mind. So you can create a task, for "disabling protection" (type run command, use the command from the example from Marcos). Then the only thing to do, is that you click on the device in ESET PROTECT, and choose option "run task". Find the one pre-created (you can name it as you wish) and execute it. However, as Marcos stated, this is not something that users / admins should be doing, as disabled protection is disabled protection. Therefore, it´s not as straight forward, but could be done that way.

For such behavior, you need to create two different dynamic groups. One for the Endpoint, one for the Inspect Connector. For ESET Inspect the below example should work, for standard Endpoint just change the "source" to "security product". Hope that this helps.

Hello @Glitch absence of this functionality is due to a bug. It will be fixed in next hotfix of EP 10.

Hello @PMIadmin can you please share details about as what kind of detection the CW Control is flagged with? I would expect, it would be some kind of Potentially Unsafe Application, as despite being a legitimate software, RMM / remote connection tools are many times misused by attackers to gain control over the victim´s computer. We will need to investigate the reasoning further, but based on my experience if specific application was misused like this in the past, we keep flagging it as unsafe. https://blog.morphisec.com/connectwise-control-abused-again-to-deliver-zeppelin-ransomware

Hello, transition of an endpoint to a specific group / company, does not change the license automatically. You can schedule a regular recurring "activation" task, that would reactivate the endpoints with the correct license. Or you can do it in a way, that you will create a dynamic group, that will be checking if Endpoint does not have a correct license (new dynamic group template, condition for "Activation / License public ID" is not one of and specify a license. It would require some manual work, but since then, you can easily automate the license deployment. I will check with product managers, whether this could not be automated, so license is changed, depending on company / group membership, in case of MSP automation.

Hello, maybe @Kstainton will be able to provide some advice. However, if you plan to use "EFDE", the boot password is the only way of working (comparable to BitLocker, where the encryption pre-boot password is tight to the device, not the user). Also, as the encryption is a system demanding process, it should be acknowledged by the local end-user.

Hello @eclipse79 - the connection in ESET PROTECT Cloud is based on when the ESET Management Agent last connected to the management console. - the connection in ESET Business Account, is based on when the ESET Endpoint 6.11. last connected to our licensing servers. Reason why this might be not matching is that the client could have been updated, or underlying hardware fingerprint has changed, and that computer entry was duplicated on EBA (this tends to happen when a different network adapter is being used). You should be able to make those "matched" by retriggering the product activation task which would force the licensing servers sync issue. Also look for the duplicate entry. Regards, Michal

Hello @David Fletcher Each of the notifications could be configured, and you can set different recipients for each / or multiple recipients. Just navigate to "notifications" tab, edit the particular notification, and in the panel "distribution" add the e-mail addresses of your colleagues.

Hello @Eleia ESET PROTECT Advanced allows you to use following functionalities: - ESET Endpoint Security instead of ESET Endpoint Antivirus. To get the added functionality (Firewall, WebControl, etc) you will have to upgrade existing installations of EEA to EES. - ESET LIveGuard Advanced. This can be activated for both EEA / EES. Activation is quite simple, you can do it "per device" or via "ESET Solutions Tab". - ESET FullDisk Encryption. This can be as well activated regardless of product used, either per machine, or via "ESET Solutions Tab". Regards, Michal

Hello. this might be related to a fact, that "shutdown" actually not shutting down the computer, but putting it into some state of hibernation (when the "fast startup" is enabled"). I would expect, that when you disable it, then the particular entry will be correctly updated.

Hello, I would follow instructions in the documentation: https://help.eset.com/protect_install/91/en-US/?migration_same_version.html

There was a temporary glitch in EMA, which allowed setup of ESET Inspect Cloud instance with the "on premises license". Which will however not be shown inside the cloud platform. If you would have "ESET PROTECT Enterprise", there should not be any issue like this.

Hello @Informatics as far as I know, there is not "condition" that would identify client as outdated, besides specifying a version being lower than a particular number. Of course, DG like this would be come obsolete quickly. Just to double confirm - you want to identify machines, which are outdated, by the means of dynamic group. Question I have is - what should happen next? Automatic software install task, or something else? As there might be a different solution to the problem you are trying to solve.