MichalJ

Hello @Tita314, Yes, similar functionality is in planned for the upcoming releases.

@rubencastello90 As stated by Marcos, we in the upcoming release, we will have both configurable dynamic groups and support for mobile devices (in the first iteration the Android ones). With regards to the patch management, we are tracking such request in the backlog, but nothing is yet confirmed.

Hello, packages are not split by 32 / 64 bit. Agent automatically install correct bit version based on the installed operating system.

@AlphaundOmega can you please share your ECA instance ID (you can find it in your EBA account, in HELP / ABOUT, under the terms of use as it seems that your issue is not related to general ECA issues, and might need deeper investigation.

Hello @slarkins, yes, for mac ESMC Agent, you need to use "component upgrade task" and for the Endpoint client, you need to use "software install task". Please note that in order to use agent on V7 and never, you first need to upgrade your server to the V7 as well.

Hi Sandro, you can navigate to the dashboard "ESET Applications", where you would see a list of outdated software. You can drill-down to the list of computers per each outdated software version. In case you are using ESMC 7.x, there is a dashboard element, that clearly shows the share of updated and outdated agents.

Hello @damtechmatt I have good news for you. Towards the end of the year, we will be releasing an update to ESET Cloud Administrator (It will come with adjusted naming) that will remove the "size limitation" of 250 seats, and will also be available for our MSP partners to order / provision cloud instance from the ESET MSP Administrator (msp.eset.com). So stay tuned for upcoming news in the following months.

@ChrisR as you have mentioned "ESET Remote Administrator", we need to double check, if you have already upgraded your ERA server (version 6.x) to ESET Security Management Center (version 7.x). If not, the first thing you need to do, is to upgrade the server. Upgrade might be possible via a component upgrade task, if your 6.x version is at least 6.5. Please note, that ESET Management Agent is not compatible with the ERA Server 6.x, and first thing you need to do, is to upgrade the management server. After that completed, you can proceed with the upgrade of agents, as written in the post by marcos.

@SeanMSys You are running a very old version of ESET Remote Administrator. As marcos stated, all Windows 10 machines that will receive the update 21H1 will have to be running management agent version 7.3 and newer. In order to be able to deploy the management agent of that version, you will first need to update the server to version 7. Please note, that 6.x agents are able to communicate with the V7 server, but the newer agent is not backward compatible with V6 server. So management server upgrade is the first step you need to take, in order to solve the issue. Then you can proceed with the management agent updates, on the affected machines.

Hello @mikechan, most likely, it will. What Marcos tried to explain is, that there is no reason to not upgrade the ESET Endpoint client software on your machine to the latest version, as it it is compatible with Windows 7, and brings many benefits. Of course, the decision is yours, however from the vendor standpoint, ESET guarantees module update support for the products that are in full / limited support only.

Hi @Reto, per my knowledge, number of active terminal sessions should be reported in the column "Subunits" within ESET Business Account next to the name of the particular server. This information is not displayed anywhere in ESET Security Management Center at the moment.

You can click on the task, and select an option to "run on", where you can specify another targets.

Hello @LesRMed Techncally, EFSW and EEA share the same "activation matrix" , meaning it is technically possible to activate EFSW with the EEA (ESET Endpoint Antivirus) or EEPS (ESET Endpoint Protection Standard) license. You can easily "move" the EFSW under the right license by simply sending an product activation task to the computer where the EFSW is running, including the "File Security" license.

Hello, you will need to deploy "ESET Security Management Center Management Agent" to the device. Also, you will need to configure your ESMC server, to accept connection from the "outside" in case it is running within your internal network.

Hello, it seems to me your case is similar to this one, where resolution was provided:

Also, please note that the product that is intended to be used on Windows Server operating system is "ESET File Security for Microsoft Windows Server", not the ESET Endpoint Antivirus / Security.

Hello, in case you have access to the "ESET Business Account" or "ESET License Administrator" (I do not know, which one you refer to as "ELB", you should be able to list all of the currently activated seats / devices with a particular license, and deactivate them. This will make all of your endpoints "deactivated", but once you have connected them to the ESMC server, you can create a product activation task, and reactivate them with a correct / corresponding license. Hope I understood your case correctly and it would help.

You can set a password via a new policy for "ESET management agent" which will have the password protection enabled in it.

Yes, it should be possible. Please note, that the ESMC component upgrade task, targeted at the computer where ESMC is hosted )server itself) will update both server, and webconsole components, to the latest version 7.2

Hello @mo_zaidan would it be possible to post in English? I would then ask my colleagues who have better experience with the API to check.

You can theoretically create a report, that will pair "seat name" (name under which the computer is known to our licensing server) with "computer name" (name under which the computer is known to ESMC). Then you can search the reported output for the value.

Hi John, I will send it to our engineers for investigation. The entries where you have the same device twice, is a known issue when the old version of Endpoint remains "registered" as activated. However, only one unit of a license is consumed in that case, due to the fact that license consumption is tight to a hardware fingerprint. It´s safe to remove the duplicates. The other issue (different names of the devices) is something that might need to be investigated. You can theoretically "reset" them in a way, that you deactivate all of them, and reactivate them from ESMC, ideally via a dynamic group set to trigger activation task automatically when any product reports it is not activated. (if they are connecting all-right). That might result in correction of the issue. If it reappears, then we will have to investigate it in more detail. Regards, Michal

If you want to put them back into the license pool, you just need to delete the offline files from the license administrator / business account. However you need to make sure, that the servers which were activated by them, are no longer present. I will have to check with my colleagues, if there is any effective way of finding out which machines were activated by them. Theoretically a report in ESMC could be created, but that is usually based only on "public license ID" so both online and offline activated seats might appear in such report. But if those servers were decommissioned, one can expect they are no longer in use.

Cloud MDM for management of Android devices is planned for December 2020

Hello @Zen11t Can you please elaborate more about the need for seeing the agent version in the computers table?