Jump to content

MichalJ

ESET Staff
  • Content Count

    2,027
  • Joined

  • Days Won

    59

MichalJ last won the day on December 23 2019

MichalJ had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Slovakia
  • Interests
    customer problems, but besides that cycling, architecture, and everything that rides, flies or floats (transportation industry)

Recent Profile Visitors

7,674 profile views
  1. 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.
  2. Cloud MDM for management of Android devices is planned for December 2020
  3. Hello @Zen11t Can you please elaborate more about the need for seeing the agent version in the computers table?
  4. Hello, this issue is known, and we plan to fix it in the upcoming service release (currently planned by end of July).
  5. 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.
  6. Hello, the correct path for Windows machines should be: C:\ProgramData\ESET\RemoteAdministrator\Agent
  7. 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.
  8. 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".
  9. 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?
  10. 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.
  11. @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.
  12. 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.
  13. @isaha do I get it correctly, that you use a locally created "update mirror" server for updating, instead of clients connecting directly to ESET?
  14. @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.
  15. 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.
×
×
  • Create New...