Previously we were using Microsoft Configuration Manager. The Microsoft Configuration Manager is the dedicated server for managing devices on-prem. We need to make sure the device is on the same network through which the policy is getting replicated. The dependencies with that server as well as with the network are important, and the devices need to be online on the network. Using Intune as a backup solution, if the device is not on the network or if the device owner is not in the location but it has an internet connection, then we can deploy all our physical solutions onto the devices. We are using both, the Microsoft Endpoint Configuration Manager as well as Intune, since a couple of policies are still only being managed with the Configuration Manager.

We migrated to Azure and our requirements changed. We have found Endpoint Manager to be suitable because of the compatibility and overall performance issues.

We faced so many issues, three to four years back, when we were using VMware and Cisco-based cloud security solutions. There were threats detected and but some valuable financial transaction information was lost. It was very painful. After analyzing our requirements, we are now using multiple security solutions because we have multiple applications. Every application has its requirements in terms of data storage and security. We are using not only Microsoft Endpoint Manager, but a solution for DDoS, as well as Microsoft Sentinel. They are top-level security solutions provided by Microsoft, so that we can secure our email, data, and overall user information.

We used System Center Configuration Management, and we did it all on-prem. When Covid hit we switched to Intune.

We previously used Microsoft System Center Configuration Manager, Microsoft's on-premise configuration management solution. We switched to Intune because we purchased an EMS E3 license that covers Outlook, Teams, Intune, etc. 

Ultimately, it comes down to costs. We don't need to spend money on SCCM licensing, and we get better cloud-based monitoring and reporting than SCCM. Most people prefer to move to Intune because they get some additional features included for free when they buy the EMS E3 license from Microsoft.

I have used ManageEngine from a company called Zoho Corporation to do inventories and patching. Microsoft Intune lacks capabilities to patch Windows, Office 365, Acrobat Reader, etc. There is no way for me to apply and manage patches. I can create a patch configuration, but I cannot control when it has to be deployed and on which machines. If Intune adds patching, I don't need to invest in another patching tool.

I've used Rocky MDM and Google MDM. Microsoft is the primary platform on which we do business. Intune works better with the Windows operating system, desktop applications, and SharePoint. It also reduces vendor complexity. I don't require multiple vendors, which reduces my costs because many features are baked into it. 

I log into fewer systems daily. Microsoft's virtual monopoly on productivity applications in your average small business makes them the right choice in most situations.

We did not buy any similar solution previously.

I have used Jamf, Microsoft Configuration Manager, Altiris Symantec Endpoint Management Suite, and Cisco Meraki Systems Manager. Microsoft is considered a leader in endpoint management solutions. While Jamf excels in specific areas, Microsoft Intune is generally recognized as the market leader due to its comprehensive capabilities. Intune also integrates seamlessly with other solutions such as compliance checks, conditional access policies, and mobile application management. Microsoft Intune offers several advantages over competitors, providing a comprehensive suite of mobile device management capabilities.

We used ManageEngine Endpoint Central. Its features and functionality are quite similar to those of Microsoft Intune. But we had to migrate to Microsoft-based solutions and we found Intune to be better than the others.

Another main reason we are using it is that Intune provides end-to-end security for Windows OS, macOS, and our systems. Earlier, it was Microsoft Endpoint Manager. Intune is very good software, a good cloud-based solution.

We are busy migrating from Microsoft System Center Configuration Manager and Endpoint Manager because of the infrastructure requirements. We want to be on the cloud.

We are a key government department that looks after and advises 13 other departments. They are rolling up Intune to those 13 departments.

Before Microsoft Intune, we were using SCCM, which is a more traditional approach. We switched to Intune for its modern and comprehensive capabilities, as SCCM lacked certain functionalities and agility.

At the moment, we're using VMware AirWatch, which isn't my first choice purely because it's a super segmented platform. We are predominantly, about 95%, Microsoft. It feels a bit of an oversight not having a solution on a Microsoft platform where we've got full transparency and can make live changes. Currently, we have to go through our outsourced IT to make the changes and then we have to wait to see those changes rather than me or a colleague being able to make those changes in a live environment, so it would be my personal preference to get that moved over, which we're looking at. 

I wasn't a party to why they used AirWatch. I presume it was bundled in with the Microsoft service partner's offering originally. The IT team here is quite new. I've only been in the post for about a month, and my IT manager has only been in the post for about two months. We're just making sure that everything is easy to use and easy to manage, and it's cost-efficient for the charity moving forward.

