brandobot 2 Posted October 25, 2018 Share Posted October 25, 2018 I have ~40 machines in our environment who are in this current status. When I ssh or remote into the machines, I find that only the ERAAgent process is running and not the ESET Endpoint Security app. I've tried to uninstall and re-install the app. Is there a way to remotely restart all of the eset processes on a Mac and Windows machine? Link to comment Share on other sites More sharing options...
Administrators Marcos 4,593 Posted October 25, 2018 Administrators Share Posted October 25, 2018 You can only reboot the machine remotely. That will also restart the ekrn service or esets daemon. Is ESET actually installed? If possible, please gather logs with ELC on a Windows machine and provide me with the generated archive. Link to comment Share on other sites More sharing options...
brandobot 2 Posted October 30, 2018 Author Share Posted October 30, 2018 HI @Marcos These are primarily on Mac machines. ESET is installed, but the processes are not running. Is there a script or a way I can re-start the services? We do not want restart end users machines. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 430 Posted October 31, 2018 ESET Staff Share Posted October 31, 2018 (edited) Hi Brandon, can you please share couple more details about the machines? What is the OS version, and what is the Mac Endpoint version? If I do recall correctly, this once happened to me, when I have upgraded the mac OS to High Sierra, however non-compatible Endpoint application was installed. But that´s just a guess. Also, have you contacted ESET support with it already? If yes, I would like to follow up with them, transfer it to HQ support, so your issue could be analyzed. Edited October 31, 2018 by MichalJ Link to comment Share on other sites More sharing options...
brandobot 2 Posted October 31, 2018 Author Share Posted October 31, 2018 4 hours ago, MichalJ said: Hi Brandon, can you please share couple more details about the machines? What is the OS version, and what is the Mac Endpoint version? If I do recall correctly, this once happened to me, when I have upgraded the mac OS to High Sierra, however non-compatible Endpoint application was installed. But that´s just a guess. Also, have you contacted ESET support with it already? If yes, I would like to follow up with them, transfer it to HQ support, so your issue could be analyzed. About half were on ESET Endpoint Security 6.5 still. I will try to update these again. (I had updated through the ESMC a couple weeks ago but these must have failed. All are running High Sierra (10.13.6) The other half are up to date. Products & Licenses ESET Endpoint Security 6.6.866.1 Up-to-date version ESET Management Agent 7.0.418.0 Up-to-date version I will open a case now. I have a couple cases open and it generally takes a couple days to get a response. I normally get a faster response on the forums. Thanks. Link to comment Share on other sites More sharing options...
brandobot 2 Posted November 2, 2018 Author Share Posted November 2, 2018 This just happened on my own Mac. Was working fine for a few weeks, did a macOS Mojave update, restarted, and now it's saying the ESET kernel extension isn't loading. Maybe something similar is happening to other Macs? Link to comment Share on other sites More sharing options...
brandobot 2 Posted November 2, 2018 Author Share Posted November 2, 2018 Reboot does not help, but I reinstalled the product and now it is working without errors. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 430 Posted November 3, 2018 ESET Staff Share Posted November 3, 2018 What was the version before upgrade? Was it the latest 6.6? I will have it checked by our internal QA, whether they will be able to reproduce the issue. Link to comment Share on other sites More sharing options...
brandobot 2 Posted November 5, 2018 Author Share Posted November 5, 2018 On 11/2/2018 at 10:45 PM, MichalJ said: What was the version before upgrade? Was it the latest 6.6? I will have it checked by our internal QA, whether they will be able to reproduce the issue. Yes, it was the latest version, 6.6*. I was running macOS 10.14 and upgraded to 10.14.1. After reboot, this is when I noticed the error. Link to comment Share on other sites More sharing options...
Recommended Posts