MichalJ

Hi @Carl S - when you just delete both entries, the one that has agent, and is correctly connecting will reappear in the ESMC server, however it will be placed into the ESMC group. Such situation might happen, when the system / agent was reinstalled, so it connects to the server with a newer ID. In general, you did nothing wrong, deleting machines will however wipe their previous data history of tasks, and reported detections.

Hello @Piter - yes, when you renew your license, you will just have to generate a new offline file with the ESMC token, and then create a product activation task, that will deploy the license to your clients. It should work without any issues, if the license is generate for the correct application (offline files are application specific, so if you use EEA, you need file for EEA, etc.).

If you are using the "EFDE" managed via ESMC / ECA, you need to decrypt it by assigning a policy that sets the encryption to "disabled". Then it will be possible to initiate the decryption on the laptop itself.

Hello, such procedure should be possible for both EEE and EFDE, I have contacted my colleagues, and they will respond with instructions on Monday.

@DAP Also one suggestion. As you have explicitly stated that you have 150 PCS, what I would recommend is to evaluate "ESET Cloud Administrator". This is cloud based service, hosted and maintained by ESET. With recently planned updates, the ecosystem should "auto update" to the latest version, meaning you will seamlessly transition as the time goes, and ESET releases new version. I do understand your reasoning, but a lots of time has passed since we have released the first version of the V6, so I can easily say it´s a different product now. Please note, that the V5 will most probably reach EOL in December 2020, so its recommended to commence preparations. As Marcos suggested, you can deploy just the ESMC agent, this does not require the restart. Then you can use the agent to uninstall the legacy V5 product, and install the new V7 endpoint. Regards, Michal

@jcook & @Palmolive I have briefly checked it with our senior development staff and according to them we are not aware of those issues. Therefore, to perform proper diagnostic before investigation I have to kindly ask you to contact our technical support, and provide whatever evidence you have (for example the screen videos you have mentioned). We will for sure analyze those issues. You can send me your ticket number, and person from ESET who has responded to you on your ticket for easier identification. Thank you, Michal

You can theoretically even automate this, using dynamic groups: Create a dynamic group template, that will monitor specific functionality problems Create a dynamic group using this template, ideally under the "all group" You can either set a policy, that will be applied to make sure feature is enabled (however, once the machine leaves the dynamic group, settings will revert back to state before) You can execute a run command task, that will enable specific protection features, if they were not "disabled permanently", but just paused (by a local user, having admin rights). Details are here: https://support.eset.com/en/kb6382-use-eset-command-line-ecmdexe-to-importexport-security-product-configurations-in-eset-endpoint-products-65-and-later

You can find the details here: https://help.eset.com/esmc_install/71/en-US/installation_deployment_scenarios.html In general, appliance is not recommended for bigger environments over 5000 seats, due to the included configuration of all of the components. Below this threshold, it should follow recommendations for the ESMC hardware (VM should be given similar parameters, as if installed on a physical HW). Details for that are available here: https://help.eset.com/esmc_install/71/en-US/installation_deployment_scenarios.html?infrastructure_sizing.html

Hello @Jason Yeoman I have to say, that I am a bit confused. In your post, you refer to it as "NOD 32", however then you talk about "ESET Agent" version 7.1.717.0 which is indeed the ESMC agent only (not a security product). Couple questions: How was your installer configured? Out of what you have said, I deduct it´s "all in one installer" (EXE package), with only agent configured, correct? Have you attempted to just download and run a standard MSI, with a "server assisted install? If you want to remove the crippled agent install, I recommend to use ESET Uninstaller https://support.eset.com/en/kb2289-uninstall-eset-manually-using-the-eset-uninstaller-tool

Hello @Adam S Can you please share with us your ECA instance ID? This seems to me like a problem with the identity server (EBA portion). If you try to access EBA.eset.com, does it work?

@DAP Please, which version of ESET Remote Administrator are you using? If V5, you need to import a new license file (not key). File should be included in the activation e-mail, or you can get it from ESET License Administrator / ESET Business Account. Please note, that ESET Remote Administrator V5 (as well as Endpoint V5) will reach end of life by December 2020, and as they are approx 8 years old, they should not be used. Newer products provide much better management (even from Cloud), and much better level of protection, given the many changes. Within your license you are eligible to use always the newest product from ESET, so I would encourage that you upgrade at earliest convenience.

