Jamf Pro alternatives and competitors

Microsoft Intune is used for Mobile Device Management. We enrolled our mobile devices as well as the mobile device solution for corporate devices. We have a lot of policies such as the compliance policy, and the conditional access-based policies for the corporate mobile user and we use the solution to assign their  Outlook Teams and other configurations for the organization. 

We use Intune to design compliance policies that apply to corporate devices and to wipe data from devices when users are terminated. Intune is also used for mobile-based solutions, but we have recently explored its capabilities by using the Autopilot feature. With Autopilot, Windows 10 devices can be reset and new versions of Windows 10 can be deployed from Intune.

Intune has many benefits from the Microsoft perspective. This solution can manage Windows 10 devices, app management, and provide security solutions. We don't need to worry about our network connection, and we'll be more secure with regular security patches and compliance. Since everything will be deployed through the internet and users will log in using the internet only, the risks have been mitigated. Security updates, security patching, and the application will be targeted from Intune. The location tracker will be available to track where the device is and the user's location. The user will be restricted from accessing certain applications using compliance policies. Conditional access policies will be based on the reason why the user needs access to the application.

Microsoft Intune is one of the best products in the industry for managing Windows devices. The solution has more feature restrictions. The conditional access policies also eliminate the dependency on the on-prem network for the devices. The solution also manages our security settings and a lot of other beneficial features such as Microsoft Purview which gives us the compliance portion. We can manage all aspects of our device from a single console, including M365 services. This allows us to configure data classification types, such as public, private, internal, confidential, and highly confidential.

The best feature is that we don't need to worry about downtime. We don't need to worry about the network connections of our office or the virtual private network. Everything is being done through the internet. Using Intune Autopilot, we can configure and deploy everything to the devices.

We need the capabilities of the Cloud Management Gateway (CMG) to be enhanced through Intune instead of Azure. I suggest that Microsoft consider this. If the user already has a subscription to Intune, they should not need to buy an additional subscription for Azure services.

The support needs improvement. When we need support, we don't get a response within the SLA because the support has been outsourced.

I have been using the solution for five years.

Microsoft Intune is a stable product. For the configuration, we could reach out to technical support, but other than that, we need not worry about anything. If we have configured the product correctly and we are not going to enhance any additional capabilities in Intune, then we need not worry about technical support.

The solution is extremely scalable. I give scalability ten out of ten.

Microsoft has outsourced its technical support so if we raise a ticket with severity, the technical support team may not be able to respond to us within the timeframe or the standard we expect. Sometimes we get the call within four hours. Sometimes we won't get that call for a day or more. The service side is pathetic now. To get support from Microsoft, we need to have our TAMs in place and then we need to submit the ticket. If we have already aligned a TAM for the tickets, we get support from Microsoft.

Neutral

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.

The initial setup is straightforward. Once we have subscribed to the license, we will receive our tenant ID and organization ID. We can then access the portal and configure whatever we want. To save the configuration, we must enable it from the portal itself. The Azure Ready Connect GUI console makes it easy to join devices to Azure and to create and deploy conditional access policies.

We have four or five global administrator access levels in our organization. The most limited level is for the global administrator, who can be limited to one person. We need to involve them to enter the password while configuring the CMG, and then the Microsoft support in case we are missing any configuration during the installation or managing Microsoft Intune.

We deployed across more than 10 to 15 countries. The solution is used in India, the US, and England.

We have seen a return on investment using Microsoft Intune. We can save money by establishing our management point and cloud distribution point in Azure. Cloud support is an additional cost. We have to pay Microsoft for the VM, which doesn't act as a management point and the cloud distribution point for the endpoint. Endpoints are the on-prem devices.

Earlier, Microsoft used to give the license using the MSDN subscription, now the subscription part uses the M365 E3/E5. Existing E5 license holders for M365, Intune, and Azure, receive a free license.

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.

I give the solution a ten out of ten.

I manage the endpoints for the implementation strategy and use the desktops or Windows for migration. I'm not from the mobile device management team, but I can give presentations on how the devices will work in the Autopilot zone with Intune. I'm also familiar with conditional access policies and what needs to be in place for a successful migration.

We have 35,000 end-users.

Maintenance is minimal. There have been no reports of any outages from the cloud perspective, meaning that any downtime is from Microsoft itself. However, on-prem systems may experience challenges. We don't need to worry about downtime and all the systems will still be operational.

