You can also access the EEI UI directly, if you are interested in just the EDR functionality.You may hear security professionals talk about threat hunting. From there, you can easily navigate to details of each detection. Once you have your environment setup, EEI detections will appear also in ESET PROTECT.

Also, you will have to activate EEI Agent (If you have the latest version of ESET PROTECT, there is a context menu option called 'deploy EEI Agent', that will do the trick for you). You will have to specify the EEI server connection details into the policy for EEI agent, that you can assign to group all (they will connect). Even though it is named 'agent' it is a very small binary, that just sends the detection metadata gathered by our Endpoints (Endpoint is the 'AGENT' per se) to the EEI Server, where the detection logic resides. Once your EEI Server is installed and running, you can proceed with installation of a component called ' EEI Agent'. EEI server needs to be installed manually, you can´t do it from EP Server (not the first time). On this machine, also install ESET PROTECT Agent (you will need it, for future updates). You will have to connect it to your ESET PROTECT, as it uses single sign on between those two, and ESET PROTECT is the one that is also managing user access rights. Install ESET Enterprise Inspector on a dedicated machine.

So given the fact that you have already deployed ESET PROTECT environment, those are the steps needed: Management / deployment / activation still happens in ESET PROTECT. Our EDR works in a way, that it requires a separate server with a separate console, however the ' EDR console' is inteded only for incident investigation.

Enterprise inspector eset