jurajm

Great. Thank you. That worked. For some reason I ignored looking into Eset security management center task category. Thats why I could not find it.

Could you walk me through the "component upgrade" task? All I see from the options available to run is "component update." Thank you.

I am quite interested in the solution to this problem as I am currently facing the same issue. Simply "update module" does not do anything, it doesn't even go to the tasks thus not creating the log on the local workstation. I can upgrade the module manually on workstations, but it would be handy not to do this on 50+ of them. Thank you for looking into it?

Update: I restarted the Eset management service on the server and it seems to be communicating again. Just weird while other agents would work fine, new connections wouldn`t.

Hi Marcos. I have done that too. I uninstalled the remote agent from the local computer, generated a new Agent live installer. I did check the batch and the hostname was correct. I have attempted the process on a new computer with a different hostname and the result is the same. trace.log

I have ESMC installed on the server and it has been working just fine, currently managing 50+ workstations. I have encountered an issue when a local computer hdd failed and needed to reinstall the machine completely. On the newly installed operating system, I installed the remote management agent but it would not connect. The computer had the same hostname and IP address. I followed a few threads on how to troubleshoot the communication between the agent and the server. I am attaching the status log from the computer having the issue communicating. A few things were blurred out and to confirm the host is the server hostname with the domain name. The local machine is able to ping the server and DNS is able to resolve the hostname. I have already tried to replace the file networkgrpc.dll on the local machine. Any pointers to fixing this issue is much appreciated. Juraj.