MichalJ

Hello, there is no concept of "server to server" replication in ESET PROTECT (or any ERA newer than version 6). It is based on a concept of a central server, and multi tenancy, meaning you can have different admins responsible for different sites / locations, however all of the computers still connect to a central server. You can theoretically use HTTP Proxy component, to forward the connections. More details can be found in architecture portion of our help: https://help.eset.com/protect_install/80/en-US/?architecture.html

Hello, in this case, the original configuration will be retained, meaning installer will just replace the installers but the settings will be kept. In this case, also license is not mandatory.

Hello, currently such option is not available. I will check with a respective product manager, whether this is in the product backlog.

Please note, that if the screenshot from your policy, secure browser is actually not set by the policy. You will have to click on the full circle to apply the setting. Currently, even though the switch is in "disabled" state, it does not affect the endpoint behavior, meaning if the user enabled it locally (for example if having admin rights), that might have triggered the "non functional" error locally. Your policy should look like this:

Hello, Secure browser is a new functionality that was added in V8 Endpoint: https://help.eset.com/ees/8/en-US/solving_problems_protocol_filtering.html?whats_new.html You can disable secure browser via policy from ESET PROTECT: https://help.eset.com/ees/8/en-US/solving_problems_protocol_filtering.html?idh_config_sb.html Most likely, this might be related to either fact that your endpoint was recently updated, or your computer was recently updated. We might need more details (logs from client) to investigate, but for that, a customer care ticket is recommended.

@beethoven Local pausing of the protection requires administrator privileges. Meaning a standard user won´t be able to pause the product. However, pausing is really simple, just click on the machine in ESET PROTECT, choose "new task", and then in the options choose a "run command" option . Over there, just copy the command line from the linked help article (for example to pause the AV "ecmd /setfeature onaccess pause"), and click execute. Paused protection will trigger a red computer status. Corrective action (re-enabling) can be done by one click over the reported problem.

@gointern in order to be able to properly identify the problem, it will be essential to see the actual e-mail you are referring to. Can you please share with us the particular e-mail message?

@beethoven what you can do, is you can do this via "run command task". and use the command line options, to pause protection on the client. Here are the respective commands: https://help.eset.com/ees/8/en-US/?idh_config_ecmd.html

License itself covers any Mail Security product, that ESET currently develops. Meaning, even after the "ESET Mail Security for LInux" is discontinued, you will be able to activate our Mail Security products for Microsoft Exchange, and IBM Domino. There are no plans currently, to have a Mail Security product that will be running on Linux.

Hello, yes this is possible. The only thing you need to do, is to navigate into the section "Reports", search for the report "Audit Log", and edit the report template with a filter "relative time occurrence" set in the way, that it is 3 months ago and now. Please note, that the newly released ESET PROTECT (V 8.0, successor of ESMC) has a "audit log" section, which allows you to filter by time, and by user, and by action type. It might help you to find what you are looking for.

Hi Dennis, That would indicate that there is some problem in communication between the particular device, and ESET licensing servers. https://support.eset.com/en/kb332-ports-and-addresses-required-to-use-your-eset-product-with-a-third-party-firewall Other possible explanation would be, that device will be present there "twice", meaning, it changed the network adapter, and it resulted in the seat "duplication", so the total amount of used devices in EBA would be higher than the actual number of devices in use. Do you use "ESET PROTECT" to manage them, or are the devices just installed and controlled locally by the computer users on each machine?

Does I get it right, that what you want to achieve, is clearly see which machine is outdated directly in the "computers" table, meaning outdated = endpoint software / agent is outdated. Is this correct? What I am confused about is the word "license" in your report. The "outdated status" only refers to the installer itself, and has nothing to do with the license. Please note, that for both Agent, and Endpoint, we are working on introducing an automatic update, meaning the agents, and security product instances will update transparently, the same way how product modules (detection engine) is updated.

Hello, you have not stated to which product this relates to. My assumption is, that it is related to ESET Security Management Server / ESET PROTECT Server. Unfortunately, our SysLog Export is not multi-tenant, meaning it can only export data as a whole, not selectively based on locations / different admin users.

Hello, This will be a tricky. They should upgrade the server to ESMC 7.x, and also the agents to at least 7.x in order to allow the agents to connect to the cloud. ERA 6.x agent can´t communicate with ESET PROTECT Cloud, due to different replication protocol. However, agent V7 can´t communicate with V6.5 ERA. So in this case, unless the server / agents are updated, the only idea would be agent redeployment, from the ESET PROTECT Cloud instance.

