Jump to content


ESET Staff
  • Content Count

  • Joined

  • Days Won


MichalJ last won the day on September 19

MichalJ had the most liked content!

Profile Information

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

Recent Profile Visitors

5,330 profile views
  1. Thank you for the feedback. I will check on our side, whether there is anything to be done to change it. I agree, that impossibility to turn it off when anything is wrong is an inconvenience. I will try to give you update here next week.
  2. From which version of ESET Remote Administrator you have upgraded to V7? Obviously, the installation is corrupted, as old registry entries were not removed from the system. I can see duplicated entries for both ESET Remote Administrator Server, and Mobile Device Connector. This is the issue that manifested after the release of V7.
  3. You are right, as of now, there is no way for you to suppress the yellow warning in ESMC. Couple of questions though, to properly understand your setup: Do you use EMA 1 (ema.eset.com) or EMA 2 (msp.eset.com). In case of EMA 1, you will have the licenses added via security admin account of ESET License Administrator. In case of EMA 2, you add them by entering directly the EMA 2 account. Do your customers have their own ESMC instance, which they do access and you just order licenses via EMA, or you are an MSP, that just let the users to access their system? We are tracking improvement request, I am inquiring whether this change would be feasible in the near future.
  4. Yes, you can duplicate the entry, and change the name of it. Also, in "distribution" section of the notification parameters you can change the output locale (so the actual text is in the language of your choice).
  5. @smash007 In general, there might be one thing you can do. If the IP address of the ESMC server changed, if you revert it back to its original value, agents will be bale to connect. However, it depends, whether the certificate / address was configured for the IP, or the hostname. If you revert both to original values, no redeployment might be needed.
  6. License status is inherited from the licensing server. You can’t disable “closed to overusage” warning on EBA as of now, but this is in the backlog. Also, ERA is a direct predecessor to ESMC and in most cases solutions recommended for ERA 6.x are still applicable for ESMC.
  7. Notifications are “preinstalled objects”, which are set in the language of the server installation chosen during install. Only option is to recreate them, in the language of the currently logged in user. The same is valid for report templates / pre-defined (built-in) policies.
  8. When you remove the "offline computers", is the checkbox "deactivate license" checked? As licensing is evaluated on the cloud licensing servers, you need to make sure, that checkbox for license removal is set. Also, you will have to click "synchronize licenses" in the license screen, to update the listing, as by default it refreshes every 24 hours.
  9. Computer description is not collected by ESMC agent. It´s "server only" field, and the only way how to populate it, is either manually, or via synchronization with active directory, by the use of "custom attributes".
  10. @maneet kaur You can correct such issue by creating a dynamic group set for "product not activated" and setting up an automatic reactivation task. That will auto-correct such behavior, if it would ever happen again. But if you contact support and provide them with your PLID, we can ispect the logs on our side, and check what was the source of the deactivation. There are basically two "normal" ways how this could happen, besides some unexpected error in the app (but the fact it happens everywhere at once somehow reduces this probability): - device has not connected to ESMC for some time, and ESMC sends "deactivation request" to our licensing server (this is part of a "delete not connecting computers" server task). We had customers that created a clone of their server for testing / validation purposes, did not isolate it from the network, and it triggered such task. - manually from ESET License Administrator / ESET Business Account, where you can select list of devices, and click "deactivate". That would "kill the license seat" and deliver such information to the Endpoints.
  11. With regards to the number 7, this functionality will be available in the next release. You will have an option to download the generated report output directly from the dashboard. What is also possible in current version is, that when you drill down, apply filters, you can click "generate and download", to get the data exported in CSV format.
  12. Exactly the other way around. Security product is "Endpoint Antivirus" and Agent is the ESET Remote Administrator. You can uninstall the product via the console (software uninstallation task) and then you can execute "stop managing, uninstall ERA agent ask". It´s exactly as you have stated, you were using really dated version, which has been improved greatly on both management interface side, and on the Endpoint side. If I may ask, to which vendor you are moving to? If you do not require to disclose this information publicly, it might be interesting for us to understand why you have decided to do the switch, and what were the decision criteria. Thank you, Michal
  13. For number 1, maybe @MartinK might be able to shed some light. I can confirm that the "is one of" and "is not one of" is working for me OK. Point in 6 is related to the fact, that the underlying data is not correlated with computer information. However I do agree, it would be a good idea to have it somehow interconnected, so I will report an improvement request for that. However, you can apply a filter on "dynamic group" so if you have a DG set on particular criteria, you can also filter the report (for example windows XP DG).
  14. Add & Remove should suffice. In case of any issues, you can use ESET Uninstaller, however this one needs to be run in safe mode. In general, I would recommend to uninstall the security product first, and agent the second. If I may ask, what is the reason for the removal? You are running quite dated versions of the products, 6.2 is almost 4 years old.
  15. Hello, I will try to give you some advice: Your fist case, should be done in a way that you use "nested dynamic groups". First one will do "Machine is not Windows XP" where I would recommend solution when you first filter out Windows XP machines: Then you will filter out the ones that do not have the right version: You can run a task on a list of computers differently: Select them in the computers table, choose each entry, and then click in the footer button "actions" and run task From the task wizard, when you specify a trigger, you can inside specify either "add groups" or "add computers". When you click "add computers" you can choose whatever computer you like. When you are in the "client tasks" section, and you expand the entry of the task, grey lines are for triggers. If you click on the "trigger entry" it shows you "delete". Afterwards the console asks you whether you want to delete a trigger. In client tasks section. It will install over, perform the upgrade of the computer. However, if you have already Agent installed, the most convenient way is to use software install task.
  • Create New...