| Reference Number |
Related Article |
Found
ENSM Version |
Resolved ENSM Version |
Issue Description |
| ENSM-788 |
|
10.6.1 |
|
Issue: When a product deployment fails, two client events with ID 2412 are generated for the system. |
| ENSM-708 |
|
10.6.0 |
10.6.1 |
Issue: An attempt to load com.McAfee.FileCore.kext happens during an ENSM Threat Prevention upgrade even if the system does not have user consent to load the kext. The experience should match the behavior described in KB89728.
Resolution: This issue is resolved in ENSM 10.6.1. |
| ENSM-680 |
|
10.6.0 |
As Designed |
Issue: The user on the macOS system must approve the FileCore extension again to load on the system. The reason is because the earlier approval for com.intelsecurity.FileCore.kext is not valid for the renamed kext: com.McAfee.FileCore.kext.
Resolution: This behavior is as designed. The user has to open System Preferences, Security & Privacy and click Allow for the McAfee kernel extension to load on the system. |
| ENSM-689 |
|
10.6.0 |
10.6.1 |
Issue: Wild cards are not supported in firewall rules although they are enforced and displayed in the client preferences user interface.
Resolution: This issue is resolved in ENSM 10.6.1. |
| ENSM-683 |
|
10.6.0 |
10.6.1 |
Issue: After you disable ENSM Web Control from ePolicy Orchestrator, the menulet shows a yellow exclamation point. This issue does not occur when you disable ENSM Threat Prevention and ENSM Firewall from ePolicy Orchestrator.
Resolution: This issue is resolved in ENSM 10.6.1. |
| 1266150 |
|
10.5.9 |
|
Issue: Editing a repository name on the Update preferences Repository List tab of the local client user interface adds a duplicate entry with the new name. But, it retains the repository entry with the older name.
Workaround: Delete the older repository from the user interface. |
| 1265479 |
|
10.5.9 |
|
Issue: The Repository List tab in the Update preferences of the local client user interface does not list the Repository URL of the ePolicy Orchestrator Spipe repository. |
| |
|
10.5.7 |
As Designed |
Issue: After you upgrade to ENSM 10.5.7, the file format of quarantined items changes to ZIP. As a result, if ENSM is reverted to a version earlier than 10.5.7, the restore from quarantine feature does not work for files in the new format.
Resolution: This behavior is as designed. To restore quarantined items, manually extract the quarantined items using the "Archive Utility" application on the Mac system. |
| 1259847 |
|
10.5.6 |
DLP Endpoint 11.1.0 Hotfix 3 |
Issue: On a Mac system running ENSM 10.5.6 or later, installation of Data Loss Prevention Endpoint (DLP Endpoint) 11.1.0.45 downgrades certain common components used by ENSM.
Workaround: Install DLP Endpoint 11.1.0.45 before you install ENSM.
Resolution: This issue is resolved in DLP Endpoint 11.1.0 Hotfix 3. |
| 1254818 |
|
10.5.5 |
10.5.5 (Repost)
10.5.5 Hotfix 1254818 |
Issue: Global Threat Intelligence (GTI) connectivity is intermittent in ENSM Web Control.
Resolution: This issue is resolved in ENSM 10.5.5 (Repost) and ENSM Web Control 10.5.5 Hotfix 1254818.
- If you have not deployed ENSM 10.5.5 Web Control, use ENSM 10.5.5 (Repost).
- If you already deployed ENSM 10.5.5 Web Control, you can either uninstall the existing version and install ENSM 10.5.5 (Repost) or install ENSM Web Control Hotfix 1254818. This hotfix is available from Technical Support.
|
| 1254777 |
|
10.5.5 |
10.6.2 |
Issue: Quarantined files that have unicode characters in their name do not display on the Quarantine screen.
Resolution: This issue is resolved in ENSM 10.6.2. |
| 1249594 |
|
10.5.5 |
As Designed |
Issue: User interface elements of 32-bit managed products do not display in the ENSM 10.5.5 64-bit console.
Resolution: This behavior is as designed. Upgrade the 32-bit managed products to their 64-bit variants. Only user interface elements of the managed products are not loaded. All functional features of the products must work as expected, because 64-bit ENSM provides backward compatibility support for 32-bit managed products. |
| 1250801 |
|
10.5.5 |
As Designed |
Issue: Sometimes the following message displays in macOS Mojave when MERTool is invoked to collect Minimum Escalation Requirements (MER) logs:
"McAfee Endpoint Security for Mac" would like to control the application "Terminal"
Resolution: This behavior is as designed. With macOS Mojave, Apple changed the way applications try to access another application. If you see such a message, it is safe to approve the request for ENSM to control the Terminal. |
| 1250488 |
|
10.5.5 |
As Designed |
Issue: The ENSM console displays the following error message when ENSM 10.5.5 Threat Prevention is uninstalled and Management of Native Encryption and Data Loss Prevention are left on the system:
Your MAC is at Risk
Resolution: This behavior is as designed. Upgrade the 32-bit managed products to their 64-bit variants. ENSM 10.5.5 Threat Prevention must not be uninstalled before you uninstall other 32-bit managed products from the system. |
| 1248901 |
|
10.5.5 |
As Designed |
Issue: ENSM 10.5.0 Threat Prevention on-access scan detection stops working after you upgrade any other ENSM module, such as Firewall or Web Control, from 10.5.0 to 10.5.5.
Resolution: This behavior is as designed. When you upgrade to ENSM 10.5.5 from a previous version of the product, upgrade all modules of ENSM on the system. |
| 1248528 |
|
10.5.5 |
As Designed |
Issue: Installation of the standalone package of McAfee Agent 5.5.1 through the ENSM 10.5.5 standalone installer package (.dmg) changes the existing McAfee Agent manageability status from managed to unmanaged. This result occurs on systems where ePolicy Orchestrator manages ENS.
Resolution: This behavior is as designed. Perform ENSM 10.5.5 upgrades on an ePolicy Orchestrator-managed system, from ePolicy Orchestrator through a deployment task. |
| 1248160 |
|
10.5.5 |
As Designed |
Issue: The ENSMac License ePolicy Orchestrator extension shows its version as 10.2.0.
Resolution: This behavior is as designed. There is no change to the ENSMac License ePolicy Orchestrator extension from 10.2.0 to 10.5.5 or later. The same 10.2.0 license extension supports ENSM 10.5.5 or later. |
| 1244716 |
|
10.5.5 |
As Designed |
Issue: Sometimes spin dumps are logged to System Reports in macOS Mojave, for the menulet and McAfee Endpoint Security for Mac application processes.
Resolution: This behavior is as designed. |
| |
KB90267 |
10.2.3 |
10.5.0 Hotfix 1244068
10.2.3 Hotfix 1238954 |
Issue: Users see emails stuck in their outbox or slowness when they send emails using Apple Mail. This issue is experienced when ENSM Threat Prevention 10.2.3 or 10.5.0 is installed on macOS High Sierra that runs on an APFS partition. This issue does not occur when on-access scan is turned off.
Resolution: This issue is resolved in ENSM Threat Prevention 10.2.3 Hotfix 1238954 and ENSM Threat Prevention 10.5.0 Hotfix 1244068. See the related article for more information. |
| |
KB90520 |
10.2.3 |
10.5.5 |
Issue: ENSM runs as a 32-bit application. When you start "McAfee Endpoint Security for Mac.app" for the first time on macOS High Sierra 10.13.4 and later, you see the following alert. The alert notifies you that the ENSM application is not optimized for Mac.
"McAfee Endpoint Security for Mac" is not optimized for your Mac.
Workaround: The alert appears only once. It does not impact the product functionality, so you can safely ignore the alert. For more information, see the Apple article at https://support.apple.com/en-in/HT208436.
Resolution: This issue is resolved in ENSM 10.5.5, which has native 64-bit binaries. See the related article for more information. |
| |
|
10.2.3 |
As Designed |
Issue: ENSM Threat Prevention 10.2.2 cannot co-exist with the ENSM 10.2.3 Firewall and Web Control modules.
Resolution: This behavior is as designed. When you upgrade to ENSM 10.2.3 from a previous version of the product, upgrade all modules of ENSM on the system. |
| 1215275 |
|
10.2.3 |
10.5.5 |
Issue: When you browse any blocked URL, the McAfee block page displays. If you leave the block page idle for some time and then click OK, it redirects to a page with OK and Continue buttons, but with no message displayed on the screen. This issue occurs with Safari 10.1.2 and later.
Resolution: This issue is resolved in ENSM 10.5.5. |
| 1211992 |
|
10.2.3 |
As Designed |
Issue: During installation of ENSM Web Control 10.2.3 with Safari 11, the Preferences - Extensions pane is displayed to the user to enable Web Control, but it does not list Web Control.
Resolution: This behavior is as designed. The user has to close the Safari 11 browser and relaunch it, to see the Web Control extension and enable it. |
| 1219538 |
|
10.2.2 |
As Designed |
Issue: On a Mac system running ENSM, on-demand scan policy settings do not display in the client UI.
Resolution: This behavior is as designed. |
| 1185563 |
|
10.2.2 |
Unable to reproduce |
Issue: Access Protection violation events are reported immediately for Web Protection, after installation. This issue is intermittent. If you can reproduce this issue, contact Technical Support. |
| 1181639 |
|
10.2.1 |
10.2.2
10.5.5 |
Issue: ProductConfig.xml gets corrupted when ENSM blades are installed on an existing installation of Data Loss Prevention, File and Removable Media Protection, Management of Native Encryption, or McAfee Client Proxy.
Resolution: This issue is resolved in ENSM 10.2.2 and 10.5.5. |
| 1177587 |
|
10.2.1 |
10.2.2 |
Issue: The Functional Module Platform daemon (fmpd) crashes, after you upgrade from McAfee Client Proxy 2.2.0 to McAfee Client Proxy 2.2.1.103 on a Mac system.
Resolution: This issue is resolved in ENSM 10.2.2. |
| 1158287 |
|
10.2.1 |
|
Issue: You installed or upgraded to ENSM 10.2.1 on Mac OS X El Capitan 10.11.x or Mac OS X Yosemite 10.10.x. Then, after you upgraded the operating system to Mac OS X Sierra 10.12, the product does not display a notification when it detects malware.
Workaround: After you upgrade the operating system to Mac OS X Sierra 10.12, restart the Mac system. |
| 1154900 |
|
10.2.1 |
As Designed |
Issue: The Endpoint Security Web Control extension for the Safari browser is not installed on a Mac OS X Sierra 10.12 system.
Resolution: This behavior is as designed. When you install the Endpoint Security Web Control extension, you must click Trust when prompted. |
| 1144747 |
|
10.1.0 |
10.2.0 |
Issue: Installation of ENSM 10.1 after Data Loss Prevention Endpoint (DLP Endpoint) for Mac 10.0 has been installed, causes both ENSM and DLP Endpoint for Mac to stop working.
Workaround: To run both applications, install ENSM 10.1 first, and then install DLP Endpoint for Mac 10.0.
Resolution: This issue is resolved in ENSM 10.2.0. |
| 1077269 |
|
10.0.0 |
10.2.2 |
Issue: Incorrect self-protection violation events are generated for Threat Prevention and Web Control locations, after product deployment.
Workaround: If the processes that are stopped during deployment are Mkdir, CP, or WebKitPluginHost, you can safely ignore the events. The event ID is 1092.
Resolution: This issue is resolved in ENSM 10.2.2. |
| 1071362 |
|
10.0.0 |
MNE 2.1.0 Hotfix 1072394 |
Issue: When Management of Native Encryption (MNE) is installed with ENSM, the Encryption UI does not display any information.
Resolution: This issue is resolved in MNE 2.1.0 Hotfix 1072394. |
| 1067096 |
|
10.0.0 |
MCP 2.1.0 |
Issue: On a Mac system running ENSM, installation of McAfee Client Proxy (MCP) 2.0 downgrades certain common components that ENSM uses.
Workaround: Install MCP 2.0 before you install ENSM.
Resolution: This issue is resolved in MCP 2.1.0. |
| 1056455 |
|
10.0.0 |
DLP Endpoint 9.3 Update 5 |
Issue: On a Mac system running ENSM, installation of Data Loss Prevention Endpoint (DLP Endpoint) 9.3 downgrades certain common components that ENSM uses.
Workaround: Install DLP Endpoint 9.3 before you install ENSM.
Resolution: This issue is resolved in DLP Endpoint 9.3 Update 5. |
| 1019557 |
|
10.0.0 |
|
Issue: Multi-slot policies in Web Control, such as the Block and Allow List and Content Actions, are not supported on Mac systems.
Workaround: Assign a single policy to the Mac system or group. |
| |
|
10.0.0 |
|
Issue: Management of Native Encryption (MNE) and Data Loss Prevention (DLP Endpoint) are not supported in ePO Cloud. Do not uninstall MNE and DLP Endpoint before you install ENSM from ePO Cloud.
Workaround: Use ePolicy Orchestrator On-Premises to manage MNE and DLP Endpoint with ENSM. |