New customers are definitely going to reach out to Microsoft for purchasing all the products. Microsoft will have its own lab. They will give us the live demo from the lab, but that won't be a feasible solution. We should check and bring that solution to our environment. It would be good if we can create our own test environment and then ask Microsoft to perform all those configurations and just train our engineer about the Intune part. We will know all the legacy parts of our environment which could impact when we are moving our devices to Intune, either the legacy app, legacy hardware, whether those devices are supported, the TPM, the Tested Platform Module, the BitLocker configuration, everything we need to understand before we move our device to Intune.

We found that most of the use cases we needed were for mobile devices, such as Android and iOS. In one of the use cases, we wanted to use a secured email on iOS. Since we have Workspace ONE, we have what is called the Box application. We wanted to make use of the Box application and push it from VMware. We also wanted to make use of accesses such as a gateway or VPN to gain access to our internal resources.

The solution can be deployed on-prem or in the cloud.

For Workspace ONE, because they have an integration with the Workspace ONE access, the most valuable feature is the integration with the tool. We can do single sign-on and make use of the same user account to log into multiple applications. Security-wise, the solution is also very secure. Workspace ONE is very flexible in a way. Functionality wise the solution is okay.

The only downside to the solution is that the dashboard is very confusing. When we are not really working in Workspace ONE control for a long time, we tend to forget where to go because there are a lot of links.

The solution is similar to Intune. Basically, VMware Workspace ONE is still the macOS management, which is still lacking as compared to other MDM solutions. VMware needs to focus more on macOS, and managing macOS.

I have been using the solution for one year.

I give the stability eight out of ten.

I give the scalability of the solution ten out of ten.

The solution is more expensive than Intune.

I give the solution a nine out of ten.

I suggest if a person wants to start using Workspace ONE, they should make use of the cloud instance instead of the on-premise instance. There is an on-premise instance available, but the cloud instance is a better option now. I advise them to make use of the cloud instance. This is because management-wise, there is no need to manage a server. For example, we don't need to buy a server, and we don't need to buy network switches, which are required for the on-premise. At the same time, I can advise setting up all the functionalities or whatever functionalities are available for the trial version. We need to check if the Workspace ONE integration includes Azure AD or other identity providers. A lot of applications are using these providers for authentication, such as Ping, Okta, and others. If the Workspace ONE integration doesn't include these providers, the company might have to find a different solution. Security projects should also be considered. Specifically, if the solution can integrate with local security solutions to secure mobile devices.

We use the solution for mobile device management and file transfer.

The most valuable features of the Ivanti Avalanche are the remote control and the file transfer.

The solution can improve by adding a kiosk mode option to the devices.

I have been using the solution for four years.

I give the solution a ten out of ten for stability.

I give the scalability of the solution a nine out of ten. As long as we pay Ivanti for the licenses, we only need to wear the devices.

The initial setup of Ivanti Avalanche is good. I give the setup a seven out of ten.

We require two people to deploy the solution.

The solution is a time and money saver because if our customer has lots of devices that need to be remote controlled and regularly changed, the profiles on them, the files on them, it is very useful, especially for the IT department.

Although the solution is a bit costly in my opinion, for customers who really need this solution, Ivanti Avalanche is worth it.

I would give the solution a seven out of ten for cost, with ten being the most costly.

I give the solution an eight out of ten.

Maintenance of the solution usually requires two people. One engineer from Ivanti and one of ours.

The solution is used by the people that scan devices in the warehouse. We currently have around 200 users.

Ivanti Avalanche is a great tool for the management of devices and I recommend it to others.

We use it for patch management. It is used for patching servers and workstations.

We're using the web version.

Its flexibility is most valuable.

It should have integrated workstation access. So, there should be a remote desktop feature.

We dealt with it for a couple of months.

It has been pretty stable.

It should be easy. We're probably going the opposite way. We're not going to be doing much scaling up. If anything, we'll be scaling down.

There are three people who use this solution. They are from desktop support and server infrastructure.

I never had to contact them other than during the implementation.

It wasn't complex at all.

Its licensing for a year was nine grand. There was no additional fee.

It is a flexible solution that does a majority of the tasks. The only thing it really doesn't do is Mac, which is something that Jamf Pro does, but it is not necessary.

I would rate it a nine out of 10.