ManageEngine Endpoint Central Reviews

We primarily use the solution for managing patches and centralizing updates for applications. We can also blacklist and whitelist applications on our users' laptops.

Besides the office and operating systems, there are lots of other products that need to be taken care of, which are beyond your control. I have 250 endpoints here, sitting here and 100 roaming users, so for me, each and every application in the current scenario is very difficult, wherein the digital signatures are happening, the tokens are happening, which ask for the updates of Java, which ask for the update of a browser. It is very difficult for me to do the update of every PC individually. However, when handled in a centralized location, I get the control I need so that I can see which endpoint needs to be updated, which endpoint has been updated, et cetera. This is very helpful for me, very good.

The solution is very easy to use.

Everything is easily centralized and managed under this one product.

When we do the patching, I can select the applications which are applicable to my network. We will get multiple templates and tons and tons of applications, however, you can select and download and it'll start patching. It'll consume lots of bandwidth and disk space. What you can do, is that, whichever applications are applicable for you, you can select those applications and it will start patching only those applications. It will reduce the bandwidth, it'll reduce the disk space, and tracking will be much easier.

In terms of the warranty, you need to install the agent on the laptop, or desktop and once the agent is installed, when the communication happens, it fetches the entire detail of the hardware, software, and everything. The beautiful thing with that is it gives you the warranty information also, whether the product is out of warranty or not. I can set an alert for devices where the warranty is going to expire. I'll get an alert that it is going to expire in one year, a month, six months, whatever the term I defined.

Since I'm able to see whatever the applications are installed on the user's PC on the endpoint. Sometimes most of the roaming users who are out of my network tend to install applications that are not applicable as per company policy. You can define which applications are allowed. There was a couple of cases where my users had installed a YouTube Downloader, and while downloading and installing that filter, by default or by accident, they installed some of the adware also. That won't happen under this solution.

Desktop Central gives me an option wherein I can prohibit any software. When I blacklist software, the user will get an alert saying "This is prohibited software." Then they call IT and I'll get a notification. For me, I'm very much in control of my network now. I have the power of whitelisting or blacklisting.

For users that work from home and are not in the office, sometimes minor things happen, such as email not working properly, et cetera. Desktop Central will give me remote control of a user's machine and I can troubleshoot or find out what the issue might be. If something needs to be installed, I can do it remotely as well. I don't need to buy TeamViewer or AnyDesk or other software. 

There are so many features available to us. They've added a lot over time. Initially, the asset management was there, however, there were no warranty features. The remote control was there, however, there were various limitations. They've just gotten better and more robust over time. 

For the most part, all of my needs are met with this product.

I would like to see them come out with a SaaS version of the product in the future. There are dependencies with on-prem. For example, since it's on my data center, my bandwidth, it is totally dependent on my network. On the cloud, I don't have to worry about anything. 

One feature we're testing is when we have a laptop with just a DOS OS and we need to do a full installation, including installing the underlying OS. I'd like to have the option where we could create a template to allow the system to install the OS with the typical software. It's a feature we're testing now to see if this is possible. We don't use it yet. However, I'd like it if we could just run one script, one command, and then get an alert when the process is done so that I can go in and configure emails or whatever else I need so that it is ready for the end-user.

I've been working with the solution for around three years. 

The stability is very good. We have been using it for the last three to four years and there is not a single downtime where the product has failed. In terms of service updates, service backups, and whatever the features are coming, we have faced a 99.9% success ratio.

In the initial stage, at that time, we had a hybrid environment internally, where we had Windows 7, Windows 8, Windows 10, and some of the servers which had Windows 2003 OS. There were compatibility issues, however, we've since migrated and upgraded the systems and there is no longer an issue.

The solution is scalable.

We are using the solution quite extensively and have about 250 users.

Technical support has been good and we've been satisfied with their level of service. They have a good inbuilt chat option if you need to reach them. They have a technical team right within the solution that you can talk to in real-time. They can provide workarounds or escalate issues quite easily.

