Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


apatheia last won the day on March 12 2015

apatheia had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

765 profile views
  1. Yeah, it's nice, but it's also a shame they don't seem to have documented this anywhere.
  2. So, I may have solved my problem in the short term. I haven't found the exact setting my original question referred to, but this may be a start... Digging around, I found a binary called esets_set, which is of particular interest if you are managing Endpoint products with ERA 6. ERA 6 doesn't have complete policy management yet, so this binary might useful for managing some settings that policy doesn't quite yet. In the terminal, ​/Applications/*ESET\ APPLICATION\ HERE*/Contents/MacOS/esets_set --help OR /Applications/.esets/Contents/MacOS/esets_set --help yields: Usage: eset
  3. Found 'em. The are a handful of binaries inside the the ESET application. Go to /Applications/*ESET\ APPLICATION\ HERE*/Contents/MacOS/ Inside you'll find Inspector esets_daemon esets_gui esets_mac esets_sci esets_ctl esets_esi esets_kac esets_scan esets_set The esets_scan binary is the one you are looking for. Type the following to see all of the parameters you can use with this binary (fix the path to include your application - don't forget to escape spaces with a leading \ . /Applications/*ESET\ APPLICATION\ HERE*/Contents/MacOS/esets_scan --help
  4. Don't know your specific problem, but the attached are my notes for a working installation process for getting ERA 6 to function on CentOS 7 64-bit Minimal. I know it works because I just ran through it in my lab environment this morning. The domain join and LDAP lookup has not been documented completely yet, so maybe skip that part for now unless you know what you are doing. It doesn't include post installation steps, but this should get you started. YMMV. centos 7.x - era 6 scrubbed.pdf
  5. *Bump*. Reviving this thread. I'd be interested in some command line parameters too for the Mac and Linux. Especially for settings that policies that ERA 6 doesn't cover.
  6. Yeah, the sooner you all can flesh out the OS X and Linux policy support, the better. I've found it severely lacking. As for disabling it in the setup, I can't tell my users to "Go into the settings, click tab A and flip switch B to get result C". Ain't gonna happen. I don't mean to sound like an elitist IT guy, but some people just aren't capable of dealing with a settings window with out calling the help desk... Have to ask: you have a time frame for this (and any other new policy controls)? Any time you have a setting that defaults to notifying the user client-side, you must have
  7. Ok, so is anyone else bothered by the fact that their users are being notified that the operating system is not up to date? Where I work, IT manages all system updates and deploys them through separate managed software update deployment system (we use Munki since we're an all OS X operation). It's confusing and annoying for our users, since they can't do anything about it anyway. Also, the notification includes a link to the App Store application, which in our case, is useless. Again, we use Munki and it's accompanying Managed Software Update application to managed all software patches, up
  8. So, Marcos, I have a question for you: I'd also like a custom installer. Manually running the latest installer for Eset Endpoint Antivirus for OS X, I noticed the option to create a customized "Remote Install". This allows me to remove certain components (like Email protection - we only use web mail clients) from the resulting installation. It's just less to manage. Less is good I would love to see this type of custom install through ERA6 with installation parameters, which I believe are currently useful for Windows .msi installs only. Correct? So, I'm wondering this: is it ok to
  9. Here is an updated version of the walkthrough. Again, some areas are incomplete, but this one will at least install and configure a database that works. No guarantees that the steps below will work in your environment. With that said, you might find some of it useful for troubleshooting your own specific issues. See attached file in written in Markdown format. YMMV CEntOS 7.x - ERA 6 SCRUBBED.txt
  10. I have ESET Remote Administrator Server and Agent installed and running on CentOS Linux release 7.0.1406 (Core) Minimal. All prerequisites are installed. The Remote Administrator Agent is also installed on the clients and can successfully contact the server. In the web console, the status of the clients is inconsistent. Some show the Remote Agent icon badge, others do not. Some show the badge for a time until, for example, the computer is moved to a static group, at which point the Remote Agent badge disappears, along with the associated computer information. For example, OS Type = Mac OS
  11. Is there a time delay between adding an agent reporting system information to ERA server and a system appearing in a given Dynamic group? If so, what is the time period and can it be shortened to expedite the testing period? I have an agent installed and functioning on the ERA server. OS information is reported correctly, but the system does not appear in the Linux dynamic group. Please advise. I can provide logs if needed.
  12. Never mind. All I needed to do was apply "Policies" -> "Connect every 20 minutes" to the affected systems. Before doing so, I changed the server list in this policy. I removed and added the ERA server FQDN, ie. era.example.lan. Problem solved.
  13. I am experiencing a similar error with one major exception: Error: CReplicationManager: Replication (network) connection to 'host: "" port: 2222' failed Why are the client systems attempting to contact localhost at a server port?
  14. In addition to the official documentation for installing ERA 6 on Linux (which you should read first), I expanded the official documentation with some of my own notes for building up a Linux-based installation of ERA 6. It's not complete, but it will get you further along than the official documentation does. Hopefully, this will be of use to someone else. No guarantees that the steps below will work in your environment. With that said, you might find some of it useful for troubleshooting your own specific issues. Process is attached as a clear text file formatted in Markdown. CEntOS_
  • Create New...