MichalJ

Hello, this issue is known, and we plan to fix it in the upcoming service release (currently planned by end of July).

Hello @mxp, we would like to identify the root cause of the problem. Can you please send me the license ID of the affected license via a private message? I will follow up with my colleagues. Indeed it should not take that long, so it´s either an one time issue, or a possible bug in the implementation.

Hello, the correct path for Windows machines should be: C:\ProgramData\ESET\RemoteAdministrator\Agent

Hello, you will have to troubleshoot the agents connection. You can find out the status of the agent on the machine that you want to connect, in programdata/eset/remoteadministrator/agent. Try to search for "status.html" that should inform you about what is wrong. Also the "trace.log" might include any communication errors. As an ESET customer, you can entitled to contact ESET distributor for Poland, Dagma, that should be able to help you with your troubleshooting.

I have been able to reproduce the behavior. It seems to me as a bug, so I will report it to our QA / DEV teams. that a confusing description is displayed for the group, as indeed it shows "dynamic group" even when "static group" is set as target. It only shows like that when you try to "edit trigger".

Hello, have you tried "Component upgrade task" targeted to the affected agents? Although it might not upgrade the agents to the "latest version", but it might upgrade it to the "latest compatible version", so via two tasks, you might eventually get them upgraded to 7.2. This is just a guess. What might also influence the agent capability to update is the version of the endpoint client. What are the EP versions that you have installed?

Hello, this option is already available in ESET Cloud Administrator console. Currently, as agents are updated via "Components upgrade task", which does not differentiate between agents, and other components of the ESMC infrastructure (server / webconsole) this option was disabled. However, in Cloud the server is fully hosted / maintained by ESET, so "one click agent updates" are possible. Please note, that for the future releases we work on "automatic agent upgrades", meaning agents would automatically upgrade themselves to the version compatible / matching with the server.

@Valleria if you authenticate using your "AD user" and option "login to domain" is checked, then after a password change, new password will work for your ESMC instance automatically.

Hello, In this case, if you want to have the task executed only "first time" upon entering the group, you should not use the "joined dynamic group trigger" (there is no such trigger available for static group). Instead you should set a trigger "ASAP" and make sure there is no expiration set, as past the expiration date, the trigger will stop working: I would however recommend you to create a dynamic group, focusing on a computer problem "product not activated", eventually together with a condition for a specific software installed (EEA / EES / ...). By that, even if any issues with activation appear, such trigger would "fix it". Alternatively, you can have the same task triggered on "joined DG" and then "scheduled repeatedly", with for example once a day, so it will retry the reactivation later again. Hope that this helps. PS: Are you sure, that the "Approved" is indeed a static group? As That´s not possible to be checked from the screenshot you provided.

@isaha do I get it correctly, that you use a locally created "update mirror" server for updating, instead of clients connecting directly to ESET?

@MarceUTD Release of ECA that will included EDTD screen is coming later during July*. Currently, EDTD tirlal license would not be visible in ECA, however this is going to change by the beginning of August*. *- this is current plan, and might eventually change, but as of now the plan seems feasible.

Hello, if you want to protect just the "host server" and not the "e-mail protection component" (mail flowing via exchange will not be scanned), you can also install ESET File Security.

Hello, after you synchronize the Active Directory, you need to deploy the management agent and a security product. You can use various methods for deployment, like GPO / SCCM, remote deployment tool or manual deployment by using a generated installer. None of the tasks will be working, before the machine is actually managed = agent is installed on the target computer.

Hello @Cp3p0, thank you for your feedback. I have forwarded it to the responsible product managers and UX experts. All of the issues you have highlighted are not user-errors, and we plan to address them in the future releases of EMA 2 (especially option to automatically hide suspended sites, de-provisioning of customers (incl. replication of such changes into ESMC) and adding settings with the option for auto deactivation. We do not however plan to allow retroactive creation of a trial license per customer where full license was already present due to the potential of license misuse. However I do agree that the noisy records of cancelled license should be hidden / removed. That is AFAIK planned as well as some other improvements in the user behavior.

Hi @ShaneDT Indeed, you are right, and I can assure you, that enabling automatic product updates, for both the endpoint clients, and the management environment (both cloud / on premise) is our uppermost priority.

On the screenshot in the original post, the Live Grid Feedback is enabled, and "locked from editing" meaning it is set via policy. What is needed, is to disable that particular setting in the policy assigned to your clients, and then the alert should go away. You can also disable that particular alert via user interface section of the policy, in the list of the application statuses that should be shown on the client computers, and sent to the ESMC server. That would resolve your issue.

Hi @Cameron. Yes, you can easily setup a new ESMC server, deploy couple of endpoints. If you activate those endpoints, they will add to the total of your license, meaning if you for example have 100 licenses, and 95 are used on the "current ESMC", then you have 5 seats to use on the new ESMC instance.

Hello, can you please provide the version of the operating system that agent is installed on? Also, after a brief check with developers, can you please upgrade agent to the latest version 7.2, at least on the affected system, to check whether it would have any effect on this?

If I do understand it correctly, you have left the "agents protected by password" on your client computers, and uninstalled ESMC server + installed a fresh one. I assume that you have not performed the certificates backup from the old server. Please note, that what you should have done, is to just remove the "agent password" via policy (reset it to empty value and then apply the settings to all of your computers). I do not want to be a bad prophet, but I hope either @Marcos or @MartinK would have some suggestions.

Yes, that´s the way to go. If you have one account name.surname@company.com used for both EMA and EBA, just add the EDTD license under the EBA portion of the account, and then when you add this into ESMC, you will see licenses from both EBA and EMA. I have it done that way in my setup, and it works correctly.

Yes, @karsayor it is completely normal. As mentioned, what was previously solved in EMA 1 (ordering) and ELA (transport of the license / management of seats), is now handled just by EMA 2. So if you have only MSP licenses, the only system you need to use is EMA 2. Just add your EMA 2 account into ESMC, and all of your MSP licenses will be automatically synchronized there. EMA 2 also features the views that will show you the seat usage and list all of the activated seats under any chosen license, with the option to deactivate them, for example in case computer was malfunctioning, so you can free up the license quantity for future usage.

What you can also check, is to drill down into the computer details, and in the overview tab, there should be indication whether there is any user currently logged in.

Hi @Alexku - export logs to syslog server from Cloud Administrator is currently not possible. We are planning to add such feature in the future versions of our product. Maybe @igi008 can provide more information.

Hello @karsayor, in general you do not need EBA at all, unless you do have any license that is "non MSP". EMA account and EBA account is in fact the same account on the backend, meaning you have the same e-mail address, and password. Once you have been migrated to MSP Administrator 2, you can use your EMA 2 credentials to synchronize all of your MSP licenses with ESMC. EBA is needed only in case when you have a traditional license, that was obtained outside of EMA. Please note, once ESET Dynamic Threat Defense is available in EMA, EBA won´t be needed as well. In Q4/2020, we will make available ESMCC, which would be a solution that would replace ECA, and also remove the 250 upper seat limit for management of devices. Once a compatible license is ordered via EMA 2, it will directly allow you to setup your ESMCC instance, so you can have a fully cloud based ESET Management Environment for your MSP, consisting of EMA 2 + ESMCC. In case of any further questions, please let me know.

Hello @ZJeyZ, deletion of a the customer from EMA is not possible for the moment. Only thing that you can do, is to "suspend" the company, however that would not allow its deletion from ESMC. We are working on a change, that would allow customer removal from EMA and also from ESMC. Internal reference: P_EMA2-3334