ManageEngine OpManager Reviews

I am working on two projects. Currently, I am with one of my clients on the task of ManageEngine manager. They want us to simply batch ManageEngine. I recommended ManageEngine batch OpManager, and I have to report to them why they should choose the batch manager. I am searching for reports and working on service management, operation management, and access management.

I like all the features. I will mention NetFlow OpManager ABM and port monitoring. Managing platforms and network device virtualization on one platform is beneficial. I can easily configure it. The dashboard is unique and user-friendly. Most of the work is straightforward, making it easy for users or those monitoring it.

We manage a client's network. We put all applications/devices into ManageEngine OpManager. This allows us to manage everything from a single interface.

It's not just about endpoint devices; it also improves switches and servers. For example, if we have the same switches across our organization, we can apply a patch to all of them at the same time. It is really easy. 

A good example is with vehicle tracking. We installed a device in our vehicles, and OpManager is able to monitor their status. We offer vehicle tracking and support services, including driver behavior management, and we can pull all that information directly from OpManager.

This eliminates the need to switch between applications to view job management details. OpManager can monitor it effectively.

OpManager has so many good options. You can manage your entire network with it. PRTG doesn't have that capability. It has scripts you can run, but not the options OpManager has. There are so many other little options that are very good.

Real-time monitoring and automation benefit the organization. OpManager can monitor network utilization, downtime, and services in real time.

We can monitor server bandwidth and disk usage. If there's a cap, it will alert you. It's real-time monitoring for all processes. For real-time monitoring, you need an agent. It will install the agent and give you real-time monitoring. PRTG doesn't have an agent, so it can only update after a time interval if a server is down. There is a huge difference between PRTG and OpManager.

I have had a gratifying experience with ManageEngine OpManager. The solution is easy to use and implement, and almost all the desired features can be obtained from it. Compared to other deployed solutions, ManageEngine OpManager works satisfactorily with our company's environment. ManageEngine OpManager is also more affordable than competitor solutions. 

The ease of use and comprehensive integration are the most valuable features of ManageEngine OpManager. The product offers a straightforward integration of a multitude of devices, networks, storage, and services. The historical reports provided by ManageEngine OpManager are crucial for our company in identifying incidents and errors on devices or monitoring points. 

When it's tried to connect a domain controller for monitoring to the tool, it's mandatory to use a domain admin privilege for the integration. Whenever the domain admin is changed for the solution, monitoring processes come to a halt. Our company hasn't been able to fix the aforementioned issue. 

The tool can create a high-privilege service account to monitor the domain controller. WMI and SNMP integration with the domain controller should be seamless, and domain admin issues should be resolved in ManageEngine OpManager.  

We primarily use the solution for monitoring servers, networks, and security.

We run weekly and monthly reports to provide exceptions. And yeah, it's helped our organization remediate problems proactively.

Our primary use case for the solution is monitoring all the infrastructure in our company.

The dashboard, versatility and larger horizon are valuable.

We use the solution for monitoring devices, health checks, performing some level of monitoring tasks, availability management, and capacity management. We also use it for some level of network bandwidth utilization. The technical reports available in ManageEngine OpManager suffice our specific needs.

The solution's most valuable features are reporting, event notifications, and alert management.

The features we found most valuable in ManageEngine OpManager are the probe server and reporting because they're pretty good features.

What I'd like ManageEngine OpManager to improve on is artificial intelligence.  In particular, the machine learning feature should be integrated with the sensor flow. Doing this will give leverage, especially when you look at other products such as the Cisco DNA Center. When a switch goes down, I should be able to build on the correlation of other physical devices it's connected to so that I can integrate that with my CA CMDB. The ManageEngine OpManager team needs to draw a long-term roadmap where that feature becomes an integral part of the solution because right now, machine learning in ManageEngine OpManager is a long process. The solution doesn't have MLS search and I want to see ML being developed and applied for CA CMDB to greatly reduce the burden of tying everything.

For example, if I have a data center switch that goes down now, I should know what server it's connected to, and when that switch goes down at twenty-four ports, I would get twenty-four alerts for different devices plugged in. I should be able to make a correlation that the major problem lies in the switch and not with the twenty-four elements connected to that switch. That is where machine learning should come into play and the ManageEngine OpManager AI should indicate "This is where the root of your problem is."  It could be difficult, but this is a feature that should be improved or added to the solution.

What I'd like to see in the next version of ManageEngine OpManager is for the machine learning and AI to be tied with the correlation engine because, at the moment, the existing correlation is lacking in terms of contextual awareness. Contextual awareness has to be more customized so that the operator or the person building or customizing the tool should have the flexibility to tie it with the CA CMDB application and the underlying inventory. This way, ManageEngine OpManager becomes more of a straightforward, next-generation solution concerning monitoring. For example, another player like New Relic has an application management module that's far ahead, but it's still lagging and would still need to catch up in terms of managing needs.

ManageEngine OpManager has integrations through APIs, but still needs further enhancement because there are still certain applications that would take hits, so the level of contextual awareness needs to be built on more, and that takes time.