The offline repository may not work on all systems (it might fail in the case of weak internet connectivity).
Cannot download offline repository using Mirror Tool due to corrupted or incomplete downloads.
When manually upgrading ESET Mobile Device Connector, the upgrade may fail due to the previous installation of Mobile Device Connector not being able to stop its service.
Solution: Set the Mobile Device Connector service Startup type to “Manual”, then restart the service from within Services and run the upgrade procedure again.
It is not possible to use Windows Phone for two-factor authentication if ESET Remote Administrator is a part of the domain and domain user is provisioned.
Certificates with validity ending after the year 2037 are not supported on Mac OS X. It is not possible to parse a date variable from the Certificate Authority on Mac OS X. The Agent cannot connect, because OS X cannot accept the Certificate Authority.
Mobile Device Connector (MDC) requires unique device identification to be able to process device enrollment correctly since the internal structures of MDC need unique device identification. Some Android devices might have the same device identification, and those devices will fail to enroll into MDC.
Versions of ESET Rogue Detection Sensor included in previous versions (220.127.116.11 and earlier) of ERA cannot be upgraded to the version included in ERA 18.104.22.168. Solution: Uninstall the previous version of RD Sensor, and then install a new RD Sensor from the repository.
Installing ERA Agent on macOS Sierra (10.12) requires root privileges.
MDM can stop working after a mobile device's static object is removed (for example, if a task or policy is removed from the device). Solution: This is a database-related issue — contact ESET technical support to resolve.
When performing an upgrade of previous versions of ESET Remote Administrator to version 6.5, it might happen, that it is not possible to connect to ERA Server. Even though the MSI is already upgraded to version 6.5, the upgrade of the database is still in progress. In specific cases, when the database is too large, or hardware is not powerful enough (slow HDD, not enough RAM) it could take a longer time to complete. It is forbidden to reboot the computer during this process, as it will result in a corrupted database. Solution: Revert DB from backup and perform the upgrade again.
Upgrading the MDM appliance to version 6.5 using Client Task ends with an error: "Failed" -> error : ReadUpgradeStatus: Upgrade infrastructure task failed: Command failed (exit code: 1)" "Failed to run custom action DbUpgrade. ./MDMCore-Linux-x86_64.sh: 1079: Error '1' occured while running custom action DbUpgrade." Solution:1) Give the database user all rights for a database or 2) Uninstall the product while keeping the database and then reinstall.
Using emojis or other 4-byte characters will cause database errors and server crashes in some cases.
ESET Endpoint Antivirus and ESET Endpoint Security for Windows (6.6.2095.1)
ESET business product no longer supported
This content applies to an ESET product version that is currently in End of Life status and is no longer supported. This content is no longer updated.
The endpoint may not restart automatically after an upgrade if it is installed via the ESET Remote Administrator software install task with AUTOMATICALLY RESTART IF NEEDED enabled. Workaround: Edit the software installation task "Installation parameters" field with the custom command line parameter REBOOT_WHEN_NEEDED=1.
An upgrade takes longer if a large Web control list is presented in product (50k+ links). Solution: The upgrade will finish successfully when the list is processed.
After upgrading from ESET Endpoint product 6.3 and older, specific modules (Firewall, Protocol Filtering, and HIPS) are not functional until OS is restarted.
Empty groups of application statuses might be displayed in “Advanced Settings / User Interface / Application statuses” on slow machines.
When the policy with configured Override mode is applied to the client, and the client attempts to run the Override mode on the client, immediately after the installation, the client user interface might freeze. Solution: Wait at least one minute after installation, to initiate the Override mode.
ESET File Security for Microsoft Windows Server (6.5.12018.0)
ESET business product in Limited Support status
This content applies to an ESET product version that is currently in Limited Support status and is scheduled to reach End of Life status soon.
The password for accessing system logs cannot be changed when SFTP access is already enabled. Solution: The password can be changed by disabling SFTP access and enabling it again with the new password.