Ivanti Neurons Service Mapping - Release Notes V5.12 (Aug 2024)

4 min

Note: Before using Ivanti Neurons for Service Mapping post-release, you’re advised to clear or delete your browser cache. See below for procedures to update to the latest version.

What’s new

Service Mapping	New feature or enhancement
Discovery	Added support for importing assets from Microsoft Intune and Microsoft SCCM. Added support for sending email reports for the Schedule Scan Import feature. Renamed the probe from 'Deep Host Scan for Windows Devices (PowerShell)' to ‘Deep Host Scan - SSH \| SNMP \| Windows(PowerShell)'. Renamed the probe from ‘Deep Host Scan for Windows/Linux/Network Devices (WMIC)’ to ’Deep Host Scan - SSH \| SNMP \| Windows(WMIC)’. In the Vulnerability Management module, if multiple CIs are associated with the same CPE URI, all Asset IDs are now displayed, separated by commas. Added a field called "Operational Status" for Blueprint Virtual Machines when importing Azure records. Added support for scheduling imports for Azure, AWS, and Meraki. Added support for using “ip addr” as an alternative command to fetch IP addresses on Linux OS. Added support for discovering a Juniper Chassis. Implemented support to set the status of the connected agent to false if the Discovery Client goes down. Added support for ping in the PowerShell scans.
CMDB	Added support for displaying both the Add and Cancel buttons when selecting a Blueprint while adding a CI from the UI. Implemented support for flagging parent CIs as vulnerable in the BSM Map View when a child CI is vulnerable. Added support for enabling the Network view in BSM map views for all blueprints.
Integrations	Implemented support for users to delete ServiceNow Mappings. Added support for advanced search options for mapping Ivanti, Cherwell, and Jira link properties. Added a help link for the ServiceNow credentials popup. Added support to include Boolean properties in a ServiceNow copy.
Admin	Added support for users to return from the Map Property tab to the Configuration tab in Ad Configuration.
Reports	Added support for including user properties in Ad hoc Reports.
Discovery Application & Agent	Discovery Application (v1.0.4018) & Agent (v1.0.113): Enhanced the App and Agent update processes to include periodic checks and the ability to download the agent from the Discovery Server. Added support for Linux-based agents. Implemented support for users to build an agent for Windows and Linux hosts. Added support for importing credentials on the Discovery application. Added support for bulk deleting and flushing credentials on the Discovery application. Added a feature to mask the ‘Configuration Name’ value during data entry for Windows credentials type. Added support for Windows Agent scans via PowerShell probes. (Note: Requires Discovery App version 1.0.4018 or higher)

Fixes

These fixes automatically display upon upgrade and do not disrupt daily use for existing customers.

Fix	Description
Discovery	Fixed the issue where sorting the column for the resource group in the ‘Import from Azure’ module was not working correctly. Fixed the issue where the count of edited users was not updating in the Import logs after importing from AD and Azure AD. Resolved the issue where customizing columns for applied filters displayed all records instead of only the filtered ones, specifically for the AWS, Azure, and Meraki modules. Fixed the issue where the ‘Imported On’ date was not updating when importing AWS records. Fixed the issue where 'JBoss' CI records were created even though the host did not have JBoss running. Fixed the issue where some host CIs incorrectly included information from a different host. Addressed an issue with certain scans failing to update their status to Completed.
CMDB	Fixed the issue where the tabular order was not displaying correctly after deleting a CMDB record from the Details tab. Fixed an issue where the value of a Custom Date field in CI records was displayed in timestamp format. Addressed an issue with the date and time format while importing CIs. Addressed an issue where an IIS Server duplicate record was being created.
Vulnerability Management	Resolved the issue in Vulnerability Management where the total number of records displayed did not align with the pagination settings. Fixed the issue with filtering CVE data by selecting the published year from the drop-down. Resolved the application error encountered while filtering columns for CVEs in Vulnerability Management.
Integrations	Fixed the issue where property mappings in Jira mappings for certain blueprints were not displaying correctly. Resolved the filter issue in Incidents and Changes within the ‘CMDB for ServiceNow’ module. Resolved the issue where filtering the Status field on the My Request page was failing. Resolved the issue where updating condition mappings for blueprints from Ivanti and Cherwell were not applying correctly. Addressed an issue where ‘Communicates With’ relationships were failing to be copied. Resolved an issue where the CI history showed the CI was copied to Ivanti, but the record details had it as false.
Business Rule	Fixed the issue where the action type ‘Create New Record’ was not visible in the Discovery module. Added an alert for missing mandatory link properties when creating a business rule. Resolved the issue where updating the Hardware Assets business rule was removing associated configuration items from the corresponding records.
Admin	Addressed an issue where updates to a user’s display name were not being reflected in the tabular view across all modules.
Reports	Resolved an issue where the properties names for Hardware, Contract, and Vendor in Reports did not match those in the main models. Fixed a bug where duplicate reports with the same name were created when reports were scheduled.
General	Fixed the issue where the Advanced Search results did not clear previously searched values when changing operators to 'Not Empty' and 'Is Empty'. Resolved the issue where certain scheduled jobs were not being triggered as scheduled. Fixed an issue in SAML where email addresses added as claims in the Service Provider portal were not reflected in service mappings. Addressed issue related to personalized columns.
Discovery Application & Agent	Discovery Application (v1.0.4018) & Agent (v1.0.113): Fixed the issue where the agent’s ‘Last Scanned On’ date was not updating correctly. (Note: Requires Discovery App version 1.0.4018 or higher)

Required actions post-release

Post-release, follow these steps to ensure a smooth transition and to take advantage of the latest updates:

Clear or delete your browser cache before using Service Mapping after the release.

Navigate to the Admin portal > Client (Discovery) page.

Click the update icon to update to version 1.0.4018.

Note that if you’ve clicked the update icon but your application is still not updating to the latest version, restrictions on your network may be preventing the updates from downloading.

In such a case, you’ll need to download and install the most recent version of the application manually. To do so, follow these steps:

Stop the current application.

Back up the following files:

C:\Program Files\Virima Discovery Application\cat.json

C:\Program Files\Virima Discovery Application\hcm.json

C:\Program Files\Virima Discovery Application\session.txt

C:\Program Files\Virima Discovery Application\config\configuration.xml

Uninstall the application.

Delete the old application record from:

https://servicemapping-yourregion.ivanticloud.com/www_em/pages/probe/?entity=clients

Download the latest version of the application from:

https://servicemapping-yourregion.ivanticloud.com/www_em/pages/adminHome/ ?entity=adminHome

Install the latest version of the application.

Replace the backed-up files.

Under Windows Services logon, add the service account permissions for the Virima Discovery Application.

Start the application as an administrator.

Verify that all the required credentials are active in the Discovery Application Credentials section.