IT Central Station is now PeerSpot: Here's why

Device42 OverviewUNIXBusinessApplication

Buyer's Guide

Download the IT Asset Management Buyer's Guide including reviews and more. Updated: July 2022

What is Device42?

Device42 makes IT decision making easier. With accurate, automatic inventory tracking powered by automatic discovery, Device42 is your go-to for everything from day-to-day ITSM to IPAM to encrypted secret storage, DCIM rack modeling, migration planning, and more!

Say Hello! to Automated Data Center Management

Say goodbye to spreadsheets and manual drawings which are, at best, inefficient and quickly outdated. Device42 auto-generates accurate infrastructure and inter-dependency diagrams making data center management faster, easier, and more accurate.

  • Gain – Gain accurate infrastructure visibility — know what you have, where it’s located, how it’s connected, and who owns it.
  • Beyond – Go beyond just the physical — gain visibility into blades, virtual machines, cloud instances, and the applications running on them.
  • Support – Support and document the entire lifecycle from purchase order to retirement.
  • Infrastructure – Device42’s comprehensive infrastructure management enables more informed decision making.

Know Exactly What is Running, and Where, with Deep Application Mapping

  • Mapping – Powerful application mapping tools relate data from various sources.
  • Related – Auto-discovered data is related with imported and input data.
  • Components – Dependency flow diagrams relating application components are automatically generated.
  • Visualize – IT managers can visualize the application’s different parts and interdependencies.
  • Charts – Automatically-generated impact charts show the relationships between applications, hardware components, and facilities.

Transform IT Anarchy into IT Organization

Access real-time configuration data to understand where resources are and how those resources are being consumed. Support future capacity and growth planning.

  • IP Address – Get the next available IP address (eliminate ping and pray).
  • Capacity – Locate racks with enough space and power capacity to house new servers.
  • Affected – Determine which users are affected by scheduled and unscheduled outages.
  • Supported – Know if a server/OS is still supported, and where to find it.
  • Accurate – Maintain accurate server-switch port connections.
  • Manage – Accurately manage rack power and cooling capacities.
  • Device – Know device interdependencies and their service relationships.

Efficiently Manage Growth and Consolidation with Powerful Capacity Planning Tools

  • Rack – Find available rack capacity with heat maps colored by available units.
  • Power – Ensure power availability at a glance with overlaid color bars.
  • Find – Quickly find space, outlets, and power capacity for new equipment with “What-If” scenarios.
  • Connections – Visually ensure all your machines are redundantly connected.
  • Hardware – Easily identify any hardware without redundancy.
  • View – View power consumption, temperature, and humidity over time.
  • Data Center – Locate data center hot spots and eliminate problem areas.
  • Reports – Comprehensive reporting includes abundant pre-configured reports or easily create your own.
  • Change – Instantly report change history, contracts, rack space availability, and much more.
  • Consolidate – Remove the guesswork — know if you have room to grow, or power and cooling capacity to consolidate.

Dramatically Reduce Data Entry

Increase data center staff productivity. By minimizing or eliminating redundant and low-value data entry, IT staff can spend more time on high-value business initiatives.

  • Automatic – Device42's autodiscovery, import tools, and 3rd-party integrations do a vast majority of the hard work for you.
  • API – All the documentation you could ever want on our open API is available at http://api.device42.com.
  • Powerful – Device42’s open and powerful REST API is thoroughly documented, easy to use, and extremely powerful —enabling input and output of data to and from external sources with features like .XLS API imports.
  • Better Place – Freedom from excessive data entry means you can focus on building the next cool thing and making the world a better place!

Enhance IT Service Management

Device42 integrates with many popular 3rd-party tools and imports from almost anywhere!

  • Input – No need to input the same data into multiple systems!
  • Information – Enhance the information in your ticketing system with data from Device42.
  • ITSM App – Out-of-the-box integrations with popular ITSM applications such as JIRA, Confluence, ServiceNow, and Zendesk.
  • Automation – Out-of-the-box integrations with automation platforms like Rundeck, Puppet, and Chef.
  • CMDB Providers – Import data from other CMDB providers like Aperature, Microsoft SCCM, Solarwinds, OpenDCIM, Racktables, Rackmonkey
  • Anywhere – Import from spreadsheets, Visio docs, and anywhere else you can get a .csv file.

Effectively Manage Asset Life Cycles

Make the most out of your budget. Track software and support entitlements, and full hardware asset lifecycles.

  • Purchases – Record purchases.
  • Lifecycle – Asset lifecycle tracking from the day of purchase to the day it’s retired.
  • Contract – Associate a service contract with the actual asset it applies to.
  • QR Code – Automatically generate a smartphone-readable QR code for physical inventory.
  • Planning – Improve planning with accurate financial data for budgeting and auditing.
  • Proactive – Proactively manage contracts and maintenance renewals with powerful reporting and renewal notices.
  • Track Well – Track software licensing and ensure compliance.
  • Eliminate – Eliminate waste and save money.

Resolve Technical Issues Faster

  • Services – Improve your IT service delivery with accurate and actionable data.
  • Flexible – Device42 will discover and correlate relationships between physical, logical, and virtual environments – providing a powerful tool for problem solving.
  • Ticket Makes – Attaching the actual device to a ticket makes confusion about which device is being referenced a thing of the past.
  • Locate Device – Locating the device has never been easier when it’s attached to a ticket; click the device and get all the relevant details from Device42.
  • Emergency – The next time a data center emergency arises, save the day in style!

Centrally Manage Shared Accounts and Passwords

  • Find – Take control of who has access to what systems
  • Ensure – Ensure that data center teams have the information they need, when they need it
  • Very Fast – Quickly map service accounts and secrets to devices and applications
  • Powerful Control – Protect account and password information with granular access controls
  • Locate – Track password views, expiration dates, and password changes
  • Happiness – And yes…keep the auditors happy, happy, happy!
Device42 Customers

Computershare, Concur, Doosan, Fitch Ratings Inc., Fujitsu, HomeAway, Jasper Wireless, Mercedes-Benz, Square, Twitch, UCSB, Zayo Group Inc.

Device42 Video

Archived Device42 Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Giovanni Schiano-Moriello - PeerSpot reviewer
IT Business Analyst at a university with 5,001-10,000 employees
Real User
Leaderboard
Everything is in one place linked altogether
Pros and Cons
  • "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 functions pretty well. There could be some improvement if there were some automated scripts to get it off the ground. I know it takes a bit of effort to get all of various managed devices into one place. We have to go and change how they are managed and make sure they are all linking up correctly so they can be tracked in Device42. Some type of automated script for each to get over that initial activation."

What is our primary use case?

The first use case is the most important. It is Application Dependency Mapping. We want to track what is dependent on what. We want to know when something goes down or a change is made. We are also trying to use it as a change management database for what hypervisor is in what rack which links over to what business application is running that uses what services and has what account. We have information scattered in a lot of different places. This seems to be a very nice solution for taking everything, integrating it together, and linking it all up. 

There seems to be a lot of automation available with our inventory. We have been putting a lot of work into getting our entire infrastructure into Device42 rolled out. However, we have had a lot going on recently because we're going through a merger and acquisition so this has been a bit of a chaotic time. So, we are trying to get everything smoothed out, put in, and figure out. It hasn't been too bad. 

Since we upgraded recently, we are probably using the latest version.

How has it helped my organization?

Device42 instantly improved password management because we didn't have a solid solution for that. Upon installing it, I saw that was one of the little hidden gems of functionality for this. Instead of going with a single solution or platform that we weren't interested in for password management, we have that built into this functionality. It covers a lot of bases and hits a lot of points needed for an IT department. Everything is all in one boat and the solution links up to LDAPs. Whereas, if you don't go with them, you may need to get two or three solutions from different companies or providers. 

It has definitely given us an idea of dependency mapping. We have been trying to see what we can do to link all of our applications. This would improve our security posture for auditing into Device42, as we integrate that with Jira, then link all three together. It's still a work in progress, but it's getting there.

What is most valuable?

  • The password management feature
  • Data center management and tracking
  • Room management
  • Application Dependency Mapping
  • Automated asset tracking and inventory

Any successful IT department needs to have the functionalities that these features provide, whether through Device42 or through a different support application. The better that they can be supported, the more organized and successful a department will be, especially when an outage/issue comes up. 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.

Application Dependency Mapping is in a lot of places scattered through different applications. We are trying to centralize that into Device42. When you first start, you look at things like they are just one application or issue. However, when you can think of it as a dependency map, then you can trace any issue you have back to the source and figure out where the issue is happening and what will be affected when I change this one thing. It has improved our thinking about an IP application or IT system in a sense that everything is linked together and one thing will change another.

The asset discovery is pretty comprehensive and covers everything needed.

The solution provides continuous asset discovery, which is great. If there wasn't continuous discovery, then there would be no way to have devices updated if things changed.

Right now, we have full use of the password management functionality that Device42 provides. The main thing is everyone can login to use it for all their setup. This is the password management under "Secrets".

What needs improvement?

The solution’s automatic IT asset discovery and inventory functionality functions pretty well. There could be some improvement if there were some automated scripts to get it off the ground. I know it takes a bit of effort to get all of various managed devices into one place. We have to go and change how they are managed and make sure they are all linking up correctly so they can be tracked in Device42. Some type of automated script for each to get over that initial activation. Once everything is in and tracked, it is a very robust solution. By the end of this year, I am looking forward to getting it rolled out and properly set up in our organization.

It gets a bit confusing sometimes when you're trying to map things to a certain spot when you are trying to configure it. The only trouble we have had with it is the initial activation to get started and get things linked in there. 

Buyer's Guide
IT Asset Management
July 2022
Find out what your peers are saying about Device42, ServiceNow, BMC and others in IT Asset Management. Updated: July 2022.
619,967 professionals have used our research since 2012.

For how long have I used the solution?

Approximately six months.

What do I think about the stability of the solution?

It is pretty stable. I haven't seen any stability issues yet.

Device42 links up to LDAPs. We've had no issues with managing that.

We need one person (an IT business analyst) to maintain and deploy the solution. I currently perform this function and fulfill a lot of different functions for the company. I wear a lot of different hats. I'm one of the more veteran people in the company here. I have a lot of different roles: application administration, application architecture, and account management. All three of those come together to loop in infrastructure, architecture, and administration. All those come together to get this application ready and deployed in our environment to improve our IT posture.

We upgraded in November.

What do I think about the scalability of the solution?

The scalability is very capable. There are a lot of things that you can do with this solution. I'm hoping that as our configuration matures that we can take more advantage of them.

We have 15 users who are segmented into users of the application. There are administrators of the application and super admin accounts for the management of the back-end. We have two super admins, three administrators, and then all of the rest are users.

