We performed a comparison between Device42 and ManageEngine IT Asset Management based on real PeerSpot user reviews.
Find out in this report how the two IT Asset Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The topology layout is the most valuable feature."
"The import/export for bulk operations is a valuable and good feature."
"They've also just created some new interactive dashboards. CEOs can see and interact with the data rather than scrolling through endless Excel worksheets to find what they need."
"The solution has some very good relational capabilities that show us how certain devices relate to each other and how some of our environment actually works together."
"A big plus for Device42 was the auto-discovery. With it, we have updated devices, updated systems, and up-to-date systems."
"Device42 has everything in one place and links it altogether. This helps when you need to figure out where things are going wrong, where things are happening, or how everything is linked together."
"We use the automatic IT asset discovery for different things, like VMware discovery and SNMP discovery for network devices. It helps us to keep hardware information up to date in Device42, and the VMware discovery helps us to keep virtual device inventory up to date... We are sure to have 100 percent of our devices in Device42. Not more, not less."
"The asset inventory is great because previously we had devices all over the place. We have been able to do multiscans to find devices that we didn't know about, which was great."
"The technical support is great."
"The auto-discovery feature has helped us a lot."
"In my opinion, it is the MDM; patch management and deployment are the valuable features."
"A con for Device42 is that Kubernetes integration is lacking. You pay for 10,000 spot licenses and if you're spinning up a Kubernetes cluster, or four or five or six Kubernetes clusters like we do, you're going to have 5,000 or 6,000 nodes in each of those, doing different types of business things."
"Configuring rPDUs in the data center for Device42 required us to add multiple discovery jobs. The rPDUs were referred to the ISPDUs and daisy-chained. They would automatically assign a unique SMP port, but Device42 didn't allow SMP ranges, so we had to create a discovery job for each rPDU individually. We submitted a feature request to mitigate that."
"The architecture is a bit old-fashioned. Device42 is on one server, appliance, virtual machine, or guest. We are loading more into Device42 than it can hold. Overloading Device42 with REST API calls or tasks will directly impact every aspect because the server will be too busy to answer requests."
"I would like to see API management as an additional feature in the tool's future versions. It will give more API security."
"The dependency mapping can be quite slow sometimes, if you've got a lot of things connecting to services. It can be very slow to build up the map."
"Since I was focused on deploying connectors and getting all the servers to be scanned, one of the biggest pains was when a job would fail, then the output (logging) was poor. For example, "Why did it fail?" In these cases, you get a generic error. It doesn't point you in the right direction and tell you why you got the error, which is really annoying. There have been times I asked, "Is there somewhere I can see a better log as to why is this failing?" That would be a really nice improvement."
"Currently, if you want to ping devices, you need to log into Appliance Manager. This feature should be available on the Device42 side. You should be able to use the ping utility without logging into Appliance Manager. The features that are there in Appliance Manager should also be available on the main Device42 server so that you have more control on one screen. You don't need to switch to another portal, but it is not something critical."
"The product must provide AI features."
"The asset management tool is costly."
"The engineering area needs improvement."
"The assets that can be discovered are pretty easy to manage, but there should be a better way to manage non-discoverable assets. Our development team works on bots and tests particular hardware. They have got different varieties of hardware. They want a feature for managing these assets within a warehouse kind of environment. For example, our IT has received 100 items, and they have assigned these items as a bulk unit to a project manager. The project manager further wants to distribute these items within his or her team. Instead of maintaining a separate Excel sheet, the project manager should be able to reallocate these items from within the tool so that we have hierarchical entities for the same unit."
More ManageEngine IT Asset Management Pricing and Cost Advice →
Device42 is ranked 4th in IT Asset Management with 25 reviews while ManageEngine IT Asset Management is ranked 11th in IT Asset Management with 3 reviews. Device42 is rated 8.4, while ManageEngine IT Asset Management is rated 9.4. The top reviewer of Device42 writes "Good reporting and discovery capabilities, and helpful for understanding device dependencies and asset management". On the other hand, the top reviewer of ManageEngine IT Asset Management writes "Stable and scalable solution ". Device42 is most compared with ServiceNow, ServiceNow CMDB, Infoblox IPAM and JIRA Service Management, whereas ManageEngine IT Asset Management is most compared with Lansweeper, ServiceNow, Axonius, Freshservice and Qualys VMDR. See our Device42 vs. ManageEngine IT Asset Management report.
See our list of best IT Asset Management vendors.
We monitor all IT Asset Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.