Ivanti Neurons for ITSM and Neurons Integration - Best Practices

This topic lists out the Ivanti Neurons for ITSM and Ivanti Neurons integration steps, some common issues faced during the integration along with troubleshooting details.

Intended Audience: Administrators

Import Discovered Data from Ivanti Neurons

You can take advantage of the Ivanti Neurons device discovery capabilities in ITSM by importing the package from Ivanti Marketplace. This enables ITSM customers to restore the existing devices in the Ivanti Neurons for ITSM CI/Hardware Assets workspace from Ivanti Neurons. Also newly discovered Ivanti Neurons devices gets synced to Ivanti Neurons for ITSM CI/Hardware Assets workspace.

Applicable only for cloud customers. Device data can be imported from Ivanti Neurons only during the synchronization process.

For Ivanti Neurons Device Sync

•New and existing Neurons for ITSM customers can apply the CMDB package (that is less than 1 MB) from Ivanti Market place for enabling the Ivanti Neurons Device Sync.

•New and existing customers who are Neurons for ITSM version 2020.3 or later can apply the Ivanti Neurons integration package from the Ivanti Marketplace for enabling the Ivanti Neurons Device Sync.

For Complete Asset Management Capabilities

New and existing Neurons for ITSM customers can apply the AMC (Asset Management Cloud) package from Ivanti Marketplace.

Ivanti Neurons to Neurons for ITSM Integration - Device Sync Only

1. Download the package (CMDB or the AMC) from Ivanti Marketplace.

2.Validate and apply the package if there are no errors on the Neurons for ITSM 2020.3 upgraded tenant.

Ivanti Neurons to Neurons for ITSM Integration – Device Sync only.

1.Log in to Ivanti Neurons for ITSM as Administrator.

2.Open the Ivanti Neurons Asset Import Configuration workspace.

3.Enable device type in the Ivanti Neurons Asset Import Configuration workspace.

Ivanti Neurons Asset Import Configuration

4.Open the Asset Processor Configuration workspace.

5.Ensure that the below configurations are enabled in the Asset Processor Configuration workspace.

Asset Processor Configuration

1.Log in to Ivanti Neurons for ITSM as Asset Administrator.

2.Open the Ivanti Neurons Asset Import Configuration workspace.

3.Enable the Device, Invoice, Software Inventory type in Ivanti Neurons Asset Import Configuration workspace as Asset Administrator.

Ivanti Neurons Asset Import Configuration

4.Open the Asset Processor Configuration workspace.

5.Ensure that the below configurations are enabled in the Asset Processor Configuration workspace.

Asset Processor Configuration

• New CI Type will be set to ivnt_UnmanagedAsset for Windows by default. You can update New CI Type to the required type such as Computer, Database, or Contract so on.

• After configuring Ivanti Neurons to Neurons for ITSM Integration, the devices should start syncing in Neurons for ITSM based on the scheduled connectors.

1.Log in to Ivanti Neurons for ITSM as an Administrator.

2.Open the CI workspace.

3.Ensure the newly imported devices are listed under CI workspace.

Imported Devices

4.Open the Message Queue Journal workspace.

5.Review the Message Queue Journal workspace for the incoming device messages processed from the Ivanti Neurons.

Message Queue Journal

6.Run the Decompress Message Quick Action for a selected message in the Message Queue Journal workspace to view the discovered Device details.

Device Details

1.Log in to Ivanti Neurons for ITSM as Asset Administrator.

2.Open the Hardware Assets workspace.

3.Ensure the newly imported devices are listed under Hardware Assets workspace.

Imported Devices

4.Ensure the newly imported list of software is listed under the Software Assets workspace.

Imported Software

5.Open the Message Queue Journal workspace.

6.Review the Message Queue Journal workspace for the incoming device, software messages processed from the Ivanti Neurons.

Message Queue Journal

7.Run the Decompress Message Quick Action for a selected message in the Message Queue Journal workspace to view the discovered Device details.

Device Details

By default, the Decompress Message Quick Action will be disabled for device message. To enable the Decompress Message Quick Action of Message Queue Journal business object, follow the below steps:

1.Open the Configuration console > Build > Automation Tools > Quick Actions.

2.Click Frs_MessageQueueJournal from the Action Manager list.

3.Click Quick Action tab.

4.On the left side panel, click Decompress Message.

5.Click Edit to open the Edit Expression window.

6.Add Device type in Quick Action expression field Disable in UI as shown in below image.

Edit Expression

The Filter Manager in IN connector (Ivanti Neurons Connector- Device) enables filtering inflow of device types based on the filter criteria. For instance, an Administrator can select to import Asset Type only of Laptop by creating the filter value as Laptop.

