Business article search

Known issues for version 6 ESET business products

Issue

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

 

Solution

| | | | | EMSX | |  |



ESET Remote Administrator (6.4.29.0):

  • When manually upgrading ESET Mobile Device Connector from version 6.1 to version 6.2 on Windows, an error dialog is displayed.
    Solution: Close the error dialog and the installer will continue normally, with the setup finishing successfully.
  • When manually upgrading ESET Mobile Device Connector, the upgrade may fail due to 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.
  • You cannot enroll the same device that has been previously enrolled and un-enrolled using the task "Stop managing / Uninstall ERA agent"
  • Android devices remain visible in ESET Remote Administrator 6 after sending the Stop managing (uninstall ERA agent) client task from ERA to mobile devices.
    Solution: Select the devices in the ERA Web Console ComputersGroups and then click Computers Delete.
  • Versions of ESET Rogue Detection Sensor included in previous versions (6.x and earlier) of ERA cannot be upgraded to the version included in ERA 6.2.11.0.
    Solution: Uninstall the previous version of RD Sensor, and then install a new RD Sensor from the repository.
  • You cannot upgrade from EFSW 4.5 to EFSW 6.x using the ERA “software install task” because the upgrade will fail due to a necessary restart
  • 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 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. 
  • Installing ERA Server on Windows Server 2003 fails when a License Key is used during installation.
  • Component Upgrade Task does not upgrade the Agent on OS X 10.10.
  • ESET Mobile Device Connector does not support MySQL ODBC driver version 5.1.5 or older. 
    Solution: Update MySQL ODBC drivers.
  • 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 into MDC.
  • Versions of ESET Rogue Detection Sensor included in previous versions (6.1.33.0 and earlier) of ERA cannot be upgraded to the version included in ERA 6.4.29.0
    Solution: Uninstall the previous version of RD Sensor, and then install a new RD Sensor from the repository.
  • Installing ERA Server on Windows Server 2003 fails when a License Key is used during installation. 
    Solution: Install Server without license and then add license using the ERA Web Console.
  • Using the ESET Remote Administrator Agent Component Upgrade task with ESET Shared Local Cache (ESLC) and ESET Virtualization Security (EVS) will upgrade the ERA Agent but the appliance will show a red Malfunction status (“Product is installed but it is not running”) in the ERA Web Console. The appliance will continue to function but will not be manageable using the ERA Web Console.
    Solution: Do not upgrade ERA Agent in ESLC and EVS until the upcoming service release of ELSC and EVS and then replace the entire appliance.  If you have already upgraded, redeploy the appliance with the previous ERA Agent to restore functionality.
  • Generating the “All-in-one installer“ for ESET Remote Administrator Agent and Endpoint product might fail on ERA servers with slower internet connection due to hard coded timeout that is set to 120 seconds.
Known issues for ESET Remote Administrator (6.3.12.0)
  • ESET Mobile Device Connector cannot be upgraded using the task “ERA Infrastructure upgrade”
  • When manually upgrading ESET Mobile Device Connector from version 6.1 to version 6.2 on Windows, an error dialog is displayed.
    Solution: Close the error dialog and the installer will continue normally, with the setup finishing successfully.
  • When manually upgrading ESET Mobile Device Connector, the upgrade may fail due to 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.
  • You cannot enroll the same device that has been previously enrolled and un-enrolled using the task "Stop managing / Uninstall ERA agent"
  • Android devices remain visible in ESET Remote Administrator 6 after sending the Stop managing (uninstall ERA agent) client task from ERA to mobile devices.
    Solution: Select the devices in the ERA Web Console ComputersGroups and then click Computers Delete.
  • Versions of ESET Rogue Detection Sensor included in previous versions (6.x and earlier) of ERA cannot be upgraded to the version included in ERA 6.2.11.0.
    Solution: Uninstall the previous version of RD Sensor, and then install a new RD Sensor from the repository.
  • You cannot upgrade from EFSW 4.5 to EFSW 6.x using the ERA “software install task” because the upgrade will fail due to a necessary restart
  • 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
  • Server and Proxy cannot be started in Linux failover cluster. Issue is caused by incorrect cluster scripts shipped with the setup scripts. It can be worked around by manually replacing the cluster scripts with fixed versions (after install/upgrade). Even if the fixed cluster scripts are used, ERA Server and Proxy are not protected with SELinux policies in Linux cluster. In addition there is a minor bug in the Agent SELinux policy which makes impossible for the Agent to discover Server on the cluster nodes.
  • The wipe function doesn't work on iOS devices. As a workaround, use Client Task called Anti-Theft Actions and choose Enhanced factory reset option in Settings. This will wipe an iOS device despite the fact there isn't an apple icon indicating it can be run on iOS devices.
  • Certificates with validity ending after 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 can not connect, because OS X can not can not accept the Certificate Authority. 
  • There is a spelling mistake in License Manager section of ESET Remote Administrator Web Console, where word "Business" appended to each license is misspelled as "Bussiness"