Hello, can you please provide more details, for which reason would you need such functionality? ESET Endpoint have eRMM interface, that can theoretically populate data about the application statuses (reboot required is among them) to a 3rd party system. Also, as you have indicated that you work for an MSP, it´s quite non standard, that MSP will operate a software without proper management console.

Hello, do the machines have something in common? (operating system, device type, agent version ...). Also, as you said "REMOTE ADMINISTRATOR", the first thing would be to upgrade your infrastructure to the latest version, as ERA 6.x is currently reaching EOL, and has been replaced in the meantime by versions 7.x and 8.x (released last December, under a new name ESET PROTECT). In order to check what is the problem, you will have to inspect the affected machines, about what could be the reason for them not connecting (any issue with the agent, corrupted local DB, or machine simply being shut down).

Hello @pronto, ESET PROTECT (8.x) is basically a next iteration of ESET SECURITY MANAGEMENT CENTER (7.x). As you might have noticed, ESET has released a new offering line up, where the word "PROTECT" plays a major part, and as the console is the "centerpiece" it was decided it will be renamed as well. But in reality, it is the same, like if the 7.x numbering would continue, so I will easily compare it to 7.3. It´s not a generational shift, rather an evolutionary release. As marcos commented, upgrade is quite easy, just run a component upgrade task, targeted on the machine where server is running. We also recommend to upgrade the agents afterwards, which is since V8 possible also from the status overview dashboard.

Can you please send me your public license ID, (xxx-xxx-xxx) so we can check on our side? Also, have you tried adding the license to an EBA account and then adding the account to your ESET Protect?

You can validate whether the license works by remotely connecting to the server where the Mail Security is installed, and entering the license key into the activation wizard on help and support section of the local program user interface.

I will ask the documentation team, to look into this.

Hello, thank you for your feedback. I will follow up with our product management / engineering team. I do agree, that such scriptable option should be available for a large scale/silent deployment, especially in MSP environment. Will let you know, why I hear back from them.

@dfrey you have not specified, whether you have entered the license key during the installation, or after into the "licenses" screen of ESET PROTECT user interface. What was the error it gave you? More details can be found in server trace log, where you can search for "ERROR" from the time you have attempted the insertion. You can send me your license ID via private message, I will check, whether I have the same problems, or there might be a connectivity issue between your instance, and our licensing servers.

Hello, license can be upgraded from EEA to EES, however in order to use ESET Endpoint Security, you will have to install the corresponding software package (upgrade the software). Upgrade should be possible, however you will have to reboot your computers, once the software has been upgraded to EES / newer version. Latest installer can be found here: https://www.eset.com/it/aziende/endpoint-security/endpoint-security-windows/download/ With regards to the license upgrade, there are two options for you: 1, Use ESET Endpoint Protection Advanced (that convers both Desktops / Servers) - and will allow you to install Endpoint Security 2, Use ESET PROTECT Entry (in Italy still available under the original name ESET Endpoint Protection Advanced Cloud, that will also allow you to use also our cloud management console, if you would prefer it that way (however, this option is a bit more expensive, especially if you have been paying renewal prices). Both offers are here: https://www.eset.com/it/aziende/it-security-piccoli-imprenditori-startup/bundles/

Hello, I think that there is a principal misunderstanding. Dynamic group behaves like a filter, that is evaluated on the client, and only the matching clients are listed in a dynamic group. Dynamic group does not have it´s own view, it uses the "computers" table, which does not have any option to add a column with agent version. As of now, this is not planned to be added, as for the future versions we are implementing automatic agent update. Also, information about if your agent is / is not up to date, can be found in dashboard, specifically sections "Status overview - product version status", where there is a dedicated column for "agent", which can be drilled down. There is also a dashboard "ESET Applications", where are particular report templates listed, which outdated versions you have present, and you can drill down to computers page, where only computers having that particular version are listed. You can also create a custom report template, that will list you computers, with particular installed agent version (just make sure, that in sections "filter" you set condition to "application name" is one of "ESET Management Agent". Would that solve your issue?

Unified hardware report that will allow you to combine Device info + info about CPU / RAM / STORAGE is already implemented, and will be released in a next version of both ESET PROTECT / PROTECT CLOUD. For the combination with installed software details, I will follow up on this with our technical teams.