MichalJ

@Embercide in case your computers still retain connectivity with the server, you can still issue the "software install task" with the 7.3 as target version and send it to the clients. They will download the the installers from ESET repository, so will use their connection. Nothing will be downloaded from the locally installed ESMC server. For the future, most probably for 2021, we will enable auto updates of ESMC agent as well, and the uPCU should be as well launched, as the common goal is to have a "transparent and easy" migration between product versions, so it would work as seamlessly as the module updates.

Hi @helis - you should be in general getting a tiny notification in the upper right corner of the webconsole, about new version of ESMC being available. Alternatively, you can create a "ESET Security Management Center component upgrade task" and target it towards the machine, where the ESMC server is running. It should upgrade the agent, server and webconsole to the latest version. However, even if your agents are on a newer version, there should not be any problem in communication, as those versions are mutually compatible, and no break in communication should occur. I would investigate one of the affected machines, for problems in agent tracelog / status.html to determine the underlying problem.

Yes, you can always increase seat count as compared to the pack, the EEPAC spans from 5-250 seats (and we will expand it even further in the near future).

@beethoven Thank you for your feedback. Can you share with me the feature list of the Business Pack (web link, or any other source), I will make sure that this is corrected, as it creates unnecessary confusion.

Hello @beethoven. What confuses you is that the "ESET SECURITY MANAGEMENT CENTER" is a newer version of "ESET REMOTE ADMINISTRATOR". So you just need only one, and in this case the first one (V7.1 is the latest version). If you opt in for ESET Endpoint Protection Advanced Cloud, the primary difference is, that you will not have to install and maintain the management server (update it to newer versions, patch the system, etc ...), but it will be instead provided via a cloud service, maintained, updated by ESET. You will just download the installers, deploy them to your computers, and that´s it. So the primary benefit is that for you it´s almost zero maintenance solution, which will be always updated to the latest version by ESET to ensure you have the latest features at your disposal. If you want to see how this solution looks we have an interactive demo available here: https://www.eset.com/us/business/cloud-administrator/demo/

Hello @RSS, this is already being tracked, however due to relatively lower prevalence of this request it´s not yet planned for implementation. Internal reference: IDEA-1281

@beethoven I would recommend that you use ESET Cloud Administrator, meaning purchase one of the eligible cloud bundles (ESET Endpoint Protection Advanced Cloud would be my choice). In those cases, the console is hosted by ESET in the Cloud, you do not need to maintain it, and as it is cloud based, the only thing you need to handle is internet connectivity at your two locations.

Hello @avar39 - as stated by Marcos, this is currently not possible. However, we have seen such requests in the past, so we are tracking improvement request for it. Can you please share your details / use-case, for what you would like to use this mechanism?

Hello, as stated by Marcos, exclusions super-cede any blocking rule, regardless whether it is by hash, or the detection is triggered by Live Grid, our updated detection database. The same would apply for the case, where it would be present in the excluded folder.

Hello, the build you have installed is in fact ESET Endpoint Antivirus, which compared to ESET Endpoint Security does not have Firewall in it. Now the question is, whether it is due to the FW not being present, or the actual beta helping to address the issue. Maybe @Peter Randziak who shared the build can comment further.

