| Product Version | Availability |
| MNE for MVISION ePO 5.2.0 Hotfix 1 (GA) | May 27, 2021 |
| MNE 2104 for MVISION ePO (GA) | April 14, 2021 |
| MNE 2010 for MVISION ePO (GA) | October 13, 2020. |
| MNE 1910 Update 1 for MVISION ePO | November 12, 2019 (released for Trial use only) |
| MNE 1910 for MVISION ePO | October 16, 2019 (released for Trial use only) |
Management of Native Encryption for MVISION ePO Known Issues
Artigos técnicos ID:
KB91839
Última modificação: 5/27/2021
Última modificação: 5/27/2021
Ambiente
McAfee Management of Native Encryption (MNE) for MVISION ePO
Resumo
Recent updates to this article:
Click to expand the section you want to view:
Back to top
| Date | Update |
| May 27, 2021 | Added:
|
| April 16, 2021 | Added MNE 2104 for MVISION ePO release details. |
| February 9, 2021 | Added reference MNE-5904 under Critical Known Issues. |
| October 13, 2020 | Added MNE 2010 for MVISION ePO. |
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.
Click to expand the section you want to view:
| Reference Number |
Related Article | Found in Version |
Fixed in Version |
Issue Description |
| MNE-5941 | KB94582 | 5.2.0 | 5.2.0 Hotfix 1 |
Issue: Installation of MNE 5.2.0 fails while you install on Windows 10. The installer rolls back because it fails to start the
|
| MNE-5904 | - | 5.1.1 HF1 | - | Issue: FileVault Activation/Key Escrow fails on M1 chipset-based Mac systems. Reason: Apple introduced ARM-based M1 chipset in the latest Mac systems. These systems exhibit a different behavior with MNE, when compared to the Apple Silicon DTK environment that was used to validate for zero-day support. Resolution: Investigation is in progress to identify a fix. NOTE: MNE 5.1.1 HF1 is no longer available for download. There is no impact on Mac systems that are not based on the M1 chipset. |
| 1230491 | KB90380 | 4.1.3 | - | Issue: Reason: Apple has introduced a secure token on macOS High Sierra systems with Resolution: See the related article for how to add an Active Directory user to |
| General | ||||
| Reference Number |
Related Article | Found in Version |
Fixed In Version |
Issue Description |
| MNE-4921 | - | 1910 | MVISION ePO Update 1 |
Issue: MNE for MVISION ePO does not support Drive Encryption GO (DEGO) Resolution: DEGO is now disabled during policy import. |
| MNE-4959 MNE-5098 |
KB92082 | 1910 | MVISION ePO Update 1 |
Issue: You can't save the MNE policy within MVISION ePO after you edit it. Seen after you migrate an MNE system managed by an MNE 4.x administrator extension, to MVISION ePO.
Workaround: Upgrade your on-premises version of the MNE administrator extension to version 5.x before you perform the migration. See the related article for more details. |
| MNE-4958 | 1910 | Issue: When you import an MNE 4.x policy into MVISION, it selects all system authentication types under the V5 System authentication tab. | ||
| MNE-4590 | - | 1910 | - | Issue: Uninstall task is not localized and shows as |
| 1054974 | - | 3.0 | - | Issue: When two users from two separate domains have the same name, and have logged on to the same system, the system properties show only one of those users. Specifically, it shows the last domain that the user logged on to. |
| MNE-3064 | KB91243 | 5.0.0 | Expected Behavior |
Issue: Users are prompted to confirm their enhanced PIN after an upgrade to MNE 5.0 Resolution: The MNE 4.x distinguishing issue between TPM and PIN is resolved in MNE 5.0.0. But, users are needed to resupply their enhanced PIN during policy enforcement so that the correct authentication type can be configured. See the related article for more details. |
| 1048977 | - | - | Expected Behavior |
Issue: Compliance Report gives conflicting information regarding encryption state when a volume transitions between an encrypted and decrypted state, or conversely after a policy enforcement. |
| 1049955 | - | - | Expected Behavior |
Issue: The following is seen when you upgrade MNE from an earlier version to MNE 4.x: |
| Windows BitLocker | ||||
| Reference Number |
Related Article |
Found In Version |
Fixed In Version |
Issue Description |
| MNE-3582 | KB91314 | Microsoft Windows v1803 |
Issue: An MNE 5.0 user enters into an endless recovery loop on a Resolution and Workaround: See the related article. |
|
| - | - | 5.0 | - | Issue: MNE 5.0 removes |
| 1122952 | - | 4.1 | - | Issue: The postponement timer does not persist across system reboots. |
| 1127648 | - | 4.1 | - | Issue: If the change credential Control Panel applet is not closed after use, it will prevent subsequent activation attempts from completing successfully. |
| 1055149 | - | 4.0 | - | Issue: Hardware test failure after reboot does not send an audit to the ePO server. |
| 1049957 | - | 3.0 | - | Issue: Hardware test failure after a system restart fails to send an audit. |
| 964274 | - | - | Expected Behavior |
Issue: Resolution: This behavior is expected because there is a requirement that MNE reports information about all historical volumes on the system. This information Includes volumes that have been removed. Part of the information gathering process tries to query the keys. Which are not stored for security reasons, for the volume that has been removed. Thus, the keys are not available. The entry in the log is there to show that when gathering volume information, an attempt was made to get the keys for the volume. But, none is available. This entry is only a DEBUG level entry and is not an error message. It is intentionally present for removed volumes. |
| Mac OS X, macOS[FileVault] | ||||
| Reference Number |
Related Article |
Found in Version |
Fixed in Version |
Issue Description |
| - | KB92083 | 1910 | - | Issue: You are unable to migrate Mac client systems to MVISION ePO when Resolution: Remove |
| MNE-4833 | = | 1910 | - |
Issue: When an invalid
|
| - | - | 5.0 | Expected Behavior |
Issue: As of macOS Mojave 10.14 or later, the user can select between light and dark mode themes. Dark mode theme is not supported with MNE. If dark mode is selected when MNE is installed, it does not update the look of any MNE components. In dark mode, some MNE user Interface components do not render appropriately, and might make reading text on the components harder. There are no known functional issues when operating MNE with macOS in dark mode. |
| - | - | 5.0.2 macOS Catalina 10.15 |
macOS Issue |
Issue: After an upgrade from macOS Mojave 10.14 to macOS Catalina 10.15, the option to enter recovery key might be missing. After the upgrade, it is possible that the option to enter the recovery key during user logon (the “?” symbol in the password dialog box) is missing. This issue was observed in the beta 8 build of Catalina (build 19A558D), and is not an issue with MNE 5.0.2. The issue has been reported to Apple via the beta feedback portal Resolution: Customers must contact Apple to have this issue investigated. |
| - | - | 5.0.2 macOS Catalina 10.15 |
macOS Issue |
Issue: Mac users are prompted for consent when MNE enables Resolution: Users are recommended to provide consent to make sure that |
| - | - | 4.1.5 | - | Issue: MNE Workaround: Use the packaged version of MNE 4.1.5. The package can be deployed from ePO or the regular non-standalone installer of MNE, which does not contain MA. |
| 1212078 | KB89819 | 4.1.2 | - | Issue: FileVault recovery is not possible when automatic password expiration is enabled. Workaround: Make sure that the password expiration policy is not set in ePO. Apply the policy to all systems that run macOS 10.13 or later. See the related article for details. |
| 1109657 | - | 4.0 | - | Issue: The first two characters are not displayed at the left side for the Custom message. Seen on |
| 1110836 | - | 5.0 | - | Issue: MNE 5.0 product details are not displayed at the menulet on installation of MNE. Seen after either Endpoint Security for Mac (ESM) or Endpoint Protection for Mac (EPM). |
| 1055134 | - | 4.0 | - | Issue: After you disable |
| 1212353 | KB89825 | 4.1.2 | Expected Behavior |
Issue: MNE can't accept the Resolution: Sync the passwords before you try to manage |
| 1212900 | KB89834 | 4.0.0 | Expected Behavior |
Issue: MNE Mac Remote Provisioning tool requires a reboot before communication with ePO. Resolution: Restart the computer. |
| - | - | - | Expected Behavior |
Issue: MNE 4.0 co-exists only with EPM 2.3 or later. If an earlier version of EPM is installed, the MNE OS X client does not install on that system. |
| - | - | - | Expected Behavior |
Issue: MNE successfully disables To |
| - | - | - | Expected Behavior |
Issue: Unable to activate |
| - | - | Expected Behavior |
Issue: The |
|
| 910502 | - | - | Expected Behavior |
Issue: When you turn off
|
| 910511 | - | - | Expected Behavior |
Issue: A user can't log on to the client system if the ePO administrator has:
|
Back to top
Produtos afetados
Idiomas:
Este artigo está disponível nos seguintes idiomas:
English United StatesSpanish Spain
French
Italian
Portuguese Brasileiro
Glossário de termos técnicos
Realçar termos do glossário
Reserve alguns momentos para navegar por nosso Glossário de termos técnicos.
