[KB6927] Known issues for latest versions of ESET business products

Issue

Solution

ESET PROTECT

  • Incorrect character encoding in the Web Console error message in non-English languages when the help pages are not set up in an offline environment.
  • Some context menu actions in Computers are unavailable (grayed out) when they should be available (for example, Isolate from network, End network isolation, Enable EDTD, Last used tasks). Workaround: You can run these actions from Computer DetailsComputer button (Enable EDTD), or use Client Tasks.
  • After upgrading from ESET PROTECT 8.0 to 8.1 via Components upgrade task, domain logins fail after one successful login. Workaround: After the failed login, unselect the Log Into Domain check box on the ESET PROTECT Web Console login screen and then select the check box again.
  • Unable to log into the Web Console after the upgrade when a username or password contains special characters – Fixed in ESET PROTECT 8.0.17.1
  • Generating of .pdf reports does not work for ESET PROTECT Server installed on CentOS 8 – To fix this issue, you can buy and install a third-party QtWebKit4 package.
  • Windows Server 2008 SP2 is no longer supported from the last release.

ESET PROTECT Cloud

  • It is not possible to create a Live Installer from ESET PROTECT Cloud for EFDE for macOS.
  • Cloud MDM: Dynamic groups filtering is not working with managed Android devices.
  • Windows Server 2008 SP2 is no longer supported from the last release.

ESET Security Management Center (ESMC)

  • The server task does not save credentials (password) when you edit or change a task.
  • When editing a notification with filters enabled, the filter configuration is not displayed but the notifications continue to work.
  • If a computer name includes special characters in the hostname (emojis), it will not connect to ESMC Server.
  • If you add exclusions from policy and choose the option “Exclude collected threats”, exclusion by URI and Threat Name does not work (values are swapped and written into incorrect fields).
  • MDM Core cannot be installed on Windows Server 2008R2 SP1 x64 in “offline mode”.
  • Logs in LEEF format are missing computer name/computer FQDN/and time zone specification with event time.
  • After upgrading from version 6.x ESET Remote Administrator, tasks set with monthly triggers will stop working and cause the “Unexpected Error” message.
  • Solution: Click "Continue", edit the task and recreate the trigger in ESMC.
  • Mobile Device Connector does not accept certificates from ERA 6.5 after the upgrade. A new certificate with the CA included needs to be generated in ESMC version 7 and updated via policy to connect clients, to prevent the need for re-enrollment.
  • 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 Security Management Center 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, as unique device identification is needed by internal structures of MDC. Some Android devices might have the same device identification, and those devices will fail to enroll in MDC.
  • 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 ESMC V7 it might happen, that it is not possible to login to the web console for a longer period of time.
  • Using emojis or other 4-byte characters in certificates & object names will cause database errors and server crashes in some cases.
  • Proxy settings for replication are not applied from an agent policy using the All-in-one installer.
  • The Computer details view for a client incorrectly displays static group hierarchy and shows the device as a member of all parent dynamic groups. However, policies are still applied correctly. 
  • An On-demand scan launched from the ESMC console shuts down the computer even if this post-scan action was not selected

ESET Endpoint Security/Antivirus (EES/EEA)

  • HIPS component reports incorrect status after enabling before restart. (This also applies to versions 7.1 and 7.2)
  • In some cases, sending configuration to ESMC takes up to 30 minutes (7.3 and later)

ESET Mail Security for Microsoft Exchange (EMSX)

  • No known issues

ESET Business Account (EBA)

  • General failure might appear when the site is deleted and devices are deactivated
  • ESA users quantity might exceed the specified margin
  • Application error might display when user tries to download a legacy license file for some invalid products
  • Adding units to the site might end with an error
  • Activated EFSU and EFDE devices might not appear after activation with Offline license file
  • ESET Cloud Office Security reactivation might end with issues
  • Multiple license removals might end in an unexpected error
  • Duplicated activated devices might appear when a license is migrated from ESET License Administrator to EBA
  • The number of activated devices displayed on the dashboard might not synchronize with product usage
  • Downgrading a license to a Home product might not apply in EBA

