[KB6927] Known issues for version 7 ESET business products

Issue

  • Known Issues for version 7 (and version 7 compatible) business products

Solution

ESMC | EES/EEA | EMSX | EBA | EEI | ESA | EEE | EESA

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)

ESET Mail Security for Microsoft Exchange (EMSX)

  • Upgrade from version 4.5 does not transfer activation.
    Solution: Run the "Product activation task" with a correct license after the upgrade.

ESET Business Account (EBA)

  • Password update in some cases might perform slowly.
  • ESET Secure Authentication over usage might exceed the declared limitation.
  • ESET Secure Authentication activation via Site might result in an error.
  • An issue with allocating units to a site might happen in a specific case.
  • Application error might appear when user logins after logout.
  • Incompatibilities in some browsers might appear.

ESET Enterprise Inspector (EEI)

ESET Secure Authentication (ESA)

  • None. 

ESET Endpoint Encryption (EEE)

  • Logins using 'Network Login' authentication type are not migrated in an upgrade from a previous version.

ESET Endpoint Security for Android (EESA)

  • Due to recent 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 recent 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.

  • ESET Endpoint Security for Android function Call Filtering is nonfunctional on some builds of Android 8.0 and 8.1. due to the technical limits of the Android operating system.