Recent updates to this article Date Update December 5, 2018 Updated non-critical issue 1259847 as resolved in Data Loss Prevention Endpoint 11.1.0 Hotfix 3. November 13, 2018 Updated for ENSM 10.5.7. Added non-critical issues: 1254777 and 1259847.
If you do decide to use your drive with Time Machine and you are using macOS version 10.9.5+, you will not be able to run a Mobile Backup from the Seagate Dashboard software to the Seagate drive. This is due to a Time Machine drive permissions limitation introduced in 10.9.5. Due to NPAPI plug-in removal from Safari 12 (in macOS 10.12.6, macOS 10.13.6 and macOS 10.14), Pulse Secure Java-based applications such as JSAM and Java RDP Hob Applet will not launch via Safari browser.
October 9, 2018 Updated for ENSM 10.5.6. September 21, 2018 Added non-critical issue: 1254818. Added ENSM Web Control 10.5.5 Hotfix 1254818 and ENSM 10.5.5 (Repost) to the 'ENSM product release information' section. September 11, 2018 Updated for ENSM 10.5.5.
Added non-critical issues: 1249594, 1250801, 1250488, 1248901, 1248528, 1248160, and 1244716. Changed all 'patch' references to 'update.' NOTE: McAfee updates were previously referred to as patches. ENSM Version Release to Support (RTS) General Availability (GA) Release Notes 10.5.7 N/A November 13, 2018 (ENSM) (ENSM Threat Prevention) 10.5.6 N/A October 9, 2018 (ENSM) (ENSM Threat Prevention) 10.5.5 Hotfix 1254818 (HF1254818) September 21, 2018 N/A Available from Technical Support (ENSM Web Control) 10.5.5 (Repost) N/A September 21, 2018 (ENSM) (ENSM Threat Prevention) 10.5.0 Hotfix 1244068 (HF1244068) N/A July 10, 2018 (ENSM) (ENSM Threat Prevention) 10.5.0 Hotfix 1229511 (HF1229511) July 10, 2018 NOTE: This hotfix is available only from Technical Support. See the Related Information section below for contact details. N/A Available from Technical Support (ENSM Web Control) 10.5.0 N/A June 12, 2018 (ENSM) (ENSM Threat Prevention) 10.2.3 Hotfix 1238954 (HF1238954) June 20, 2018 NOTE: This hotfix is available only from Technical Support. See the Related Information section below for contact details.
Non-critical known issues Reference Number Related Article Found ENSM Version Resolved ENSM Version Issue Description 10.5.7 As Designed Issue: After upgrading 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, installing 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 installing 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, which is available by contacting Technical Support.
1254777 10.5.5 Issue: Quarantined files that have unicode characters in their name do not display on the Quarantine screen. 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 for collecting 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 uninstalling 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 upgrading 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: Installing the standalone package of McAfee Agent 5.5.1 through the ENSM 10.5.5 standalone installer package (.dmg) on a system where ePolicy Orchestrator manages ENS changes the existing McAfee Agent manageability status from managed to unmanaged. 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.
The same 10.2.0 license extension supports ENSM 10.5.5. 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. 10.2.3 10.5.0 Hotfix 1244068 10.2.3 Hotfix 1238954 Issue: Users see emails stuck in their outbox or slowness when sending 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 running 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. 10.2.3 10.5.5 Issue: ENSM runs as a 32-bit application.
When starting 'McAfee Endpoint Security for Mac.app' for the first time on macOS High Sierra 10.13.4 and later, you see the following alert notifying 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. 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 upgrading 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 upgrading 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: Installing 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, installing McAfee Client Proxy (MCP) 2.0, downgrades certain common components that ENSM uses. Workaround: Install MCP 2.0 before installing ENSM.
![“install Kaspersky Endpoint Security” Is Not Optimized For Your Mac. “install Kaspersky Endpoint Security” Is Not Optimized For Your Mac.](http://support.kaspersky.com/us/images/kis2014_9853_07_en88-208446.png)
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, installing Data Loss Prevention Endpoint (DLP Endpoint) 9.3, downgrades certain common components that ENSM uses.
Workaround: Install DLP Endpoint 9.3 before installing 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 installing ENSM from ePO Cloud. Workaround: Use ePolicy Orchestrator On-Premise to manage MNE and DLP Endpoint with ENSM. To contact Technical Support, log on to the ServicePortal and go to the Create a Service Request page at:. If you are a registered user, type your User Id and Password, and then click Log In. If you are not a registered user, click Register and complete the required fields.
Your password and logon instructions will be emailed to you. NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision.
What Are 32-Bit and 64-Bit Apps, and Why Do They Matter? Posted on August 6th, 2018 by You may have heard recent news about Apple's warning to end users that the company intends to phase-out 32-bit apps running on macOS computers in 2019. And you may be wondering a few things, such as what are 32-bit and 64-bit apps, and why do they matter? We'll get to that below, but first, let's cover some things you may be encountering as part of this change.
Apple has been gradually pushing developers to move their software to 64-bit since mid-2017, and as part of its agenda, in recent month, you may have seen a popup message like the one below when launching apps on your Mac. The somewhat vague dialog that says that the app is 'not optimized for your Mac' and 'needs to be updated by its developer' offers little help as to why that is the case.
This alert first appeared when was released, back in April, and depending on how many old apps you have, and use, you may have seen it often. Below we'll explain what the 'WhatSize' is not optimized for your Mac alert means, and how to find apps that will need updating. What's the difference between 32-bit and 64-bit apps? Understanding the difference between 32-bit apps and 64-bit apps can be confusing as such terminology is often obscure, and sometimes is understood only by initiates. In the example alert shown above, this is a good example; Apple doesn't explain much, but this dialog suggests that something is awry.
MacOS is going to require that all apps be 64-bit in the future, and most average users have no idea what that means. Is it about bandwidth, how fast they can download files from the internet? Something about the quality of audio files or photos? Or does it have something to do with file size, which is measured in bits and bytes (and mega-, giga-, and tera-)?
Without going into too much detail—if you want the nitty gritty, you can read this that explains what is 64-bit computing—64-bit apps allow your Mac to do more, and do so more quickly. Bits are calculated as powers: one bit is 1, two bits is 2, four bits is 8, and so on. Essentially, 64 bits allows for numbers as high as 18 quintillion, meaning that a computer can calculate more, faster. That's a simplistic way of explaining this, but another way of looking at this is that with 64-bit computer, a processor can use—hold on to your hats—16 exabytes of memory. (An exabyte is 1,000 petabytes, a petabyte is 1,000 terabytes, and a terabyte is 1,000 gigabytes.) When we get down to that scale, most people understand the numbers; in fact, your Mac probably has at least 8 gigabytes of RAM, perhaps more, but nowhere near those numbers.
This doesn't mean you need to go out and buy a truckload of RAM for your iMac, but that its processor can pretend to be able to access huge amounts of virtual memory. Why bits matter Bits matter because processors used on today's Macs are 64-bit, and running 32-bit apps will be inefficient. Apple isn't shutting the door right away; instead, they're giving app developers plenty of time to update their apps.
The cutoff won't be with macOS Mojave, due out this fall, but with next year's operating system. However, as Apple explains: 'At our Worldwide Developers Conference in 2017, Apple informed developers that macOS High Sierra would be the last version of macOS to run 32-bit apps without compromise.' It's not clear what Apple's 'compromise' is, but it's possible that 32-bit apps will run in Mojave with some sort of emulation. This means that they may run more slowly, or manage memory less efficiently. It's likely that you won't notice this when using older apps, but for apps that depend heavily on graphics, there may be some limitations. How do I know which apps are 32-bit? You could launch every app on your Mac; in doing so, High Sierra will display the dialog referenced above the first time you launch each app, but not later.
So launching all your apps now won't help much, unless you plan to chase down their developers right away and query whether their apps will be updated. Some apps will not be able to be updated, others have already been updated. You probably won't notice when your favorite apps are updated to 64-bit, unless you read the release notes for update. You can search your Mac to find which apps are 32-bit. To do this, choose the Apple menu, then About this Mac. Click System Report, then scroll down and select Applications.
The rightmost column header is 64-bit (Intel). Click this header to sort applications. Those applications where No appears in this column are 32-bit.
One thing you'll notice is that big-ticket apps—Microsoft Office, Adobe Creative Cloud, and Apple's iWork apps—are already compatible. But you'll see a lot of applications that you probably don't know about. For example, the driver for one of my scanners shows as not being 64-bit, as you can see above, yet I don't think of it as an 'application,' since I never launch it as such. Many 32-bit applications are drivers for hardware devices. Likewise, some are from Apple, such as the DVD Player app, QuickTime Player 7, printer drivers supplied by Apple, and a number of extensions that are part of macOS.
Apple will most likely update the system elements, but will they update QuickTime Player 7, which is 'deprecated,' or DVD Player? What will happen if I run 32-bit apps? For now, nothing. But check to see if there are updates for the apps you use, especially if they are required for hardware devices, such as scanners, printers, keyboards, and other tools. You still have more than a year, so if there are apps that show up as not being 64-bit, and you don't use them often, but may still need them, launch them and check for updates. If you depend on them, contact their developers to ask if and when they're planning to update the apps.
You may find that some will become obsolete, so you'll have plenty of time to search for replacements. It's worth noting that those hardware drivers don't usually display auto-update dialogs, so you'll need to check the websites of the manufacturers and grab the latest versions of their software. This change is necessary to ensure that hardware and software work as efficiently as possible. Understanding the vague dialog that displays when you launch a 32-bit app will help you plan ahead. There's no need to worry too much now, but when macOS Mojave launches, you may find that some apps are not as fast or as efficient as you're used to. So start checking to see if there are newer versions now, or find other apps to accomplish the same tasks. Further reading:.
About Kirk McElhearn Kirk McElhearn writes about Macs, iPods, iTunes, books, music and more on his blog. He is co-host of the, The Next Track, and PhotoActive, and a regular contributor to The Mac Security Blog, TidBITS, and several other websites and publications. Kirk has written more than twenty books, including Take Control books about iTunes, LaunchBar, and Scrivener. Follow him on Twitter at. This entry was posted in and tagged,.
Bookmark the.