VMware Workspace ONE 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.

MobileIron UEM will be used to manage mobile devices. We will be able to manage a wide range of endpoints from the MobileIron console, similar to VMware Workspace ONE.

The user interface is user-friendly.

I don't believe I have, given the scope of this, because I haven't explored them thoroughly. So I don't think I have a problem with them right now.

For a new user, the initial setup could be simplified.

We had an issue with the integration of an add-on, but it has been resolved.

They are using a MobileIron as the base mobile device management solution, and we have added some additional solutions to that, such as Advanced Neurons. The integration between the MobileIron and Advanced Neurons isn't completely in sync, and we're still working on that.

I have been testing MobileIron UEM for two to three weeks.

We are working with the latest version.

MobileIron is still with Ivanti. We are still working on the proof of concept with them, and I believe the tenant is still with them. I'm not sure who the host is.

MobileIron UEM is a stable solution.

MobileIron UEM is a scalable solution.

We are only going to deploy it to 200 plus, users at first. That will increase in the future, depending on how our business grows.

When it comes to technical support, the person who is fixing it is the one who leads the POC. The same engineer who is assisting us with the proof of concept is also the one who is repairing it. I believe technical support is quite responsive because he is the one who is resolving the issues.

We are working on the proof of concept for both MobileIron and Workspace ONE.

We are only testing MobileIron and Workspace ONE. After that, we will decide which device to use.

Workspace ONE by VMware Similarly, we will use MobileIron as a mobile device management tool, allowing us to manage our endpoints remotely. So far, we have not had any issues with VMware, and we have resolved some, if not all, of the issues.

I have been testing with VMware Workspace ONE for the same amount of time as MobileIron UEM, three weeks.  We are using the latest version, and it is deployed on a public cloud. The cloud provider is VMware.

I have also been working with Google Chrome. Google Workspace is an email production tool provided by Google.

We don't have a firewall because we're in the cloud right now. We have no on-premises network and all of our systems are hosted in the cloud.

Perhaps because it is my first time, it is quite complex, but there are engineers guiding us, but it is quite complex on my end.

We had assistance from a MobileIron team member. We will investigate their features and see what capabilities they have while conducting a proof of concept. That is our proof of concept's goal.

We don't have the cost until we have completed the proof of concept.

They need to research other platforms or solutions to determine which solution best meets their needs. In particular, I don't think I have any recommendations for MobileIron because my experience with it has been limited. I lack extensive experience with MobileIron.

I'm a potential customer.

I would rate MobileIron UEM an eight out of ten.

As an organization, we are resellers, we provide services to our clients, and we work on various government and manufacturing projects.

We provide consultancy, as well as our services for both Jamf Pro and Apple products.

We also offer assistance if they encounter any problems with the integration of Apple products.

When I first started using this product, there were a couple of features that still excite me because there was no scope to address those issues. And these features completely eliminate some of our previous issues.

I am most excited about a feature that is called User-Initialed Enrollment.

I also like the Composer feature, which is a unique feature.

Snapshot is one of the tools that allows any package, container, or package creator to find a way to work with various applications. 

I really liked the Self Service applications as well. It is very convenient and useful.

The response time for support could be significantly improved.

I have some customers who are struggling to get a response.

The amount of time required for remediation is also a challenge. If the problem is identified on the first call, it should be tagged and resolved within the tag. This is something we have been dealing with, as well as a problem that some of our clients have encountered.

The cost could be lower.

I've been working with Jamf Pro for five years. I received my Jamf certification in 2017 and have been using it ever since.

Jamf Pro has been stable.

Jamf Pro is a product that can be scaled. Scalability is something that must and should exist, and I always believe in possibilities.

At the moment, the way the product is designed for managing Apple devices meets my needs.

When I need to scale it in the future, I know it's a possibility.

Support is something I believe could have been improved.

They offer one of the best cloud services available.

However, the response time and remediation could have been significantly improved.

Prior to Jamf Pro, I worked with three different products: SOTI, MaaS360, and VMware Workspace ONE.

The initial setup is quite simple. It is not at all complicated.

It is extremely simple for any user from an endpoint and an administrator's perspective.

It would be beneficial if it could be reduced slightly.

The price for these products is designed in such a way that I believe it is a little on the high side.

They are really evolving, and there have been a lot of improvements since 2017. I like the changes that have been made.

It is now designed in such a way that it can serve the needs of any organization. I have not encountered any issues where I felt it could have been significantly improved, and a specific feature could have greatly aided in addressing issues. So far, everything is running smoothly.

It is recommended for any of our organizations. Jamf Pro is superior to MDM on an Apple platform. If you put Jamf into context and you only want to manage Apple, I believe this is one of the best options.

It can be argued that the fact that it only supports Apple is either an advantage or a disadvantage.

Jamf is your go-to solution for managing your Apple Suite. You should investigate and deploy this product.

I would rate Jamf Pro a nine out of ten.

I use only the asset-management part. 

The asset management is a good feature. It's not the best. However, it's a good feature to use.

It is stable and reliable. 

We can scale the product.

The OS deployment could be better.

Technical support from our local partner is not the greatest.

I'm still exploring the solution. There is yet more to uncover.

Typically, if anything was missing, I would put in a feature request. However, I have not done that yet.

I only started using the solution a few months ago.

It is a very stable solution. There are no bugs or glitches, and it doesn't crash or freeze.

It is very easy to expand. You just need to add extra licenses that are required, along with the computer resources. If I add enough computer resources along with the licenses, it's very easy to scale.

We have around 2,000 endpoints on the solution.

How ManageEngine works is they have partner support. In my region, they have only one partner. If my understanding is right, they only have one partner for the full GCC, and the partner I'm with is not great. If you ask me to rate them, it'll be a zero.

The service from the OEM itself, ManageEngine itself, is good. It's just the partner that is not helpful.

I've also worked with VMware. 

We use the asset management from LANDesk Ivanti, although we can't compare all the features as we use it for other processes. 

We had assistance with the setup and only require three admins for maintenance tasks. 

I received professional support for the initial setup.

I don't directly deal with pricing. 

We're customers and end-users. 

I'd rate the solution seven out of ten. It's still new to me, and I'm still exploring its capabilities.