HAM - Sync Mobile Fields with CI Class (IMEI)

[Pascal Vinke]

Good evening everyone,

we have kind of a complicated situation and I have not found the correct solution.

When using HAM Pro an additional Tab on the Hardware Asset for mobile is shown, which includes e.g the IMEI field. By default this is shown when the model category "Mobile Device" is selected. The model category links the tables "alm_hardware" and "cmdb_ci_comm_devices".

1.) When using the included Service Graph Connector for Intune all mobile devices are imported into the CI Class "cmdb_ci_handheld_computing". Therefore we need to create a new model category which leads back to the point to edit the Client Script. Otherwise we would need to edit the complete import mapping of the Service Graph Connector. But this could be resolved and works for now (ServiceNow used in the Client Script a hard coded Sys ID)

2.) Both tables (Asset and CI) have an IMEI field. But the Asset CI Field Mapping only allows the mapping of cmdb_ci attributes and alm_asset attributes. Is there a way to sync the information or do I have to import them on both tables? Usually the CI is created first and the scheduled job creates the asset but this field will not be filled. How can I solve this with minimal effort? 

[Scott Halverso1]

• In San Diego the Model Category called Mobile Device points to cmdb_ci_handheld_computing (not the old comm_devices table)
• •  By using the Mobile Device model category the hardware asset form correctly displays the mobile tab when needed
• Syncing mobile attributes to hardware from CI (or vice versa) is an issue that you'll need write your own custom syncing.  The out-of-the-box syncer only works if the attribute is defined at the base layer of alm_asset and cmdb_ci.  These new attributes like IMEI, Carrier, etc are not defined at the base layer.
• • To date I haven't written a solution for this.  I've only solution it on advance shipment notice processing by creating the asset first and then having the transform map on a on after script go update the CI with the cellular specific attributes

[Roberto Corradi]

I'd have hoped that for cases where the instance pre-dates San Diego but ITAM is being introduced post SD that there might be a "fix" for the model category at least, something simple like SN providing that updated Model Category.  Has anyone had any joy in these circumstances?  The less said about the current support ticket and responses in that ticket the better....