Some folks on our DR Disaster Recovery team want to work with a vendor to implement Service Mapping by using Device42. The vendor *claims* D42 can do Service Mapping with very little intervention or input from our application teams - I'm highly skeptical of their claims.
From what I've read about D42, it's clientless, uses a credential, very similar to ServiceNow Discovery.
I've seen the relationship mappings that Discovery builds and maintains, and while we've tried Service Mapping, we found that the ML option not very useful and obtaining "Entry Points" from our application teams has been challenging, along with getting then to review the results.
The vendor using D42 claims they can easily map applications to hardware, but based on my experience with ServiceNow's Mapping tool, I'm very skeptical.
Does anyone on here have actual experience with implementing Device42 for Service Mapping (i.e., linking hardware relationships to applications)? If yes, please post your opinions on the output produced and level of effort required. Also, were you able to ingest anything produced by D42 into ServiceNow?
I did ask for a demo or actual results, but to date, have not received anything.
Thanks!