We previously used SCCM. We switched to Intune due to its better usability, cost-effectiveness, and alignment with our Microsoft-centric environment, as we predominantly use Windows across the domain.

We have previously used MobileIron and Jamf Pro.

I'm not aware of any other solution being used. I know there were one or possibly two failed mobile device management project implementations. I was not a member of the department then, so I don't know the details. I only know that both of the deployments failed. In other words, either the vendor promises were not met, or we found a function that was supposed to exist but did not exist. 

We used the MDM included with Google Workspace, but we transitioned to Microsoft because we were unhappy with the platform. Managing files and data wasn't intuitive, so it didn't meet the needs of our growing company. Most of my users complained about losing data while using Google Workspace. Unlike SharePoint, Google Workspace doesn't sync automatically so that you can work remotely offline.

SharePoint saves all your work locally and updates it when you connect. It's easier to use and a better platform overall. Google Workspace is a good platform, but it can't keep up with our growth.

We used AirWatch before Microsoft Intune. We switched because of cost and customer care issues. We are currently in an SCCM environment. 

We previously used TeamViewer Remote Management. However, we switched to Microsoft Intune because TeamViewer did not offer application deployment or vulnerability management. Microsoft Intune offers both of these features, as well as integration with Office 365 Defender.

We used VMware AirWatch. We switched because of the ease of use that we get from Intune. It's much simpler to work with.

We previously used VMware Workspace ONE which is a very good solution and in some areas better than Intune, and Cisco Meraki Systems Manager. We switched to Microsoft Intune because of the better integration with Microsoft products.

We were using Symantec, and we ended up using Intune. Symantec is a nice security piece, and it does some device management. There is a domain-joined service for laptops. Intune has a similar service set. You do what is called the hardware hash join into the Microsoft Intune to have the laptop cleaned by an organization rather than turning on a VPN and connecting to a domain service for a domain controller that an organization has. A lot of that is cloudly or natively handled by Intune. Especially if you go further with the Intune hardware hash joining process, there are some script sets that were put out. You can even do hardware hash harvesting from where you are purchasing, so you can have the OEMs give you the hardware hashes to be able to input that into your cloud environment. You then know that anyone cannot just walk away with the laptop because it is still joined to your Intune base.

In terms of differences between these two solutions, there is the domain service set. Intune manages the whole domain set, and then it also integrates into the other application sets. Intune is more of a product suite set. It also does the policy and detection pieces for devices, whereas Symantec is more strictly the policy sets and security.

We previously used an on-premises solution, Microsoft Endpoint Manager, to manage our devices. The pandemic necessitated a shift to the cloud.

We were using the SCCM server. It is a Microsoft product.

I have not worked with any other solution recently. 

We also do business with Amazon, Google, and other cloud providers. 

We currently also use BigFix.

I previously used MobileIron UEM and VMware Workspace ONE.

I think if you have the money and want something more stable, you should go for AirWatch. I don't think Microsoft is offering the same stability as VMware at this point. On other hand, I think the support from Microsoft is better, particularly the support in Asia. In VMware, all the support is from India, and sometimes I have a hard time with them.

For remote access, we are not using Intune, but in my previous company, we used Intune for that. It worked very well. We did not have any problems with it. For managing remote devices, we are using Bomgar.

We have a lot of departments. We are using Intune only for the production computers. For others, we use SCCM. We have a hybrid environment.

We used Citrix Endpoint Management in the past. We used it about two years ago. It was a good product. They are comparable, really, Citrix and Microsoft. 

I have only used SCCM which was provided by Microsoft and was totally on-premises. I have not used any MDM solutions from them.

In the past, we utilized Windows services.

Previously, we used Workspace ONE. While I find Intune to be generally better, there are still some specific areas where Workspace ONE offers functionalities that Intune currently lacks. Additionally, Workspace ONE was significantly faster for generating reports. However, I acknowledge that Intune has undergone significant improvements over the past year and a half, and it's steadily approaching the level it needs to be. Nevertheless, there's still room for further improvement.

We use a family of products. We don't want to put all our eggs in one basket. For example, we use software from other providers for security awareness training, phishing protection, and so on. 

However, as a Microsoft Gold Partner, we're heavily integrated with Office 365, Microsoft Defender for Security Center, and everything that goes along with Azure and Office. We essentially have a suite of different tools depending on the specific need.

For our Endpoint Detection and Response (EDR) or physical endpoint security on laptops, we also use CrowdStrike. Our approach involves leveraging different options depending on their strengths.

