We performed a comparison between Device42 and OpenText Service Manager [EOL] based on real PeerSpot user reviews.
Find out what your peers are saying about ServiceNow, BMC, Freshworks and others in IT Asset Management."One of the most valuable features in my experience is the precise tracking of hardware devices and their locations registered in the solution. The solution allows to determine the exact placement of assets based on the building maps and the room details. This feature has allowed us to gain upper hand on the customers and provide them with a great satisfaction because they can visually see the arrangement of their assets within the organisation or building."
"The solution is agentless."
"It has agentless discovery; you don't need to put agents on your servers. You can open one or two ports to discover all your infrastructure."
"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."
"The solution's automatic IT asset discovery and inventory functionality are top-notch. The thing I like is that it's open-source. If I need to change them — and they've given me links on GitHub to have them — I can go and change them to pull exactly what I want, as frequently as I want."
"I like the tool's agentless discovery feature. The tool configures the devices based on the documentation provided. I am also impressed with its auto-discovery feature. The tool also keeps on tracking and finds whatever is in the environment."
"The REST API abilities enables us to run scripts that pull information from our servers about software, storage, etc. Anything we need is pushed through REST API to the Device42 server and reflected in the report it generates."
"The IP address tracking [is valuable]... We have a lot of different devices and some of them have many IP addresses, so keeping track of which ones are assigned where is very critical for putting new devices on the network and giving them new addresses. All of our devices are statically assigned, so if we don't keep good records then we could accidentally assign a duplicate, which would cause problems on the network."
"We can have all our requests and incidents registered in one system."
"Service Manager's best features are flexibility and customizability."
"It can adapt to any process in the organization."
"The workflow engine that standardizes and globalizes the process steps. It drives people through the process by standardization and automation."
"Incident management is the most valuable because we're using it to manage tickets for an accounting system. With the reports that are available, it allows us to track and identify trends at the type and item level. It also helps us in managing the workload better than what we had in Remedy, which is what we were using before 2013."
"A valuable feature for us is that we have an ordered way to handle all the cases that we can handle with the infrastructure."
"The initial setup is easy."
"The solution is simple to set up."
"The only thing which I have noticed so far that is not good is that we had an issue with some reporting from the tool, reporting we had to export. We couldn't do it in the way we wanted to, so we tried to reach out to their support but it took pretty long until we understood how we can manage the reports. We still haven't received a complete explanation of what we need to do and how to do it."
"While the automatic IT asset discovery is great, the first time using it can be confusing when you are configuring the SNMP. I don't remember for sure but I don't think it said "SNMP community," it said "password". The first time I used it I was thinking about communities but the tool said "password," and when you say "password" in SNMP you are thinking about SNMP version 3. This is the only thing that is confusing, although there were some devices that were not included in the discovery."
"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."
"In my experience I believe that the key concern is the pricing strategy of the solution. Instead other solutions such as lanweber are much more cost effective. Previously, Device42 operated on perpetualysis without any fees. But recently they have altered the pricing model to include a subscription fee which I see as a very costly affair. Therefore I would like to suggest that they evaluate their pricing strategy and licence scheme, conduct a market research and ensure that they provide the right product in the market at the right price."
"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 resources table needs a few tweaks. We've raised a feature request for this. When you click on resources, it opens up the entire CMDB or the entire data stored in Device42. If that could be customizable, it would be good. We should be allowed to add our own columns to that by writing a script or something like that. There should be an option to add or limit whatever we want."
"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."
"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."
"With the new version moving toward the codeless configuration is good, but it's losing flexibility."
"It needs to be easier to use for the end users because one problem we had was that we are handling different kinds of cases."
"The interface could be better."
"I don't see anything lacking."
"Micro Focus Service Manager is not very great. It would be better if it had more features. When it comes to features, BMC tops the chart. When it comes to usage, people use BMC more."
"The user interface is very clunky. It's only now beginning to be a web-based interface, but for now it's still very clunky."
"Pure cloud-based native functionality is lacking."
"The greatest issue for us is to understand the roadmap. We want to know whether we should upgrade now or should we wait three months."
More OpenText Service Manager [EOL] Pricing and Cost Advice →
Device42 is ranked 6th in IT Asset Management with 25 reviews while OpenText Service Manager [EOL] is ranked 12th in IT Service Management (ITSM) with 48 reviews. Device42 is rated 8.4, while OpenText Service Manager [EOL] is rated 7.2. 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 OpenText Service Manager [EOL] writes "A solution that works out of the box. The solution's real strength is its ability to change for your organization's infrastructure". Device42 is most compared with ServiceNow, ServiceNow CMDB, Infoblox IPAM, JIRA Service Management and BMC Helix Discovery, whereas OpenText Service Manager [EOL] is most compared with ServiceNow, JIRA Service Management, OpenText Service Management Automation X (SMAX), BMC Helix ITSM and IBM Maximo.
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.