Jump to content


  • Posts

  • Joined

  • Last visited

About brandobot

  • Rank

Profile Information

  • Location

Recent Profile Visitors

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

  1. We noticed the same thing in our environment. The issue seemed to be fixed within half an hour.
  2. Per US Support, they recommended we install ESET back onto these machines. Within 3 hours, 2 machines already restarted/crashed upon wake from sleep. Without it installed, we went about 4 days without any crashing. I'm running the log collector script now and will PM it to you.
  3. 1) Yes, only wake from sleep. 2) Only sometimes. We sent a survey to 150 of our users on 2018 Macbook Pros and they experience crashing 1-2 times per week on average. 3) Yes, only 2018 and newer. (t2 macs) 4) Entire system reboots. Upon waking up from sleep, we'll see an Apple logo, then get kicked back out to the login screen. Upon login, you'll find that all apps are closed and the system had rebooted. This is indicative of t2 performing a reboot when it thinks it detects an intruder. I have removed Endpoint Security 6.7.654.0 from 4 of our test machines over the last 3 days and have not experienced a crash. I will keep running without endpoint security for a few more days to be sure this is the case. On one of my test machines, I wrote down the date/times of two crashes. Is there any specific log files I should be looking at and gathering? Edit:: I used the ESET log collector and have sent you logs from 2 of the affected machine and the date/time it experienced the unexpected reboot. I've also created a case with ESET support
  4. On our t2 chipset macOS laptops (2018 and newer), we are seeing crashing on wake from sleep. On average, crashing happens 1-2 times per week for all of our users. we are running 6.7.654.0. Is anyone else experiencing this?
  5. The fix for me was to uninstall and re-install the new version. I am still uncertain why installing over an existing install worked for about 90% of our machines, but required uninstalling for the other 10%.
  6. I'm trying to deploy 6.7.6 on top of 6.6 ESET Endpoint Security. On about 15% of our machines, they are failing. Is there any pre-requisites that need to be met to install properly? Any logs I can check that will tell me where it is exactly failing. Downloading ESET Endpoint Security 6.7.600.0.pkg... Downloading https://use1-jcds.XXXXXXXXXXXXXXX... Verifying package integrity... Installing ESET Endpoint Security 6.7.600.0.pkg... Installation failed. The installer reported: installer: Package name is ESET Endpoint Security installer: Installing at base path / installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
  7. Thanks for your help @TomasP Looking forward to the future release as the current 6.7 is not deployable with the current issue.
  8. These errors are from SCCM. Is there somewhere on the local client that has the install logs so I can track down what may have happened?
  9. Just installed this new version. No pop-up once installed. I used my existing TCC exclusion profile. I will continue monitoring to make sure no other unexpected behavior pops up.
  10. We are working on deploying ESET Endpoint Security/Agent upgrades for all our Windows endpoints. On a small handful of machines, I am seeing Error: The extended attributes are inconsistent and "the application was not detected after installation completed. Where is the log file for Windows endpoints so I can figure out what may be causing this error?
  11. I had this issue on both 6.6 and 6.7 on Mojave. On multiple times on test machines, as soon as ESET installed, the whole Mac just froze and required a forced reboot. After reboot, it appeared fine. We're holding off on 6.7 until they fix the TCC profile issue. Unfortunately, we've been so busy and I don't have time to keep going back and forth collecting logs and trying betas...we've been doing this for over a year with the remote administrator...
  12. Agreed, I do not think this is a TCC profile issue. I have 8 other TCC profiles in production for various apps and have not had an issue until ESET.
  13. Same issue with the beta version. I've created a new config profile based on the beta to allow both all app data and system files. I tested by uninstalling ESET, applying the configuration profile, restarting the Mac, then re-installing the Beta version.
  14. I just tested suppressing the GUI upon install by creating an empty file into the "cache" folder and it apperas to work. The esets_gui process does not launch, there is no splash screen, and no icon in the menu bar. I am able to verify that the proxy, mac, fcor, daemon, pidmapper and ctl processes are running in activity monitor. Does this mean the machine is still being fully protected? Not a huge issue, but Is there a way to suppress the splash screen upon install, but retain the ESET icon in the menu bar? Another thing I noticed is that the "do_not_launch_esets_gui_after_installation" file is removed after the install. So after every upgrade, we'll have to re-create the file.
  • Create New...