---
title: Ivanti EPMM 12.7.0.0 - Resolved issues
slug: epmm/release-upgrade-guide/ivanti-epmm-12700-resolved-issues
createdAt: 2026-10-27T04:46:04.612Z
---

- **1687362**: Previously, the custom variables included in the Android Managed App configuration was set to null, regardless of the assigned values. This issue is now fixed.
- **1675573**: Previously, the EPMM admin portal would not start after upgrading to EPMM 12.6.0.0 if the number of available processors are more than 20. This issue is now fixed.
- **1641329**: The installation request from NAC now converts the un-managed app to managed app.
- **1624620**: Previously, EPMM was not showing the supported languages in EPMM templates. This issue is now fixed.
- **1620364**: Tunnel for iOS is now detecting VPN configuration even when EPMM is using non-English language.
- **1612042**: The issue with Splunk permissions inconsistency is now fixed.
- **1603095**: Previously, EPMM was generating DEP certificate in .CRT format instead of .PEM format. This issue is now fixed.
- **1600669**: Previously, the macOS Script configuration would fail with HTTP 401 unauthorized error. This issue is now fixed.
- **1599886**: Previously, when there were no updates available the In-house apps were getting re-installed when the "**Send request for Updates**" option was selected.
- **1586643**: Starting from EPMM 12.4.0.0, the status of migrator service in the **System Manager **portal was displayed as **Not Running** even though it was enabled. This issue is fixed now.
- **1565536**: Previously, the API query validation "**/api/v2/devices/query\_test**" used to verify the queries would provide a valid result even though the used field was incorrect. This issue has been fixed.
- **1350536**: In the **LDAP setting > Custom Attributes** section, the user-interface text is now corrected for clarity regarding custom attributes usage:
  - Previously, the description in user-interface mentioned about only custom1 to custom10, though it is applicable for custom1 to custom20 attributes. This is now fixed.
  - In **Advanced Search** or **Creating Labels**, you can use the custom1 to custom4 attributes as; custom1, custom2 or with actual values. Whereas, starting from custom5 onwards you can only use with values.