A big push will be when we build our new data center, then that will be hopefully set from the ground up when we redo our network. The solution is not being used too extensively right now. The infrastructure upgrade network is the main upgrade component. You have to start with the networking in Device42, so I'm hoping it will give us a fresh slate to do everything properly instead of mismatching everything in there. We definitely have plans to use the software fully and to fully utilize all of its functionality. However, we're still in the early phases.

How are customer service and support?

We have had very positive experiences with the technical support. They have been great. We have received so much support from their end that sometimes it may have even been too much. Anytime I'm looking for something, support is coming at us. I even had a little trouble figuring out who I should reach out to when I needed something, but that was clarified recently. There is no lack of support with Device42.

Which solution did I use previously and why did I switch?

We used different solutions from different platforms. Some of them only fulfilled one specific portion of what Device42 would fulfill. They were coming from all over the place. E.g., we were using Excel spreadsheets and Word documents for some stuff. It was a mess and all over the place.

Our IT lead worked with Device42 in the past. He heavily recommended them so we moved forward with it. There has been a big need for our organization to centralize everything and have a proper change management and inventory system with live updates.

How was the initial setup?

I found the overall process of the initial setup straightforward, but certain parts lacked direction.

The install guide could be a bit better. I ran through it to see where to start. Once I figured it out, we connected with support, figured out where to start, and got a plan together. Now, it's been going smoothly. However, when you first start and install the application, you log in and it's like where's the best place to start? For example, "How do I get from here to everything tracking and linking up?" The answer: It depends on your environment. A segmented approach may be more helpful, which support definitely cleared up.

We are still in the configuration phase. A lot of that is due to the lack of time put into getting this configured. The deployment phase probably took a couple of days. We are still working on the configuration phase. A lot of that is due to our own equipment not being supported anymore. We're in the process of infrastructure upgrades now, which doesn't exactly help.

The implementation strategy is to get it installed, then do whatever initial adoption we could (which was "Secrets"), as we're trying to get our network onto it. As we're going through a network infrastructure upgrade, this is a bit chaotic right now but the goal is to start with the network then flow down towards each specific server and VM that we have. On the opposite spectrum, we want to start with our rooms, then build those out into building our data center and racks, meeting in the middle. We're still in the configuration phase, which has been slow.

What was our ROI?

We have seen ROI, but we are still in the early phases. We still need a bit more time for the configuration on our end to get our infrastructure ready to be able to be imported and managed properly. 

Which other solutions did I evaluate?

Our IT lead evaluated this.

What other advice do I have?

There are pros and cons to the solution’s agentless approach to asset discovery. Without agents, the benefit is that you don't have to manage an agent, update it, install it, and go through the application management on it. It's definitely easier from a longevity perspective. The con is that it takes a bit more configuration with higher activation to set up. If there were agents, it might be a bit simpler to deploy.

Something that we are in the early stages of is the solution’s CMDB, ITAM, and DCIM features creating a single source of IT truth in our environment. It is in our roadmap plan and where we hope to see ourselves at the end of our configuration phase.

I have learned is that there are ways for various different types of networking equipment, servers, and systems to all have ways of reporting into an application. The biggest one is SNMP. Finding out that those are not all configured properly leads to a lot of headroom once the application's already in place. I know I have to go back and configure all of our switches to be doing what they should.  The biggest lesson is that there is a lot of preconfiguration with your infrastructure to ensure that it is ready to be imported into Device42 due to the various ways that equipment can be reported.

Look into getting SNMP configured on everything ahead of time. Ensure you have an LDAP ready for use with the products. Definitely keep support in the back of your mind because they have helped a lot as we have gone through our process.

I would rate the solution as an eight point five (out of 10).

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Francois Sureau - PeerSpot reviewer
Manager, Hosting Operations at a tech vendor with 10,001+ employees
Real User
Leaderboard
Helps do full device-lifecycle tracking and automate VM deployment
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

We use Device42 mostly for asset inventory because our compliance rules require us to know what devices we are using: the warranty for each device, when we install it, when we remove it — so full tracking of the device lifecycle. We use Device42 mostly for asset inventory, including physical pieces of hardware and virtual devices as well.

We expected we would use a SaaS version but it was not possible, so we use the on-premise version.

We have more than one instance of Device42. We have four implementations of it in our company. Each of them is dedicated to a single environment: government, our AWS environment, co-location, and corporate co-location. There is no possibility for each of these environments to speak with each other, so that's why we use four different Device42 instances in our company.

How has it helped my organization?

Device42 is a source of trust for many things in our company, like IP addresses. In the past, we tried to have IP addresses centralized in an Excel spreadsheet, but now we have built automation to get information from Device42 with an API call. As a result, it's possible to deploy a new VM in 15 minutes and all the information is pulled from Device42, by our automation, to build that new VM.

It's the same for load balancers. When we want to create a new virtual IP for load balancers, we have it automated with an API call and Device42 provides all the information needed to get the job done. So Device42 helps us to build automation into our infrastructure.

Device42 is also a source of trust for our security scan. When a vulnerability is detected in our system, the system automatically looks for information in Device42 to find out who owns the server that has the vulnerabilities and what the contact email is for that team, etc.

The continuous discovery for us works daily. We can be sure, if a device has been updated, that information will be correct in Device42. We are tracking which devices haven't been updated in the last few days and, for each of them we try to understand why, and to fix things so that the discovery does update those devices' information.

I don't know if we can say it has reduced the time we spend on asset management, but in that same amount of time, we now have reliable information. In the past, we were not confident about the information we had. Now, we expect that the information we have is correct.

Also, we have many audits each year. Each audit requires us to provide evidence about how we manage our assets. There are inventory questions and it's easy for us to provide an audit report. When an auditor asks us information, we just have to a share-screen and show him, in 10 minutes, how we manage our assets, and he understands that everything is correctly managed. The audit is very quick.

What is most valuable?

We use asset management and program management. For some implementations, we also use the software management.

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. It helps us ensure that we don't have more entries in Device42 than we have in our actual co-location and that we don't have more virtual servers than we have in Device42. We are sure to have 100 percent of our devices in Device42. Not more, not less.

The agentless approach to asset discovery is a good option. Sometimes it's better off to have agents, but in our environment, for most of our servers, it's really good to have the agentless. For a few of them we would prefer to have an agent because, from the network perspective, it's sometimes difficult to allow external Device42 discovery to have access to some devices for security reasons. The security team does not allow certain kinds of access. That's why it's easier if the secured server can have a call to an external service, rather than an external service calling the server.

What needs improvement?

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.

Also, when we do an upgrade, it's mandatory to shut down the application. It takes 10 or 15 minutes to upgrade and it's once a month. It's not a big deal, but if it were possible to have no downtime, that would be better. We can plan for upgrades, but we try to have 24/7 availability in our organization, so there really isn't a good time to shut down service. Doing so always has an impact. We have teams around the world.

For how long have I used the solution?

We were early adopters and we have used Device42 since 2013.

What do I think about the scalability of the solution?

The scalability is pretty good. It's possible to have many devices in Device42, but we can see some limits. For a very large organization, it would be a little bit difficult to use Device42 because it's a single server. It's not possible to have scalability by load-balancing the load onto different servers. That's one of the reasons why we decided to have four different implementations, to be sure that we do not have everything on the same server.

We have more than 1,000 users in Device42 and most of them use it for the password management. Some users are using it for audit purposes, for asset management, and to be able to provide reports to senior management.

We have deployed Device42 everywhere. If our organization does not expand the number of devices, we won't need to extend Device42.

How are customer service and technical support?

Technical support is pretty good. Each time we need them, we can have a call with them. They respond quickly. It's good support.

Which solution did I use previously and why did I switch?

Before we used Device42 we had nothing except Excel sheets. We began our asset management with Device42.

How was the initial setup?

I was one of the main stakeholders when we decided to choose an asset management tool. When we decided to use Device42 it was mostly because of its ease of use and that it is easy to implement. We had some meetings with other companies that provide asset management tools. With all of them, there would have been months of implementation with an implementation team to help us. It would have been a big project to implement these applications. With Device42 it was easy. It was easy to install, it's easy to manage, and easy to understand how it works. That's one of the things we like with Device42.

Our implementation of Device42 took a few months. After one month we had 80 percent of our infrastructure in Device42, and the last 20 percent took a little bit longer because we had to discuss things with security. Within three months we had 90 percent in the solution and, after six months, we had 100 percent in it.

We were looking to have automated discovery to be sure that when new devices come in, they would be automatically ID'ed in Device42 and we wouldn't need someone to add them. In one month we automated most of the implementation.

What about the implementation team?

We did it ourselves, and that's one of the reasons we decided to use Device42. All of the other products asked us to use an integrator or a reseller or someone who would help us. Device42 was easy, so we decided to run with it. We were able to manage everything by ourselves.

What was our ROI?

It's difficult to say if we have seen ROI. We need the functionalities so we pay for the service. It did not replace something that might have been more expensive.

What's my experience with pricing, setup cost, and licensing?

We pay $100,000 per year. There are no costs in addition to the standard licensing fees.

What other advice do I have?

The biggest lesson we have learned from using this solution is that if we want to have clear asset management, we need to have the same processes, policies, and rules in each part of our organization. If each part of the organization works only on its side, it's really difficult to reconcile asset management. That's why each technical team that owns devices has to share their processes and work in the same manner. When that is done, it's really easy to have good asset management.

We don't use the solution's Application Dependency Mapping. In our organization, it's too difficult for a team to be able to provide information on application mapping and to be able to reconcile what Device42 discovers with what we have. So we decided not to use it.

Device42 does not affect our security. We try to use it so that it fits within our security requirements.

In the past, one person was working on maintaining Device42 and that was enough. But now that Device42 is critical for our organization, we have two people working on it to be sure that when someone is on holiday, a second person is there in case of trouble. They work as managers of asset management.

I would rate it at nine out of 10. It's difficult to give a 10 because it's always possible to do better, but it's a pretty good solution.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
IT Asset Management
July 2022
Find out what your peers are saying about Device42, ServiceNow, BMC and others in IT Asset Management. Updated: July 2022.
619,967 professionals have used our research since 2012.
Sr. System Engineer at a tech services company with 201-500 employees
Consultant
We are making it our single point of truth; no other tools needed
Pros and Cons
  • "A big plus for Device42 was the auto-discovery. With it, we have updated devices, updated systems, and up-to-date systems."
  • "When servers have two network adapters, automatically discovered will be only one network card because the other one is a backup. Device42 has some problems to find the other connection."

What is our primary use case?

Device42 will be the single point of truth for our network, service, and device documentation. The first step is to put all data inside with the goal to discover all things automatically. We do have a few things we must fill in manually. The second step is to use this data and create automation. When we can do this, it will be a big step towards successfully automating our processes overall. Processes can be in connection with the driver ticketing system, the installation of new virtual machines in new containers to grab data automatically to ask the system what is free, determining what we can use, and also automatically returning data to Device42.

