HenrysCat 0 Posted December 18, 2020 Share Posted December 18, 2020 Hi all, we are testing Eset Protect Virtual Appliance in Hyper-V v8.0.2216.0, got it up and running connected to 2012 r2 domain, created the installers with Managment Agent (8.0.1238.0) installed ok on Windows 10 clients, but they never show in Lost and Found on the web dashboard. Can't find any info on first run set up etc, can you help? Thanks Link to comment Share on other sites More sharing options...
Administrators Marcos 4,706 Posted December 18, 2020 Administrators Share Posted December 18, 2020 Please check C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html and trace.log for possible connection issues. Link to comment Share on other sites More sharing options...
HenrysCat 0 Posted December 18, 2020 Author Share Posted December 18, 2020 Where on the Protect server or client machine? As it does not exist on the client machine, and the server is the Hyper V virtual appliance. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 430 Posted December 18, 2020 ESET Staff Share Posted December 18, 2020 Hello, if the agent is not communicating with the server, you can check the reason on the client computer. Non existence of such folder might indicate, that the agent is actually not installed / is not running. Are you able to find it in "installed application", or is it among currently running services? Link to comment Share on other sites More sharing options...
HenrysCat 0 Posted December 18, 2020 Author Share Posted December 18, 2020 (edited) Hi, finally got it work it working, we added '192.168.0.25 eset.mydomain.com' to the hosts file of each client. 192.168.0.25 being the Hyper-V ip and eset.mydomain.com the host name. Probably not the correct way to do things but it works Edited December 18, 2020 by HenrysCat Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted December 18, 2020 ESET Staff Share Posted December 18, 2020 1 minute ago, HenrysCat said: Hi, finally got it work it working, we added '192.168.0.25 eset.mydomain.com' to the hosts file of each client. 192.168.0.25 being the Hyper-V ip and eset.mydomain.com the host name. Probably not the correct way to do things but it works When creating installers, it is possible to override default (and possibly invalid hostname/IP) with value that will enabl clients to connect properly. Just be aware that SERVER's certificate has to be created in a way that such alternate hostname can be used. In case of already deployed clients, it is possible to specific list of hostnames/IP addresses where clients will be connecting via configuration policy for ESET Management Agent. Link to comment Share on other sites More sharing options...
Recommended Posts