Known issues

For known issues found in previous releases, see the "Known issues" section in the release notes for those releases.

This release includes the following known issues.

  • VSP-65009: There is an issue when Federal Information Processing Standards (FIPS) is enabled or disabled in Core, which prevents the Apache Tomcat web container from starting.
    Workaround: Contact Ivanti support for information about this workaround.

  • VSP-64962: There is an issue with macOS devices during iReg or DEP enrollment, in which the FileVault policy is not successfully pushed to the devices. Enrollment succeeds, but device encryption cannot be enabled.
    Workaround: A database trigger is available from Ivanti Customer Support for those users who need device encryption.

  • VSP-64912: There is an issue when the Core Admin portal is configured to access port 8443, the self-service user portal text is misaligned due to a stylesheet issue.
    Workaround: Use port 443 to access the Core Admin portal. For more information, see the chapter "Pre-deployment tasks" in the On-Premise Installation Guide for Core and Enterprise Connector.

  • VSP-64868: There is an issue where an iPad image displays on the Self-service portal instead of an iPhone, when the phone number is not present.

  • VSP-64835: There is an issue where Core continues to hold the Integrated Circuit Card Identification Number (ICCID) of a device in memory, even after the SIM card is removed.

  • VSP-64820: There is an issue with iPad devices failing iReg registration when the Apple Safari browser is in Mobile mode.

  • VSP-64796: There is an issue where the host "pcs.mobileiron.com" must be whitelisted for Core outbound connections when the Azure device compliance feature is enabled.

  • VSP-64669: There is an issue where, when a managed configuration is added to a device and a label is applied, if the app configuration is saved as the lowest priority configuration, the label does not display in the Admin portal > App Configuration table as having been correctly applied, and instead the field is blank.

  • VSP-64191: The Lightweight Directory Access Protocol (LDAP) Sync function cannot import more than 1000 organizational unit (OU) objects. The LDAP server allows only 1000 entries per search request. This value is controlled by the LDAP server attribute MaxPageSize. As a result, sometimes not all OU objects will display on the LDAP management page.
    Workaround: Configure the LDAP server attribute MaxPageSize to a value higher than 1000 OUs.