We now have nine data centers in Device42. We have data centers in Germany, the US, Singapore, and Australia. 

The company creates software and sells those services. The software send mails, SMSs, and faxes globally. We host everything ourselves. We have security, network, and infrastructure teams, which are all in-house. Nothing is outside in the cloud. We can create everything that we need in short time and easily ourselves.

I am using the latest version.

How has it helped my organization?

When all data centers have been added, it will be a success at this time. It is a time saving tool because we can connect all our other tools to Device42, which gives them the advantage to speak with Device42 and the ability to use data in all directions.

Device42 will be our single point of truth, and only Device42. There will be no other tool, no other person, and no other Excel sheet; it will be only Device42.

A big plus for Device42 was the auto-discovery. With it, we have updated devices, updated systems, and up-to-date systems. 

What is most valuable?

The auto-discovery and API are big values for us. We like these features because:

  • They make requests easy against the Device42 system. 
  • They are an open standard that we can use for all our other systems, connecting to all our other systems. 

The solution’s automatic IT asset discovery and inventory functionality is a great feature. It was a great idea to create this functionality because we have thousands of systems. To do this manually, it's really a pain.

What needs improvement?

I tried in the beginning to use the agentless discovery. I had a few problems. There was an employee before me who started with Device42 in 2018. I came to the company in Summer 2019 and was the new tool owner. We had some problems with the agentless, so we switched to the agent discovery. We have a big Linux environment with a lot of Linux services. All Linux services are orchestrated. Therefore, I had no problems rolling out the agent approach to 2,000 to 3,000 machines. The scheduled task for the control for the agent I can create this in a few minutes with the orchestration.

I have a feature requests for the UI to sort numbers or estimates.

When servers have two network adapters, automatically discovered will be only one network card because the other one is a backup. Device42 has some problems to find the other connection. I have open some tickets for this.

For some of the network devices, the auto-discovery could be a bit improved. Some switchboards for some devices have problems to receive their connections automatically, and support names are sometimes incorrect. These are only for special network devices when we have a clustered network device.

For how long have I used the solution?

I have been using Device42 since last summer (2019).

What do I think about the stability of the solution?

The stability is great. No problems overall with it.

What do I think about the scalability of the solution?

We have a lot of devices with a modern database architecture. It does not have a problem handling our data. 

Many people from my company are now working with Device42. They switched over from the old tool to Device42. There are about 300 people working at the company.

The whole technical department is using Device42 (120 users). Technical department, at our company, means we have infrastructure, network, application management, and application support teams along with an internal IT department. Even development uses this tool to see devices and clusters.

How are customer service and technical support?

I'm often in contact with the support team, as I have a few ideas about feature requests or fixing thing. If I do find a few mistake or problems in the tool, then I speak with the support team.

It's good support. I like it. They answer quickly, but sometimes you can feel the support does not know the solution. The roadmap from the development is now cloud-based, which is a big thing. The development is going to cloud and cloud discovery, but some of the basics are not working perfectly and development has no time to fix them. It would be great if they could fix these basics, then concentrate on bigger, newer things, such as, the cloud, container discovery, and database discovery. They need to fix these basics, but overall, I'm happy with the support.

Which solution did I use previously and why did I switch?

Our tool before was Rectangles, which is an open source tool. The usability is a bit old but people like to work with it. However, everything in this tool is created manually. To create all devices manually, it's a big pain. To update everything is another big pain. In a big environment, it is not possible to use. With the auto-discovery of Device42, we are nearly up-to-date with all our systems.

I have also used another tool that was written by an application developer inside the company. It contained some special reports and other things.

How was the initial setup?

In our solution, configuration was easy because we can automate this configuration over all the servers in the world and roll out the configuration in the agent. It's done in a few minutes.

For a very small installation with a few devices inside, the tool is too big. If you have a few different devices and are using cloud virtualization and cloud applications, then it's a good tool. Though, it is not specifically for this. It is a good quality tool, which is easy to manage.

What about the implementation team?

One person is needed for deployment and maintenance. 

What was our ROI?

We have not yet seen ROI.

The solution has not reduced the time spent managing IT assets. I must first add all data centers in the tool. I'm not finished yet. But in the end, it will reduce time for the company as a whole.

What's my experience with pricing, setup cost, and licensing?

On a yearly basis, our licensing is $10,000. However, our license is now nearly full with devices. We need the next bigger license with 5,000 devices, which will cost us $19,000. We pay for a set of licenses, a maximum number of devices, and a maximum number of IP addresses. We have the smallest amount of features, which is enough for us at this time. E.g., we don't need application discovery, but possibly in the future, it will be a good thing.

Which other solutions did I evaluate?

We evaluated a few other tools, even open source tools. Big pluses for Device42 were the price was clear and the features received. 

The problem with using other vendor, like BMC, is the pricing. The price is so horrible and nobody wants to pay this money.

What other advice do I have?

Overall, I am happy with tool because we have a big infrastructure across the world with a lot of different devices. We have a lot of service, virtualization, hardware machines, and network devices. You can't find a perfect tool for all devices in this world. You must find something in the middle, and Device42 is a good tool for this. 

The agentless approach is a good feature. It didn't work for me. I was happier with the agent, as I had immediate good results. 

There are only a few people still manually creating tools because we have no option for these specialty devices. For these specialty devices, we not need automatically update them because these devices are aesthetic. It's only a few devices, so administrators for these devices do this work manually.

The solution doesn't affect our environment or security.

Compared to other tools, I would rate this solution as a seven point five (out of 10).

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Security Engineer at a tech vendor with 501-1,000 employees
Real User
Automatic, continuous IT asset discovery is key to our operation; when changes happen they are pulled in
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

We have a pretty unique use case, one that isn't used by a lot of companies. We have Azure, AWS, as well as Google Compute Engine in the cloud. We want to have all of those in one central station. That's why we're using Device42, so that it can track all of our IPAM in one place.

We have it on-prem in our data center.

How has it helped my organization?

The fact that the solution provides continuous asset discovery is key to our operation because we treat our instances like cattle, not pets. If something breaks in the build or along any step of the way, or something just stops responding, normally we just shoot it and spin another one up. So we have to have something that notices that something remotely changed, and that can then pull that back into the records inside of Device42.

The solution's CMDB, ITAM, and DCIM features absolutely create a single source of IT truth in our environment. That's why we use Device42; because that is what we have to have. When I worked at Bluehost, we were using Act! tables and they were really painful to use as a source of truth because they were never kept up to date. Device42 is much easier to keep up to date. And because of the way it works, and the reports that it has, we all trust it as our IP address management tool. It's the best IPAM tool out there.

And deployment of the solution has definitely increased our security posture because you can only secure what you know about. If you don't know about it, you can't make sure that it's secure.

What is most valuable?

The discovery is the most valuable feature. Device42 has remote connectors that will go out and look for the changes. You can run Nmap. You can do one-way DNS zone syncs and that's pretty important. Those are the things that are really quite strong for Device42 to report back on your infrastructure.

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. 

Also, I can show this to CEOs, and they understand it. So the front-end is awesome. 

Once you get the reports done

  • the monthly device add-on trends are awesome
  • the changes are awesome
  • the IP statistics, device statistics, and your building's statistics are all really good.

What needs improvement?

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. And those don't flow in and out. Yes, you can purge them — they do have a purge function — but the way that that works for security purposes leaves a little bit to be desired. I want to keep track of those for a security solution. If there were a compromise, it would be nice to have that rather than have it taking up some of your spots. Something that's missing is Kubernetes-based statistics so you can get a peek inside your clusters there.

Also, the reports are a little clunky, they could be better.

Finally, the comprehensiveness of the asset discovery is not perfect, but that's part of it being open-source. The scalability, the time that it takes to get things inside, could be faster.

For how long have I used the solution?

I've been using Device42 for about seven years. At Bluehost, a company I used to work for ages ago, we brought it in and I started using it there. It was in one of its earlier releases. We were buying other companies and that's when I started using Device42.

What do I think about the stability of the solution?

It's very stable. We've never had a problem with Device42, and we've used it quite heavily.

What do I think about the scalability of the solution?

Nmap is the de facto standard. But Nmap is still slow. If you wanted to look at 10,000 different IP addresses and get a little bit of information from each of them, it would take a little while, unless you multi-fitted them. There's a new tool out called Masscan. I've taken it and written a middleware so that the Device42 stuff uses Masscan now. That would be something that would really help Device42 scale much faster, in the discovery-specific portion of its tool.

For what we're doing, the scalability hasn't been an issue. We knew a lot of people were going to be using it. We have people from all over the world — from three different places in India, seven different places in the United States, and a bunch of people in the European Union —  working on this at the same time, 24 hours a day, seven days a week.

How are customer service and technical support?

The technical support is fantastic. We wanted to bring in a whole bunch of information from NetBox. We wanted to basically seed Device42 from the information we kept in NetBox, and they made that very easy. It was very helpful.

Which solution did I use previously and why did I switch?

We used NetBox. We switched to Device42 because it's better.

What was our ROI?

Device42 is not that expensive. To have something that has all of our IP address scheme in there, something that is up to date and current, is a huge ROI for our organization. The ROI is very high.

What's my experience with pricing, setup cost, and licensing?

At Device42 they were really kind. We were working through the licensing agreements this year and they said, "Hey, we'll open this up for you if you'll give us your feedback." They're willing to make something work, and they are working on a solution that will work better for people who are using Kubernetes.

We follow the Kubernetes lifecycle. Every quarter they release a new one, and then end-of-life every six months. Our development is a little bit ahead of that, so we're testing things, bringing them up, spinning them down, for QA. And that uses quite a bit of address space, so the licensing thing is my only, "Hey, guys, you're not super-hot on the licensing."

Which other solutions did I evaluate?

I've used NetBox, MyIP, and RackTables. I've used quite a bunch of these other tools out there, and honestly, Device42 is the best. The others don't compare to it. It is so much better.

I, myself, and people in roles up to the VP, looked at a whole bunch of options, ones that they've used in the past. Together, we came to the conclusion that, for pretty much any commercial company — and this is really the takeaway — that would rather focus on making money than spending a whole bunch of time fiddling with different databases, different underlying hardware; any company that wants an app that will get up and running, the very best thing to do is to get Device42.

What other advice do I have?

Just choose Device42 first.

Device42 hasn't reduced the time spent managing IT assets in our company because it has given us a better look at all the assets. It has created some work for us. But once we're done with all that work, I think it will go down.

