Is there a way for Service Desk/Asset Management to determine or compare items that have been already entered manually and items imported from Management Suite? When a person enters a new item on Service Desk/Asset Management, is there a way to auto-populate the rest of the fields assuming it grabs the rest of the information from Management Suite

JohnO The Data Import is intelligent in that, given the correct primary key (obviously), it will update CI’s if mapped fields have changes. Typically the key is the machine name or the computer Idn from ldms/epm but that depends on how you want to deal with the concept of machine rebuilds/renames on the epm side so that the import subsequently doesn't incorrectly create duplicate records. For example “machine name” could work but what happens if the machine is renamed downstream as you wouldn't want 2 CI’s in the CMDB for the same box right! So then “Computer Idn” would seem the logical choice (as the internal ID number in epm right); well yes and that is what I generally use as that transcends renames or bare metal rebuilds. But beware one caveat with this latter method, it is often best practice on the epm side to upgrade epm as a side-by-side process and depending how that is done the Computer Idn can be preserved (parallel system uses copy of DB) or not (parallel system uses clean DB) and if latter you need to (usually) do a one-off import with the key set to machine name so that you get the new Computer Idn values before switchinf the key back again to as before. All of this can be worked around but the key here is for people to be aware that whenever epm/ldms is upgraded, that person considers possible downstream effects they could have on the CMDB imports whether it is to ensure both sides work together so duplicates arent created or simple that the data import data connection strings need to beupdated to point to the new core server.

All of that scaremongering aside....assets created in SD/AM but enhanced by additional data from epm is common. Obviously and mapped fields will overwrite any manually added data for the mapped fields if the data is different in epm of course.

Also using the view method for integration is more flexible and faster than the old dedicated ldms connector as well and better in support for different SD and EPM version combinations as well (as dedicated connector very picky as you’ll see in the compatibility matrix on the community). Even better is you can cleanup data via Data Analytics or in the view as well if needed; ie preferred sizes (instead of bytes) for memory and disk sizes or remove zero padded IP addresses etc.

Thank you Julian! A strange issue I just encountered was a laptop being imported as "desktop" class instead of "laptop", Under Data Import > Import Mappings > LDMS Device Import > Workstations source there is a query created to sort workstations that has no battery and the chassis type is desktop and still being imported as "desktop" class.

JohnO I think the laptop query should include Has Battery = true. Also there are probably more chassis types for laptops that might be used; “Portable” for one. Suggest you see what chassis types your “estate” thinks it has via am EPM query or querytool query on the EPM data connection.