Ivanti Neurons for ITSM and Neurons Integration - Best Practices

intended audience administrators this topic lists out the and neurons integration steps, some common issues faced during the integration, and troubleshooting details import discovered data from ivanti neurons you can take advantage of the ivanti neurons device discovery capabilities in by importing a package from ivanti marketplace this enables you to restore existing devices in the ivanti ci/hardware assets workspace from ivanti neurons also, newly discovered ivanti neurons devices get synced to the ci > hardware assets workspace applicable only for cloud customers device data can be imported from ivanti neurons only during the synchronization process package selection for ivanti neurons device sync new and existing customers can apply the cmdb package (that is less than 1 mb) from ivanti marketplace for enabling the ivanti neurons device sync new and existing customers who are using 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 customers can apply the amc (asset management cloud) package from ivanti marketplace ivanti neurons to integration device sync only download the package (cmdb or the amc) from ivanti marketplace validate and apply the package if there are no errors on the 2020 3 upgraded tenant post package import configuration device sync only ivanti neurons to integration – device sync only log in to as administrator open the ivanti neurons asset import configuration workspace enable the device type in the ivanti neurons asset import configuration workspace ivanti neurons asset import configuration open the asset processor configuration workspace ensure that the below configurations are enabled in the asset processor configuration workspace asset processor configuration asset management capabilities log in to as asset administrator open the ivanti neurons asset import configuration workspace enable the device , invoice , software inventory type in ivanti neurons asset import configuration workspace ivanti neurons asset import configuration open the asset processor configuration workspace 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 the new ci type to the required type such as computer, database, contract so on after configuring ivanti neurons to integration, the devices should start syncing in based on the scheduled connectors post import verification device sync only log in to as an administrator open the ci workspace ensure the newly imported devices are listed under the ci workspace imported devices open the message queue journal workspace review the message queue journal workspace for the incoming device messages processed from the ivanti neurons message queue journal run the decompress message quick action for a selected message in the message queue journal workspace to view the discovered device details device details asset management capabilities log in to as asset administrator open the hardware assets workspace ensure the newly imported devices are listed under hardware assets workspace imported devices ensure the newly imported list of software is listed under the software assets workspace imported software open the message queue journal workspace review the message queue journal workspace for the incoming device, software messages processed from the ivanti neurons message queue journal run the decompress message quick action for a selected message in the message queue journal workspace to view the discovered device details device details enable the decompress message quick action by default, the decompress message quick action will be disabled for a device message to enable the decompress message quick action of the message queue journal business object, follow these steps open the configuration console > build > automation tools > quick actions click frs messagequeuejournal from the action manager list click the quick action tab on the left side panel, click decompress message click edit to open the edit expression window add device type in the quick action expression field disable in ui as shown below edit expression customizing asset data imports from ivanti neurons device filter in mapping the filter manager in in connector (ivanti neurons connector device) enables filtering inflow of device types based on the filter criteria for instance, you can select to import asset type only of laptop by creating the filter value as laptop filter manager the filter settings made during import remain saved for further import based on the filter settings, only those messages which are relevant to the mapping will be processed by the 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 a device that does not have serial number to sync from neurons the filter settings work only for a single value filter in each row if the field selected in the left panel of the mapping results in multiple values, then those filters will not work you are advised to use the filter settings accordingly for example, if you choose device bios biossettings in the root table, all the properties related to device bios biossettings will be displayed on the filter settings page when you set the filter settings as shown in the image below, then the filter will not work sample mapping scenarios use case 1 \<portable > computer> = \<ciparenttype> = \<computersystem property citype> the asset imported from the in connector having device type > portable has mapped to the parent type computer in hence, the device is imported under the category “computer ” use case 2 \<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 export and import the ivanti neurons connector you can now edit the in connector mapping and export it as a metadata package and import on other 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 have a controlled import in stg/uat, verify the imported asset, and update the mapping before importing all the assets in a prd landscape this feature is applicable only for an update scenario; a package exported from here will not create a new connection if the connector does not exist post import of the package, you are advised to review the changes once before you start syncing the devices clone and delete actions for ivanti neurons connector – device are disabled or removed ivanti neurons connector – device – only device sync ivanti neurons connector – device & invoice – asset management capabilities non device type import support you can import non computer type devices to for instance, a printer received from ivanti neurons can be imported as a printer in the tenant schedule page removal the ivanti neurons connector device schedule page is no longer an application of ivanti neurons connectors publish options removal the publish option on the ivanti neurons connector – device page is disabled this page is no longer applicable any filter and mapping changes made require you 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 configuration between ivanti neurons and ivanti neurons for itsm the to neuron data center level one time configuration is required to make sure that discovered devices messages are read by the integration service this is usually done by the cloudops team and does not require any change unless its mandated uno landscape you need to contact ivanti support to set up the connection between neurons and when you set the 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 discovery, and the increased volume degrades performance create and schedule the ivanti neurons connector for more information on scheduling the discovery to data sync by api, refer to the scheduling api data sync from ivanti neurons for discovery to ivanti neurons for itsm docid\ kb7g1jtcsohot2vshsqox scheduled connectors in ivanti neurons you can install and configure the required connector and schedule it to run for more information, refer to connectors https //help ivanti com/ht/help/en us/cloud/vnow/connectors htm connector page discovered devices in ivanti neurons post configuration in ivanti neurons, the run now button allows you to run the connector on demand the discovered devices will appear in devices page device page test ivanti neurons connector – device from ivanti neurons for itsm you can confirm if the newly created ivanti neurons connector – device test connection has succeeded this step is very important and without test connection success, devices will not sync with confirm discovery data processed by ivanti neurons for itsm the discovered device information from ivanti neurons is read by the integration service, which can be viewed in the integration queue workspace once messages are read, processing of the messages is done by the 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 if the test connection fails, it is likely a configuration issue raise a 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 what is the sequence of steps involved in on boarding cloud itsm customer to itam? a identify the current version of application you can check in the aspects workpace in the application or patch logs in admin ui can help to find out the latest content package applied 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 configuration e post configuration the device should starts synching from ivanti neurons to tenant why is the neurons data to neurons for itsm integration device sync slow? the device sync depends on few factors such as inflow of device messages from ivanti neurons to rate at which 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 solution is to raise a service ticket to support, the support team will analyze and take necessary actions how to track the delay in sync in the neurons data to neurons for itsm 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 is there an ability to force a sync or option to sync specific device? 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 is there a dashboard to see how many messages are piled for itsm to process? there is no common dashboard to view in 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/48d79312 fa8f 4dee 8db0 b1fb52ad778bhttps //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/7e1cefe4 489b 4785 8068 80520b53d149https //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 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 when a neurons tenant and itsm tenant is linked, is there a way to find (from neurons for itsm) which neurons tenant it is linked to? currently this can be viewed only from config db the only way to know is to raise sr for cloudops when configuring an import from neurons the publish and run now and the publish and test run are disabled 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 why not all devices are synched from ivanti neurons to neurons for itsm tenant (data miss match)? the missing devices in side post sync up from ivanti neurons could be due to the following reasons the device message has not reached the device message has reached to 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 can i configure single neurons tenant to more than one neurons for itsm tenants (stg/uat/prd at a time? it is not recommended to configure single neurons tenant to multiple tenant at a time as it can create data inconsistency in one can always change the configuration from stg to uat or prd at any time by raising sr with cloudops can i export & import connector from one itsm tenant to another? yes, one can export the odata connectors (ivanti neurons connector – device & ivanti neurons connector – invoice) from one 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 application to have consistent default mappings can i have multiple odata connectors like ivanti neurons connector – device or invoice? yes, but its recommended to enable only one odata connector at a time can i have multiple mappings in a single odata connector like ivanti neurons connector – device? yes, but enable only one active mapping by name device at a time and turn off other mapping what is limit for maxsize and batchsize parameters in object mapping of odata connectors? no limit for both the parameters, however its better to retain the default values if parenttype not matched as per the mapping, then will device get created? 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 can we remove both parenttype and subtype? we can remove subtype fully but one mapping is mandatory for parenttype are we updating assettype > subtype? no, we are not updating assettype as subtype if mapping does not exist when does a device get brought in? the odata connector does not trigger based on 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, integration service starts reading them in fifo order if devicetype doesn't exist in ivanti neurons or amc what happens? device will honor the asset processor configuration can both odata and neurons for itsm connectors co exists? yes can we set it up to populate devices always into ivnt unmanagedasset? yes, possible on updating assettype & subtype, will the next import from neurons change the assettype and subtype? no can we set any field for mapping fields in asset processor configuration workspace? no only constant value field can be set for mapping fields like previd, serialnumber etc … troubleshooting when performing data sync from neurons discovery to neurons for itsm, system performance is degraded resolution when you schedule the data sync, ensure that the max size is no greater than 500 for more information, refer to scheduling api data sync from ivanti neurons for discovery to ivanti neurons for itsm docid\ kb7g1jtcsohot2vshsqox when scheduling data sync from neurons discovery to neurons for itsm, preview fails 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, refer to scheduling api data sync from ivanti neurons for discovery to ivanti neurons for itsm docid\ kb7g1jtcsohot2vshsqox opening unmanaged throws error resolution create ci extended bo ivnt unmanagedasset add forms by am unmanagedasset brief open and select layout of ci (relevant) > open in grid view > add the ivnt unmanagedasset with newly created form open layout of the ci bo and select layout of ci (relevant) > open in form view > add the ivnt unmanagedasset with newly created form object reference null error resolution can be observed by multiple reasons and some of the primary reasons could be check ivanti neurons connector device test connection missing odata connection information like api path object more than one odata connections defined this can happen if customer has already created an odata connector ford device import manually before importing the cmdb turnkey package form marketplace at a time only one odata connector can be active for connection name device 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 device creation failure resolution enable the asset processor configuration missing create ci checkbox mandatory fields for creating ci missing, eg hostname, citype etc duplicate of serial number, asset tag, ci component etc connector test connection failure device type not updating resolution if the ivanti neurons does not have device type such devices will honor the asset processor configuration if connector doesn't have the mapping details for device type which present in neurons such devices will honor the asset processor configuration device field values are not populated resolution review the mapping details in the connector how to initiate the device scan on neurons agent manually? resolution run the following 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" issue where the neurons connector doesn not kick off the schedule nor does the run now option work resolution possible reason could be the same agent has been installed on multiple neurons tenants uninstall one of the agents, and other should start working custom queries 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 community article ivanti neurons troubleshooting the neurons connector utility https //forums ivanti com/s/article/ivanti cloud troubleshooting the cloud connector utility?language=en us ivanti neurons online help setting up connectors https //help ivanti com/ht/help/en us/cloud/vnow/connectors htm?cshid=1001