parisan

Reading this forum I have stumbled on the answer: So basically it does not work. And: So the delay can be 1 or 2 months. 2 months while ominous warnings are reported in the dashboard. Why a warning if it's normal that product is not updated ? How can product managers not realize that supervision products that are drowning users in warning are not much better than no supervision ? Closing this.

Bump 2 - is there a way to get an actual answer on this forum ? I have just updated the console to 9.1, and now when I hover over the component state version, there is a blue line stating that the number of computer waiting to be updated is 0. Tired of waiting, I have launched manual update. Failing still to see the point of so called 'automatic updates'.

Bump. it has been 5 weeks and there are still not a single computer updated. Automatic updates don't seem to work at all.

Hello It's stated in the online help that automatic updates are delayed for stability reasons. What is the typical delay ? It's annoying that the product displays warning in the mean time.

Hello Virtual appliance Linux 9.0.2144 This morning I was experimenting with the WEB UI (I just upgraded it a few days ago) and suddenly I lost connexion. I got back a few minutes later and logging through SSH I found out that the appliance had rebooted. As I had not asked for an update of anything this morning, I can't explain why the appliance restarted. I have searched the logs (/var/log/messages, era server trace) and I have not found any explanation, just that the era server was stopping, and that systemd got a SIGINT signal. Is there a place where reboots are configured or logged more precisely ? I searched also cron jobs, systemd timers and found nothing. I even browsed a few tables in the Mysql database without lucking on something interesting. I'd quite like for restarts to not happen during business hours. Thanks.

Thanks @Marcos I tried it and it worked. To expand if other people have the same question: I added the license to ESMC, launched a task to install the Agent on an h Eset 5 workstation, it worked (after a few troubles involving invalid customer DNS), then when the workstation was managed by ESMC, I created a new task to install last Eset version on the station, Eset 5 was uninstalled automatically, after a few minutes the computer restarted and Eset 7.2 was functional. In the ela.eset.com page the new license appeared too. So far, so good. Worthy of note is that the new installed Eset version launches immediately a full scan, a lengthy operation. About the monitoring, I'm investigating the API, but it's a real pain to have to do programming to interface with a monitoring system! It should be possible out of the box...

Hello The Era 5 system is installed on a Win 2012 server that will be decommissioned in a few months, to evaluate the problems with passage to ESMC 7 (never used it till now) I have installed an appliance running under a Win10 workstation using Hyper-V. The Win10 workstation had a Endpoint 7 installed using the customer license. This Endpoint was installed well before the ESMC appliance, and was not (of course) managed by the Era5 system. I installed the Agent for this workstation and updated the Endpoint through the ESMC. So far so good. Now the remaining part is to bring the remaining 2 dozen or so of Endpoint 5 managed by the Era5 to the ESMC. Obviously I need to get the customer license in the ESMC, but I'm worried on the effect on the Endpoint 5 systems. If I go to ela.eset.com for the customer license, I only see the one Win10 computer, I don't see the Endpoint 5 usage. Can I just install the customer license on the ESMC and install the agents on the rest of customer's computer ? Or is there a step that I should do before ? I don't see how this could harm Eset since no more computers would be using the customer license but you never know how license restrictions work so I ask. Another smaller problem: currently Era5 is managed in customer monitoring system (ie, something similar to Nagios) by using an exe called eracmd.exe that is used to export the current system state in a file that the monitoring system reads and uses to update the general organization state. I was happy to update to ESMC 7 as I was believing that I could eliminate this annoying hack, but despite having searched a full day I don't find *anything* to monitor ESMC: no SNMP (I have found how to enable snmpd but it's useless since it does not report anything specific to Eset, just the general virtual machine state), no REST, no REDFISH. There are SNMP traps but it's said that this does not work with the appliance. So zero, nada, and not even eracmd. How in the world can an ESMC appliance be integrated in a monitoring system ? Thanks for your insights.