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).