- #BEST ENDPOINT PROTECTION 2018 FOR MAC HOW TO#
- #BEST ENDPOINT PROTECTION 2018 FOR MAC FULL#
- #BEST ENDPOINT PROTECTION 2018 FOR MAC CODE#
Open "/Applications/ESET Endpoint Antivirus.app" "/Applications/ESET Endpoint Antivirus.app/Contents/MacOS/esets_set" –apply=/path/to/exported/gui.cfg –cfg=/Users/"$loggedInUser"/.esets/gui.cfg LoggedInUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk -F': ' '/]+Name]:/ ' )
#BEST ENDPOINT PROTECTION 2018 FOR MAC FULL#
via a Launch Agent, or with something like Outset, or appending sudo -u username to the commands if running at root level with Jamf, it depends on your environment) and the –cfg flag needs to have the full path to the user’s home directory – ~ didn’t work in my testing.
This has to be run in the current logged in user’s context (i.e. You can apply individual settings to it with esets_set, or just capture that file and re-import it, e.g:Įsets_set –apply=/path/to/exported/gui.cfg –cfg=/Users/username/.esets/gui.cfg If you’ve turned off the web and email modules, you’ll see nags about that too which are suppressed with those user level preferences – definitely something we don’t want!Īnyway, those are stored in the file ~/.esets/gui.cfg and you can modify those with the old esets_set command, much in the same way as you did with scep_set. You’ll notice that the settings file doesn’t account for GUI preferences that are user specific (everything under Preferences –> User –> Interface/Alerts and Notifications). Maybe ESET support can offer some guidance? What’s slightly annoying about this is you can’t change settings in a granular, programatic way – it’s just the whole file’s worth or nothing. Then restart or log out/in to bring the GUI back – or you can add the necessary commands to do that in a script, but this might vary depending on your management tools – I would work out the username of the logged in user then run an open command on the ESET application in their context, myself – a bit beyond the scope of this post. Launchctl load /Library/LaunchDaemons/_ist Launchctl unload /Library/LaunchDaemons/_ist You should kill the GUI and daemon as part of this process then re-load them to avoid user nags, e.g: Then you can use the command line esets_daemon to import them (you need to specify the full path to esets_daemon of course – I’ve omitted it for simplicity here):Įsets_daemon –import-settings /path/to/settings/file Then export your settings as a file via the menu icon –> Setup –> Import/export settings. Set up ESET how you need it in the GUI – scan options, disable the email/web modules etc. This is all still fresh and it’s the weekend but I will write this up fully soon, like I did for SCEP at my blog – here’s the short of it:
#BEST ENDPOINT PROTECTION 2018 FOR MAC HOW TO#
There is a light at the end of the tunnel and it’s not all doom and gloom…Īfter some conversations with other helpful members of the MacAdmins Slack in #endpoint_security we’ve worked out how to get ESET AntiVirus configured in via the command line – both the system level settings and user-specific GUI stuff. I’ll write up a proper post soon once I’ve got my deployment fully tested.
#BEST ENDPOINT PROTECTION 2018 FOR MAC CODE#
I’ve posted this on the ESET forum (awaiting moderation) but here it is (sorry for the unformatted code snippets – WordPress comments…).
0 kommentar(er)
