Release Notes 5.12

Implemented support to set the status of the connected agent to false if the Discovery Client goes down.

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/Linux/Network Devices (WMIC)’ to ’Deep Host Scan – SSH | SNMP | Windows(WMIC)’.

Renamed the probe from ‘Deep Host Scan for Windows Devices (PowerShell)’ to ‘Deep Host Scan – SSH | SNMP | Windows(PowerShell)’.

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 Juniper Chassis.

Added support for ping in the PowerShell scans.

Fixed the issue where sorting the column for the resource group in the “Import from Azure” module was not working correctly.

Addressed an issue with certain scans was failing to update it status to completed.

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 Page 6 of 8 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

Implemented support for flagging parent CIs as vulnerable in the BSM Map View when a child CI is vulnerable.

Added support for displaying both the ‘Add’ and ‘Cancel’ buttons when selecting a Blueprint while adding a CI from the UI.

Added support for enabling the Network view in BSM map views for all blueprints.

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 the CIs.

Addressed an issue where IIS Server duplicate record was being created.

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 Service-now copy.

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 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 was not applying correctly.

Resolved an issue where the CI history showed the CI was copied to Ivanti but the record details had it as false.

Addressed an issue where “Communicates With” relationships was failing to be copied.

Implemented support to consider the email address as the username when importing an MSP user if the username is not present.

Added MFA support for MSP users.

Fixed an issue with Change password link not showing up for MSP Vendor in user details page.

Implemented support for users to build an agent for Windows and Linux hosts.

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.

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 ‘Configuration Name’ value during data entry for Windows credentials type.

Added support for Windows Agent scans via PowerShell probes

Fixed the issue where the Agent’s Last Scanned On date was not updating correctly

Added support for triggering a Runbook linked to an ITSM record for both the Associated CIs and the Root Cause CI.

Fixed the pagination issue in the Catalog Items sub-tabs.

Resolved the export functionality issue for the Knowledge model.

Fixed the page redirection issue when navigating from the Stockroom to the Hardware sub-tab.

Resolved the error encountered when adding a new comment to a knowledge article in the end-user portal

Fixed an issue of duplicate ‘State property’ appearing in the personalized columns of the Procurement module.

Resolved the issue where PO Line Items property values were not being imported with hardware assets

Added previously omitted properties such as change plan, back-out plan, test plan, and approval notes to the personalized columns for the Change module.

Fixed an error encountered during bulk editing of Link Properties in the Hardware Assets module.

Resolved the issue with dissociating a department from the user page.

Fixed the issue related to hiding and showing records in the Vendor sub-tabs.

Added support for users to return from the map property tab to the configuration tab in Ad Configuration.

Addressed an issue where updates to a user’s display name were not being reflected in the tabular view across all modules.

Added support for including user properties in Ad hoc 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.

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 dropdown.

Resolved the application error encountered while filtering columns for CVEs in Vulnerability Management.

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 hardware assets business rule was removing associated configuration items from the corresponding records.

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 Virima.

Addressed issue related to personalized columns.

User Advisory: Clear/Delete Browser Cache before using Virima for this release.

1. Virima Admins must ensure the latest Discovery Application client is installed and updated to the latest version. Instructions for the same are provided below.
2. Click on Client icon in your Discovery App to update to the latest version 1.0.4018
   (Please note that if you have clicked the update button but your application is still not updating, restrictions on your network may be preventing the updates. You can download and install the most recent application version in such a case.)
3. To manually update the application, please follow the below steps:
   1. Stop the current application.
   2. Backup 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,’ and ‘C:\Program Files\Virima Discovery Application\config\configuration.xml.’
   3. Uninstall the application.
   4. Delete the old application record from https://login-yourregion.virima.com/www_em/pages/probe/?entity=clients.
   5. Download the latest version of the application from https://login-yourregion.virima.com/www_em/pages/adminHome/?entity=adminHome.
   6. Install the latest version of the application.
   7. Replace the backed-up files.
   8. Under Windows Services log-on, please add the service account permissions for the Virima Discovery Application.
   9. Start the application as an administrator.
   10. Verify that all the required credentials are active in the discovery application credential section.