Search the Community
Showing results for tags 'osx'.
Found 3 results
I've noticed lately that a lot of the time when I run commands against Mac OS X endpoints, the shell returns "OK" rather than the expected result of the command. For example: ls /Applications OK This happens when running commands interactively as well as when the commands are executed by a script - I enable script engine logging (and even explicitly log %shellresult% to the console) and the same thing happens: a long list of comments on what the command is doing, with "OK"s between them. Does anyone know why this is happening and/or how to fix it? Some Mac endpoints respond fine to shell commands, but then stop. Others have a chain of "OK" entries in recent history but then respond fine to interactive commands when I test them. Makes no sense to me.
Does anyone have a working AV Definition configuration for ESET Endpoint Antivirus on a Mac? I have tried a few combinations today, but can't get it working. I found a post from 2013, which mentioned LT Support had informed it was not possible to monitor AV on OSX, but it was a long time ago now, so hoping that has been resolved! Below is what I have tried. Thanks Kev
Hey All, We are running into an issue with machines running the latest version of OSX (10.13) Apple has enabled a feature blocking apps that touch the kernel (Eset in our case), and make you click a couple buttons to allow it. May not seem like a big deal on the face, but tracking down users and clicking a couple buttons on over 100 machines is going to become a lot of work fairly quickly Her is the Eset and Apple KBs: https://developer.apple.com/library/content/technotes/tn2459/_index.html#//apple_ref/doc/uid/DTS40017658 https://support.eset.com/kb6512/ Eset just told me they don't have a workaround. I wanted to know if you guys have any ideas on getting around this in an automated fashion. Thanks, Stephen