So eset has a script to install the agent which worked great. Now im getting a script error 1. I have no idea whats going on here. Im not getting alot of detail. Anyone else see this?
Sending Wake On LAN command... Opening SSH Connection to 10.10.160.21... Authenticating... Successfully authenticated. Verifying Computer's Identity... The MAC Address has been verified. Checking Operating System Version... Running Mac OS X 10.14 (18A391) Verifying /usr/local/jamf/bin/jamf... /usr/local/jamf/bin/jamf is current (10.7.1-t1536934276) Verifying /usr/sbin/jamf... /usr/sbin/jamf does not exist. Verifying /Library/Preferences/com.jamfsoftware.jamf.plist... Preparing Policy... Executing Policy 2018-10-16 at 3:16 PM | jalcorn | 1 Computer Running script Eset Agent Installer... Script exit code: 1 Script result: Error running script: return code was 1. Submitting log to https://jamf.chathamfinancial.com:8443/ Finished.
Solved! Go to Solution.
Does anyone know the location of where the ESET config file is saved?
We would like to push out the config file, and while we can export and import it, I cannot find where it is saved when imported (does not look to be the same location as for SCEP).
Found it: Library/Application Support/ESET/esets/modules/data/backup/ (or is this just the backup of the config file) distributing to this location does not seem to work? Any suggestions gratefully received.
Trying to run the esets_set command throws this error when I test:
"Cannot open file /Library/Application Support/ESET/esets/etc/esets.cfg: No such file or directory"
So I assume thats where it may save them. I've also been toying with moving around the settings.json from /Library/Application Support/ESET/esets/cache/data/ but I've not made much headway.
Also I'm unsure if there is any script available to those of us moving over from SCEP for Mac, and when I contacted their support about it I was told there was no way to customize the installer at the time of installation, even though the pkg file allows for GUI customization choices.
@jalcorn I opened a ticket with ESET support, this is their response ...
Thank you for contacting ESET North America Technical Support.
At this point there is no official script that is offered to assist wit the deployment. With JAMF you should be able to preload the kernel extensions and push out the package installer.
@jalcorn Thanks, that helps confirm what I thought. Microsoft and ESET are offering users a free year of the client as Microsoft is EOLing SCEP for Mac at the end of the year, however it appears to be only the client and there are no real configuration or deployment options available to the installer.
@a.simmons : To configure it you should run the 'business' installer, select the remote option and configure it as needed. This will produce setting files (/tmp/esets_setup.dat and /tmp/program_components.dat) you ship with the installer (or create by a pre-pre-install script). I did so, but still get the same pop-up about 'New network connection' :( So I am not sure whether my config was not taken, or whether this is a feature that can not be configured.
I find it very hard to find mac related info on the ESET website, and in particular anything related to remote install without using their Remote Admin Console.
@mschroder I've had a rather long email thread with their support and the culmination is that customization of this product without the ERA is not possible. Logic would dictate that since options can be changed manually when running the GUI installation then there must be a command line method of doing so, but I've not been able to come up with anything yet.
Looks like I need to retract some of my previous statements. I contacted them once more about ERA and ESMC and just got a message back from support that "... you already have business license, those products are already available to you." So it appears to be something available once you claim your license(s).
All I did was put both the .pkg and the downloaded tool in the same directory and did the below, so I would say no I have not set the execute bit?
In the terminal run the command: ./add_token ees_osx_en_0.pkg "1111-1111-1111-1111-1111" Run the command in the directory where you saved the installation file and add_token file. Replace 1111-1111-1111-1111-1111 with your ESET license Key. Replace ees_osx_en_0.pkg with your installation file name.
My mistake, sorted now, thanks
Ahh ESET... yep you can capture settings for it then apply/import them as part of deployment and you don't need their ERA solution to do it - I really didn't want to go through having to configure another on-prem service.
Basically, the "system level" stuff is stored in /Library/Application Support/ESET/esets/cache/data/settings.json and the "user level" bits (like suppressing the GUI prompts/notifications) are in ~/.esets/gui.cfg
The system level stuff is different from how it used to be managed in good old SCEP - it can be exported/imported using the GUI or esets_daemon.
The user level settings can be modified granularly using the esets_set utility in the app bundle itself, or you can just replace the entire file with one containing your preferred settings in the logged in user's context and force a reload of the esets_gui process for them.
I've documented all of the above in more detail on my blog post.
The add_token tool is working for me but you have to set it executable before you run it - i.e:
chmod +x /path/to/add_token
I'll add that little nugget to my post at https://soundmacguy.wordpress.com/2018/12/04/hello-eset-endpoint-antivirus-deployment-management-and...
It's also worth registering for an EBA account to keep track of your license usage.
When exporting the configuration file right from ESET what file extension should that use?
@neil.martin83 I am looking to use your Extension Attributes for ESET (the ones for SCEP were very useful thanks).
I am not getting any result, I have changed ESET Endpoint Antivirus.app to ESET Endpoint Security.app as that is what we are using, but no joy.
Am I missing something obvious?