---
title: Ivanti EPMM 12.1.0.0 - Resolved issues
slug: epmm/release-upgrade-guide/ivanti-epmm-12100-resolved-issues
createdAt: 2026-10-27T04:45:01.678Z
---

- **VSP-70613**: Previously, Ivanti EPMM did not display the latest iOS version to be updated. This issue is now fixed.
- **VSP-70984**: Previously, some configurations such as fonts had an internal version parameter associated with them and were not removed from devices.
  This issue is now fixed.
- **VSP-71013**: Previously, device details from Wi-Fi MAC was unable to be retrieved.
  This issue is now fixed.
- **VSP-71039**: Previously, EPMM sent retire commands to Enhanced Profile Owner (EPO) mode devices for RSN difference.
  This issue is now fixed.
- **VSP-71112**: Previously, deleting retired macOS devices failed.
  This issue is now fixed.
- **VSP-71152**: Previously, removing or disabling a critical internal system account, such as misystem, caused major startup problems.
  This is now fixed. Such accounts cannot be disabled now.
- **VSP-71290**: Previously, Android devices could not be re-registered if the devices were registered through bulk enrollment earlier.
  This issue is now fixed.
- **VSP-71335**: Previously, when adding an Android device, the username was not provided in the registration instructions.
  This issue is now fixed.
- **VSP-71344**: Previously, during iOS device registration, EPMM added duplicate requests that caused repush of configurations multiple times.
  This issue is now fixed.
- **VSP-71399**: Previously, the text in the iOS restriction configuration did not have the comment that "Allow iCloud Documents & Data" is only available for supervised devices.
  This issue is now fixed.
  The configuration now displays a text to "Allow iCloud Documents & Data (iOS 13 or later with Supervised devices only)".
- **VSP-71417**: Previously, the Splunk indexing configuration was not compatible with Splunk' documentation with regards to resource specifications.
  This issue is now fixed.
- **VSP-71621**: Previously, when an application was reimported or updated automatically, the global app policy setting was reset. This issue is now fixed.