We used to have a Windows SUS server for patch management. There were other products that needed to be taken care of - for example, Adobe, the WinRAR, and multiple other software, which needed to be patched, and in which the assets needed to be managed. There are things such as warranties that need to be managed, and their tracking needs to be done, we were looking for an application wherein we would get everything on a centralized product, which is why we chose this solution.

The initial setup was straightforward. At the time, when we were in the phase of testing for the product, we did whatever testing to fulfill our requirements. That way, when we went into production, there were not any hiccups.

Deployment took around ten to 15 days, due to the number of endpoints that needed to be done, and the number of products that needed to be whitelisted. Also, everything needed to be configured. Around four to five people were involved in that project.

In terms of maintenance, if there is any product update, or if the application will have any service package coming, then I need to take downtime, to go through everything and do testing of the service pack to see whether it will hamper any current writing process or not. Once I do it in the test environment, then I have to put it in production.

That said, once we move to SaaS, this process will be obsolete in the cloud.

I have two dedicated resources for maintenance. That includes me. The other person looks at the patch management and the warranties. I look at server maintenance and deal with whatever resources are required for servers. 

We were able to set it up ourselves in-house. 

At the time we signed onto this product, it was a bit more expensive than SolarWinds, however, I'm not sure if that's since changed. 

We looked at SolarWinds, however, we went for the Desktop Central. We evaluated it and we found Desktop Central was quite user-friendly in terms of patch management and in terms of asset management. Right from the user inception, until the exit, everything is tracked under Desktop Central, whatever the asset allocated to the user, whatever the warranty, whatever the application, the install, everything is tracked under the Desktop Central.

Kaseya was also evaluated which was on the cloud. However, it was costlier and there were manageability issues. SolarWinds was a bit very complex in terms of handling. Technical support was also different as they only have an email option.

I'm a customer and an end-user.

Currently, we are using on-prem. I am waiting for SaaS, however, I really don't have the SaaS version. It'll be very good if they offer a SaaS version; my manageability will become very much easier.

If you're looking for third-party patch management, asset management, and/or remote control support, then this is the best app. For remote control, it doesn't require much bandwidth. Often, people sitting in a remote location are using their 3G data cards or mobile data, mobile phone, and they still got connected with the seamless connectivity. There has been no issue.

I'd rate the solution at an eight out of ten.

Our primary use case is to manage most aspects of the endpoints in 21 remote sites. All sites are connected via IPSec VPN mesh and have distribution servers at each site, OS deployment, software deployment, patch management, remote administration, configurations, mobile device management, and browser management. One of my favorite features is a simple remote CMD. This enables us to troubleshoot certain things without interfering with the user desktop session or needing to ask them to take remote control of the machine. It's very valuable being able to fix a problem without stopping user productivity.

It has become a single pane of glass for a majority of client support and administration. It has enabled my team to quickly identify machines, who is using it, what applications are installed, and a huge set of tools to solve most problems. OS imaging and deployment has significantly reduced the amount of time and resources needed to deploy a large set of new computers or even just reimage a problematic PC because of malware or other problem that would take much longer to troubleshoot. Software deployment has taken the task of installing a common application on hundreds of computers to just a few clicks.

Honestly, I have to say all features together have become the Swiss army knife of desktop management. They all work hand in hand. Software deployment saves an unbelievable amount of time installing an application on hundreds of computers. A full suite of remote administration tools to troubleshoot problems or make a change via PowerShell without intruding on the user desktop. Mobile device management eliminated the problem of missing iPads or iCloud locked tablets and phones. The mundane process of patch management is now a breeze.

I really feel like asset explorer should be a component of desktop central. That would make it the ultimate desktop management tool. This would also simplify the asset management role since an agent is already being deployed and assets could be added at the same time.  the CMDB would be quickly populated with a PC hardware and software inventory along with user relationships. Device assignment and tracking would be another added value. Adding that feature set would tie everything together and be the one-stop-shop of desktop management suites.

Approximately a year.

It's very stable it just seems to always work.

Very scalable. Distribution servers are the main factor.

The few times we have contacted customer support they have always very quickly solved the problem. Every support agent has been very professional and curteous. 

We did not use a different solution. We did a trial Desktop central and immediately fell in love with it and have not regretted the decision.