I give it a solid nine out of 10. If it had a way to better work with Kubernetes and the pricing was different, it would be a 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Chad Crider - PeerSpot reviewer
Lead DevOps Engineer at a financial services firm with 5,001-10,000 employees
Real User
Leaderboard
Helps you understand how everything is connected in your environment
Pros and Cons
  • "The way the solution’s automatic IT asset discovery and inventory functionality works is you set up a discovery job, then you can schedule it to run. I schedule all of the runs daily at different times so nothing is interfering with anything else. It's nice to know that you can set up the scan, schedule it, and sit back. You can check them every day and make sure everything ran, making sure nothing had errors, then you're good to go. Anything new is going to automatically be discovered, which is nice. It takes some of the stress off because you don't have to know, "If this team opened new servers, we need make sure now it will automatically pick them up." It is one less thing to worry about. It gathers a lot of data points."
  • "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."

What is our primary use case?

Our goal for using the product is to be able to migrate apps to the cloud successfully. E.g., you can't move something if you don't know all the dependencies or all the bits and pieces that need to go with it. If you move something and forget, "Because it talks to this database," and no one realized, then it's going to fail. You will have downtime and have to move everything back. App dependency is the biggest part for us right now. That is the immediate need. 

I have been focused exclusively on bringing in data, connecting it and making sure all the servers and network devices are being scanned. I haven't spent any time trying to figure out how to get data out.

We are on the newest version of the next-gen line.

How has it helped my organization?

I know they're using Device42 to prep for moving stuff to the cloud. I'm not aware if they've used that data to move an app to the cloud yet. I think we are still learning the product and figuring how to get the data out so we can get the right reports, giving us the information we need.

I like the solution’s agentless approach to asset discovery because the IT and OS teams don't want to go install and maintain an agent on their systems. It's just more overhead when they have to do something like that and make sure there's enough space on the server. It's nice that it's agentless, as it will go out and connect, then do its thing.

It is not about the app affecting our security. Instead, it is about how the app will change to adapt to our security, which is very tight. Security was discussed from the very beginning and all the way through. However, we didn't change for the app. The way we deployed the app, it had to change to fit our security.

What is most valuable?

The most valuable feature would be the scanning stuff: the discovery. It has a lot of different hardware that it can talk to, providing a lot of good information. The way the solution’s automatic IT asset discovery and inventory functionality works is you set up a discovery job, then you can schedule it to run. I schedule all of the runs daily at different times so nothing is interfering with anything else. It's nice to know that you can set up the scan, schedule it, and sit back. You can check them every day and make sure everything ran, making sure nothing had errors, then you're good to go. Anything new is going to automatically be discovered, which is nice. It takes some of the stress off because you don't have to know, "If this team opened new servers, we need make sure now it will automatically pick them up." It is one less thing to worry about. It gathers a lot of data points.

We use the solution’s Application Dependency Mapping. It was the biggest reason that we went with Device42. I've seen some eyes open in surprise, for example, "Whoa, I didn't realize this talked to so many things." It's really eyeopening. This is the whole point of app dependencies. Sometimes, you're not able to take a step back, look at the big picture, and go, "Wow, things talk to other things a lot more than we thought they did."

What needs improvement?

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.

For how long have I used the solution?

I was brought onto the project five months ago.

What do I think about the stability of the solution?

For an enterprise solution, it seems pretty stable most of the time. The discovery scans just work. When they don't, it's sometimes difficult to figure out why. We have had the odd occasional issue or two, which I don't know if it was just our environment or due to instability in the app, like a remote scanner suddenly becoming corrupt to where I had to remove the scanning software from the computer and reinstall it before it would work. Twice that happened, and I had to call support. When you go in and tell a piece of software to uninstall, and it's like, "Error, couldn't complete." Okay, that tells me nothing. Then I call support who has to send me a special script that cleans things up in the background. Finally, it will let me do things in the normal way that you're supposed to do them. This is something that they have some things to work on.

What do I think about the scalability of the solution?

It is scalable, though it all depends on the size of the database. If that grows, you have more room to read in more devices.

We are looking at some long-term goals of other teams using it. We are looking at having the network team map out everything, then letting them have access to go in and look at all their inventory. However, for now, we have started the push to the cloud, which is about mapping all the dependencies into the topology of the network, such as what talks to what ports so nothing gets left behind, firewalls, dependencies, etc. This is all flushed out ahead of time.

Device42 is currently hitting about half of our environment/LOBs, which is approximately 4000 servers. From what I've heard, there are plans to extend it to the rest.

There are two to three system admins who I have handed the project over to for day-to-day operations. The project that I was on, which was on hold, has picked back up, so I'm on it full-time. Therefore, I have been training other people to take over Device42. Right now, I'm in more of a training role than an active user of it.

How are customer service and technical support?

The two times that I had to contact the technical support when the machine went corrupt, they were helpful. They sent me a script with a nice email telling me how to use it. I got on the phone with them just to make sure everything was going correctly. We have no issues with them.

Which solution did I use previously and why did I switch?

Previously, it was just a black hole. People guessing they knew what talked to what. There was no centralized tool for bringing it altogether.

We primarily chose to go with Device42 because we needed to know our application dependencies before moving to the cloud. We didn't want to rely on individual teams, like the network team, to say, "We have this diagram, app, or program that we use." We needed somewhere where we could see it. We also needed all the different parts to come together to see what's going on.

How was the initial setup?

I took over the solution because a project that I was working on was put on hold. They handed this solution to me after the initial setup was done, and I ran with it from there.

The deployment is easy. I did it myself. You don't need a lot for this application. I handed it off to two or three people because they also are doing other things. This way, they can share the load. Once you get everything set up, it just runs. It is not like it needs a whole lot of constant handholding.

For deployment, you need to roll out the servers, install the software on them, and get the firewalls opened up. Each company will be different on how long stuff like this takes. You could have something up and scanning servers in a couple of weeks.

The deployment strategy that we used was hitting environments that needed to be moved to the cloud first. Once that is done, then they will to start expanding into other areas.

What about the implementation team?

Be careful who you partner with. We partnered with a third-party to come in and help us set everything up. The first technician that they gave us did not know what he was doing. Every time I would ask about something, he would say, "Oh, this looks different. They changed that from an older version." He didn't seem to know the current version. He was stuck in the past. Finally, we got a different guy who knew what he was talking about. So, it stunted our growth in the beginning.

The second guy comes along, and he's like, "App dependency wasn't even checked in the scans," because we weren't told to. We didn't know that we needed that checked to get what we needed until we talked to the new guy. We were like, "This has been useless so far," because this one checkbox alone is essential to what we want to get out of it. He had several suggestions on tweaks to the scans, etc. 

If you're going to partner with a company to come in who are supposedly experts to help you set up and configure it, pay close attention because there are a lot of things about the app to learn. You need to know exactly what you want out of the app so they can help you figure out how to get it.

What was our ROI?

It has not had an impact on our managing of assets yet, as we are still in the learning phase.

Which other solutions did I evaluate?

I believe that they evaluated one or two other options.

What other advice do I have?

The environment is a lot more complicated than I thought. It is like, "Wow, there are so many more servers, devices, and things talking to things." I have been in corporate enterprise environments for many years now, and this is the point of the app. I never really stopped to look at the big picture: "Wow, the environment is really complex." It's an eye-opener and makes you think about things differently. E.g., when you make a change to one thing, it helps you understand all the different things that could or could not be impacted. If you think small, then, "I will make this change to this one server." But, if you step back, you realize, "That's part of this, which is part of that. These things are all connected." It's like the butterfly effect: One thing will affect another, and another, and another.

There is an enterprise architect who is focused on getting information out of Device42:

  • The right reports
  • All the app dependencies
  • The data that we need to help us get stuff to the cloud.

We are not using the solution’s CMDB, ITAM, and DCIM features.

If you know what to put into the app to get out what you need, then it can do it. I would give it an eight (out of 10).

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Viktor Dzhokin - PeerSpot reviewer
Procurement Specialist at a computer software company with 501-1,000 employees
Real User
Leaderboard
Enables us to track everything in our data centers, including inventory, and even purchase orders
Pros and Cons
  • "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 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."

What is our primary use case?

We are using it for our data center operations, to monitor the stack layers that we have. We are also using it for our procurement operations, taking orders and tracking deliveries. In addition, we use it for following up on contracts so that we make sure not to miss any renewal or cancellation of a contract.

How has it helped my organization?

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 has reduced the time spent managing our IT assets. It's an easy-to-use program and everything is pretty understandable. We are able to manage everything pretty quickly, definitely saving time with the tool. For every task, my colleagues have told me that they save between five and 15 minutes. There might be some 30 tasks to do during the day, so it can save a lot of time.

What is most valuable?

It's an easy-to-use tool. It's not too complicated with too many settings. It has a pretty friendly user interface and is understandable at first sight. Everything was pretty clearly explained in the tutorial when I started using it.

And I would rate its automatic IT asset discovery and inventory functionality at eight-and-a half or nine out of 10. It works well for us. I haven't been working with the tool for that long, but over those five months it's has been really helpful for us. My colleagues who have been working with the tool longer than I have are also very satisfied with it. It's really helping us to keep track of everything: 

  • the buildings we are using for data centers
  • all the rooms in them 
  • all racks 
  • inventory 
  • following purchase orders
  • and information about all our vendors. 

What needs improvement?

Sometimes we need to add some details on the purchasing side of the tool. If we have a contract, we need to keep track of the beginning of the contract, the end date of the contract, and a notification period when we need to decide whether we are going to cancel it or renew it. This is related to the reporting because we wanted to add these details in the list which we see on the tool, but even when we succeeded with that, we couldn't see this information on a report. 

But overall it's an easy program and we can manage it without too much trouble.

For how long have I used the solution?

I have been using Device42 since I started working for my current employer in mid-October last year. So it has been about five months.

What do I think about the stability of the solution?

It's a really good product in terms of stability. It works in the way we expect. We don't have any complaints except with the support for our request on the reporting, which didn't go as we expected.

What do I think about the scalability of the solution?

I don't deal with the scalability of it. I deal with procurement mostly. But my colleagues say it's easy to work with and they don't have difficulty with this. 

I think it can be a bit tricky when they need to add many assets. We may need to do some internal upgrades when it comes to serial number scanning of small items for replacement, but that's not related to the tool. In the end, all this information will go into the tool and it will help us to track things better.

How are customer service and technical support?

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. We understand that the master admin can do this, but it still hasn't been explained, completely, how it's possible. Their support has been a bit slow.

And we also don't know if the master admin can provide access to other users to download such reports. It's one guy who takes care of all of this, who receives requests from everyone in the company who is using the solution.

I had one other issue, in the beginning. The tool didn't work for the whole company so I opened a ticket and had a remote session with a guy from support. He worked really well and really fast and resolved the problem within an hour-and-a-half. He found there was a programming issue and contacted his colleagues and they fixed it pretty quick so we had access again.

What was our ROI?

We have definitely seen a return on investment. I cannot give you numbers, but from what I have heard from my manager, they are satisfied with the tool.

What's my experience with pricing, setup cost, and licensing?

We have a yearly license.

What other advice do I have?

If a company with our type of business asked me if they should go for it, I would definitely recommend it if they have the same kinds of operations that we do.

