j-gray 37 Posted February 9, 2023 Share Posted February 9, 2023 I have about 175 OS X clients (mix of v6 and v7) with the latest agent (10.0.3091.0) that do not show EI Connector installed in EP 10 Console when displaying the list of installed applications. This also throws them into a dynamic group for clients w/o EI Connector installed. EEI Console shows the EI Connector installed and functional. Subsequent EI Connector activation tasks run and complete without error. And, in fact the 'EI Connector' icon appears next to the hostname along with the Agent and Desktop icons that indicate the product is installed. For some reason it does not appear in the list of applications and lands in the dynamic group as if no EI connector is installed. What is causing these clients to appear to not have the EI Connector installed when it is, in fact installed? Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,171 Posted February 16, 2023 ESET Moderators Share Posted February 16, 2023 Hello @j-gray this behavior is by design as the EI connector is not installed as an application, but is perceived as an additional service / endpoint extension. Peter (P_EP-27801) Link to comment Share on other sites More sharing options...
j-gray 37 Posted February 16, 2023 Author Share Posted February 16, 2023 @Peter Randziak EI Connector does appear as an installed application on all platforms we use (Win10, OS X, and Windows Servers). It also appears in Add/Remove Programs on all Windows clients. Here is an example from an OS X client (one of the ones that actually reflects correctly); Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,171 Posted February 21, 2023 ESET Moderators Share Posted February 21, 2023 Hello @j-gray, I appologize for the confusion, as the info provided was not complete. The EI is not listed among installed applications locally, but it should be displayed in the ESET PROTECT console. We seen cases, when it was not reported into the management console, those were resolved by clearing the system cache on the macOS. Hope it will resolve the issue for you too. Peter Link to comment Share on other sites More sharing options...
j-gray 37 Posted February 21, 2023 Author Share Posted February 21, 2023 It's odd, because the the icons (eg Desktop, Agent, Connector) are displayed correctly next to the computer name indicating the component is installed, but it doesn't show in the application list and of course (negatively) affects dynamic groups that group computers without the component installed. I was hoping that upgrading the connector to the latest version would update it in the console, but no luck there, either. Is this another known issue that might be addressed in future releases? Otherwise, I'll have to see if I can find a way to reliably automate clearing the cache via the EP console. 170+ clients is too many to address manually. Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,171 Posted February 23, 2023 ESET Moderators Share Posted February 23, 2023 Hello @j-gray, my understanding is that the issue is caused by incorrect data provided by the OS. We have seen a case, where this system cache somehow fixes itself after a time. Peter Link to comment Share on other sites More sharing options...
j-gray 37 Posted March 7, 2023 Author Share Posted March 7, 2023 @Peter Randziak It's been a few days short of a month since initially observed and we still have the same ~160 OS X clients not registering EI Connector being installed. This is even after upgrading the EI Connector to the latest version. I've tried uninstalling/reinstalling the EI Connector and it does not resolve the issue. Any more info on this? Possible bug? Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,171 Posted March 10, 2023 ESET Moderators Share Posted March 10, 2023 Hello @j-gray, sadly I do not have any specific info regarding it, for sure that is something worth checking. I recommend to start with getting a ESET PROTECT agent log with a debug verbosity to see what is being reported to the EI server... Peter Link to comment Share on other sites More sharing options...
Recommended Posts