Filter Manager

•The filter settings made during import remains saved for further import.

•Based on the filter settings, only those messages which are relevant to mapping will be processed by Ivanti Neurons for ITSM tenant and rest of the messages will be discarded.

•To filter out null parameters, use the NotEqual operator instead of NoContain . For example, when filtering device which does not have serial number to sync from Neurons.

•The filter settings works only for single value filter in each row. If the field selected in the left panel of the mapping results multiple values, then those filters will not work. It advised to use the filter settings accordingly.

For example, if you choose Device.BIOS.BIOSSettings in root table and all the properties related to Device.BIOS.BIOSSettings will be displayed on Filter settings page.

When you set the filter settings as shown in the images below, then the filter will not work.

In the below screenshot, for mapping

<Portable > Computer> = <CIParentType> = <ComputerSystem.Property.CIType>

The asset imported from IN connector having Device.Type > Portable has mapped to parent type Computer in Neurons for ITSM and hence, device is imported under category “Computer”.

<Laptop > Computer> = <CIParentType> = <ComputerSystem.Property.CIType>

If the required mapping does not exist for Laptop as shown in the image below, then the device type Laptop will be moved to the default setting in the Asset Processor Configuration workspace.

Use case 3 If the CIParentType mapping is not defined in the IN connector field Mapping section, then default setting mentioned in Asset Processor Configuration workspace will be considered.

An Administrator can now edit the mapping in IN Connector and export it as metadata package and import on other Ivanti Neurons for ITSM tenants on demand. The exported connector will include the default Table selection, Filter option, and Field Mapping changes.

This functionality is intended to help the Asset Administrator to have controlled import in STG/UAT, verify the imported asset, and update the mapping before imported all the assets in PRD landscape.

•This feature is applicable only for Update scenario, package exported from here will not create a new connection if connector does not exist.

•Post Import the package, you are advised to review the changes once before start syncing the devices.

•Clone and delete actions for Ivanti Neurons Connector – Device is disabled or removed.

Ivanti Neurons Connector – Device – Only Device Sync

Ivanti Neurons Connector – Device & Invoice – Asset Management Capabilities

The Administrator can import non-computer type devices to Neurons for ITSM. For instance, the Printer received from Ivanti Neurons can be imported as Printer in Ivanti Neurons for ITSM tenant.

The Ivanti Neurons Connector - Device Schedule page is no longer an application of Ivanti Neurons connectors.

The publish option on the Ivanti Neurons Connector – Device page is disabled. This page is no longer applicable.

Any filter and mapping changes made, requires the Admin to save the changes using the Publish action and it is the only action required before synching the devices from Ivanti Neurons.

The schedule part is applicable only on Ivanti Neurons Connectors as the device messages are directly processed from Ivanti Neurons Discovery.

The Neurons for ITSM to Ivanti Neuron Data center level one time configuration is required to make sure that discovered devices messages are read by the ITSM integration service. This is usually done by CloudOps team and does not require any change unless its mandated.

Uno Landscape

•You need to contact Ivanti Support to setup the connection between Neurons and Neurons for ITSM.

•When you set the Neurons connector synchronization frequency, set it to synchronize weekly instead of daily. Daily synchronization sends a high volume of asset messages to the Ivanti Asset Manager for Neurons Discovery, and the increased volume degrades performance.

For detailed help scheduling the Neurons Discovery to Neurons for ITSM data sync by API, see the Scheduling API Data Sync from Ivanti Neurons for Discovery to Ivanti Neurons for ITSM help document.

Ivanti Neurons administrator can install and configure required connectors and schedule it to run, for more information, see Connectors.

Connector Page

Post configuration in Ivanti Neurons, Run Now action button allows to run the connector on-demand and discovered devices will appear in Devices page.

Device Page

Administrator can confirm a newly created Ivanti Neurons Connector – Device Test connection succeeds. This step is very important and without Test Connection success, the device does not sync with Neurons for ITSM.

The discovered device information from Ivanti Neurons are read by the Neurons for ITSM integration service which can be viewed in “Integration queue”. Once messages are read, processing of messages is done by message queue service which can be viewed in the Message Queue Journal workspace.

You can manage the devices which are created as part of Ivanti Neurons discovery along with existing devices in the CI workspace as an administrator.

If Test Connection fails, its likely a configuration issue, raise Service Request to CloudOps to rectify.

Integration Queue

 

Message Queue Journal

 

CI Page

 

Hardware Assets

Ivanti Neurons messages processing history data is not populated in Integration History workspace.

FAQs