Hello, if you use ESET Cloud Administrator, you can replace the license using product activation task (select your computers, choose “new task” / “product activation” and choose the new license. If you have entered the trial license manually to clients, you will have to switch the license the same way. Automatic reactivation is not supported.

What I can think of is that you might have old, non-compatible version of ESMC agent installed. Linux V7 product needs the latest version of 7.1 agent. Besides that, it should work without any issues. I have forwarded this case to a more skilled colleague, who might bring more insights, but 7.1 agent and V7 linux EFS should work without any issues.

@Glitch 6.5 is kept in support only for the Windows XP. If you do not have Windows XP in your portfolio, we recommend to install a newer version, especially version 7. Also, considering the size of the network (10 000 devices), what is the reason you have chosen to not use ESMC / ERA? It would make your life a lot easier. Also, for the version 7.2, we are planning to introduce automatic product updates, that will keep the Endpoints on the latest version, so such difficulties will be prevented. Is there any particular reason, why you want to stick with the older version besides the workload it would generate? Also, what is your standard "software update" policy, meaning how is software life-cycle handled for other products you use? Just a side note, not to annoy you, but to explain the situation a bit: with dramatically changing "ecosystem variables" (Microsoft releasing Windows 10 2-times a year, and Apple having annual release cycles), us as software vendors have no other choice, than to adopt more aggressive life-cycle policies, and towards the future abandon "versioning" as we were used to it, and more move towards the "as a service" model, meaning you have your subscription and ESET guarantees a working version, which will update itself without you taking care of it. Our cellphones are doing it, office is doing it, and security software (in order to work efficiently for you) have to do it as well.

Hello, Diagnostic logging basically transfers all of the information from the log files stored on the clients, for whose the diagnostic logging is enabled. It might take a while, till the task executes, the collection is enabled, and logs are transferred. For how long you kept that function that enabled? Also, which logs in particular you want to collect? Is the particular feature actually enabled on the target machine?

EFSW: http://repository.eset.com/v1/com/eset/apps/business/efs/windows/v6/6.5.12018.0/efsw_nt32_enu.msi http://repository.eset.com/v1/com/eset/apps/business/efs/windows/v6/6.5.12018.0/efsw_nt64_enu.msi EMSX: http://repository.eset.com/v1/com/eset/apps/business/ems/exchange/v6/6.5.10059.0/emsx_nt32_enu.msi http://repository.eset.com/v1/com/eset/apps/business/ems/exchange/v6/6.5.10059.0/emsx_nt64_enu.msi EMSL: http://repository.eset.com/v1/com/eset/apps/business/ems/lotus/v6/6.5.14026.0/emsl_nt32_enu.msi http://repository.eset.com/v1/com/eset/apps/business/ems/lotus/v6/6.5.14026.0/emsl_nt64_enu.msi

You have hidden the relevant information - your license ID, that would allow us to explore the problem further. Can you please send me a private message with your PLID, so we can take a look at the issue? How many devices in total have you connected / activated with the license?

Hi @TonyK Can you be please more specific in which product you are trying to use? V7 won´t have this issue at all, as it uses the new native licensing system. Also, where are you getting the lic files? As for MSP licenses, those are not accessible in the MSP licensing portal (EMA). Based on the knowledge I have, the installation of AV + license together via task from ESMC / ERA won´t work for V4.5 linux server products. I have contacted our teams to find out, if we can provide any suitable solution / workaround.

Hello to all. Next versions of ESMC / ECA will have the "old behavior" reverted back. Meaning single column sorting by default, with one click application, and multi sorting available on request, via a context menu. We are sorry for the inconvenience caused.

Hello, 6.5 agent is compatible with the ESMC server. Do NOT upgrade agents before having completed the upgrade of the server. As newer agents (7.0+) are not able to talk with the older server Yes, license is compatible with the ESMC. Also, please note, that after the upgrade of the server, you should also upgrade the agents to the latest version, to be able to use all of the new features of the ESMC 7.1 properly. Once the old 6.5 agents connects to the 7.1 server, you will be able to send a "component upgrade task" to them to upgrade them remotely.

Hello @ST20, per the page: https://www.eset.com/int/business/security-packs/ you should be eligible to use ESET Security Management Center without any issues.

Hello @NoMayo, yes your case is related to the problem posted on the forum (issue with expired certificate).

In some cases, combination of symbols is not possible due to internal database limitations. This is exactly the case. What would be the purpose of such report?

Just send me a private message with your public license ID (XXX-XXX-XXX)

Hello @magielonczyk, such request is already being tracked in our backlog, however it was not yet prioritized for development. Internal reference: IDEA-1205