Actually I see you select via the "Show All Tables" checkbox BUT it doesn't show these in the list if you reopen which is a tad non-intuitive.
How did you get TCP address mapped as it is not one of the source mapping tables.
You have to check the box "Show All Tables" then hold down Ctrl and select all of the tables to include in the mapping including the TCP table to get the IP Address.
When you come back into the mapping it only shows the default set of tables and not all the tables you have selected unless you check the box "Show All Tables" again.
Would be nice if you added tables that it would show up in the list but it doesn't.
Yeah discovered that after a few attempts.
Is it possibile to import other objects aside from computer? (scanner, monitor etc...)
is LDMSPrimaryOwner a custom field?
Has anyone had success with importing Printers or un-managed devices in general?
Thank you for posting this - really helpful.
My question is: how did you determine which fields to use on the Service Manager side? My understanding is that these exist in the Discovery side of ISM, and are 'translated' to the actual CI fields during the import. I can't find any information that shows how the Discovery and HEATSM fields relate, or any listing of the Discovery fields.
1 of 1 people found this helpful
Can someone from Ivanti answer the questions in this thread? I really need to understand more about how this works.
1. How to import devices from the Data Analytics side of IEM (printers, etc.)?
2. How do Discovery fields map to CI fields? (Why can't we just map to the CI fields?)
4. Does the order of the field mapping matter (is it processed sequentially)? If so, what are the rules?
5. How to handle when the IEM agent is reinstalled on a device (such as after a reimage)? When they get a new agent, they get a new ID - if that is the unique identifier (not the device name), how can ISM know to update an existing record rather than add a new one?
6. When a device is remove from inventory in IEM, can the integration remove it from ISM?
I may have found at least part of the answer to my 2nd question: how do Discovery fields map to CI fields.
In the Asset Data Mapping workspace, you can see asset maps - for example, for CI#Workstation. When you open that, there is a Field Mappings tab that shows the XML property for the CI fields. These don't always match exactly to what you see in the field mapping in the Integration, but close enough to get started.
It would be really nice if we could just map the integration to the CI fields, rather than have to go through the Discovery XML fields.