CraigG
-
Posts
8 -
Joined
-
Last visited
Posts posted by CraigG
-
-
I will need to provide logs from a new machine next week, as we've installed the msi on every machine so far.
Some things that I've noticed:
- After the msi was installed, I can now run the Installer we created and it successfully launches and installs the management agent.
- If I delete the installer from the catalog in the eca, the installer throws an error about it not being valid any longer. This tells me that communication with the repository server is ok.
-
The MSI did in fact install without issue.
ESET PROTECT Cloud, yes.
We've tried the Live Installer on Windows Server 2016, 2019, and Windows 10. Per the documentation, these all line up with the supported versions matrix. We've even tried to install old versions of the products using a new Live Installer of course. -
Marcos,
Can you provide a kb or a description of how we should do this exactly?
-
It is not. We get this same error on several different servers, at totally different networks/regions. Let me try the msi anyhow. I'll report back.
-
-
Edit: Please see next reply.
-
Our existing installers just expired so we created new ones for the Server/File Security Packages. We've tried to install on different machines, different networks, etc. Every single one of them throws this error when the installer starts up:
We've also gone through and created the installers with every combo to no avail. Thanks in advance for any guidance here.
Every new installer we create errors out with "Compatible package not found"
in ESET PROTECT On-prem (Remote Management)
Posted
We just installed a few new instances using the installer. I guess we can chalk this up to a temporary issue.