The users of the solution in our company are from the lowest positions to almost the top. It might be over 300 people. We are using it on a daily basis. As a company, we are growing every day and more and more people are starting to use it.

It's a pretty good solution for data center operations, for what we are doing, and for procurement as well. I would recommend it because it's easy to use with a friendly user interface. It's not a difficult program at all. So far, everything is going well.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Network Engineer at Despegar.com
Real User
Continuous discovery displays new racks after installation, but some devices are not discovered
Pros and Cons
  • "The solution's agentless approach to asset discovery is very important for us because installing agents on physical or virtual devices is not easy in our company. We have to escalate these kinds of things to different levels of security. Not having to install agents makes it easy for us."
  • "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."

What is our primary use case?

In the beginning, we were looking to use it as an IPAM device but we saw all the benefits in having control of the assets, the racks, and how the physical servers are connected to the switches. We set up our data center with all the racks inside and all the devices inside the racks. 

So at first, we used it for IPAM, but after that we constructed the building with the rooms and the racks. So IT inventory is the second purpose of this tool. We use it to track how VLANs and our different virtual devices are connected and to inventory VMware and Xen virtual machines. 

But the main purpose is IPAM and inventory of the physical devices. In the case of networking devices, we are using SNMP, and with virtual devices we use an administrator-user to check different aspects of the ESXi in VMware.

The solution itself is a virtual machine over a SAN server and it's running in our data center.

How has it helped my organization?

We were working with Excel sheets and they were not automatic and were difficult to administrate and update. It required manual work every time we needed to add new hardware or new virtuals. With the automatic discovery in the tool, we have been able to leave these Excel sheets behind.

The continuous asset discovery is great. For example, a few months ago we installed new racks with new servers and, with automatic discovery, all the new racks are showing inside the tool. The people who have a password to get into the tool can check what kind of hardware was installed and how many virtual machines are inside the servers. That's great.

The solution's CMDB, ITAM, and DCIM features create a single source of IT truth in our environment. For us this has had a very good impact. It's easier for our managers and others who consume this tool. We can show to the rest of the teams how things have become more visible throughout the company.

Device42 has also saved us a lot of time, not necessarily in managing the devices but in collecting the devices. And with the inventory tool, we discovered that we have a lot of old things configured in the devices. That saved us a lot of time because, for example, we had old VLANs around that had been forgotten. With the tool, we can discover which devices have old configurations and we can remote to them and remove these configurations. If we didn't have the tool, we might have to go into each, device by device, numbering in the hundreds or thousands of devices, and check if they have this configuration in them. But with the Device42, we have this information in a few minutes. A task that might take two or three hours a day can be achieved in 40 minutes.

In security, we can check specific things that have to be configured in devices. While the security team is not 100 percent involved in the project, they have started to use the tool to check different security things on the networking devices. With the inventory check, they can see if a specific configuration in various routers has already been configured.

What is most valuable?

The most valuable feature is the part that enables us to draw or build our rack and represent all the devices and interactively click on a physical device to "see" inside it. We can see the virtual machines inside a given server and all the details about them, with the storage connected to them, etc. From a global, data center perspective, you can see the rack and you can click and see all the virtuals running inside. That's a cool thing.

Overall, the automatic IT asset discovery is very comprehensive.

The solution's agentless approach to asset discovery is very important for us because installing agents on physical or virtual devices is not easy in our company. We have to escalate these kinds of things to different levels of security. Not having to install agents makes it easy for us.

What needs improvement?

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.

For how long have I used the solution?

If we count the PoC time, we have been using it for about one year.

What do I think about the stability of the solution?

For us, it's very stable.

There were some problems at the beginning because the Xen server was not supported. We started with VMware, but we were migrating from that where to Xen. But the problem lasted for two days and then we fixed it quickly.

What do I think about the scalability of the solution?

We haven't reached the solution's limits. The solution's collectors give it very good scalability because you can separate the manager from the collectors.

We continue to check its capabilities. We plan to expand to another, small data center, a location with, say, 10 racks, with a rack dedicated to communications — such as a firewall, router, and switches — and the rest of the racks for servers. Expansion depends on the plans of our regional offices in other countries. The idea is to test if we can install info-collectors in these offices to give us information about their assets. We are planning these kinds of projects. Maybe we can expand our usage in this way.

How are customer service and technical support?

Technical support is very good. The support person we talked with was very kind. For example, we opened a ticket for a specific case and the support person who took the case explained more than we asked about. That was good.

How was the initial setup?

The setup was easy. We are used to using these kinds of tools — not specifically inventory or IPAM tools — but we have installations of solutions that collect things and give us information. So for us it was very easy.

The PoC was ready within one week, where the data was in the system and we got information from it. In production it has taken more time because we have different kinds of devices and every device or every brand requires a new configuration. For example, HPE enclosure devices take a lot of time to configure, although VMware was easy to configure as were network devices. But when you move to a new brand you may have more complex tasks to do.

When we did the PoC, we focused on it as an IPAM solution. In the PoC we saw the benefits of the hardware inventory. So we changed plans in the middle of the PoC. When we focused on IPAM at the beginning, everything looked fine, it was quick. But when we saw that the inventory is available in this tool we moved the PoC toward the hardware inventory. So the deployment took more time than we planned because of the change of plan.

What about the implementation team?

We did it ourselves.

What was our ROI?

We have seen ROI because it saves us a lot of time, and time is money.

What's my experience with pricing, setup cost, and licensing?

For our budget it's okay. It's not an expensive tool, although we are not used to paying for software because we are using a lot of open-source software. But within our networking budget, we needed an IPAM and it was easy for us to justify this kind of tool, given its cost.

Which other solutions did I evaluate?

We evaluated KiwiTech, but only for IPAM. We also checked out some free tools.

The main advantage of Device42 was the ability to have IPAM and another solution in the same tool. The rest of the vendors had different tools for different purposes. There were different KiwiTech tools for IPAM and for hardware inventory. It's not easy to administrate four or five tools. It's easier to administrate only one tool. This was an important advantage for us. Also, the discovery process was very easy with Device42 and more complex in the other tools.

What other advice do I have?

Test it. You may discover that tools that you hadn't thought about. As I said, we tested it only for the IPAM, but we saw that we also needed the hardware inventory. If you do a PoC, you may discover that you need other features that are part of Device42.

The biggest lesson I have learned from using this solution is to stop using Excel sheets. That was number-one. And the visibility that we have made available with Device42, to the rest of our company, has had a very positive impact on our team.

In terms of the automated asset discovery, we have had to configure and customize some things because, for us, some aspects of the virtual machines and the physical devices are important and these were not reflected in the inventory. Since then, everything has looked good. We achieved visibility of all the parts that we need to see.

There are five administrators using Device42 in our company. These five participated in the development of the solution in our company from the beginning and they maintain it. There are also three networking guys, two sysadmin guys, and the rest of the technical area's team members are users, including security and security compliance users.

I would rate Device42 at seven out of 10 because we need to fix it to find the devices that are not discovered.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
DC Lead Engineer at a financial services firm with 5,001-10,000 employees
Real User
We know exactly where our comms rooms are, what they're called, and what's patched into them
Pros and Cons
  • "The continuous asset discovery is good because it means not having to manually input all the small data, such as IP addresses, leases, etc. It helps and saves us a lot of time."
  • "If I want to delete an asset from a cabinet it does take a while. And if I'm doing it in bulk — say, for example, if we have one cabinet that has 20 servers in — if I want to remove all 20 servers, I have to do them individually, which is a bit time-consuming. If there were a way that I could just bulk-remove everything from there, that would definitely save some time."

What is our primary use case?

We mainly use it to keep an inventory of everything, because we've got 77 offices and data centers globally. We use it mainly to keep track of assets we have in cabinets and the like. Also, some of the other teams use it for the auto-discovery and license renewals. Device42 tells you when a license is about to expire on a server. 

I'm sure there are a lot more uses but because I work in data center management, and from my side we mainly use it just for inventory. We're aware of exactly what we have, where it is, whether it's powered on it, whether it's in service, etc.

How has it helped my organization?

Before Device42, the company didn't have any kind of asset management software at all. So if there were to be a fire in an office, for example, and we would want to make a claim on insurance, we would have had no idea what, exactly, we had in that office. Now that we have Device42, we're integrating every single office into it so we know exactly what's where. That's a huge improvement.

It has also reduced the amount of time spent on managing our IT assets. It has probably halved the time it takes to do the management side of it.

What is most valuable?

I think the auto-discovery is very good. It works well. I don't use it too much myself, but from the feedback I get from other teams — they use it a lot — it seems to work really well. From what I understand it's very comprehensive because it picks up everything: all the IP address ranges and locations, as long as we've input the devices correctly. It is very comprehensive and picks up a lot of stuff.

Also, the continuous asset discovery is good because it means not having to manually input all the small data, such as IP addresses, leases, etc. It helps and saves us a lot of time.

The DCIM makes everything easier. If we need to do something remotely, or if we need to get an engineer out to a comms room somewhere, we can tell them exactly where it is, what it's called, and what's patched into it. It ensures that people don't make mistakes.

What needs improvement?

The overall speed could be improved. Sometimes it's very slow to do certain functions. General navigation is quick but if I want to delete an asset from a cabinet it does take a while. And if I'm doing it in bulk — say, for example, if we have one cabinet that has 20 servers in — if I want to remove all 20 servers, I have to do them individually, which is a bit time-consuming. If there were a way that I could just bulk-remove everything from there, that would definitely save some time.

Also, I know there is a function where you can add cables in Device42, as in you can say: So-and-so port on this server is connected to this port on that server, for example. But that's quite a drawn-out process, trying to use the spreadsheet just to add a single cable. I think that could be simplified a lot. You could just have a column for the device name, the port, and the end-device port. If it could be populated that way it would be a lot easier. At the moment, the spreadsheet that you have to use to add cables has a whole bunch of columns which I think are irrelevant and shouldn't be there.

For how long have I used the solution?

I've been using Device42 for about 18 months now.

What do I think about the stability of the solution?

The stability is good. There have been a couple of times where it's been down for maintenance, but it's never down for too long. 

I believe Device42 has some software where it clears out old or redundant stuff after a while. We've had it happen that things we put into cabinets have suddenly disappeared. However, I'm not sure if this is actually a Device42 issue. It might be somebody on our end doing something wrong.

What do I think about the scalability of the solution?

From what I understand, it's very scalable. It's very easy to scale up on it as well. But it's more the app team that would know that kind of stuff. I deal more with the DCIM stuff.

It's being used very extensively in our company. As I said, we've got 77 offices globally and about half of them have been populated fully in Device42. The rest still need to be audited, so we are going to be increasing the usage of it. It just takes a bit of time.

How are customer service and technical support?

Technical support is excellent. I've used it a couple of times and it is really good. They always reply very quickly and they always give you a very simple way of doing what it is you need to. I would give technical support a 10 out of 10.