ESET MSP Administrator (EMA 2)


ESET Enterprise Inspector (EEI)


ESET Secure Authentication (ESA)

  • No known issues

ESET Endpoint Encryption (EEE)

  • Logins using "Network Login" authentication type are not migrated in an upgrade from a previous version.
  • Uploading an EEE for MacOS client package into an EEE server in non-multi-tenant mode will fail. You can verify the version number on the login screen. For example, 3.3.0.321 MT indicates the server is in multi-tenant mode. 3.3.0.321 indicates it is in non-multi-tenant mode and will experience failure.

ESET Endpoint Security for Android (EESA)

  • Due to changes in Stock Android by Google, we are not able to execute the relevant steps related to Wipe command properly anymore. To ensure at least some data security on Android 6 devices, this command behaves the same way as Enhanced factory reset, i.e. among other things, the process will end up with a restore to factory default settings.
  • Due to changes in Android 7.0, Google allows the user to deactivate an active device administrator and uninstall the application in a single action. Users can now uninstall EESA without entering the admin password.
  • If you have an active application on your device that has screen overlay permissions on your Android 6 (Marshmallow) device, you will be unable to grant permissions to any other application including your ESET product. To enable permissions for your ESET product, you must disable screen overlay permissions for the application.
    Permission settings for Android 6 (Marshmallow)

    If you receive the message "Screen overlay detected" after granting permissions in your ESET mobile product for Android, see our Knowledgebase article to resolve the issue.

  • To access features that use SMS services in ESET Endpoint Security downloaded from Google Play, you need to install the ESET SMS Tool application. For more information, visit the ESET SMS tool documentation or our Knowledgebase article.

ESET Endpoint Antivirus and ESET Endpoint Security for macOS

  • Scheduler tool in ESET Endpoint Security for Mac and ESET Endpoint Antivirus for Mac running on macOS Big Sur (11) cannot run scheduled task for sandboxed applications. For example, all applications downloaded from the Apple store are sandboxed. You can find more information about Sandbox in the Apple documentation.
    Scheduler can still create tasks for ESET applications and other non-sandbox applications.
  • A computer scan that is triggered from ERA and finds malware displays an action window on the endpoint computer that requires user interaction.
    Solution: Use Strict Cleaning when triggering scans from ERA.
  • Media Control settings are not migrated to Device Control during an upgrade from version 6 to 6.1 and later.
  • Mail protection cuts off an email when sending it with ISO-2022-JP encoding.
  • Upgrade to version 6 is possible only from ESET NOD32 Antivirus 4 Business Edition version 4.1.100 and higher.
  • Folders used as a storage place for several OS X Server services must be excluded from scanning.
  • You cannot deactivate Endpoint License from ESET License Administrator.
  • The “Scan on File“ action blocks communication between VMware Fusion from version 7 and vCenter on OS X from version 10.10.4
    Solution: You must set exclusions and exclude the following folder:
    • On macOS 10.13 and older :
      /System/Library/Preferences/Logging/Subsystems
    • On macOS 10.14:
       /private/etc/*.*
      /Applications/VMware Fusion.app/Contents/*.*
      /Library/Preferences/Logging/*.*
  • Cleaning loginwindow.plist on macOS 10.13 only works if you upgrade with products that have the same application bundle name.
  • Text is missing in firewall dialogues in your ESET product for Mac.
    Products affected:
    • ESET Cyber Security Pro 6.10.600.0 and later
    • ESET Cyber Security 6.10.600.0 and later
    • ESET Endpoint Security for Mac 6.10.900.0 and later
    • ESET Endpoint Antivirus for Mac 6.10.900.0 and later
    You can resolve this issue by rebooting your computer.

ESET Server Security for Linux (ESSL)