a. Identify the current version of Neurons for ITSM application. You can check in the Aspects workpace in the Neurons for ITSM application or Patch logs in admin UI can help to find out the latest content package applied.

Ivanti Neurons for ITSM Version – Marketplace drop#

•201813 - Drop#13

•201902 - Drop#15

•201903 - Drop#16

•201904 - Drop#17

•201905 - Drop#18

•201906 - Drop#19

•202001 - Drop#20

•202002 - Drop#21

•202003 - Drop#22

•202004 - drop#23

b. Apply the right AMC package & apply.
c. Configure the post asset management configuration – Asset Processor Configuration and Ivanti Neurons Asset import Configuration.
d. Initiate a Service request for CloudOPS teams for Ivanti Neurons to Neurons for ITSM configuration.
e. Post configuration the device should starts synching from Ivanti Neurons to Neurons for ITSM tenant.

The device sync depends on few factors such as:

•Inflow of device messages from Ivanti Neurons to Neurons for ITSM.

•Rate at which Neurons for ITSM can read the device messages from Ivanti Neurons. Currently we are facing some technical challenges in terms of device processing rate and creating/updating asset in real time.

The immediate solution can be looking at the Azure Service Bus message count and then restart integration service to speed up processing.

The MessageQueueJournal workspace will display the latest received device message along with software messages. One can make out the device processed vs the device processing failed. The dashboard will be added to have details on how many device messages received, how many failed etc.

This feature is not available. The messages are read in FIFO order and hence the more recent scan device message takes longer time to sync in Neurons for ITSM.

There is no common dashboard to view in Neurons for ITSM application. However, the following Azure dashboards are being used for debugging purpose:

•https://portal.azure.com/#@ivanticloud0.onmicrosoft.com/dashboard/arm/subscriptions/ce2d1113-70c5-4301-ac59-e53efc23bca3/resourcegroups/dashboards/providers/microsoft.portal/dashboards/48d79312-fa8f-4dee-8db0-b1fb52ad778b

•https://portal.azure.com/#@ivanticloud0.onmicrosoft.com/dashboard/arm/subscriptions/ce2d1113-70c5-4301-ac59-e53efc23bca3/resourcegroups/dashboards/providers/microsoft.portal/dashboards/7e1cefe4-489b-4785-8068-80520b53d149

•https://portal.azure.com/#@ivanticloud0.onmicrosoft.com/dashboard/arm/subscriptions/ce2d1113-70c5-4301-ac59-e53efc23bca3/resourcegroups/dashboards/providers/microsoft.portal/dashboards/003058ac-cb7d-44e7-9093-df270a32d0a6

Currently this can be viewed only from Config DB. The only way to know is to raise SR for CloudOps.

These buttons are made disabled as their functionalities are not required. The data is directly read by integration service from Ivanti Neurons service bus.

If any change done in OData connector one has to perform publish action to save the change. Else connector might get disabled.

The missing devices in Neurons for ITSM side post sync up from Ivanti Neurons could be due to the following reasons:

•The device message has not reached Neurons for ITSM.

•The device message has reached to Neurons for ITSM but not processed successfully due to missing information.

In any of the cases, we need to look at the issue individual basis. Please reach out support for assistance.

It is not recommended to configure single Neurons tenant to multiple Neurons for ITSM tenant at a time as it can create data inconsistency in Neurons for ITSM. One can always change the configuration from STG to UAT or PRD at any time by raising SR with CloudOPs.

Yes, one can export the OData connectors (Ivanti Neurons Connector – Device & Ivanti Neurons Connector – Invoice) from one Neurons for ITSM tenant to another tenant. Please make sure you have taken back up before importing can would overwrite the customer mapping. Also export and import should be on same version of Neurons for ITSM application to have consistent default mappings.

Yes, but its recommended to enable only one OData connector at a time.

Yes, but enable only one active mapping by name Device at a time and turn off other mapping.

No limit for both the parameters, however its better to retain the default values.

•2020.2 - Device will be moved to ivnt_UnmanagedAsset

•2020.3 - Device will honor the Asset Processor Configuration

•2020.4 - Device will override the mapping details based on Asset Processor checkbox.

We can remove SubType fully but one mapping is mandatory for ParentType.

No, we are not updating AssetType as subtype if mapping does not exist.

The OData connector does not trigger based on Neurons for ITSM scheduler it always works based on the discovered devices available in Ivanti Neurons. As soon as device messages are available in Ivanti Neurons Service bus, Neurons for ITSM Integration service starts reading them in FIFO order.

Device will honor the Asset Processor Configuration

Yes.

Yes, Possible.

No.