Some vendors like CrowdStrike claim they can do everything, but we prefer specialization. We want different providers to handle different aspects of our security.

We have Microsoft Defender, which provides access to threat intelligence and also offers endpoint protection. While Defender is a competitor to CrowdStrike, we avoid using its endpoint protection functionality to maintain our distributed security approach. However, we utilize Microsoft Intune for Mobile Device Management (MDM).

And through Intune, we can push out policies that enforce specific security standards on all our computers, such as encryption.

We leverage it for managing device security policies. Additionally, all our devices access Office 365.

We use Microsoft security features within Office 365, SharePoint, and OneDrive. 

We worked with Cisco network monitoring, using Cisco ASA with RSA deployment. It had its issues. It wasn't very user-friendly. If a device wasn't posture-compliant, for example, it wouldn't explain to the user what they needed to do. There was also a bit of limitation with the operation alongside things like antivirus software. It didn't work very well with Sophos and other applications.

We previously used Microsoft System Center Configuration Manager (SCCM) for group and on-prem policies, which we also pushed out to devices. We switched because Intune is more modern and cloud-based, so it fits our organization better.

At my old organization, we used Microsoft System Center Configuration Manager (SCCM), which is more of an on-prem system. Microsoft seems to have recognized that everyone is moving to the cloud, and I expect they will bring SCCM's capabilities onto Intune as a kind of product upgrade.

SCCM is a more versatile tool than Intune; we can't patch third-party applications in the latter, which is a significant headache.

I have been mostly using SCCM. The move to Intune was a part of the cloud transition. Most companies are moving not only the MDM solution but all kinds of services to the cloud. Intune is just one of them. It covers one of the areas.

I have not used any similar solution.

We previously used Microsoft System Center Configuration Manager and switched to Microsoft Intune so we could better secure our personal and corporate devices.

I have not used a similar solution to Microsoft Intune.

We were using on-premises Active Directory, and we were restricting certain things through GPO, but there were a lot of challenges when the users started to work from home. 

I've worked with Ivanti and LANdesk and other tools.

I've used Endpoint Manager every day. I'm currently using it. I've been using it for 25 years. However, there are other ones like BigFix, which I've rarely used. I've used LANdesk a few times. And people would try to use LANdesk to avoid the expensive Endpoint Manager, however, at the end of the day, it costs them more in time to use the LANdesk solution. Ivanti is a competitor, however, they're cobbled together with Shavlik, for patch management they've got Altiris. They bought Altiris and Altiris has been passed around like a cheap hoe from Symantec to Intel, to everybody.

Altiris was actually developed to support Endpoint Manager and provide asset management. At the time, Endpoint Manager didn't have good asset management, so they actually worked with Altiris, only to find out that Altiris was actively taking Microsoft customers. Microsoft booted them to the curb and they haven't done well since. That was back probably in the late nineties that they did that. Endpoint Manager has been around the longest, it's survived, it's matured and it's the top dog in general.

I previously used Microsoft SCCM. 

We were not using any similar solution previously.

We used BlackBerry. We switched because that was getting outdated, and it didn't have all the features that Intune has. Intune is continuously being improved because of the cloud service.

Previously, we were using Workspace ONE, but it was cost-prohibitive. We moved because of Microsoft's ecosystem. It was a business decision. The integration of the systems made it easier to stay with something like Intune.

I have used Workspace ONE, and I would highly recommend it over Microsoft Intune.

I have used multiple endpoint management solutions in the past nine years. I also work with Jamf, a solution that focuses on iOS devices. Compared to Jamf, Intune also has some limitations when working with iOS. For example, Jamf can create specific policies for each iOS device, whereas Intune can't go that far. It also has role-based and device-based features. You can do more customization on iOS devices with Jamf. 

We did previously use VMware. We tried mainly to reduce some costs. This product seems to come as a part of a bundle, which slightly reduces costs. Also, VMware had plenty of functionalities that were not necessarily fitting into our landscape. We were not able to capitalize on the cost of the process. They didn't have any great integrations with broader enterprise systems.

SCCM is no longer known as SCCM. It's known as Endpoint. Microsoft no longer recognizes that product. Endpoint refers to both the local and cloud-based installations. And, prior to their acquisition by Dell, we were a long-term partner with Quest. We've had clients use Quest products, but we haven't.

