Resolved issues

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

  • 1865502: Fixed an LDAP synchronization issue between Active Directory (AD), Ivanti Cloud Connector, and Ivanti Neurons for MDM. Although Ivanti Cloud Connector received the correct user details from AD, it returned incorrect data to Ivanti Neurons for MDM. As a result, Ivanti Neurons for MDM continued to display users as group members after AD removed them from the group. Ivanti Cloud Connector now synchronizes group membership correctly, and Ivanti Neurons for MDM reflects the updated information from AD.

  • 1726115:The Ivanti Cloud Connector CLI now correctly displays the hostname when you run the show hostname command.

  • 1725788: Connector R100.0.0.35 did not use the configured internal DNS servers when both DHCP and manual DNS settings were configured. Instead, the AWS-assigned DNS server was set as the primary DNS server. This issue is resolved, and the searchserver value now correctly updates /etc/resolv.conf.

  • 1721632: Ivanti Neurons for MDM now correctly updates LDAP group user information during LDAP sync. When an administrator adds or removes a user from a group in Active Directory, Ivanti Neurons for MDM reflects the membership change during the next LDAP sync.

  • 1564040: Resolved an issue where the AWS internal DNS server took priority over manually configured DNS servers when DHCP was enabled. Manually configured DNS servers now take priority over the AWS internal DNS server.

  • 1548827: Previously, the Netmask defaulted to /23 regardless of the user's input during network configuration in Ivanti Cloud Connector. This issue is fixed now. The Netmask can be set based on the value provided by the user during initial setup. Additionally, after upgrading the system, you can configure the Netmask through the configuration shell. For users who are already encountering the Netmask issue, administrators need to update the required Netmask using Clish > Configure Terminal. For example, execute the command netmask 255.255.255.0.

  • 1573415: The Ivanti Cloud Connector failed to start the Splunk services and exited with an error. This issue is fixed now. To enable Splunk using Clish > Configure Terminal, for example, execute the command splunk server logserver.com:9997.

  • 1564040: Previously, while configuring the network using DHCP with manually specified DNS servers, the internal AWS DNS server was given priority, making the manually configured DNS servers unreachable. This issue is fixed now by prioritizing manually configured DNS servers over the AWS internal DNS server.

  • AW-70957: Starting with this release, the error notifications will now display for Connector registration failures from CLI.

  • AW-72930: The generation of the Windows Config Identity Certificate issue is resolved in this version of Ivanti Neurons for MDM Connector.

  • AW-59527: The Ivanti Neurons for MDM Connector now registers on-premises certificates with its internal certificate service, which no longer causes on-premises certificate revocation failure.
  • AW-62875: Starting with this release, the Ivanti Neurons for MDM Connector validates all the certificates strictly.
  • AW-61300: Ivanti Neurons for MDM Connector can import PKCS12 file packages created with OpenSSL 3.0 or higher.