It was very easy to setup initially. The side effect is you will spend a lot of time tweaking and fine-tuning everything. 

In-house.

Time saved is money saved.

Go with what you can afford. Every part of the application is going to save time and money and a very worthwhile investment.

We did not evaluate competing products. Everything we were looking for was there and worked well and was easy to use.

We use this solution to manage all aspects of our use of Windows.

The centralized control of all of our Windows hardware that this solution offers has been most valuable to our organization.

Compared to the solution we use to manage our Mac products, this solution lacks the ability to create dynamic groups. We would like the ability, for example, for machines that have been upgraded to form part of a grouping based on this upgrade. 

Another feature we would like is a distribution server to allow communication between our company's different servers using the internet. I have already suggested this functionality and it is being worked on by ManageEngine. 

We have used this solution for more than one year. 

This is a stable solution. When there are bugs, they are fixed with new updates which are easy to install. 

This is a scalable solution. We have more than 5000 users.

The customer support team is great. I have not experienced a support team like this using any other solution. There is an online chat channel that is easy to use. 

The initial setup was straightforward. Vendor support is not needed. The solution's support team are helpful and good at providing support. 

I haven't had any issues using this solution and would recommend it to other users if it fits their business requirements. 

I would rate it a nine out of ten. 

We use the product to know about our assets and manage remote support. 

The tool's security can be better. 

I have been using the product for five years. 

The tool is stable. 

The solution is scalable. My company has 7000 users for the product. 

We don't require any support from the product since we have a good engineer. 

The product's setup is easy. We have around 45 people to manage the tool. 

The solution's deployment was done in-house. 

I have seen ROI with the tool's use. 

The product is cheap. 

I would rate the solution an eight out of ten. 

We deployed ManageEngine Desktop Central mainly for the patching of systems. Additionally, we have used it extensively for doing ad hoc software deployments, making changes to systems, such as if we need to deploy a registry fix. The solution also allows us to have local repositories. When we do a deployment at a local operation, everything is deployed locally from within that operation. We do not have to use the network to receive anything.

We do not use it for remote assistance very much, and the reason is we use ScreenConnect. I know that the Desktop Central remote control works. The other thing that we use Desktop Central is to receive quick access via the command line. It's very convenient that we can open a command prompt on a remote host.

We have seen a lot of benefits in reporting, we are able to pull a lot of information. For example, we can go ahead and pull out a report saying how many Windows 11 machines are in the organization, how many machines are missing patches that are older than 60 days, and how many machines have a specific version of the software.

ManageEngine Desktop Central automatically alerts you if there are newer releases or updates. You do not have to go to their website and check.

Your agents or your assets that are managed by ManageEngine Desktop Central, if you have a relay server, the agents will work over the internet. If there is an asset, then there is some vulnerability. As long as it's powered on and connected to the internet, it doesn't need to be on the corporate-wide area network. As long as it's on the internet, you can go ahead and manage it.

ManageEngine Desktop Central should keep up with some of the features that other major vendors are providing, such as Microsoft. 

If this solution could include the MDM component, then it would be a very strong contender with the other competitors.

The OS deployment of the solution could improve, I tested it before, and it was weak.

I have been using ManageEngine Desktop Central for approximately four years.

The stability of ManageEngine Desktop Central could improve. We have found that at times it can become a bit unstable. We have had issues with that in the past, but not much lately. 

The performance of the solution is good.

The solution is easy to scale. What you need for your scalability is to have more assets. You can scale the resources, such as the processor and memory. The way to scale would be doing the repositories at sites.

We have approximately five IT users using this solution in the organization.

We have been using ManageEngine Desktop Central extensively in my organization but in the last year or so more we have been focused more on the SCCM. We plan to increase usage as the company expands.

I've spoken with technical support in the past. It's a hit and miss, depending on who you speak with support. Some agents are very strong and some agents tell us to read an article and come back if we have any more problems.

The technical support could improve by being more consistent.

I have used other solutions in the past.

We do our software deployment based on a logical grouping of computers. ManageEngine Desktop Central provides the ability to create groups or a collection of computers. That's what they call it. If we can create the collection, of the software we've just uploaded to ManageEngine Desktop Central, it synchronizes it against all repositories. Then based on that collection, we only need to tell it to deploy that piece of software to the computers.