According to Microsoft, SCCM is no longer in use. Microsoft Endpoint is the new name for the current build. You can now deploy an Endpoint structure locally or pull Endpoint from Azure.

SCCM is no longer active.

I have worked with both Microsoft Endpoint Manager as well as Quest in the last 12 months. We have clients running the Quest Software.

The most recent Quest software we've seen is the Exchange PTS, or mail migration tool. That is probably the tool that we've had clients deal with twice. However, that is apples to oranges in comparison to SCCM.

It is the mail migration utility. According to my understanding, Quest recently sold that to a different company. So it's an old Quest product.

I previously used BEAM for client management from an American company and SCCM from Microsoft. Additionally, I used ManageEngine and Lansweeper. Lansweeper was a light tool with similar functionality. We use it in combination with TeamViewer.

The first one we used was VMware AirWatch. The reseller overestimated our requirements, and we got a very expensive package. It was about $57,000 every year, and eventually, we found out they had a package for $6,000 every year that did exactly what we wanted, so we had to drop it. We had spent two years on VMware AirWatch with the expensive module.

We switched to Intune because we were already on a Microsoft subscription for Office 365, and the add-on wasn't that expensive.

We work with various Microsoft products, including Office 365 Enterprise licenses, Azure, and numerous other licenses and services. Our setup involves multiple tenants and subscriptions, covering a wide range of Microsoft offerings.

With Apple Business Management, we can pre-deploy everything, and we can manage everything on the phones with the lockdown. With Workspace ONE, I couldn't lock down the email profile and make it accessible only on certain devices. 

Especially with Office 365, this became the biggest issue because we couldn't lock down the profiles per device space. When I worked with VMware, I worked with Microsoft Office for a couple of weeks continuously to figure out a solution and couldn't find one. 

That's when we decided to go with Microsoft Intune management because we could lock it down to just those devices. Otherwise, it was locked, and our tenant is a government tenant, and we don't allow any external access to our tenant.

That was the issue I was having with Workspace ONE. Workspace One couldn't integrate Office 365 applications the way I wanted it to.

I previously used a different management solution called SOTI MobiControl, but I didn't switch because Microsoft Intune was better. I just changed companies. 

We used AirWatch and switched because we were facing a lot of issues with the product. Some things were really great, but some things were not.

Maintenance took a lot of time because it was on-premises. Every month, we had to do upgrades and patching of all the servers.

Previously, we used MobileIron. Some of our business units also use Cisco Meraki and several others. We are working towards using one or two globally. We're moving to Microsoft as part of our larger global strategy.

Prior to Microsoft Intune we used IBM MaaS360, but switched because the interface and configurability is horrible.

We did not previously use a different solution. We've only ever used Microsoft Intune for these current use cases.

I've migrated from other platforms to Microsoft Intune, but I've not used any other similar solution.

We've switched over from MaaS360 to Intune. We took the decision that Intune is better for Windows and IBM products.

I personally preferred IBM. I always outsourced the IT, but I preferred IBM. I liked the interface with IBM. I like being able to push out and seeing which updates were not available and which ones had to be pushed out. It was a lot easier to use. So, I preferred IBM, but I'm not really using Intune. It's outsourced to our IT.

I am familiar with a similar IBM-based product. If you have a Microsoft-based suite, InTune makes more sense, however, if a company uses something else - such as Google - IBM may be more suited. 

We did not use another similar solution prior to Intune.

AirWatch is a bit complicated, especially during a disaster or when something happens. Their technical support is very poor, and Intune is far better.

I have previous experience with VMware Airwatch. But, I find that the integration is better with Microsoft Intune because we are already using Azure as a domain. It is a much easier integration with the Microsoft products.

We also use Liquid. We are part of their development program and we helped them develop their software. We also have Liquid in the field, but that's mainly for use cases with social internet and launching applications from websites, which is a little bit more difficult using Intune.

I was previously using on-premise Active Directory with group policy management. Intune puts your dashboard and panels in the cloud, but they sync with the on-prem Active Directory. Most of the management is done from in the cloud. All we need is internet access to manage the devices.

I am also familiar with CyberArk.

I have used Workspace ONE. Workspace ONE works really well for iPads and Androids. I haven't used it recently for Windows. They had just started to sort of delve into that arena, but I can't really say how well it works because I haven't really tried it on Windows 10. Workspace ONE is far superior when it comes to iOS and Android OS. If I remember correctly, they're comparable in price.

