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."Previously, our company had a lot of issues keeping track of all the data centers and the inventory, as well as the purchase orders. All of these were managed by other tools. The good thing about Device42 is that it can be used for all this together. We don't need to spend time checking many other tools and files."
"The solution is agentless."
"The topology layout is the most valuable feature."
"The reporting part is valuable. You have classic reports, and you can also do advanced reporting. They also have the DOQL feature for queries. You can write SQL queries to get your data and create custom reports."
"The most valuable part is the ease of use. There's no training involved. It's pretty simple and straightforward."
"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."
"A big plus for Device42 was the auto-discovery. With it, we have updated devices, updated systems, and up-to-date systems."
"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 auto-discovery feature has helped us a lot."
"The technical support is great."
"In my opinion, it is the MDM; patch management and deployment are the valuable features."
"The breadth and depth of the solution's discovery of IT asset information means the system does most of the work, but they need to work on improving the database discovery part, especially for Oracle Exadata."
"I would like to see API management as an additional feature in the tool's future versions. It will give more API security."
"Mapping items wasn't as intuitive as importing in Device42, so this is an area for improvement."
"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."
"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."
"Device42 is a main part of our processes. We need reliability, not only in terms of the data but with the solution itself. It's really difficult when we have 10 minutes of Device42 downtime because none of our teams can work for those 10 minutes, and it's more time lost if there is longer downtime. An improvement would be to have a cluster implementation of Device42 to have high-availability and ensure that we don't have downtime in case of failure."
"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."
"My biggest problem with the product is the upgrades. First, we have to do them manually and second, not this last time but the time before that, we actually had to build a new VM to deploy the solution again. We had to back it up and then restore it to the new version. That was inconvenient."
"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."
"The asset management tool is costly."
"The engineering area needs improvement."
More ManageEngine IT Asset Management Pricing and Cost Advice →
Device42 is ranked 6th 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, JIRA Service Management, Infoblox IPAM and BMC Helix Discovery, whereas ManageEngine IT Asset Management is most compared with Lansweeper, Freshservice, Axonius, ServiceNow and BMC Helix Discovery. 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.