What was our ROI?

We have seen ROI with Device42. It might not be easy to see but, for example, when we have had stuff go down we now know exactly where it is so we can fix it a lot quicker. Before, we might not necessarily have known and would have had to do a lot more searching. There's definitely a return on investment in that sense, but I can't really put a monetary value on it.

Which other solutions did I evaluate?

Before Device42 we trialed dcTrack for a little bit, but it was over-complicated in terms of usability. You would really need to do a training course on how to use it properly, whereas Device42 is a lot more user-friendly. So we ended up going with Device42 because a lot of people in the company do you use it. It's not like it's a select few people. Most people have access to it: the server teams, the network teams.

Device42 is user-friendly in terms of navigating through all the pages. Everything's very simple. If we want to find out, for example, what we have in a comms room in Bahrain, we just click on the Buildings tab, scroll down to Bahrain, and it will have the comms room on there. We can then have a look. Whereas with dcTrack, doing that was a lot more complex.

What other advice do I have?

Be very thorough with it. Make sure you put in everything you need to put in and make sure the auto-discover function works properly.

The biggest lesson I've learned from using Device42 is the importance of keeping it up to date and taking out redundant stuff. Especially with the auto-discover, if I've decommissioned something but not taken it out of Device42, the auto-discover will still think something is there and that creates a bit of a problem for us internally.

In my department, there are only two of us in data center management. But the whole network team use Device42, as do the whole server team, as well as security and the app team. Company-wide, some 150 to 200 people have access to it. I'm not sure how many of them actually use it often; probably about half that number. 

In terms of updates — as in if we get new assets coming in or coming out — that's mainly my thing. In terms of the monitoring side of it, that would be the network team. They use SolarWinds, which is linked and will alert them if any device has gone down and that is linked to Device42.

Also, any time we do an audit of IT assets, the results are updated in Device42. We try to maintain a complete record of exactly what we have, although that's proving a bit difficult in certain offices which are harder to get to. We have offices in places like Ecuador and Chile and we're having to rely on people onsite, but there isn't always an IT presence there. We're having to rely on general office staff to try and give us an audit of what's in there. So from our side it might not be fully comprehensive.

I would rate it at eight out of 10. It's very good but it's not perfect. Nothing is. I'd probably give it a ten if it were quicker at doing certain things or if certain functions were more simplified. But it's a very good product.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Ernie Welter - PeerSpot reviewer
Sr. Infrastructure Engineer at a tech services company with 1,001-5,000 employees
Real User
Leaderboard
Makes it easier for me to figure out if I have room and/or power in a cabinet to rack servers
Pros and Cons
  • "The most valuable part is the ease of use. There's no training involved. It's pretty simple and straightforward."
  • "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."

What is our primary use case?

We use it for asset tracking, cabinet modeling, data center modeling, and we use it for asset disposition and to keep track of our spare parts.

How has it helped my organization?

It makes it easier for anyone to find an asset in a cabinet and it makes it easier for me to figure out if I have room and/or power in a cabinet to rack servers.

It has also reduced the time spent managing our IT assets by a good 40 to 50 percent. We have also used the solution in conjunction with audits of our IT assets and, in that context, it saves a lot of time when everything's right there at your fingertips. I would estimate that it saves 50 to 60 percent, in terms of time, when doing audits.

What is most valuable?

The most valuable part is the ease of use. There's no training involved. It's pretty simple and straightforward.

I also like the inventory functionality. I don't know that we're using it exactly how it's made to be used, but it works for us.

The asset discovery goes out and finds new devices and puts them under Unknown Devices, and then we go in and have to fix it and change it to what it is. It works really well. The fact that it's continuous is convenient. We don't have to worry about it. It just works.

What needs improvement?

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.

I would also like the ability to bulk-delete. The application is great, for the most part. There are just a few little bugs and quirks that are annoying to me.

For how long have I used the solution?

I've been using Device42 for almost five years.

What do I think about the stability of the solution?

I have no complaints. It's still working.

What do I think about the scalability of the solution?

My boss loves the fact that he can run API commands and get information that way. He's a huge API-guy, so he loves it.

How are customer service and technical support?

I've used Device42's technical support. It's okay.

Which solution did I use previously and why did I switch?

They had something called Rack Monkey. It was the most trivial program I've ever seen so that's why we looked for something else.

How was the initial setup?

In the beginning, I didn't really know a whole lot about it, so it was a little complex. But once I got a good understanding, it was very intuitive.

We were up and running within a couple of days and when I reached out for some assistance, Raj Jalan actually called me. He's the CEO of the company and it was really nice to get that kind of support.

Our implementation strategy was to get it up and running as fast as possible.

What about the implementation team?

I deployed it myself and there are two of us who maintain it. One guy on the network team does all of the discovery stuff and I'm a senior infrastructure engineer.

What was our ROI?

I would think we have seen ROI with Device42. It saves us time every day when we need to look up stuff. I can't put a price tag on it but it's very useful.

Which other solutions did I evaluate?

We evaluated other options but that was quite some time ago. We chose Device42 for its ease of use and quick stand-up.

What other advice do I have?

My advice would be "do it." It worked for us. Made my life easy.

You get what you pay for. It's a good product and I enjoy it and we don't mind paying for it.

I, myself, don't use the IP discovery a whole lot. One of the guys from our network team uses that. I know it helps them a lot. Similarly, with the Application Dependency Mapping, I know my boss has looked at it a couple times. I can't really say that we use it, but it's there. It's a great function that gives us a very good view of our network.

There are 2,500 to 3,000 users who have access to it. They're mostly just adding and updating inventory. When they deploy a new server they go in and give it a name and add stuff into it.

As far as I know, we don't have any plans to change things. Device42 is our solution.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Systems Manager at Coventry University
Real User
Continuous auto-discovery keeps infrastructure data up to date, enabling us to mitigate faster if a security patch is needed
Pros and Cons
  • "The auto-discovery is brilliant. You can have it scheduled to run on a regular basis, and the infrastructure is always getting updated within the platform. I would rate the asset discovery very highly. It's very comprehensive. It covers quite a lot of different methods for doing discovery and it supports a lot of different types of hardware as well."
  • "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."

What is our primary use case?

Our use case for Device42 is to capture all our infrastructure in a single tool. We need the ability to have that view of where our infrastructure is: servers, storage, network equipment, and applications sitting on top of servers. Our use case is to have that single pane for where all that is.

How has it helped my organization?

When we're doing patch management or when we're reviewing kit (end-of-life), it gives us the ability to manage the data center from a desk. Before we had Device42, we'd have spreadsheets or somebody would have to continually to go to the data center and physically have a look at what's available where. If somebody bought or wanted to buy new kit — if they needed, for example, six U's of space, 10 network ports and five power ports — we'd have to visit the data center and have a look at where we could fit that in. With Device42, we don't need to do any of that. We just need an internet connection to get to the Device42 appliance and we can see where the space is and what the power availability is, as well as what network capacity we've got, in which rack. Everything is there.

The continuous discovery of the infrastructure means we are able to review, and we are able to mitigate things in a quicker fashion than we would have previously. If somebody had asked us five years ago how many Server 2008's we have, because we've got a vulnerability and we need to know how many servers we need to patch, it would have taken us some time to find that out. We would have had to go through all the different platforms and find out where we're hosting 2008 Servers. With Device42, we can go in and, within 10 minutes, tell the business how many servers we need to patch.

Also, the solution's CMDB, ITAM, and DCIM features create a single source of IT truth in our environment. These too make it a lot easier for the operations team. When incidents come up on the operations monitor, that team can easily ascertain who the owner is of these devices, where they sit, and who's responsible for them. They ensure the correct people get things looked at much quicker.

In addition, we're currently on a cloud project, so we have been using the solution to assess what we have in our environment, what we want to take to the new environment, what we need to drop in terms of hardware, the age of the hardware, as well as end-of-life operating systems or applications. It has helped us a lot with getting that kind of data.

We use the solution’s Application Dependency Mapping and that gives us some insight into a number of things. For example, if we're looking at a server that currently has a problem, the operations team can look at the Application Dependency Mapping and see what the server is part of in terms of the service. There may be a number of things that are connecting to it or that it's connecting to. That mapping gives us that insight into how parts of the infrastructure are talking to each other.

Previously, when it came to asset management, people would have been updating spreadsheets or documents about where they've moved things or what they've been doing, or they would have had to visit multiple areas to find out certain information. Device42 turns that into a hands-off approach to everything. We know it has been doing discovery continuously over evenings and weekends. So whatever data we are pulling out is fairly up to date. The time saved by using Device42, across the teams, is easily equivalent to a couple of people at least. A full-time member of staff would normally work seven-and-a-half hours every day so you're looking at 146 hours a month of savings, times two, of people not having to visit data centers to do things like capacity planning, auditing, etc.

We also use Device42 for internal audits. In that context, it saves a considerable amount of time. If we were to do it manually, we're looking at a couple of weeks' worth of work, but if we're doing it in Device42 we're probably looking at a couple of days' worth, maximum.

What is most valuable?

One of the most valuable features is its ability to auto-discover a lot of the infrastructure, without having to manually put everything in. The auto-discovery is brilliant. You can have it scheduled to run on a regular basis, and the infrastructure is always getting updated within the platform. I would rate the asset discovery very highly. It's very comprehensive. It covers quite a lot of different methods for doing discovery and it supports a lot of different types of hardware as well.

The agentless discovery is the one thing that makes this a brilliant tool. The fact that you don't have to deploy an agent onto anything and you can do discovery directly through the appliance, just with credentials, is what really makes it stand out.

It's also easy for everybody to go into it and search for something, and the searching is very quick as well. You can get to get the information very quickly.

What needs improvement?

Room for improvement would be in the discovery. Although the discovery it does is really good, there are certain elements that could be better in terms of a deeper discovery. An example would be teaming on Windows Server. It doesn't currently pick up that functionality well. 

Also, 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. 

The certificate management could also be a little bit better.

Finally, it would be good to introduce a mobile app. At the moment, you can connect to the web interface through your mobile and select a mobile view, but it's still very much a desktop view on your mobile. It's not very mobile-friendly. So it would be good either to have a mobile app, or a specific mobile endpoint on the web front. You would visit a separate URL or it would detect that you're on a mobile and rearrange the view to be mobile-friendly, like dynamic websites do at the moment.

For how long have I used the solution?

We've been using Device42 for about five years now.

What do I think about the stability of the solution?

The stability is very good. We've never had any stability issues with the appliance where it continuously goes down or anything like that. We've not had a problem with that.

What do I think about the scalability of the solution?

Scalability-wise, there could be improvements. Currently, the scalability is only upwards. You have to increase the resources that you apply to it. You can't have multiple instances of the same thing. You can't scale horizontally; it's just vertical.

How are customer service and technical support?