I have used ManageEngine Desktop Central and SCCM. When comparing SCCM to Microsoft Intune, when we used SCCM we had more control and visibility on what we deployed. There are certain cases where you do not want to deploy something. For example, there are security updates or quality updates that could have bugs or glitches that you see around the world. Another example is, every second Tuesday Microsoft patches will be released and you hear that some of them can have bugs or glitches, we can take them off the list and not proceed with that particular patch. This was possible in SCCM because you can select whatever patch you want before deployment. However, in Microsoft Intune that is not possible because Microsoft releases it across the world as one data piece. You do not have control over whether to select it or not, we have to accept it.

ManageEngine Desktop Central is very similar to SCCM, you can select what updates or patches you want. If you do not want one patch you do not have to select it. 

We migrated all the services to Microsoft platform cloud architecture. We went with Intune for the patch management, but we do have ManageEngine Desktop Central, which is capable of doing patch management.

There are some customers that have switched from other products, and typically, it's because they just couldn't get the other product to work. Miradore is one in particular that many of our customers had, and I like them

We previously used AirWatch.

We are also working with VMware Workspace ONE. When comparing these two products, I prefer Intune.

It is a tricky thing to answer exactly what I have used that either was prior to or a substitution for Intune. That depends on different things and factors. First of all, Workspace One is definitely highly scalable, that I know. Workspace One also has a lot of integration options wherein we can have a lot of peripheral tools. Workspace One actually started with only UEM, but it is now not limited to UEM only.  

Intune, is only a UEM. So Workspace One has one integration as UEM, but it has many other things. Apart from that, it has Workspace One Intelligence, it has Workspace One Assist, et cetera. There are four different parts that can be integrated with Workspace One and they can work together for a highly scalable, highly secure, and highly analytical solution.  

Microsoft also has solutions. It is just that they are different solutions implemented in a different way. For example, ATP (Advanced Threat Protection) Microsoft is for advanced threat protection. WAD is for virtual desktops. They do not have the same type of tight integrations as Workspace One. All of these Microsoft products work separately. In Workspace One, all the products compliment each other and all the products can be combined more like modules under Workspace One. They can push their findings to Workspace One Intelligence where all data intelligence can be done. Auto remediation can be done. We can get findings from VMware because now Workspace One security is there to make sure that this is secure under the umbrella. VMware Carbon Black is also the same in that it can send its findings to Workspace One Intelligence. So the integration is the part that is handled differently. Workspace One has many features. Microsoft also has those features. It is just that it is a different way to orchestrate. In Microsoft, it is not under one umbrella. In VMware, that is under one umbrella, which is Workspace One.  

The pros and cons are different because both approaches have their own advantages and disadvantages. Both have solutions for each of the functions. For example, each has advanced threat protection and all those capabilities. If you stay working with that family of solutions, you do not have a problem.  

Now say, for example, a company went with Workspace One because they wanted to leverage UEM. They adopted some other modules as well with it to create solutions for problems or needs that they want to solve. They have to have Workspace One for this solution and they can not work with it separately. That might be a cost factor because they can not work with one tool only, they have to make the license for two products because they do not work separately.  

For Microsoft, since the products are completely separate, customers can choose which one to go with and only use that. They can go with only one product, or they can add any of the others. They do not need to have the central component to bring them together.  

So that might be an advantage or disadvantage in using one product or the other depending on the use case.  

We did not use a different solution for the same purpose before implementing Intune.

We've used Microsoft Endpoint Manager and Ivanti Endpoint. With Ivanti, it's a much more open system for different kinds of IT infrastructure. Whatever the operating system, whatever the application, it's good. It's easier also to deploy as well. You don't need a big infrastructure to deploy Ivanti Endpoint. The ability of Ivanti to have an extension for the ITSM solution is good.

We previously used VMware Airwatch.

Microsoft Intune is the only solution I have used.

We used a third-party package before, and we moved to Intune because it was easier to integrate with Microsoft Windows or Microsoft 365. It also provides coverage for desktops.

We used to use a SCCM or System Center Configuration Manager tool; it was also provided by Microsoft, but it's an off-prem tool. You need an on-prem setup and a server operating system and everything. On that server operating system, you can install this tool and start using it. We also used another tool called Automox, which was a patching tool. It's only meant for patching devices, different operating systems, Linux operating system, Windows, Mac operating system; however, it didn't have support for mobile devices.

We didn’t have a previous tool. The solution was required to extract a company from another as part of a demerger. The new entity was our customer.

Previously, we used Sybase Afaria. It was too complex and it was not stable.