Camilo Diaz gave kudos to Marcos in Eset management agent is outdated
For the notification to go away it is necessary to reboot the machines after upgrading the agent. Should it still show up, try turning off the computer completely or running the command "shutdown -r -t 0" to make sure that a full reboot is performed.
Camilo Diaz gave kudos to Marcos in May I ask why I got a warning of "URL/Urlik.AAO Object"?
As it was already mentioned, the detection was a false positive and occurred mainly on Chrome urls. It didn't affect files on disks, only download from the web.
Camilo Diaz gave kudos to Peter Randziak in Latest update causes eset_proxy to flip out
I opened a ticket with the dev team to check the logs provided by @Camilo Diaz
In case you have the logs (as described by Marcos), or are willing to record them feel free to provide me with them so I can have them checked...
Camilo Diaz gave kudos to MichalJ in Mac client pointed at Mirror server now unable to connect to ESMC
What you have to do is to configure the proxy for both the agent, and the mac security product.
In case the macs are showing not correct "last connected time" it would mean that they are not able to connect to the server at all, which is the thing you should troubleshoot. To confirm this, please check the status.html of one of the mac agents.
Also, what makes me confused is, that you mix topic of proxy and mirror. When you refer to mirror, do you mean actual offline generated mirror by mirror tool, or you utilize the proxy caching function. In this case, you just need to configure both agent / endpoint to communicate via proxy, and they should get the updates from there automatically.
Please note, that in ESMC 7.1 you can configure proxy details for the agent live installer, and also choose a policy that will be applied to the machine.
@Marcos can you please move this to "ERA" portion of the forum?
Camilo Diaz gave kudos to itman in Patch new wormable vulnerabilities in Remote Desktop Services (CVE-2019-1181/1182)
Camilo Diaz gave kudos to itman in All my files was changed to .KEEP FILES
Make sure your server OS has all security updates applied. Of note is Bluekeep worm patches and these just announced like worm vulnerabilities: https://forum.eset.com/topic/20484-patch-new-wormable-vulnerabilities-in-remote-desktop-services-cve-2019-11811182/
Camilo Diaz gave kudos to MichalJ in Server Task: Delete Not Connecting Computers Failed
My first recommendation (just to allow the deletion) would be to uncheck the option to "automatically deactivate such seats". What you can do, is to deactivate them manually via ESET License Administrator or shorten the removal interval there.
What might also help for us to check is to try manual removal of such computers from ELA. If that works, then it might be caused by network connectivity issues on your / our side. It might help us to actually see the PLID, so we can check whether ESMC server was able to contact our licensing infrastructure, to perform deactivation.
Camilo Diaz gave kudos to tomasS in Server Task: Delete Not Connecting Computers Failed
is there any chance to provide log files from the ESMC Server?
If possible please try to replicate the situation with enabled "trace" verbosity (https://help.eset.com/esmc_admin/70/en-US/admin_server_settings.html?admin_server_settings.html) and please provide us with logs - we are curious about the "trace.log" from the ESMC Server. Logs can be collected by ESET Log Collector (https://support.eset.com/kb3466/?locale=en_US&viewlocale=en_US)