Technical support is excellent. The engineers are knowledgeable and they respond in a very timely fashion.

How was the initial setup?

The initial setup is straightforward but, at the same time, depending on your business and the complexity of the infrastructure, it can become complex. Not the actual implementation of Device42, but to get Device42 to the point where it can do the discoveries on your infrastructure can become complicated, depending on how your infrastructure has been set up. But to actually get Device42 up and running, in terms of just the appliance, is very easy.

Our deployment took six to eight months. Getting the appliance running was very quick, but to get all of the integrations done, and working with all the different teams to allow the agentless discoveries to happen, and configuring firewalls, policies, etc., it took that long to get it all in place and to make sure that the data that we're capturing is actually useful and correct.

The implementation strategy was quite straightforward because we didn't have anything else before. We started from scratch to capture everything, starting from the network layer and going up to the server storage layer, and then the application layer.

What about the implementation team?

We deployed it ourselves.

What was our ROI?

Effectively, we didn't have a product before Device42. But with it, we're looking at a reduction in terms of man-hours to manage IT infrastructure and do asset management. That's where the return on investment has come. 

Another part of the return on investment is when a vulnerability comes out. With this solution, we can identify the machines very quickly, rather than having an engineer sitting there for a whole day or two working out what needs to be done. An engineer can go through Device42 and spend half an hour to pull a report.

What's my experience with pricing, setup cost, and licensing?

We pay annually for our licenses, which includes core, the Application Dependency module, and software discovery.

Which other solutions did I evaluate?

We evaluated two or three other options on the market. At the time, we chose Device42 because of its effectiveness in actually discovering the infrastructure. The second reason was the cost and the third was its ease of use.

We looked at RackTables, OpenDCIM, and we looked at another one from BMC and, for asset management, we looked at ServiceNow.

What other advice do I have?

The biggest lesson I would take from using the solution is to have an understanding of your infrastructure so you can better plan how you implement Device42. As with anything, there are obviously limitations as to what it can do. Sometimes there are certain politics within your business that may stop you from getting the most out of Device42.

Also, although we didn't actually do so, I think it would be good to have a close relationship with the vendor of Device42, at the implementation stage. Our relationship has matured and been built post-implementation of Device42. It's going to be beneficial, for anybody who wants to put Device42 in, to get the vendor onboard before you implement it.

I don't think Device42 has really affected our environment's security posture, as long as we understand how Device42 is doing these discoveries. We actually have Device42 in a fairly locked-down environment. Only certain teams have access to it because of the sensitivity of what's inside it. On the flip side, it provides that single pane of glass. You could say that there is a higher risk with it because we now have one place in which all the information is held. But I think the benefits outweigh that little bit of risk that we've taken on by having all the information in one place.

In terms of people using Device42 as a platform, we're somewhere around the 50 or 60 mark. They range from service desk analysts who use the secrets vault functionality, to the infrastructure team — system engineers, network engineers, infrastructure architects, network architects, desktop engineers, database administrators. Those are the kind of people who tend to use Device42's core functionality which is asset, infrastructure, and data center management. The secrets vault is spread across our whole department and the infrastructure side is heavily used by the infrastructure teams, which includes my team, systems, the network team, and the architects.

Deployment and maintenance are quite lightweight. To manage the whole thing you only need one or two people, and they are spread across the different teams in our environment. We have one person in the network team and one in the systems team to ensure that things are ticking over and for planning upgrades.

Our environment is not massive but it's not a small environment. In terms of what it costs us to run Device42, we find it a very good value for money. We will definitely be using it for the foreseeable future and our plans are to extend its usage into the cloud where we are already capturing things. But we want to make the visibility of cloud resources in Device42 much better. Device42  are improving cloud discovery as well. The way we've got it set up, it doesn't give us the same visibility that we have on-prem. So we want to start working on making sure that the visibility of our cloud deployments is just as good as we have on-prem, with deep discoveries, etc.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Deepak Pund - PeerSpot reviewer
Technical Service Engineer at Fujitsu
You don't need to put agents on your servers
Pros and Cons
  • "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."
  • "For the iPhone, the device diagram cannot be downloaded. You have to go to each device and download the device diagram for that device. E.g., suppose there are a 1000 or 2000 servers. You cannot go to each server or device to download a device diagram for each device. There should be a one-click solution for downloading all device diagrams."

What is our primary use case?

Device42 uses your infrastructure discovery and network device discovery to get information about your infrastructure CMDB. It uses this when you are migrating your on-prem servers to the cloud or VMware Cloud to public cloud. For our purposes, customers use it to discover their infrastructure, services, applications, features of those servers, CPU, memory, and RAM. All these details can be discovered in their infrastructure using Device42. Then, you can easily migrate to the cloud. 

We have used the solution in conjunction with our clients’ migration to the cloud. The view it provides of assets and application dependencies assists in getting things to work post migration because of Application Dependency Mapping. We can easily migrate the business and infrastructure applications, thus determining the other applications it is dependent on. This way we can easily predict how to migrate and the things that need to be done while migrating.

We provide support for Device42 as a managed service provider. Currently, I have two customers: one is on Azure and the other is on VMware.

I am using the latest version. 

How has it helped my organization?

It is good tool for our customers if they want to go into the details of their infrastructure for migrating their on-prem environment to the cloud.

Device42 provides almost all the details of your infrastructure. Its reporting is very good. It has reports that you can fetch easily and are easily readable. There are a few scripts that you can also use for downloading reports in different formats.

It requires only two or three ports to be open while doing discovery. Therefore, you can have an environment which can be installed in a DMZ environment or on the customer's environment. It won't affect the security or customer's infrastructure.

Continuous asset discovery lets you continuously monitor the resource utilization when using Device42, such as: 

  • Resources being used on your infrastructure. 
  • If there are new communications happening on your servers, then they are being captured in Device42. 
  • If there are any changes in your CMDB infrastructure, they are getting captured in your Device42 reports. 

You can download also these reports with a ServiceNow and other tools.

What is most valuable?

  • Device42 is very easy to install.
  • It has lighter graphics. The graphics are easily loadable.
  • The front-end is good and user-friendly. 
  • It provides network device discovery and Application Dependency Mapping.
  • 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.
  • It has a Remote Collector facility where you can use that facility to discover your DMZ environment as well as your load balancers and domain appliances.
  • It provides inbound and outbound connections for your servers.
  • Application Dependency Mapping helps us understand on which servers are our applications dependent and what things affect our application.

What needs improvement?

For the iPhone, the device diagram cannot be downloaded. You have to go to each device and download the device diagram for that device. E.g., suppose there are a 1000 or 2000 servers. You cannot go to each server or device to download a device diagram for each device. There should be a one-click solution for downloading all device diagrams.

For how long have I used the solution?

I have been using Device42 for two and a half years.

What do I think about the stability of the solution?

It is quite a stable solution. You can have 4 CPU or RAM for your appliance. You can also configure more CPU and RAM for your appliance if you want to discover more servers.

They have frequent updates, though sometimes you need to get Device42 updated to fix bugs.

Right now, we have two or three technical service engineers managing Device42.

What do I think about the scalability of the solution?

The scalability is good. Depending on the number of servers that you want to restore, you can scale up or down. You can have one or multiple Remote Collectors for more stability and load balancing.

We have three different customers using Device42, and I have supported seven to eight customers until now. One of our customers, they are doing their plans in waves: wave one, two, and three. In wave one, they managed to discover almost 500 servers. In their second wave, they helped manage 400 servers. In wave three, they are now managing 500 to 600 servers.

How are customer service and technical support?

It has very good, prompt support.

How was the initial setup?

It is very easy to setup Device42. 

What about the implementation team?

I have setup it 600 to 700 times. 

On average, the deployment requires only four to five hours. However, the requirements gathering that we need to forward to customers to follow their change process to open all ports may take two to three days.

There is no implementation strategy because it depends on customer. A few customers helped us and others deployed it by themselves. In these cases, we provide the documents, then the deploy it themselves. So, it depends on the customer.

What was our ROI?

The solution has reduced the time spent managing IT assets.

Customers are happy with the solution. They can easily deploy this solution for cost-effectiveness.

What's my experience with pricing, setup cost, and licensing?

The product cost is low. It is quite cheap.

Which other solutions did I evaluate?

We also evaluated Microsoft Mover, but it was not approved by our management.

I haven't used another solution with customers.

What other advice do I have?

It is a very good tool. It is very easy to use for migrating an on-premise to cloud. The tool is user-friendly, easy to understand, and flexible. It has good support. It is the least expensive. This is all beneficial.

I would rate the product as a nine (out of 10).

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner.
PeerSpot user
Manager, Endpoint Management at a retailer with 10,001+ employees
Real User
Provides a deeper understanding of how our applications talk to each other
Pros and Cons
  • "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."
  • "It would be nice for the agent to have an installer versus a single file across multiple systems."

What is our primary use case?

We wanted a rich database of all of our assets and multiple teams were keeping different Excel spreadsheets, etc. About two years ago, a consulting firm recommended Device42. We took a look at it and have been using it ever since. We collapsed a lot of information into it, then week by week more teams adopt it.

We are using the latest version that they have out right now.

How has it helped my organization?

Having general software inventory in one location has helped us tremendously, even around Service Desk. Our Service Desk tool integrates into the asset management. When a user calls with a problem, we can link their device to it. Then we see a history: 

  • Do they have old, aging hardware?
  • Does it need to be replaced?
  • Is this model continuing calling in for issues?

We have been able to make educated decisions about replacing hardware and software due to this solution.

We are doing discovery of cloud asset management devices. This has given us more rich enhanced data to make decisions on where to place things based on like-minded services.

I have used the solution in conjunction with audits of our IT assets. I am able to pull reports in minutes instead of it taking days of putting everything together.

It has helped us identify some areas of security enhancements.

What is most valuable?

The asset inventory and software inventory are the most valuable features. 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. From the software aspect, we have been able to keep a detailed history of software that has been installed on machines and version controls. Then, we are able to make educated decisions on, "Is this software being installed as a one-off and part of the corporate image or should it be deprecated as the software gets older where we plan to do upgrades this way?"

The solution’s automatic IT asset discovery and inventory functionality was great when we first implemented it. We made some changes that didn't allow us to use some of those automated discovery tools. However, the software was good and adapted to our needs. We just went in a different way using the same software. The asset discovery is very comprehensive. We found a lot of information that we didn't even know we had.

We use the solution’s Application Dependency Mapping. It has been able to help us with troubleshooting. We now have a deeper understanding of how our applications talk to each other.

What needs improvement?

It would be nice for the agent to have an installer versus a single file across multiple systems.

It'd be nice to have the reporting be a bit more user-friendly. The workflow could be a bit more intuitive. Though, the support has been great on helping us when we have ran into educational issues.

For how long have I used the solution?

About two years.

What do I think about the stability of the solution?

