Known issues

These are cumulative release notes. If a release does not appear in this section, then there were no associated new known issues.

  • 1464129: FIPS erroneously getting disabled after upgrade from 9.20.0 to 10.0.1.
    Workaround: Log in to the CLI and run the FIPS command to re-enable FIPS on the system.
  • 1475000: The Default option for Sentry upgrade does not function in Sentry 10.0.1 and 10.0.0.
    Workaround: You can use the URL option for Sentry upgrade.
    For more information, see Ivanti Community.
  • 1475000: The Default option for Sentry upgrade does not function in Sentry 10.0.1 and 10.0.0.
    Workaround: You can use the URL option for Sentry upgrade.
    For more information, see Ivanti Community.
  • 1464129: FIPS erroneously getting disabled after upgrade from 9.20.0 to 10.0.1.
    Workaround: Log in to the CLI and run the FIPS command to re-enable FIPS on the system.
  • 1372552: After upgrading to Sentry 10.0.0, the Ivanti Standalone Sentry reboots for 5-7 minutes.
  • 1355732: In Ivanti Standalone Sentry, the upgrade progress bar does not show the download status in real time.
  • 1378830: The Ivanti Standalone Sentry VHD image for fresh deployment on Microsoft Azure is not available in version 10.0.0. However, Azure-based Sentry can be upgraded from 9.20.0 to 10.0.0.

  • 1375857: Ivanti Tunnel for Android continues to disconnect every two minutes after upgrading to 9.20.0 in some instances.

  • AL-16207: After an upgrade to Sentry 9.17.0, Sentry connections to some CIFS servers (likely CIFS server clusters) can fail.
  • AL-16110: Apache TFE fails to work with Sentry and throws an SSL error. Hence, a secure connection to the server also fails with self-signed and third party certificates.

  • AL-16132: Advanced Traffic Control server name rule matching fails when a port specification is included in the server name header entry for an HTTP request. Hence the default rule is reverted.

  • AL-15978: Sentry mutual authentication is not enabled automatically.
    Workaround: Reset mutual authentication or reset Sentry configuration through Sentry command line.

  • AL-15927: Sentry throws a RemoteAccessException error on synchronizing and reporting AppTunnel status data to Ivanti EPMM if the number of active entries in device cache are large. The error occurs as the request body exceeds the maximum size of SSL buffer and thus cannot buffer the message body to allow SSL renegotiation to continue.

  • AL-15791: With Sentry in DA mode, emails are not syncing with Exchange configuration.

  • AL-15774: If the UEM that the Sentry is registered is Ivanti EPMM 11.5.0.0, Ivanti EPMM attempts to initiate mutual authentication step up at 03:45 UTC as part of the daily certificate check job. This action leads the upgraded Sentry to restart at 03:45 UTC once, after upgrading Sentry to 9.15.0.
    Workaround: To avoid the post upgrade Sentry downtime at 03:45 UTC, use the following workaround to initiate the certificate exchange process with Sentry as part of Sentry 9.15.0 upgrade procedure:

    1. Upgrade to Sentry 9.15.0.

    2. Login to Ivanti EPMM admin portal and click Services > Overview.
      Verify that Sentry is reachable from Ivanti EPMM.

    3. Click Services > Sentry > Edit for the upgraded Sentry.

    4. Click Save.

    This action triggers mutual authentication between Sentry and Ivanti EPMM. With the mutual authentication change made at the core, the systemconfig.xml file should be permanently stored in the CVS repository.

  • AL-15773: If Ivanti EPMM is running in a Connected Cloud environment, Sentry fails to upgrade its connection with Ivanti EPMM to mutually authenticated and as a result Sentry cannot connect to Ivanti EPMM.
    If the version of the Ivanti EPMM is 11.5.0.0 or newer and you want to upgrade Sentry to 9.15.0, contact customer support before upgrading Sentry to 9.15.0.

  • AL-15636: In the Sentry MICS portal, 'smibios_entry_point permission denied' error is logged once every week. The error is displayed in the Alert Viewer section in Sentry MICS portal.

  • AL-15396: The KBSEARCH links are not resolving to the appropriate articles.