| Product Version | Availability |
| MNE - SaaS 2312 for ePO - SaaS (GA) | October 10, 2023 |
| MNE - SaaS 2306 for ePO - SaaS (GA) | June 5, 2023 |
| MNE - SaaS 2212 for ePO - SaaS (GA) | December 15, 2022 |
| MNE 2205 for MVISION ePO (GA) | May 24, 2022 |
| 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 only for trial use) |
| MNE 1910 for MVISION ePO | October 16, 2019 (released only for trial use) |
Management of Native Encryption - SaaS for ePO - SaaS Known Issues
Technical Articles ID:
KB91839
Last Modified: 2023-12-12 07:25:19 Etc/GMT
Last Modified: 2023-12-12 07:25:19 Etc/GMT
Environment
Management of Native Encryption - SaaS (MNE - SaaS) for ePO - SaaS
NOTE: MVISION MNE has been rebranded to MNE - SaaS from version 2212 onward.
NOTE: MVISION MNE has been rebranded to MNE - SaaS from version 2212 onward.
Summary
Recent updates to this article
Contents:
Click to expand the section you want to view:
Back to top
| Date | Update |
| December 12, 2023 | Added MNE - SaaS 2312 General Availability (GA) release details. |
| June 5, 2023 | Updated MNE - SaaS 2212 (GA) release details. |
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.
Contents:
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's 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's no impact on Mac systems that aren't 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 AD user to |
| General | ||||
| Reference Number |
Related Article | Found in Version |
Fixed In Version |
Issue Description |
| TKS-719 | - | 5.2.1 | 5.2.2 | Issue: A user is unable activate the default Master key when admin revokes the custom key. |
| MNE-6284 | - | 5.2.1 | 5.2.2 | Issue: Trellix products in the Task Manager hasn't been updated for only Trellix names. |
| MNE-5943 | - | 5.2.0 | 5.2.1 | Issue: MNE default deployment task can't be removed if policy and task retention are disabled. |
| MNE-5946 | - | 5.1.0 | 5.2.1 | Issue: MNE doesn't block the product removal if the applied protector is Network unlock or preboot. |
| MNE-4921 | - | 1910 | MVISION ePO Update 1 |
Issue: MNE for MVISION ePO doesn't 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. This issue is 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 isn't 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 logs 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 the encryption state when a volume transitions between an encrypted and decrypted state, or conversely after a policy enforcement. |
| 1049955 | - | - | Expected behavior |
Issue: You see the following 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 doesn't persist across system reboots. |
| 1127648 | - | 4.1 | - | Issue: If the change credential Control Panel applet isn't closed after use, it prevents subsequent activation attempts from completing successfully. |
| 1055149 | - | 4.0 | - | Issue: Hardware test failure after reboot doesn't 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 MNE is needed to report 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. But, for security reasons, they aren't stored for the volume that has been removed. So, the keys aren't available. The entry in the log shows 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 isn't an error message. It's 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're 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. The dark mode theme isn't supported with MNE. If you select dark mode when MNE is installed, it doesn't update the look of any MNE components. In dark mode, some MNE user Interface components don't 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 the recovery key might be missing. After the upgrade, it's possible that the option to enter the recovery key during user logon (the "?" symbol in the password dialog box) is missing. This issue is observed in the beta 8 build of Catalina (build 19A558D), and isn't an issue with MNE 5.0.2. The issue has been reported to Apple using the beta feedback portal. Resolution: To have this issue investigated, contact Apple. |
| - | - | 5.0.2 macOS Catalina 10.15 |
macOS issue |
Issue: Mac users are prompted for consent when MNE enables Resolution: We recommend that you 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 doesn't contain MA. |
| 1212078 | KB89819 | 4.1.2 | - | Issue: FileVault recovery isn't possible when automatic password expiration is enabled. Workaround: Make sure that the password expiration policy isn't 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 aren't displayed at the left side for the Custom message. You see this issue on |
| 1110836 | - | 5.0 | - | Issue: MNE 5.0 product details aren't displayed at the menulet on installation of MNE. You see this issue after you install either Endpoint Security for Mac 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: The 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 doesn't install on that system. |
| - | - | - | Expected behavior |
Issue: MNE successfully disables to |
| - | - | - | Expected behavior |
Issue: You're 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 performed the following actions:
The issue occurs when the screen saver is enabled on the client system, which is how the macOS is designed.
|
Back to top
Affected Products
Languages:
This article is available in the following languages:
