If we're only upgrading to Windows 10 for the monthly security patches, Ivanti has Patch Now. Patch Now is a solution that gives us the same set of capabilities as IBM BigFix, but Intune has enhanced capabilities. Ivanti Patch Now is another product similar to the Microsoft Configuration Manager console and we have to make sure the device is on the on-prem network itself. Intune is a cloud-based solution that does not require the device to be on-prem. Everything is in the cloud, including device tracking, writing, and initiating remote connections.

We used Okta but Microsoft Authenticator replaced it. Both are good, but Okta is much higher in price compared to Endpoint Manager. Also, Okta is a third-party application for Azure, while Endpoint Manager is core, proprietary software by Microsoft. With Okta, the compatibility issue is always there. 

Also, Okta requires a lot of authentication processes, rules, and policies. Microsoft Endpoint Manager doesn't need them because it already includes overall security policies, and the rules apply to them.

We evaluated several options, primarily security solutions like Malwarebytes and Sophos, which offer remote management capabilities. Ultimately, we opted for Intune.

This is a case where remote management was initially implemented as an afterthought, primarily driven by anti-phishing and anti-malware threat response needs. Subsequently, it became the sole platform for endpoint management, despite limitations in its functionality and granularity compared to solutions like Intune.

I see a significant gap between Microsoft Intune and products by other vendors. We were using SCCM on-premises, but Microsoft Intune added monitoring and security features, so we didn't see any suitable alternatives. 

We evaluated IBM, Ivanti, and Workspace ONE but our management decided to move away from third-party platforms to simplify and save costs.

In comparison to earlier vendors like IBM, AirWatch, MobileIron, and SOTC, Microsoft Intune stands out as more flexible and user-friendly. These earlier systems were rigid and required IMEI numbers, making them less adaptable. Intune, on the other hand, is simple, similar to Azure, and excels in terms of scalability and versatility. Creating device-switching policies in Intune is straightforward and visually intuitive. It involves selecting the appropriate profile and specifying the device type (iOS, Android, or Windows). The options are readily accessible, making Intune an easy-to-use solution for managing mobile devices and endpoint management tasks.

We assessed VMware and found its MDM to be promising. However, since we were already utilizing other Microsoft solutions, and Intune was capable of meeting our requirements, we did not require further evaluation of additional solutions.

Meraki and Google are relatively common in small businesses. Many small businesses use Meraki for wireless and networking solutions, so that is one MDM option. Also, small businesses often start with Google and transfer to Microsoft 365 once they mature. Google is already in the environment. I don't sell anything as an IT guy, so I don't care what solution my clients use. I choose what's best for them in that particular instance.

I have tried Okta, but I haven't used it seriously as an MDM solution. I've only used Okta as an SSO provider. I didn't realize they did MDM solutions. I don't understand the point of Okta. If you have Azure AD and Entra, I can't fathom why you would bother with Okta. It seems redundant to me.

We evaluated a few solutions.

There are other MDM solutions, like Workspace One from VMware, which has support for server operating systems as well. I've never used it but I did a quick comparison of the supported operating systems.

In addition to ManageEngine, we looked at BigFix by HCL.

There are a lot of differences. Integration and compatibility are major aspects. If you are familiar with other Microsoft solutions, using a new Microsoft solution is not complex. It's easy to understand. That is one advantage. 

And overall, the features and suitability of Intune are unmatched.

We did not evaluate other solutions because Intune was a part of our subscription.

I evaluated VMware Workspace ONE, which is similar to Intune. They both can manage multiple OSs. 

I have used Manage Engine, SolarWinds, and Desktop Central. We switched to Intune when we realized it was a full-fledged MDM that covers mobile devices, desktops, and other pieces. The other solutions had more RMM features for device management but fewer MDM features. Intune was a better fit for our requirements,

We chose the product because it was cost-effective and easy to integrate with our system. 

We evaluated VMware Workspace ONE but ultimately decided to use Microsoft Intune because we already had a Microsoft E5 license.

We work with all Microsoft products,  like .NET, and a lot of development around those areas. 

Another one, Arc Systems, is a current platform that we use.

We evaluated Jamf Pro and will be rolling it out for Apple devices.

I evaluated MobileIron and VMware. 

The main differences between Intune and other products are, like I mentioned, in terms of the Mac. If the customers are majorly moving and adopting Mac laptops while they are using the Intune, they are leaving for other platforms, like Workspace ONE and vMOX. That is the reason for moving and the major difference I have seen these last couple of months. But at the same time, if there is not much dependency on Mac devices, they are moving from other platforms to Intune, also.

In my experience, it would be difficult to find a competitor. It's kind of the gold standard because it's Microsoft dealing with Windows. They have an inherent advantage.

If a third-party vendor tries to offer a competing MDM solution, they're always a bit behind the curve. They don't have first access to all updates or the roadmap for future developments. There's always an element of catching up. 

On the other hand, Microsoft can bake these changes into the product as they make them. So, on that basis, it's quite simply the best.

We evaluated a solution from Blackberry but did not like it because it was not as intuitive and the configuration was antiquated. Microsoft Intune was also less expensive.

We didn't consider other options; we wanted a Microsoft product, as it's great to add to our existing suite of business applications, and the integration is more seamless than it would be with third-party products.

They probably did not evaluate other options. A lot of organizations are trying to use one vendor, and they have been using Microsoft for a long time. Intune seems to be the most complete as compared to others. I have been doing some research recently for a company, and I have been going through some Gartner reports. Intune is clearly number one in this area.

We considered other mobile device management solutions, such as Davenport and a VMware product, but ultimately chose to stay with Intune due to its rapid development pace.

We did not evaluate other options.

There were quite a few, but this was the main solution that we looked at because Microsoft solutions integrate well with other Microsoft solutions.

We are primarily using Microsoft products, so our options were Google Cloud or Intune. We decided that it was better to go with Intune because the learning curve would be steeper with Google. 

MobileIron has two types of licenses. One is a SaaS-based model, and they provide support, and the other is a license for the on-premise solution. Microsoft Intune offers only a cloud solution.

I have used AirWatch in my previous organization. The integration provided by Microsoft Intune is its biggest advantage over its competitors. Most of the integration with third-party tools is good.

We did not really look at any other competition. We are a Microsoft 365 E5 customer and the product promises the capabilities that we need and is available without additional cost. It just made sense to try to use this part of the suite.  

The main difference between Intune and Workspace ONE is the quality integration between Microsoft products and Office 365, which means that Intune is part of a solution; you are not only using Intune, but you have to think about its ecosystem. For example, with EMS, it will have at least three products. The first is Azure ID Premium, which is the IAM solution (Identity and Access Management), so there are use cases where you might need to use IAM. The one difference between EMS and Workspace ONE, since Workspace ONE doesn't focus on identity management, is that it only has the access part. It can leverage all identity management, like with the directory or any of the identity solutions. 

The second difference is in the integration with Office 365 because in the Office 365 ecosystem, you have a lot of products, like Azure Information Protection, which is focused on the labeling and classifying of data. Microsoft also has Defender DLP and Defender for Endpoint. These make up a total solution. Based on that, if you have a long-term roadmap, you can actually integrate it with other Microsoft security solutions, like Sentinel, which is a SIEM solution. When choosing Intune, the main difference is the ecosystem and the roadmap.

I started my journey with AirWatch. It was primarily an MDM solution. According to Gartner, AirWatch and Microsoft are currently neck-and-neck. From an organization requirement point of view, regarding MDM, I'd say AirWatch is a step ahead of Intune.

For the last four years, I've only used Intune. I don't know how AirWatch has improved over the last four years. Still, simple things, like pushing a profile are much easier with AirWatch compared to Intune. From a UI point of view, it's really easy for an admin to go ahead and work using AirWatch. From a deployment point of view, there are multiple options for retaining user data. 

We are currently evaluating both Microsoft Intune and VMware Workspace, and we will choose the one that best suits our use cases. Our plan is to implement one of these products in a couple of months.

One of the conditions is that we have to make sure that it supports all of the devices that we have in the enterprise. For example, we have Windows, Mac, Android, and iOS devices that need support.

Second, we need to have the autopilot experience for the users running under Windows. If somebody joins the company and they are provided with a laptop then we need to have it set up correctly. Normally, when it ships from a vendor such as Dell, Lenovo, or HP, it will come with their software pre-installed. Given the current situation with employees working at home, the laptop ships directly to where they live. At this point, with autopilot, they should be able to log in using their cloud credentials as soon as the device is switched on.

Once logged in, all of the details will be picked up from Azure, including the policies, updates, and other mandatory software such as Skype, Zoom, and Microsoft Office. Essentially, it eliminates all of the laptop setup and configuration that used to happen inside the organization.

Intune supports autopilot natively through Azure, and VMware Workspace is on par with this as well.

Next, it should have good reporting features. All products are able to generate reports, but we should be able to customize them in the way that we want.

We also have to have good security, where we can push all of the security configuration and policies that our organization has. This will differ based on the department. For example, security in banking or finance will be different from the security in manufacturing.

Finally, we should be able to deploy applications all over the cloud.

I think that in comparison, VMware Workspace is a more mature product than those offered by competing vendors. It has been developed very intelligently. The UI is good, with fancy graphics. They also have Smart Groups, and a different way of deploying applications, which are very good features.

VMware Workspace also has a slight advantage over Intune when it comes to managing multiple hierarchies. Intune does not support this type of structure, where you can have sublevels. For example, I can have a root-level like Europe with sublevels such as the UK, Germany, and France. 

We looked at the Sophos solution as well. We are a Sophos partner, but it was easier to deal directly with the Microsoft solution primarily because of the rules management and the Microsoft groups and the security groups that we use. We use rule-based access, and we have access packages so that users can elevate their rights with an approval process in the back.

I'm researching VMware Workspace ONE, a new VM solution. I think it's interesting, but I don't have enough experience to give specific feedback about that tool.

I did have a look at other options, but I'm a Microsoft specialist, so it's a Microsoft-first sort of policy. If Microsoft can do it, I'll do it with a Microsoft product.

We have previous experience with VMware Airwatch.

Yes, we've tried ManageEngine and SolarWinds.

I was comparing Microsoft Intune to VMware Workspace ONE, or EMS as it is more commonly known.

We considered VMware Airwatch and IBM MaaS360. 

We did evaluate other solutions before we selected this one.

We also looked at VMware AirWatch. 

I also work with Jamf Pro but you can't compare the two because Jamf Pro doesn't have real-time features and it doesn't do most of the things that Intune does. 

We didn’t examine other tools.

We did look at other solutions. The one we did look at closely was more for larger organizations in the manufacturing industry, which wouldn't have fit with our needs. 

We evaluated AirWatch, SOTI MobiControl, and IBM MaaS360.