ESET Endpoint Antivirus and ESET Endpoint Security for Windows (6.3.2016.0):

  • Installation with AVRemover crashes while removing SUPERAntiSpyware Professional on Windows 10 x64
  • Installation with AVRemover detects Microsoft Edge while scanning applications
  • 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

ESET Endpoint Antivirus and ESET Endpoint Security for OS X (6.2.7.0):

  • Graphic User Interface (GUI) does not start on OS X 10.7 and 10.8 after an installation from ERA 6.3.12.0
    Solution: Restart OS X
  • Network traffic filtering cannot be enabled from the Menu bar icon after disabling Protection statuses
  • Web access protection cannot be started if a policy with disabled HTTP protocol checking was unassigned from ERA.
    Solution: Before unassigning, apply a policy that turns on the HTTP protocol checking
  • A computer scan that is triggered from ERA and finds a malware displays an action window on the endpoint computer that requires a 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
  • Web Protection statistics are not available if Email Protection is not installed
  • 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.x and higher
  • Folders used as a storage place for several OS X Server services must be excluded from scanning
  • Extended attributes are not scanned
  • You cannot deactivate Endpoint License from ESET License Administrator
  • If multiple bundle licenses are present in a security account, they are incorrectly grouped in the product activation dialog
  • The “Scan on File“ action blocks communication between VMware Fusion 7 and vCenter on OS X 10.10.4
  • You must exclude the following folders from scanning while using iCloud Drive on OS X Mavericks:
    /Users/<user_name>/Library/Caches/CloudKit/com.apple.clouddocs
    /Users/<user_name>/Library/Application Support/CloudDocs
    /Users/<user_name>/Library/Mobile Documents

ESET Endpoint Security for Android (2.0.152.0):

  • Due to recent changes in Stock Android by Google, we are not able to execute 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 with a restore to factory default settings.
  • Anti-Phishing is unavailable in Chrome on Android 6 devices – we are currently working on the fix.
  • You cannot start an upgrade with the “Software Install” task from ESET Remote Administrator with the new version of EESA selected from repository.
    Solution: Use the "Install by direct package URL" method in the following Knowledgebase article: How do I upgrade ESET Endpoint Security for Android (2.x) using ESET Remote Administrator? (6.x)

ESET File Security for Microsoft Windows Server (6.3.120010.0):

  • Creating infected files in a shared network folder with enabled “Network drives scan” does not trigger alarm during initial (write) phase
  • The application cannot inspect the content of spanned volumes or those part of a RAID setup because the Hyper-V storage scanner is unable to determine their structures.
  • Cancelling uninstallation process in later stage can result in partial rollback action where some protection modules cannot recover and resume full functionality
  • When managing with ESET Remote Administrator, despite a locked item in a policy distributed by ESET Remote Administrator, certain protection modules still can be disabled using GUI or eShell (including Anti-Stealth, Anti-Phishing and Document protection, which includes Automatic exclusions switch).
  • Smart optimization preset ignores configuration change in file-size limit for scanned archives that could cause the scanner not to inspect archives again despite possible malware payload
  • Hyper-V scan of online virtual machine will not be executed if other than first logical drive is selected as scan target.

ESET Mail Security for Microsoft Exchange Server (6.3.10004.0):

  • Most mouse context-menu actions (copy, export and delete) for detected threats in server log-files created by mail database scanner are inactive
  • Confusing Boolean evaluation of mail processing rule when recipients are matched with rule condition containing multiple entries

ESET Shared Local Cache (1.0.15.0):

  • You cannot schedule a task using scheduler via ESET Remote Administrator policy
  • If you install ESET Shared Local Cache (ESLC) using the provided rpm.bin package (a local installation) on CentOS 6.6, SELinux does not allow ESLC Console to start.
    Solution: Disable SELinux using the instructions in the following ESET Knowledgebase article SELinux conflicts – Disable SELinux.

ESET Virtualization Security for VMware vShield (1.0.10.0):

  • When you unregister EVSA (ESET Virtualization Security Appliance) from vShield, the TUI interface still indicates that there are protected machines connected
  • Threats detected by on-demand scanner are marked as being caught by on-access protection in ESET Remote Administrator / Threats, even when on-access protection was disabled by policy from ERA for target virtual machine

ESET Mail Security for IBM Domino (6.4.14008):

  • In a SSL/TLS browser session, trusted certificates are not stored and listed in the list of know certificates despite user confirmation
  • Cancellation of the uninstallation process at a later stage results in malfunction of several product modules
  • In a very unlikely situation, when upgrading from version 4.5 to 6.4 with completely blank configuration, most settings under Server section in Advanced configuration are deactivated and require initial partition selection

Rate this article:

We cannot respond to feedback from this form. Requests for assistance should be submitted through your normal support channel.