No more typing reviews! Try our Samantha, our new voice AI agent.

ManageEngine OS Deployer vs Microsoft Intune comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 25, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

ManageEngine OS Deployer
Ranking in Configuration Management
24th
Average Rating
6.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Microsoft Intune
Ranking in Configuration Management
2nd
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
378
Ranking in other categories
Remote Access (2nd), Enterprise Mobility Management (EMM) (1st), Unified Endpoint Management (UEM) (1st), Microsoft Security Suite (1st)
 

Mindshare comparison

As of June 2026, in the Configuration Management category, the mindshare of ManageEngine OS Deployer is 1.6%, up from 0.8% compared to the previous year. The mindshare of Microsoft Intune is 4.9%, down from 10.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Configuration Management Mindshare Distribution
ProductMindshare (%)
Microsoft Intune4.9%
ManageEngine OS Deployer1.6%
Other93.5%
Configuration Management
 

Featured Reviews

it_user363621 - PeerSpot reviewer
System Engineer at a engineering company with 51-200 employees
It adds necessary drivers for hardware on desktop and notebooks. I'd like to see more detailed explanations and support for how to use it through PXE.
It's helped us to install OS's onto desktops and notebooks It adds a simple solution for adding specific, necessary drivers for hardware on desktops and notebooks when they arrive. I'd like to see more detailed explanations and support for how to use it through PXE. I've never gotten this…
OluwashileAdeniyi - PeerSpot reviewer
Senior Infrastructure Security Engineer at a outsourcing company with 51-200 employees
Centralized endpoint security has improved and supports hybrid work and BYOD policies
Regarding what I dislike about Microsoft Intune and its downsides, I would say that more Mac controls are needed because we have limited Mac and Linux control. When comparing controls and policies between Windows, Mac, and Linux, Windows has almost everything you can think of, while Mac and Linux have limited types of control. You cannot implement certain things on Mac and Linux that you can on Windows. The limited controls are a major issue. Additionally, if Microsoft could find a way to embed servers into Microsoft Intune, that would be beneficial. Microsoft Intune is not really designed for servers or Windows servers. It is more tailored towards Windows 11 and Windows 10 operating systems. Windows servers are not fully supported. Enterprise organizations usually have both servers and endpoints, which are users' workstations. For servers, most people look for other solutions such as SCCM, which is Configuration Manager. However, SCCM is what Microsoft Intune is trying to replace. Both SCCM and Microsoft Intune belong to Microsoft. Microsoft is trying to transition organizations into Microsoft Intune, the native cloud solution. However, because this update is still in process, servers are not fully compatible with Microsoft Intune and cannot be managed by it. The current policy that has emerged from issues with clients is what they call co-management, which is relatively new, and I do not know if adoption is significant. Many legacy or older customers who have been using these products for decades still have SCCM. When it is time for them to manage their Windows devices, they use what is called cloud attach. Cloud attach is a term whereby your SCCM is connected to your Microsoft Intune. Most people do not know about it, but I have deployed it for several organizations. Cloud attach and co-management work together so that your device is in SCCM, but some policies are pushed from Microsoft Intune. It is like two different solutions working hand in hand. That is what they call co-management. Microsoft Intune does not bring all of your endpoint and security management tools into one place, which is the goal and how it should be. However, as I mentioned, servers are not included. If we talk about end users, Microsoft Intune does bring all your devices together. In a typical enterprise environment, you have end users with workstations, laptops, company-issued phones, and bring your own devices. You can create policies for all of these. However, for the backend, your servers do not have much coverage. Servers are not really covered by Microsoft Intune in that way.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Before OS Deployer, I used Microsoft WDS, which requires more manual labor than OS Deployer."
"It has helped with compliance. It has helped to ensure that devices comply with the organization's policy. If they are not compliant and secure, they cannot access the resources."
"Microsoft Intune is easy to use, and it is able to enforce policies towards multiple devices. It is able to bring multiple classes of devices into the same security posture. I found that very useful."
"It's really easy to access."
"Implementing Microsoft Intune has provided a more streamlined and consistent method for device management across our multiple domains, effectively consolidating our administrative efforts."
"EAM is a godsend."
"Comparing this to having an endpoint management solution, the efficiency gain may be up to 80%."
"Intune's most valuable feature is its centralized management capability."
"The most important part is that they're fast in implementing and integrating with the Windows operating system, as well as how it integrates with other Office 365 products."
 

