Share your experience using Cygna Diamond IP Platform

My main use case for Device42 is day-to-day asset discovery in our organization where we discover our devices like virtual machines, NICs, and operating systems such as Windows and Linux. I use it to track the expiry of certificates through a dashboard to ensure proper change management for renewals.

For asset discovery with Device42, I monitor a few VMs, and for certificate management, I deal with applications that utilize TLS certificates. A recent situation that was particularly helpful was our renewal process which occurs every six months to a year where I ensure the certificates are up to date and monitor our virtual machines on the dashboard including both on-premises and cloud resources.

I use Device42 to integrate with our Jira for our ticketing system, which is very helpful in providing alerts about our inventory's status, whether it is end of life or needs updates. It aids in certificate management by informing us through Jira, thus supporting our reporting processes and compliance efforts.

The best features of Device42 include the asset inventory, which I find very important for organizations to maintain an up-to-date inventory of their end devices and users for auditing purposes.

Device42's asset inventory feature helps our organization by making auditing easier as I can generate reports and automate dashboards for top management. I also plan to leverage features related to AI and artificial intelligence to integrate with change management systems like Jira or ServiceNow.

Device42 positively impacts our organization by providing dependency mapping for our devices, and it integrates well with applications, especially our cloud service Microsoft Azure, giving us complete visibility across our infrastructure for efficient operations and modern compliance.

To improve Device42, I hope it can revolutionize ITSM with continuously updated configuration data while simplifying compliance and license navigation. However, the dependency mapping feature needs improvement as it currently requires manual identification of device relationships.

Regarding improvements to user experience, while it is generally acceptable, I have faced some issues needing OS upgrades, which have occasional blockers. Support from Device42 has been helpful in resolving certain issues, particularly with dependency mapping. However, the asset inventory and certificate management functions work well.

I have been using Device42 for the past two years.

Stability for Device42, in terms of reliability, is generally acceptable. However, it requires correct configuration to function as demonstrated.

Device42 handles scalability well. I have successfully scaled a few times, accommodating our growing assets.

My experience with Device42's customer support has been positive, particularly with Karl Wasberg and Wahi Nascisian, despite the challenges posed by time zone differences.

I evaluated other options before choosing Device42 but ultimately opted for it.

Device42 was not purchased through the Azure Marketplace. It was acquired through our organization via our partner Aizeno, and I obtained the image from the Marketplace.

I have not seen a return on investment with Device42, as it primarily provides information and not revenue. I have just recently upgraded our licensing to avoid unnecessary charges by limiting what I discover.

I am not involved in the pricing details, but I believe the costs are manageable and within our budget range.

If others are considering Device42, it depends on their budget. There are many asset discovery tools available, and they should evaluate whether Device42 is the right tool for them.

Device42 is deployed in our organization on a private cloud, specifically under Microsoft Azure, and it is not on-premises. I would rate this review a seven out of ten.

Private Cloud

Microsoft Azure

My main use case for Device42 is for transformation projects to assess the application workloads of different organizations that are ready to move to cloud.

In one of those transformation projects, I used Device42 for assessing application dependencies and obtaining infrastructure details such as current usage, how applications are dependent on each other, networking components, memory, CPU, and other details. This allowed me to get the as-is information and application dependencies to define how to move the workloads forward and whether the applications were ready to move to cloud, essentially to check their readiness and fit for cloud migration.

I have used Device42 for transformation and modernization projects, and it has been very useful because I obtained as much detail as required for successful execution of the project.

Device42 offers great and detailed application dependency data, networking components, and provides as-is details with interconnections between applications.

The detailed application dependency data and networking components stand out in my projects because application dependency is a major factor that helps evaluate how applications and workloads will be migrated and in what move group. It is easier to define the move groups of applications to be migrated to cloud using the application dependency data, so I can easily decide what set of applications can be moved together. This is very helpful.

Device42 has positively impacted my organization by helping us lead successful migration and transformation projects, and I have successfully completed cloud movement implementation from standard data center deployments to the cloud. It was very helpful in both transformation and transition phases.

Device42 can be improved by adding more reporting features and architectural diagrams. If visual representations for application dependencies could be incorporated, that would be helpful.

I have been using Device42 for two years.

Device42 is stable.

Device42's scalability is good because it can handle larger workloads. I have not faced any challenges in terms of scalability with Device42.

Customer support for Device42 is effective. I receive responses to queries or issues related to the tool within 24 hours, and critical issues are also addressed quickly.

Negative

I was previously using other tools such as Azure Migrate and Cloudscape before switching to Device42.

I have seen a return on investment because if I am well-versed with the tool, I would need fewer people to evaluate or perform manual assessment. In that way, it is helpful.

Before choosing Device42, I evaluated other options and found that Device42 is the more effective tool that can be used.

Specific outcomes and metrics from those migration projects that I can share include that I identified very accurate details. I did not face any migration issues, and the migrations were quick and effective. Application testing post-migration was also completed very quickly because I had the pre-assessment and assessment details ready to use because of Device42. It was accurate and very effective.

On a scale of one to ten, I would rate Device42 an eight. I chose eight because I think overall everything is great about the tool and it really helps in assessing applications and migrating workloads to cloud. However, I still feel there is always room for improvement in everything.

My advice to others looking into using Device42 is to explore their options. It depends on the organization and how they want to utilize which tool. I had a great experience using Device42, so I would recommend people to give it a try for transformation projects. I would rate Device42 an eight out of ten.

On-premises