ManageEngine has a great patch management feature. It is actually one of my favorite features because it allows you to approve or decline whichever windows or third-party patches you want. You can also schedule them during off hours, force reboots, or even wake devices up for patching. ManageEngine also has a very small yet powerful installation file, which I found very easy to deploy across the network even though I have several remote locations. Considering that ManageEngine is a multi-asset and IT process manager, it enables you to effectively manage all of the assets very well and has a very intuitive and dynamic interface.
One thing I dislike about ManageEngine is their software deployment tools. It’s great for mass deployments but I wish it included one-off deployments to a single computer. Also, in order to enable the file transfer option when you are using it for the first time, you have to install a plugin. Sometimes the control center can be a little slow, too.
Microsoft Intune is robust and it allows you to deploy applications to its enrolled devices. This makes it a beneficial solution in asset management and also patching machines. It also gives you the ability to restrict user actions on their machines, which I find to be very helpful from a security standpoint. In general, Microsoft Intune’s enrollment process on devices is straightforward and easy. You can set policies, and administrators are able to guide users on how to enroll their machines. One major downside of Microsoft Intune for me is that it has inferior and poor quality device reporting.
Conclusion: Overall, I would recommend ManageEngine because not only is it a well-developed tool, but it also provides an excellent adaptation to its interface, and I have found its implementation and use to be nothing less than exceptional.
Manager, Information Technology Support at Innoveo
Real User
2021-10-25T07:55:59Z
Oct 25, 2021
Hi . I use both systems . Intune is simply too good to configure a system via autopilot and enforce AD/ Azure AD policy whereas Desktop Central is excellent for patching
Desktop Central is great for patch deployment and software deployment but falls short on many other fronts like correctly reporting information - I had to raise tickets to their support to get it fixed
Intune too has its issues - I does not have an inventory reporting functionality
The company portal is an app which has to be installed on the endpoint . The reporting mechanism is not on par with Desktop Central.
DC does not have the OS deployment capability ( OS Deployer is an add on) whereas Intune has the Autopilot capability built into the system to remote install the laptop including enabling bitlocker encryption
DC has strong patch deployment capability whereas its bit vague on Intune
In the competitive landscape of endpoint management, ManageEngine Endpoint Central and Microsoft Intune both present robust solutions. ManageEngine Endpoint Central has an edge in broader endpoint management across diverse operating systems, while Microsoft Intune is particularly advantageous for organizations heavily invested in Microsoft products.Features: ManageEngine Endpoint Central excels in software deployment, asset management, and is particularly strong in patch management. Its...
ManageEngine has a great patch management feature. It is actually one of my favorite features because it allows you to approve or decline whichever windows or third-party patches you want. You can also schedule them during off hours, force reboots, or even wake devices up for patching. ManageEngine also has a very small yet powerful installation file, which I found very easy to deploy across the network even though I have several remote locations. Considering that ManageEngine is a multi-asset and IT process manager, it enables you to effectively manage all of the assets very well and has a very intuitive and dynamic interface.
One thing I dislike about ManageEngine is their software deployment tools. It’s great for mass deployments but I wish it included one-off deployments to a single computer. Also, in order to enable the file transfer option when you are using it for the first time, you have to install a plugin. Sometimes the control center can be a little slow, too.
Microsoft Intune is robust and it allows you to deploy applications to its enrolled devices. This makes it a beneficial solution in asset management and also patching machines. It also gives you the ability to restrict user actions on their machines, which I find to be very helpful from a security standpoint. In general, Microsoft Intune’s enrollment process on devices is straightforward and easy. You can set policies, and administrators are able to guide users on how to enroll their machines. One major downside of Microsoft Intune for me is that it has inferior and poor quality device reporting.
Conclusion:
Overall, I would recommend ManageEngine because not only is it a well-developed tool, but it also provides an excellent adaptation to its interface, and I have found its implementation and use to be nothing less than exceptional.
Hi . I use both systems . Intune is simply too good to configure a system via autopilot and enforce AD/ Azure AD policy whereas Desktop Central is excellent for patching
Desktop Central is great for patch deployment and software deployment but falls short on many other fronts like correctly reporting information - I had to raise tickets to their support to get it fixed
Intune too has its issues - I does not have an inventory reporting functionality
The company portal is an app which has to be installed on the endpoint . The reporting mechanism is not on par with Desktop Central.
DC does not have the OS deployment capability ( OS Deployer is an add on) whereas Intune has the Autopilot capability built into the system to remote install the laptop including enabling bitlocker encryption
DC has strong patch deployment capability whereas its bit vague on Intune
This list goes on so Im stopping here