winstonsmith84 2 Posted November 1, 2018 Share Posted November 1, 2018 I have one PC in our environment that always shows as unmanaged in the remote admin console but Eset is installed on this PC. When you log into that machine and check Eset it says everything is OK. It appears to be working just fine but the ERA just shows the status wrong. How do I make this machine show up correctly in ERA as a managed PC? This PC has no info listed in ERA either. Everything for it just says N/A. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted November 1, 2018 ESET Staff Share Posted November 1, 2018 By any chance, isn’t there a machine in lost&found with the same name? Or wasn’t it cloned from another computer (in case of a VM)? Link to comment Share on other sites More sharing options...
winstonsmith84 2 Posted November 2, 2018 Author Share Posted November 2, 2018 Nothing in Lost and Found with the same name and it's not cloned. It's a physical desktop that used to show up as managed. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted November 2, 2018 Administrators Share Posted November 2, 2018 Is the agent service running? Does C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html show any issues? Are there any recent errors logged in the trace log? Link to comment Share on other sites More sharing options...
winstonsmith84 2 Posted December 3, 2018 Author Share Posted December 3, 2018 Service is running. Status is all green. No issues. Trace Log doesn't appear to have any errors but there is this entry occasionally: Warning: Kernel [Thread 648]: Module library +EVSAConnector was not loaded Warning: Kernel [Thread 648]: Module library +ESLCConnector was not loaded Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted December 4, 2018 ESET Staff Share Posted December 4, 2018 I would recommend to search for device using some HW specific parameter, for example by IP address. Name as seen in ERA console might be completely different as expected, especially in case reverse-DNS entries are not properly configured, or in case automatic renaming ask is not used in this instance. Also in case device has changed hostname in the meantime, it might be shown in console with old name. Is this client connecting directly to ERA Server or there is ERA Proxy in-between them? For device searching, hint might be to force this client to report some kind of functionality problem - for example disable some endpoint feature (antivirus?) and observe problematic devices as seen in console. Problem should be reported almost instantly in case AGENT is connecting to ERA. Link to comment Share on other sites More sharing options...
Recommended Posts