We can also use another tool for deployment that Desktop Central has which is really nice called the self-service portal. We have a list of applications that are common and ones that are not. The applications that not every user uses. For example, in the SAP GUI, not everybody uses SAP. We can have it published in the self-service portal and if the user needs it, they can deploy it themselves.

We use one person for the deployment of the solution. However, the deployment difficulty and time depends on a few factors, such as the size of the collection, how many computers are you deploying it to, how many users, and what is the size of the package and their complexities. Usually, once it's all replicated and the agents are online, if we tell it to deploy, it's almost immediate. Additionally, we do deployment based on off-hours, we can do them immediately or we can schedule deployments.

When the solution is up and running it does not require a lot of maintenance because it uses PostgreSQL, they have routines that manage the database. The only thing that you need to keep your eye on is the size of the repositories because as you patch more and you deploy more software, the size of your repositories grows and you need to keep a watch on this.

We make everybody else look good. We have received a return on investment because we were able to deploy applications a lot easier where we do not have to get the field services team involved.

The solution is very affordable.

The nice thing about ManageEngine Desktop Central is that when it's time for renewal, you can increase your footprint by the number of assets you're managing. I can scale up and down based on the size of my organization.

My advice to those wanting to implement this solution would be if they have a small IT department and they do not have strong IT people, ManageEngine Desktop Central is pretty simple to deploy. The complexity is not as big as an SCCM or some of the other products.

In terms of training, there's a lot of things on YouTube that tell you exactly how to do it. There is some good documentation from ManageEngine Desktop Central. It is very simple to deploy and get it up and running.

I rate ManageEngine Desktop Central an eight out of ten.

We carried out a POC on Desktop Central before implementing and it's been in production for two months. Our use case is for patching third-party applications and Windows applications. We use the solution extensively so that aside from the monthly scanning we use it to work on Microsoft vulnerabilities.

We are customers of Desktop Central and I'm an IT Manager. 

Previously, our monthly maintenance would have taken about eight hours, and two or three people continuously on a laptop. Our maintenance is now carried out by this solution and once it's done there just needs to be a check for errors. It's time-saving and resource-saving which is pretty good. 

The patch management is really wonderful, it's effortless and just a matter of building a few configurations and creating a few templates which can be reused. The UI is quite good and user-friendly. 

There are a few basic things that haven't been configured in the tool. We're dealing with 600, 700 servers. The way the solution has been configured means you can only see 500 systems at a time. The company has acknowledged that this is an issue but they haven't worked on it yet. It's a little strange given the amount of time the product has been on the market. 

We're working on migrating to Azure. It involves a new patch that was not picked up by Desktop Central. I think it's a problem for them because Azure is everywhere right now and they don't seem to be up to date with the new patches. More needs to be included because everything Microsoft is launching now is more related to Azure.

I've been using this solution for six months. 

Performance is good and stable. If it's working on 600 servers at a time, there is a 90-minute window that it uses to communicate with its agent, and that's divided between all the servers. It can hamper performance at times when compared to other tools where you just click and everything is communicated without any wait time. The IT Ops team uses Desktop Central which, in our company, is two or three people. 

We haven't yet scaled but I believe it will be quite easy. 

All the ManageEngine products are pretty straightforward when it comes to implementation. There are a few configurations you have to do on a network level for the codes, but it's not complicated. I carried out the deployment with one other person. We contacted the vendor a few times for some assistance but that was it. The POC took about a month and the actual deployment took a week to 10 days including configuring everything on the network level.

In terms of maintenance, the server and installed agent need to be updated on all servers. You do have to check it on your test environment to make sure everything is compatible with a virtual environment, otherwise it could crash your VM. 

The solution is relatively cheap because we purchased the full package. For now, we're only using patch management, but it offers many other things such as software deployment, the ability to create configuration packages and install new software. There are no additional costs to the licensing fee. 

