Andi316 0 Posted August 15, 2023 Posted August 15, 2023 Hello, I can't install ESET Server Security on a Windows Server 2019 machine. I get an "internal error" message directly at the beginning of installation. Logs attached. Thank you. ELC_logs.zip
Administrators Marcos 5,735 Posted August 15, 2023 Administrators Posted August 15, 2023 Since ESET Server Security uses an msi installer, please generate an install log as per the instructions at https://support.eset.com/en/kb406. Also please post a screenshot of the error.
Andi316 0 Posted August 15, 2023 Author Posted August 15, 2023 Screenshot attached. It's not a msi installer, the filename is epi_win_live_insaller.exe
Administrators Solution Marcos 5,735 Posted August 15, 2023 Administrators Solution Posted August 15, 2023 Does installation using an msi installer from https://www.eset.com/int/business/download/file-security-windows/ work?
Administrators Marcos 5,735 Posted August 15, 2023 Administrators Posted August 15, 2023 By the way, was the all-in-one installer that was failing to install created recently using the latest version of ESET Server Security or an older one? Did you include also the ESET Inspect connector in the package?
Andi316 0 Posted August 15, 2023 Author Posted August 15, 2023 I have another problem now. Installation and activation is ok now, but the machine does not appear in the Eset protect cloud. Can I add the machine manually to the cloud? The installer I used with no success was from the Eset Protect Cloud, see attachment. Fresh download from today.
Administrators Marcos 5,735 Posted August 15, 2023 Administrators Posted August 15, 2023 Did you select ESET Server Security as the product to install? The reason why you don't see the server in the console is that the management agent was not installed. The msi installed only ESET Server Security. You can create an agent installer by keeping only "management agent" selected here:
Andi316 0 Posted August 15, 2023 Author Posted August 15, 2023 Sorry, I can't find that. It looks different for me. But I have another solution now. The Management Agent was not installed. I was able to create a custom installer that only installs the Agent. This installation was successful. The machine now shows up in the Protect cloud. Thanks again for your help.
Recommended Posts