Jump to content


  • Posts

  • Joined

  • Last visited

About BillTheNerd

  • Rank

Profile Information

  • Location
    New Zealand
  1. Something new I have come across today, wondering if anyone else has experienced this and what they did about it: I created a policy in my ERA server (v6.3), to apply to ESET Endpoint Security (v6.3) clients, to create an "Allow" personal firewall rule for an application that needs inbound and outbound access. The policy setting was Applied, but not Forced. As soon as the agents updated to include this policy, users could no longer Add, Edit or Delete their own firewall rules. They could only view them. This means that they cannot create their own rules, plus the Interactive mode in the firewall no longer functions since they cannot add new rules based off events triggered. It seems like this behaviour is a mistake. If the policy setting is only applied, shouldn't users be able to edit their rules themselves? And even if it was forced, shouldn't they still be able to add/edit/delete their own rules?
  2. Sure - The ESET Endpoint Security never asks the client after the installation whether the current network is public or private. It just sets it to public, which disables network sharing among other things. Each of my agents is running in a remote network, their own home, which means they can't be identified by a standard IP range and other details using the known networks policies. Their network could be any combination of IPs, subnets, gateways, DNS and so on. So what I really need is a non-GUI method to set the currently connected network type to Private, post-installation.
  3. Hi all, I am doing a large number of unattended ESET Endpoint Security installations via an ERA server, and I noticed that after installation the clients existing network seems to be marked as a Public Network type in the personal firewalls Known Networks, by default. I am trying to run a fully silent unattended installation and I would like the network the client is connected to during installation to be marked as a Home or Office network zone by default instead. I couldn't seem to find any command line parameters for the installer to do it. I also couldn't find a post-installation command line option to change the current network location to Home or Office. I don't want to pop a GUI to the client to ask, if I can possibly avoid it. As the clients are spread all over the place, their network connection details are unique to each and cannot be assigned using ERA policies to alter the known network settings. Do you know of any way to achieve this?
  4. Thanks Marcos - I ended up doing exactly that in the ERA server, using OPSWAT to do the removal. I luckily found this KB article after I posted :- ) hxxp://support.eset.com/kb3638/
  5. I'd like to automate the deployment of ESET AV Remover in my business network to cleanup installations of 3rd Party AV products before pushing out ESET Endpoint products to all my users. I've been searching for a way to do this without user intervention, but just can't seem to find one. Ideally I would be able to run ESET AV Remover in the background and have it remove all AV protection from the workstations, and write a log to the file location of my choice. Is this possible using a command line or similar tools built in to the product? Or would I have to go to some automated 3rd party solution? Thanks!
  • Create New...