Added the issue with the "Does not match MVISION Console AAD" error message to the "MVISION Mobile ePO extension" section.
February 9, 2021
Updated issue MM-59 in the "MVISION Mobile ePO extension" section to include Microsoft Edge.
February 9, 2021
Added MVISION Mobile iOS App 4.16 to the "Product release information" section.
February 5, 2021
Added MVISION Mobile Android App 4.16 to the "Product release information" section.
October 9, 2020
Added issue MM-59 to the "MVISION Mobile ePO extension" section.
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.
Contents:
Click to expand the section you want to view:
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.
Issue: An error similar to the following displays when you add InTune Mobile Device Management (MDM) to MVISION Mobile:
Does not match MVISION Console AAD
Workaround: Manually provide administrator consent to the MVISION Mobile console before you add the InTune integration. See the related article for more information.
Issue: The number of connected MVISION Mobile devices in the MVISION ePO console My Subscriptions window is incorrect.
Workaround: To view the total number of connected MVISION Mobile devices:
Log on to the MVISION Mobile Console.
Click DASHBOARD.
View Total Devices on the MVISION Mobile Operational Mode tabunder Metrics.
See the related article for more information.
MM-52
-
1812
1905
Issue: Information displays on the devices and Mobile Threat log page. Information is ordered based on the updated date and last seen date. The column is sorted in ascending order and must be sorted in descending order.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1905. The latest events and device information displays in descending order.
MM-55
-
1812
1905
Issue: When the installation of the MVISION Mobile extension fails, the Orion log is not populated with the error codes.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1905.
MM-56
-
1812
1905
Issue: The Mobile Device ID in MVISION ePO does not match with the Device ID in the MVISION Mobile Console.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1905.
MM-35
-
1812
1903
Issue: Local Device Groups are not visible in ePO.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1903.
MM-48
-
1812
1903
Issue: When the size of the number increases in the MVISION Mobile Ribbon, the UI does not change.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1903.
MM-49
-
1812
1903
Issue: The displayed time for Mobile Threat events does not match with the time that the ePO administrators set.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1903.
1258930
-
-
1812
Issue: After you enter the API Key and Server Key, and click Test Connection, the response is FAILED.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1812.
1262193
-
-
1812
Issue: When you click outside a window in MVISION Mobile, the ePO Menu window appears.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1812.
1262203
-
-
1812
Issue: The Filter option is not available on the Mobile device page. You can't filter the devices.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1812.
1262206
-
-
1812
Issue: The Filter option is not available on the Mobile Threat event page. Users can't filter the Mobile Threat events.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1812.
1262199
-
-
1812
Issue: There is a data mismatch and only the last 7 days of data is shown in the MVISION Mobile Ribbon.
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1812.
Issue: A back-end release of MVISION Mobile Console 4.22 is not compatible with the previously released MVISION Mobile ePO Extensions (version 1812.01.1346 or earlier). The integration does not work and you can't take any kind of Actions on Mobile Threats and Devices. (Delete device does not work.)
Resolution: This issue is resolved in MVISION Mobile ePO Extension 1903. See the related article for more information.
1250970
-
1812
-
Issue: After a hard restart of ePO, the MVISION Mobile ePO Extension is unable to fetch events from the MVISION Mobile Console.
Workaround: Uninstall the extension and check it in again.
Critical Known Issues: There are currently no critical known issues.
Non-Critical Known Issues:
Reference Number
Related Article
Found In Version
Fixed In Version
Issue Description
7810
-
4.10.2
4.12.1
Issue: You manually install and activate the MVISION Mobile App through the QR-code or activation link on a device that has Intune Company Portal. The app then tries to get the token from the Company Portal app every time when the user starts the app.
Resolution: This issue is resolved in MVISION Mobile Android App 4.12.1.
-
-
4.9.2
-
Issue: For Chrome browser users: If you do not open the MVISION Mobile App first and click the token activation link, Chrome blocks the activation link. Chrome no longer allows starting an app from a link. But, this link does work for other browsers.
-
-
4.8.0
-
Issue: The Site Insight functionality can sometimes block access to pop-ups, even though they are valid URLs. The browser blocks access to the pop-up because pop-up URLs are only accessible in the context of a page.
Workaround: Enable Site Insight on a case-by-case basis. Select 'JUST ONCE' on the device, instead of 'ALWAYS' for Site Insight functionality.
-
-
-
4.8.0
Issue: When a network threat is detected, mitigation can have an issue if the needed condition is not met. For example, you might see this issue on Samsung Note 9 and Android 8 for Enterprise; they run as profile owner mode. The app must have the permissions needed to read the SSID or BSSID.
Resolution: This issue is resolved in MVISION Mobile Android App 4.8.0.
-
-
-
4.8.0
Issue: There is a missed alert for unsecured Wi-Fi connectivity.
Resolution: This issue is resolved in MVISION Mobile Android App 4.8.0.
Critical Known Issues: There are currently no critical known issues.
Non-Critical Known Issues:
Reference Number
Related Article
Found In Version
Fixed In Version
Issue Description
7810
-
4.10.3
4.12.0
Issue: You manually install and activate the MVISION Mobile App through the QR-code or activation link on a device that has Intune Company Portal. The app then tries to get the token from the Company Portal app every time when the user starts the app.
Resolution: This issue is resolved in MVISION Mobile iOS App 4.12.0.
Issue: For iOS users, when you select the Disable Bluetooth option in Device Action for any ThreatPolicy, Bluetooth is not disabled when the event triggers. This issue occurs with all versions of iOS.
Workaround: Use Mobile Device Management (MDM) to control Bluetooth. See the related article for more information.
-
-
4.9.2
-
Issue: Although the Sideloaded App threat is disabled in the threat policy, the Sideloaded App section in the UI still displays under the App Safety category.
-
-
4.9.2
-
Issue: Although Device PIN threat is detected and displayed correctly in the MVISION Mobile Console, the Screen Lock attribute on the Device Safety screen can display an Enabled value.
Workaround: Lock the device and then unlock the device. See the attribute while on the Device Safety screen in the MVISION Mobile App. This issue only occurs for devices running iOS operating system version 12.
-
-
4.8.0
-
Issue: There is a missed alert for unsecured Wi-Fi connectivity.
-
-
4.8.0
MVISION Mobile
Console 4.22
Issue: A Sideloaded App is detected as a threat. When it is mitigated on the device with deletion of the app, there is no alert on the server.
Resolution: This issue is resolved in MVISION Mobile Console 4.22.
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.