@Leviathan as marcos has stated, you can create "ESET Business Account" and add your license there. If the applications you are using are on the version 6 and above, after adding the license (via license key, you will have to have the license key, if you do not have it yet, you can get it via the self service function - https://eba.eset.com/LicenseConverter After this, you will receive confirmation e-mail to the address under which the license is registered, and after clicking the link license will be added, and all activated devices will be visible. In case you format the computers, it´s recommended to perform deactivation via EBA. If you do "standard uninstall" the license seat should be freed automatically.

I also looks to me that the client product is somehow broken, as in the window header it shows "ESET Endpoint Security", but the GUI says Smart Security. It might be possible, that you will have to use ESET uninstaller in the safe mode, to get the version removed as it might be somehow corrupted (the whole computer scan section of the main menu is missing).

In general, if the machines are running EP V5, I would recommend the following approach: install just the management agent (either via GPO, or agent live installers / all in one installer with just agent, pushed by remote deployment tool). Uninstall the Endpoint V5 via software uninstall task + reboot the machine Install Endpoint Security V7+

I would suggest to update both the EFDE client and ESMC agent (if not done yet) to the latest versions. Maybe there is some version mismatch between the version of the configuration module, that is responsible in delivering / translating / applying the configuration on the target computer. If the problem persists, I would recommend opening a customer care ticket, so our engineers could investigate it further.

I have been asked by the developers to ask you if it would be possible for you to submit an official customer care ticket. It would help our devs to properly focus / allocate time to the investigation of this issue. Thank you.

Hello, can you please make sure that you do not have any other EFDE policy assigned to the clients, especially if the "force flag" is not set to any of the policies? Force flag could prevent other policies to being applied correctly on the machines. Also, is the "apply flag" correctly set for the password field? "apply" means that it would be actually applied on the target devices. Apply (green box) and Force (red box) below:

Thank you @karsayor, all clear. I will check with the development team why the deletion of "MSP" group is not possible even in case when the MSP account that triggered its creation is no longer present in the console.

Hello @karsayor The most likely reason would be, that as you have synced your ESMC with EMA 2, it created the "MSP" container. This one is "read only", and can´t be deleted, unless the EMA account used for addition is still in use. You will have to reconfigure your task to sync a different container, not the group all. I would suggest to create "AD" group, and then move all other groups / computers there, and reconfigure the AD sync accordingly. As the "MSP" is empty, does it mean you do not plan to use automatic synchronization of managed companies in EMA vs. groups in ESMC? What is your EMA / ESMC setup / relation? Meaning, if there is any relation at all, between the customers list in EMA, vs. the static group structure in ESMC.

Hello, are those notifications being sent by the Endpoint itself, or by the ESMC server? Muting does not do much, except it suppress the red problematic status in the computers table, it should not affect either client side, or ESMC side notifications.

Hello @Marcelinho, you are most probably meaning installation of the latest product version. If your computers have still connection to the management server, even if they are working remotely agents are able to communicate, after you set a task to "install latest version of software", computers will connect to ESET Repository to download the latest application version. For the future, we are working on micro PCU auto-update, meaning you will be able to set your clients to automatically download latest product version upon availability, and install it, where at the end only a prompt for reboot will be displayed for your end users. This is however not yet enabled, and should be enabled with the upcoming product release.

Maybe a "Stupid" idea, but is the Windows time set correctly? There is by default a check in ESET application, that compares the date of the issue of the latest detection update, against the system time. If the system time is set in the future, it could trigger this notification, but it´s just a guess.

Hi Peter, I would suggest to use the concept of dynamic groups. You can sed a DG for "installed product" Endpoint Antivirus and "installed product" Endpoint Security, and then apply the product activation task for the first, and second dynamic group. Aslo, If those licenses were added individually, you can also adjust access rights, where admins from company A would see only company A, and license moved to "access group A" and company B, would see computers for company B, and license moved to the "access group B". (this would work only in case when licenses were added via different EBA accounts, or via separate license keys).

It seems that the agent is already on the version 7, however the server is on the version 6.x, which means that they are not compatible. Newer server will accept connections from older agents, but older server is not able to accept connection for newer agent. So you will have to update the server manually, ideally via all in one installer downloaded from the ESET website.

Is the setting set to "Apply" ? If you request the configuration from the affected computer (one click action in computer details), what is the output? My suspicion is, that the "apply" flag is not correctly set. Also, is the machine connecting correctly to the server? Meaning, if the settings correctly replicated.

Hello, AFAIK you can edit task name for the "custom created" tasks, however not for the automatically created ones (defaults). Those can be only deleted / disabled.