Rincewind

You can download the files directly from the Ubuntu-Repositories: hxxp://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2.13_amd64.deb hxxp://security.ubuntu.com/ubuntu/pool/main/o/openssl/openssl_1.1.1f-1ubuntu2.13_amd64.deb

To the best of my knowledge there is no way to approve this remotely/scripted. Even the help pages doesn't offer anything different on the subject.

At a first glance the settings match what is recommend for Jamf (https://support.eset.com/en/kb7324-deploy-eset-endpoint-products-for-macos-using-jamf-pro) so if those are applied correctly the message shouldn't appear IMHO. I have no experience with Addigy but in the screenshot it shows "Affected policies: No policy contains this item". Are you sure the settings are assigned and deployed (have you waited a full deployment cycle) to the machines? Alternatively there is a plist configuration profile provided in the help pages:https://help.eset.com/ees_mac/6.10/en-US/install_remote.html

Be aware that this creates a software repository (offline copy of the installers) and not a module update mirror. The mirror tool will create either a repository or a update mirror depending on the parameters. An example for creating a update mirror look like this: sudo ./MirrorTool --mirrorType regular \ --intermediateUpdateDirectory /tmp/mirrorTool/mirrorTemp \ --offlineLicenseFilename /tmp/mirrorTool/offline.lf \ --outputDirectory /tmp/mirrorTool/mirror You can find a full rundown of the parameters in the online help pages: https://help.eset.com/protect_install/80/en-US/mirror_tool_linux.html

The issue is with the server certificate being to strict/not matching the hostname used in the agent installer. First check the server peer certificate which hostnames are allowed (listed in the column HOST). If you want to allow additional hostnames/IPs you can create a new server certificate containing all allowed hostnames seperated by space, comma, or semicolon. Or you can leave the default (*) to allow all hostnames. Afterwards you have to assign this new certificate in the server settings and restart the Virtual Appliance (or the eraserver-Service) for the change to take effect. You can also perform a repair installation and change the hostname. Please be aware that the hostname has to match eaxctly.

You can hide this message using a policy for "ESET Mobile Device Connector". Here disable the Option "Send iOS related application statuses". Ensure that you assign this policy to the server running the MDM. Also check that the machine is currently talking to the ESMC - according to the screenshot last communication was 13th of january?

The error "ESET Windows Security Center indicates that the feature is not installed or is not running properly" is reported by the agent and not by the Endpoint therefore the Endpoint shows no issues. The agent just forwards the status of the windows security center to ESET Protect. In the computer details you will find which function is actually affected (e.g. Windows Update or Windows Firewall) or you can check the Windows Security Center directly on the machine. If you want to disable the warning please refer to the following knowledge base: https://support.eset.com/en/kb6787-disable-windows-update-or-windows-firewall-notifications-in-eset-security-management-center-7x

From my experience this happens if the push of the installer is successful but the machine is unable to download the agent afterwards. In this case you can create a offline cache file: For instructions on silent install please refer to the knowledge base article: https://support.eset.com/en/kb6820-deploy-the-eset-management-agent-and-the-eset-endpoint-product-together-7x#Silent_Install

Have you enabled pre-release updates in the config (/etc/opt/eset/esets/esets.cfg)? av_prerelease_updates = yes Otherwise you will not receive the fixed module.

Hello Peter, I also would appreciate access to the Beta builds. Thanks in advance.