We only recently started using Desktop Central, so we're comparing the results with another solution use, BatchPatch. The Desktop Central UI is very good and easy to use. BatchPatch is a cheaper product so it's more complicated and the UI is not as good. What BatchPatch does have that's lacking in Desktop Central is the granular representation of progress and what's happening on the backend. BatchPatch gives you a clear picture of what's happening step by step and progress per server; it gives you specific errors so you can check and troubleshoot. Desktop Central lacks that visibility. If you're carrying out maintenance of 600 servers, you need to have that visibility, so that if something's not right, you can look into it instead of having to wait eight hours.

If you're new to the solution, check your requirements because the solution is not suitable for every situation. We're using it for a data center, so we configured it differently. If, for example, you're dealing with local laptops on office premises and you're looking to do patch management, a product like Ivanti might be more useful. For us, Desktop Central is pretty good because we are working on servers, and the vulnerability checks we do on the security base are pretty high, so the patch management option of Desktop Central is pretty good. 

There is room for improvement, so I rate the solution eight out of 10. 

I like that we can manage everything totally in one dashboard. We can install software easily. Anyone can handle the installation. It's got good documentation. 

The setup is pretty simple. 

It's scalable. 

The technical communication needs to be better. They need better technical support.

The solution is expensive. 

I've been using the solution for one to two months. 

The product is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. I'd rate the stability eight or nine out of ten based on its reliability.

It is scalable. It is simple to expand. I'd rate its ability to scale eight out of ten. 

Technical support has not been great. I haven't been pleased with their ability to assist when we need help. That said, there are some technicians that are good if you can get a hold of them.

Negative

It is easy to set up the solution. I'd rate the ease of implementation nine out of ten. It is not overly complex. 

It is a pretty expensive solution. With one being cheap and ten being expensive, I'd rate the affordability at a nine out of ten. Compared to other products, it costs a lot. 

I'm a customer and end user. 

I'd rate the solution nine out of ten. I'm pretty happy with its capabilities. 

We use it for Windows patching, third-party application patching, and third-party application deployment. 

The advantage of this solution for us is that it has basically centralized all our IT support, both remote and on-prem. We no longer need to do a lot of sneakernet. We're basically doing full remote support with it.

This solution has many valuable features. It's a complete product that allows you to remote troubleshoot, has an inventory of systems, as well as other things. We own the entire suite. The UEM suite allows us to deploy Manage Patching, Deploy OS' as well as MDM Management. We use the entire Swiss Army knife of the product. We use some other ManageEngine products and there's seamless integration between them. They've implemented in-application support so you can type a question to support and you'll get a real time reply, which is great. They really listen to their customers and try to proactively support them. They're constantly listening to feedback and making improvements on the product. It's one of those things where they listen to the customers and they're constantly evolving the product.

There are occasional glitches but they deal with it very quickly and efficiently. They've actually just rolled out a whole new endpoint security add-on that includes the features I've been looking for. 

I've been using this solution for 10 years. 

The solution has been fairly stable. It's evolved over time and they've come a long way. It's been a consistently stable platform. We've previously used things like WSUS and Intune for Window Patch deployment, ManageEngine is by far easier to use than those products. 

This is a very scalable solution. It's deployed to our entire organization, so that's about 400 users.

The technical support is great. The challenge is that sometimes support has to go back to development and the lead time can take a while. It's no different to any other company. They're all going to do the same thing. I'd much rather have them fix it right the first time versus coming back constantly with band-aids.

The initial setup is easy. You build a server, you install, you run the executable, it installs. It has a self-contained database and it does its own thing. You're up and running in 10 minutes. Obviously, like any product, it's going to take you time to evolve the product, to use the product, to get to know the product, but you can be up and running in as quickly as 10 minutes.

The cost is fairly reasonable for what you're getting. As an end user, you always want everything for nothing, but the reality of the matter is you get what you pay for so I think the price is fair. If you compare it to things like other patch management and third party tools, I'd say the price is probably fairly good.

We've looked at a lot of solutions and, value for money, this product can't be beat. They're always packing more features into it. We've looked at a couple of other products and they're just more cumbersome to set up and more expensive.

It's worth taking a good look at this solution because I think it's a really good product and it has a lot of features. It has a lot of value added and they have great support.

I would rate this solution a nine out of 10.