No. Only constant value field can be set for Mapping Fields like PrevId, SerialNumber etc ….

Toubleshooting

Resolution:

When you schedule the data sync, ensure that the max size is no greater than 500. For more information, see Scheduling API Data Sync from Ivanti Neurons for Discovery to Ivanti Neurons for ITSM.

Resolution:

Verify that the download is no greater than 20 MB. Sync packages that are larger than 20 MB will cause the preview to fail. For more information, see Scheduling API Data Sync from Ivanti Neurons for Discovery to Ivanti Neurons for ITSM.

Resolution:

1.Create CI extended BO ivnt_UnmanagedAsset

2.Add forms by AM.UnmanagedAsset.Brief

3.Open and select Layout of CI (relevant) > Open in Grid view > Add the ivnt_UnmanagedAsset with newly created form.

4.Open Layout of the CI BO and select Layout of CI (relevant) > Open in Form view > Add the ivnt_UnmanagedAsset with newly created form.

Resolution:

Can be observed by multiple reasons and some of the primary reasons could be:

1.Check Ivanti Neurons Connector - Device Test Connection.

2. Missing OData Connection information like API path Object.

3.More than one OData Connections defined: This can happen if customer has already created an OData Connector ford Device import manually before importing the Neurons for ITSM CMDB Turnkey package form Marketplace.

At a time only one OData Connector can be active for connection name Device.

4.Ivanti Neurons Connector-Device type is disabled in Connector page. It’s advised to create the default naming as Device if your using multiple mappings.

Resolution:

1.Enable the Asset Processor Configuration Missing Create CI checkbox.

2.Mandatory fields for creating CI missing, eg: Hostname, CIType etc.

3.Duplicate of Serial Number, Asset Tag, CI Component etc.

4.Connector Test Connection failure.

Resolution:

1.If the Ivanti Neurons does not have Device Type such devices will honor the Asset Processor Configuration.

2.If Connector doesn't have the mapping details for Device Type which present in Neurons such devices will honor the Asset Processor Configuration.

Resolution:

Review the mapping details in the connector.

Resolution:

Run the below command in selected devices' console in the Neurons page:

Start-Process -WorkingDirectory "C:\Program Files\Ivanti\Ivanti Cloud Agent\UNO.INVENTORY.ENGINE64" -FilePath "C:\Program Files\Ivanti\Ivanti Cloud Agent\UNO.INVENTORY.ENGINE64\Inventory.Engine.exe"

The below command can list scanned items on the console itself:

Get-ChildItem -Path "C:\Program Files\Ivanti\Ivanti Cloud Agent\UNO.INVENTORY.ENGINE64"

Resolution:

Possible reason could be the same agent is been installed on multiple Neurons tenant. Remove one of agent by uninstall and other should start working.

•Ivanti Neurons Discovery Device Data:

customEvents

| extend itemType = iif(itemType == 'customEvent',itemType,"")

| extend customEvent_name = iif(itemType == 'customEvent',name,'')

| where itemType == 'customEvent'

| where customEvent_name == 'Discovery.InventoryEventHandler.InventoryEventReceived'

| summarize count() by tostring(customDimensions.TenantId)

| where customDimensions_TenantId == "UNO_TenantID"

•Ivanti Neurons Discovery Software Data:

customEvents

| extend itemType = iif(itemType == 'customEvent',itemType,"")

| extend customEvent_name = iif(itemType == 'customEvent',name,'')

| where itemType == 'customEvent'

| where customEvent_name == 'Discovery.InventoryEventV2Handler.InventoryEventReceived'

| summarize count() by tostring(customDimensions.TenantId)

| where customDimensions_TenantId == " UNO_TenantID "

•Sync Service Device Processed:

customEvents

| extend itemType = iif(itemType == 'customEvent',itemType,"")

| extend customEvent_name = iif(itemType == 'customEvent',name,'')

| where itemType == 'customEvent'

| where customEvent_name == 'SyncApp.InventoryEventHandler.InventoryEventProcessed'

| summarize count() by tostring(customDimensions.TenantId)

| where customDimensions_TenantId == " UNO_TenantID "

•Sync Service Software Processed:

customEvents

| extend itemType = iif(itemType == 'customEvent',itemType,"")

| extend customEvent_name = iif(itemType == 'customEvent',name,'')

| where itemType == 'customEvent'

| where customEvent_name == 'SyncApp.InventoryEventV2Handler.InventoryEventReceived'

| summarize count() by tostring(customDimensions.TenantId)

| where customDimensions_TenantId == " UNO_TenantID "

References

Ivanti Neurons: Troubleshooting The Neurons Connector Utility

Setting up connectors (ivanti.com)