Jump to content

DJD

Members
  • Posts

    5
  • Joined

  • Last visited

About DJD

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Australia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Awesome, thanks very much. I have been on leave for a bit so haven't looked at it in a while, but great to see what others have figured out. Going to go through this right now, as the deadline is rapidly approaching.
  2. Hi Alexander - 1. I was not aware of this ERA/ESMC entitlement. The migration guide doesn't mention anything about it: https://support.eset.com/kb7026/ It also doesn't mention how to configure the address of your ERA/ESMC server. I don't object to setting up a server to manage ESET, but its not what I expected, as SCEP didn't require it, and it means justifying adding another server into our data centre. If I can get away with configuring from the command-line, it would actually be easier for me, as I can do it all myself without a server administrator. 2. We use Cisco AnyConnect. Upon attempting to connect to our VPN, the following message appears: Turning off the web and mail filter, which we've never had before, restores the ability to connect to the VPN. At a minimum, I need to be able to set our domain as an exclusion. 3. If I know which tool is the right one, I can usually figure things out on my own. esets_set doesn't seem to be it, unless I'm missing a step that makes it actually pay attention to the esets_set-supplied configuration. Right now, though, I just don't know where to start and it's not making much sense at present. 4. Yes, downloaded from here: https://support.eset.com/kb3614/ If that's the latest, that's fine; I realise now the "ESET Endpoint Security and ESET Endpoint Antivirus versions 7.0.2091, 6.6.2089 and 6.5.2132.2 have been released" may have been about Windows, not Mac. 5. As I mentioned, historically with Microsoft SCEP, scep_daemon had to be restarted to pick up the changes to the .cfg file. Trying to figure out how the ESET product works and get it to pay attention to the esets.cfg file, I was restarting esets_daemon and observing this behaviour. If the command line management tools interact with it more directly and it picks up change on the fly without a restart of the daemon, this may not be a big deal.
  3. Another thing I've noticed is that if the ESET daemon needs to be restarted, it's pretty much impossible to do so without the user being very visible alerted. Even if the esets_set command worked, historically, based on my experience with Microsoft SCEP, the daemon would need to be restarted. This is typically done by launchctl stop and start, or even a "kill HUP". However, even ESET's own restartDaemon.sh script buried in the app almost immediately triggers an alert that most users would find alarming. Even though they don't need to do anything - the daemon has restarted, but the GUI just hasn't figured it out. Killing the GUI process beforehand results less alarm to the user, but involves a full relaunch, including splash screen.
  4. How do you even do this sort of client configuration, though? I cannot find any documentation about configuring ESET Endpoint Antivirus that actually works. esets_set is ignored by the app, as it's using a different file in a different location (/Library/Application Support/etc/esets.cfg vs /Library/Application Support/ESET/esets/cache/data/settings.json). The configuration that is actively in use (settings.json) doesn't have a command line tool to modify it (without actually learning json).
  5. I'm one of those who have arrived on ESET Endpoint Antivirus (Endpoint Security had too much stuff in it) from Microsoft SCEP: https://support.eset.com/kb7026/ I've previously configured SCEP through the command line, however ESET doesn't appear to behave correctly. Using the "/Applications/ESET\ Endpoint\ Antivirus.app/Contents/MacOS/esets_set" command-line initially reports that the configuration file: /Library/Application Support/ESET/esets/etc/esets.cfg is non-existent. Creating an empty version of it then allows the esets_set command to work, similar to SCEP for Mac, and values are added into it per the command-line. However, the product doesn't seem to actually use any of this. All the configuration changes are being made into: /Library/Application\ Support/ESET/esets/cache/data/settings.json Which is a completely different beast, and a nightmare to read and figure out. The entire esets_set/esets.cfg is just plain ignored. All I want to do is figure out how to configure the web and email protection, as the web filter is messing up our VPN software. However, none of the documentation covers anything but the GUI activities, and mostly this is on Windows. The Mac product does not seem to be very well documented at all, and where it is, it's demonstrably wrong. How do I actually configure the product from the command-line? Additionally, I note that there are new versions of the client software, as of November 13. Again, none of the information provided helps. We have just started out with ESET, using 6.7.500.0, provided from the download links provided. We have neither ESET Security Management Center nor ESET Remote Administrator. So, how do we get access to the product updates?
×
×
  • Create New...