It is very stable and updated on a regular basis with new enhancements and features using a very agile approach. Every week, we can get a feature in the pipeline that we/they have needed.

We require two people for deployment and maintenance for Device42: a network administrator and a dedicated system admin.

What do I think about the scalability of the solution?

It is very scalable and have had no issues. We are running the device across multiple divisions, organizations, and regions across the globe. Device42 is everywhere in our company. There are 30 to 40 users, e.g., help desk administrators and auditors. We will potentially be using it for vendor management down the road. Also, the DevOps teams is using it for information.

In the beginning, the solution did not reduce the time spent managing IT assets since we didn't do any management. There was a lot of turnover of teams with every team doing it differently. Therefore, we had to focus a lot on it. Now, it's part of the day-to-day management.

Which solution did I use previously and why did I switch?

We previously used Excel spreadsheets.

How was the initial setup?

I took over the solution last year. I set up the whole thing up again from the ground up at that time. The setup was straightforward. The documentation was there. You just followed a few steps to get it up and running.

When we redeployed, it took approximately a week. It took a half a day worth of build, then a week to discover all our assets.

Our implementation strategy in the beginning was to start with each office and redefine what their needs looked like, then scan each network which had devices on it.

What was our ROI?

As we have grown the system, less time has been focused on managing managing IT assets. We don't need dedicated teams to do this anymore. We have been able to reduce this role to a shared resource across multiple teams.

We have seen ROI. We have been able to streamline multiple teams having different options on how to do asset management and doing different things into one process for every team.

What's my experience with pricing, setup cost, and licensing?

Our licensing costs are on a yearly basis.

What other advice do I have?

You should definitely implement this product. In a normal environment, it is a set and forget it type of thing.

In the beginning, the solution’s agentless approach to asset discovery was very impressive because we heavily utilized it. However, as we made decisions on the network to not trust any device unless it was on VPN, agentless didn't work for us. They had a solution that was good for us, so we were able to pivot to an agent getting that same deep, rich information. In some areas, we do run it agentless. It's just more often we are relying on the agent because of our own infrastructure changes.

Asset management is a difficult, time consuming thing. However, Device42 has helped me streamline that so I can focus on other areas that need improvement.

I would rate this product as a 10 (out of 10).

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Jeremy Rammalaere - PeerSpot reviewer
Corporate Information Technology Manager at Supply Point
Real User
Leaderboard
Seeing how things are connected, which server ports are plugged into which network switches, helps with network troubleshooting
Pros and Cons
  • "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."
  • "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."

    What is our primary use case?

    Our primary use case is to track all of our IT information in one spot. So instead of using spreadsheets and other tools, it's consolidated here for us.

    How has it helped my organization?

    We had all the information in a mix of spreadsheets, homegrown applications, and databases, and then we moved it all into Device42. For example, we had one system that was tracking our device inventory, and we had spreadsheets for IP address allocations, while password management was completely separate. This solution really enabled us to lump everything together in one place.

    Having the ability to see how things are connected and keeping track of, for example, which server, and which ports on the servers are plugged into which network switches is very helpful when we're looking at network troubleshooting, and we want to do things like mirror ports and mirror traffic. Tracking which MAC addresses belong to which devices is also linked in there.

    The topology view enables us to show how our applications interact with each other and with the rack elevation we can see the equipment in each individual rack and which power outlets they're plugged into. That has also been really handy in a few cases.

    It definitely saves us time, but I don't know how to quantify it because we've been using it for such a long time. I don't remember what kind of time it took to track down information in the past. Right now, it's super-simple to find whatever we're looking for. I would imagine it saves us a few hours each week.

    What is most valuable?

    Just having this solution at all has been really solid for us. If I had to pick one part of it, it would be a toss-up between the IP address tracking and the password management. I'm not sure which one of those I'd rank higher.

    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.

    As far as password management goes, before we had this we didn't have anything. We had shared passwords, which is always a horrible idea. Now we have the ability to know who has accessed a password, who's looked at it, and when it's been used or when it's been changed. That's helped us from a security standpoint.

    In addition, 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.

    It also helps us track equipment replacement to know when we have swapped out parts and how much money we've spent on a particular server over its lifetime. We try to utilize all the pieces of it that we currently license.

    We use it to track our servers, storage, switches, firewalls, and most recently we started putting our desktops and laptops in it too.

    What needs improvement?

    One thing I have brought up with their product team, and we opened up a case and a feature request for it, is having a requisition-style system in the software. Right now it does have the ability to track purchases, which is okay. But I would like the ability to create a request and say, for example, I want a new server. 

    The way that it works right now is that you have to create the server object before you can assign it to an actual purchase. Obviously you won't have the server until you've bought it, so it's something of a cart-before-the-horse scenario where, in order for me to create a purchase, I already have to have the device, which doesn't make sense. It's fine if you're entering the data after the fact, but I would hope to use the system in a pre-purchase scenario, where I or one of my technicians could log into the system, create the request, and then forward that request to my purchasing people or to our ERP.

    The other area where it causes us a little bit of a hassle is if I want to track the cost of spare parts. Recently I had to order about a dozen hard drives for servers. For me to use Device42, I had to wait until the drives came in so that I could create the drives and assign the serial numbers to them, and then assign a cost to each drive. A better scenario would be where I'd say, "Hey, I'm buying 12 drives," and be able to have 12 generic drives in the system without serial numbers. Then, once the drives came in we could assign serial numbers and then further assign drives to servers as we need to.

    I worked with their product team at least a couple of years ago to express that concern. They claimed to like the idea, but I haven't seen it implemented yet. I don't know if it will ever make the cut. And I would like it not to be a paid upgrade feature. If they could include it with the license we use, that would be extra nice.

    For how long have I used the solution?

    I have been using Device42 for at least five years, if not longer.

    What do I think about the stability of the solution?

    It's been very reliable. We had a case last year when it was unavailable because I failed to pay attention to the warnings about our license expiring. That temporarily caused us a glitch because I didn't have our subscription renewed on time. But that was entirely on me.

    What do I think about the scalability of the solution?

    I would assume it would be fine for all of our future needs. But we're a relatively small organization, so I don't think we're ever going to really stress it.

    How are customer service and technical support?

    Tech support has generally been pretty good. Over the years there have only been one or two cases that maybe took a little bit longer than I thought was reasonable. Other than that, they've generally been very attentive and responsive. There have been no major hiccups with any of their support.

    I've never had to escalate. The few times that I've had to talk to support, whoever I've talked to initially has been able to get things addressed for me.

    Which solution did I use previously and why did I switch?

    We were using spreadsheets and we had a couple of homegrown databases. We weren't using any commercial product prior to a Device42.

    We came across the solution because we needed to find a better way to do keep track of all the data. We did some Google searches at the time to see what other people were out there doing. I'm also part of a few different online communities, and I'm sure I asked around those, at the time, if anybody had thoughts or suggestions.

    How was the initial setup?

    The initial setup was very easy. It was restoring a virtual machine image. It gets delivered as a virtual disk file. Spin it up on your choice of hypervisor and it's ready to go instantly. For us it was ready to go, full-production. I'm sure there are some scenarios where it could get a little bit more complicated, but ours has always been very simple. It was deployed as a virtual machine. We didn't have any wrinkles.

    Even with version upgrades that have had breaking changes — and that we had to do backups and restores for — even that hasn't been that terribly difficult. I just I told the people that use it, "Hey, we're going to be down for about 20 minutes," and ran the upgrade and everything was good.

    In terms of a learning curve, it's relatively straightforward. There are a few things here and there that, when you come across them, seem a little bit backward. I can't remember specifically what those issues are, other than the purchasing one I mentioned. But it's mostly straightforward, mostly easy to use.

    What about the implementation team?

    What was our ROI?

    There is a value to it. 

    The part that makes some of the solution's add-ons a little bit harder for me to justify and get approved is that I don't have any mechanism to show how much they could possibly save us, or what we're currently doing on a day-to-day basis that they would somehow help us with. Maybe if they had some kind of ROI calculator or, "Here's what you could be doing if you added on some of these extra features," that might help.

    What's my experience with pricing, setup cost, and licensing?

    Their pricing model is very poor. For instance, software licensing, at one point in the distant past, was a standard feature. At some point they broke it out as a separate, paid license upgrade. That was kind of rotten. 

    Right now I'm looking at my license page and all of the add-ons are disabled because we didn't pay for any of them. The solution is helpful and it is useful, but it makes adding on any of the extra applications or any of the extra components cost-prohibitive, for us at least.

    Which other solutions did I evaluate?

    We've looked at a few different products. One of them was called Sunbird and there was something by HPE that we might have looked at a long time ago.

    Sunbird did not have a full web interface for the solution, so you had to have desktop software. Quite honestly, I wasn't interested in desktop software. I wanted something that I could hit with either my computer or my tablet, or even my phone for that matter, and still be able to get at our information.

    What other advice do I have?

    It's all pretty easy to use and you'll get out of it what you put into it. We try to make sure our information is accurate and up to date and we periodically do audit against the information to make sure it is current. The biggest advice I would give is to make sure you don't let your data get stale.

    Documentation is important. We've had internal problems where we've lost a hypervisor or our network has gone down and we haven't had access to it. Those scenarios have proven that we rely on the info and we need it. So having some kind of high-availability solution would be good for us at some point. We do have a standby server that takes backups of our data and sends it to a separate Device42 instance, but I have not experienced trying to fail over and make it active.

    Maintenance of the tool does not even require one person. It's just something that runs in the background and it doesn't take any extra effort, other than what we normally do with our virtual machines and hypervisors. We treat it the same as any other server that we manage. Because it's deployed as a virtual appliance, we count on Device42 to have things hardened and patched. I'm not sure if their normal software upgrades include any system-level patches, but it's nothing that we manage or maintain.

    There are five people using it across our organization. I use it in my role as IT manager. The others are server admins, a desktop admin, and a couple of people who have access to it to retrieve asset information.

    We're subscribed to just the core product and we utilize pretty much every bit of it. It would be great if we could get into some of the other stuff, like the application discovery and the application mapping; software license management would be sweet, and power and environmental monitoring would be nice too. But those features are all paid add-ons. Right now, the biggest challenge for us is what we currently pay with our base licensing. It's reasonable in terms of the world. We've looked at competitive products in the past and either the other products weren't as well polished and as well put together as Device42, or they were just completely out of our reach in terms of price.

    It has generally been a really solid and useful tool. It would be cool if they could get around to getting that purchasing aspect worked in. Other than that, it's been solid. It's done what we've needed it to do so far.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    Buyer's Guide
    Download our free IT Asset Management Report and find out what your peers are saying about Device42, ServiceNow, BMC, and more!
    Updated: July 2022
    Buyer's Guide
    Download our free IT Asset Management Report and find out what your peers are saying about Device42, ServiceNow, BMC, and more!