thank you for your reports, I checked it with the QA and Dev, they are aware of this issue.
Once the upgrade fails, can you please collect the logs as described at https://support.eset.com/en/kb3404-use-eset-logcollector-on-macos-and-send-the-logs-to-eset-technical-support?ref=esf
upload them to a safe location and send me a private message with the download details and reference to this forum topic?
Once you do, the work-around is to disable the Web access protection to apply the upgrade.
Hello, in case you mean "ESET Full Disk Encryption", then the answer is yes, as this is managed via ESET Protect / Security Management Center Server / agents, which use HTTP Proxy. If you want to use ESET Endpoint Encryption, with a dedicated server, then this solution uses a separate Cloud Proxy component.
I am a technical support engineer for ESET's Encryption product family.
You have mentioned a few things that I feel need clarifying, some of which may require in-depth explanations in order for you to come to your own conclusion on how best to deploy ESET Endpoint Encryption in your own environment.
First I feel I need to address an important concept regarding ESET Endpoint Encryption. EEE uses a "cloud proxy", which is our patented technology which simply acts as a pigeonhole (or middleman) for communicating commands/client updates between the EEE server and EEE client workstations.
If your environment has an Internet proxy to control traffic, then you will need to add your proxy details to your EEE Server. For complete details on this, please read our article here: KB7607 - Add internet proxy server settings to ESET Endpoint Encryption Server
Providing everything is configured correctly, your EEE client workstations will be able to communicate with your EEES (through the cloud proxy) as normal.
Regarding your questions about deployment, I am not familiar with deploying EEE from ESMC itself, but I know there isn't a repository for EEE, so it cannot be installed that way. However, the EEE Server has a "Push Install" feature which allows you to install the EEE client (MSI) on clients across the network.
Sadly this may not be suitable, as you said your users never connect to your internal network. In which case I would ask, how do you currently manage software deployments for users off your network?
Regardless, EEE's installer is an MSI file, which can be easily deployed through 3rd party tools. Just ensure your Workstation Policy is configured correctly before generating the MSI for the endpoints, as the Workstation Policy is bundled into the MSI itself. Additionally, depending on your requirements you may need to create a separate Merged Installer for each Workstation Team you have set-up in your EEES.
I hope this sheds some light on your situation and what you can do to deploy EEE in your environment.
For Endpoint v8 you can find a changelog on the download page or here: https://forum.eset.com/topic/26629-eset-endpoint-products-for-windows-version-802028-have-been-released/
ESET PROTECT and ESET PROTECT Cloud are to be officially released later today. At that time a changelog will be available on the standard channels (ESET's website, forum, etc.).