hsmithjtek

Well, they really ought to update that to only show when you select Exclude Hash for the Type. It gives the v7 warning for each type of exclusion. Seems like a bug? Thanks for the info.

I went to create a policy for a new client to exclude some folders from scanning and now the policy requires Endpoints to be on v7? Why? What's going to happen to the current polices that exclude paths from scanning? Will they no longer work without v7? We need to exclude certain paths because ESET breaks business applications.

Hi all, We have a local server doing port scanning for inventory on our network and ERA is complaining about "Detected Port Scanning attack" on some clients for the IP address of that server. I can't find any business articles on how to whitelist an IP address from this alert. Any insight? ESET Remote Administrator (Server), Version 6.5 (6.5.522.0) ESET Remote Administrator (Web Console), Version 6.5 (6.5.388.0) Windows Server 2012 R2 VM Thank you.

Looking to sign up for the BETA. Thank you!

Hello ESET forum Mods and Users, In my ERA console, I currently have a machine that hasn't connected to ERA since Feb 13 2017. When I go to my remote support software, I see that the machine is online and in use. When I do an IPCONFIG on it and compare the IP address with that in ERA, there is a discrepancy which leads me to believe that is why there is no client-server connection? Is there anyway to force some sort of IP address refresh or something in ERA? How can I get the connection from the client to the server reestablished? also why would the connection permanently fail like that in the first place? Thank you!