Cons

"I'd like to see more detailed explanations and support for how to use it through PXE."
"I want more secure, reliable, and efficient security policies."
"The platform is incredibly slow and could be more responsive. Specifically, when making changes to security policies, I would like to see those changes take effect more quickly."
"I have experienced downtime, bugs, and glitches. I rate it a seven because when we have bugs or instability in Microsoft Intune, we need to wait for the backend from Microsoft Intune to resolve issues and we can't deliver solutions to clients because we need to wait for action plans and related processes."
"Microsoft Intune lags market leaders, such as Apperian, in its MAM capabilities."
"Microsoft Intune has a latency response time issue. The latency has room for improvement."
"Manually syncing devices to enforce policies is cumbersome."
"There could be more wizard-driven policy development or creation. Some of the policies can get quite complex. If they have a wizard that assists the administrators in creating the policy, that will be a great job."
"In the next release, I would like a feature to be able to properly lock down the device. For example, if an attacker or somebody steals the phone, you can be sure that the pin cannot be broken."
 

Pricing and Cost Advice

Information not available
"I don't have any problem as far as cost is concerned. It is bundled with our license."
"Most of our clients come to us with licensing already in place. On average, it costs $6 per device per month to add Intune to an Office 365 subscription, but I am not sure."
"On a scale of one to ten with one being the cheapest, the cost of Microsoft Intune is a five."
"The cost is handled through our Office 365 license, so I have yet to be able to compare it directly with other tools in its class."
"Microsoft Intune is expensive."
"The Intune license model is costly."
"It's monthly for us, but it's built into the license cost that we pay our IT each month. It's maybe 129 Kroner per head, which translates to £10. There are some additional costs. Our IT had to set up and configure their own server, so there is an extra cost for that, but I'm not sure what that costs."
"While Microsoft Intune boasts a wide range of features, its user-friendliness and bundled licensing cost are key considerations for me."
report
Use our free recommendation engine to learn which Configuration Management solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
10%
Manufacturing Company
10%
Computer Software Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business192
Midsize Enterprise62
Large Enterprise185
 

Questions from the Community

Ask a question
Earn 20 points
How does Microsoft Intune compare with VMware Workspace One?
Microsoft Intune is a great tool for managing a mobile device fleet while keeping access control. The solution makes it easy to control security and manage the usage of mobile apps when you have a ...
What are the pros and cons of Microsoft Intune?
Microsoft Intune is a great configuration management tool and has a lot of good things going for it. Here are some of the things I like about it: Pros: Protected productivity: Intune gives you th...
How does Google Cloud Identity compare with Microsoft Intune?
Microsoft Intune offers not only an easy-to-deploy data protection and productivity management solution, but also access to both Microsoft’s user community as well as around-the-clock customer s...
 

Also Known As

No data available
Intune, MS Intune, Microsoft Endpoint Manager
 

Overview

 

Sample Customers

EMC, Costco Wholesale Australia, Canyon Bicycles, Siemens Healthcare Diagnostics, Eleventh Judicial Circuit, WashingtonFirst Bank, SunEdison, Stafford Development Company, City of Redondo Beach, Columbia Medical Associates, Pratt Institute, Novati Technologies, Toyota Boshoku America, Flight Centre UK, RapidAdvance
Mitchells and Buzzers, Callaway
Find out what your peers are saying about Red Hat, Microsoft, HashiCorp and others in Configuration Management. Updated: June 2026.
900,644 professionals have used our research since 2012.