Workspace ONE UEM Reviews

We use AirWatch for mobility management. We leverage all the basic functionalities this solution provides, such as MDM, MAM, MCM, MBM, and MIM.

Our company provides managed services to customers. We are a partner and managed services provider, and we help with the installation, implementation, and configuration of VMware solutions.

We are working with its latest version. In terms of deployment, it is a mix. Some of our customers opt for the on-prem model, and some of our customers want a site-based model.

Remote management is most valuable. It allows you to manage multiple types of devices. It is not just limited to laptops or desktops. You can also manage IoT devices. If a device is lost or stolen, you can easily take control of the device without letting any information get leaked.

Feature-wise, it is fine, but its pricing could be better, given that Microsoft is on a bundling spree. AirWatch would benefit from reducing the license pricing per user per month.

It has been a couple of years.

It is very reliable.

It is easy to scale. We deal with all kinds of companies, but it is mainly used for large companies.

I don't get involved with the installation or administration of VMware. There is a different team that looks into all these things. They might have been in touch with VMware's technical team. I am in touch with their alliance team.

For mobility management, we deal with VMware AirWatch and Microsoft Intune. Both products are more or less the same. Intune is just a basic solution, and feature-wise, AirWatch is better. Security-wise, AirWatch is better, but Intune is catching up. The benefit of Intune over AirWatch is the bundling and the pricing. 

I don't handle the technical bit. I am a product manager, and I'm not the one who installs this product. 

AirWatch would benefit from reducing the license pricing per user per month. Microsoft bundles everything, and then that bundling makes the product free for the customers.

It completely depends on the use case and what a company is looking for. For example, if they are an SMB and already have Microsoft products, then I would suggest they upgrade the licenses so that they get Intune or device management complimentary. For a big organization, we need to do some feasibility study to understand the customer requirements, and based on that, we can suggest a product. 

AirWatch has been a leader, and it has always been in the top category. I would rate it a solid nine out of 10.

We deploy Workspace ONE for our customers for Windows, Mac, and modern desktop Windows 10 management. It also provides MDM capability and application push for their mobile devices. That's the use case we are focusing on — application push and patch management. That's the modern management we are doing right now.

Workspace ONE adds a lot of value compared to Microsoft because Microsoft is a late entry into the market, and they're still developing their product from an end-user perspective. Workspace ONE has a slight edge because of AirWatch. VMware has developed its product over a longer period of time, so they have better integrations as a whole solution.

Windows 10 management is there, but VMware only recently developed that part, and it's not fully mature. Patch management and other integrations are there as well as the application-pushing part, command line, mandatory commands, etc. Some out-of-the-box solutions should be available to better integrate a broader range of applications and handle application push. That's the roadmap we should look at.

We have been using VMware Workspace ONE for ourselves as well as for our customers for nearly five years.

WorkspaceONE's stability is excellent. I haven't seen any issues in the last four years— no major disasters.

We are managing around 30,000 endpoints and devices, so it's a highly scalable solution. We're recommending our customers renew the solution. We might grow 5 to 10 percent in the next year.

VMware tech support is professional. There are delays sometimes, but it's good overall.

A long time ago, I was using Blackberry. 

Workspace ONE is relatively easy to install. A few things are complicated from a high availability perspective. Otherwise, it's straightforward. Total deployment took one week. One person can deploy and manage the solution.  

I rate Workspace ONE nine out of 10. Users are working from home all over the world, so companies need to consider things from a security perspective and the segregation of personal use from office work.

Workspace ONE has a pretty broad range of features and capabilities. It's like a market-wide buffet that hasn't yet spread out. However, when compared to its competitors, such as Microsoft Intune, Intune is behind the game, but it has been catching up in terms of the capabilities and features that it now has to offer.

The Identity component of this solution is its most valuable feature.

VMware provides a wide range of services that are second to none.

They need a more flexible pricing model.

I have been working with VMware Workspace ONE for four years.

In terms of stability, I would say VMware Workspace ONE is fairly stable, but not every OEM vendor in the world can provide products that are error-free. When it comes to fixing errors, I believe VMware is on the right track. The problems aren't bothering the customers.

There are some errors but nothing that is of concern and it gets corrected quickly.

When compared to its competitors such as Microsoft, VMware is a much more scalable product, in my opinion.

When it comes to their SaaS offering, I would say the product is a little more flexible and scalable.

In terms of support, I would say it is adequate. When compared to Microsoft, I would say VMware support is excellent. However, there are times when you need to escalate certain issues in order to gain traction. And if you're not getting anywhere with your support cases, you may need to escalate internally.

Previously, I worked with Microsoft Intune.

Microsoft's licensing is more flexible and adaptive, in my opinion. In Microsoft, you pay for whatever you use. In terms of services, it is more evenly distributed. You only need to pay for one license to get access to a suite of products. From your office to your endpoint, you are essentially managing your endpoint. Everything is combined into a single console. somewhat more flexible on the Microsoft side, which is lacking on the VMware side.

In terms of features, I believe VMware has struck the right chord. However, there are some features in Microsoft that are lacking. I'm confident that Microsoft will try to catch up over time, and it will be there, within the next year or two.

I would say it was a straightforward process because if you are a potential lead for the product, the relevant stakeholders, such as the sales team, take action and then convert it. They perform POCs.

I would say that at the very least the pricing needs to be revised. Workspace ONE is on the higher end of the pricing band when compared to other players in the market.

Pricing may need to be subsidized.

The price is reasonable given the features that Workspace ONE provides. 

Not every company or every organization in the world can afford the VMware Workspace ONE just for the features. Some companies might be using some of the features, and they will have to pay for the rest of the features, even if they are not utilizing them.

I am not currently affiliated with any company, such as a solution provider, an MSP, or a product company that sells this product. I'm now more interested in DevOps.

I haven't been in touch with MDM technology in about six to eight months. We were gold-certified partners with VMware, as well as Microsoft.

I was a partner selling services and developing solutions for their customers.

I would advise them to first prioritize what they want to achieve. Rather than wandering aimlessly through the market in search of a specific product. First, they must understand or, more likely, articulate their use cases. And then, based on the pricing model, decide whether they want a lot more features so that they can use the services later on, rather than just going with whatever players are available in the market.

Make certain that it is the solution you require.

I would rate VMware Workspace ONE an eight out of ten.

We recently integrated Workspace ONE with our intelligence report, and this is a great tool from a reporting point of view. In our daily business, we get several requests from businesses to provide an Adobe request for monitoring, whether it is for Android or iOS devices. The main benefit of this tool is that we can exclude the report for applications. Another benefit of Workspace ONE is that it supports many devices, which is a major benefit for us.

There are some bugs that our team needs to work around. It required some API integration required because visitor integration was not there. For example, we are currently working on a tunnel issue, and VMware doesn't have this solution. I think the R&D team is working on this, and I think this is something they need to look into because from the Android point of view, this is the major security tool, and these features need to work as expected.

Workspace ONE is stable.

Once Workspace ONE is configured, the scalability is good.

I rate VMware technical support eight out of 10.

Setting up Workspace ONE is straightforward. In December 2020, I worked with the VMware deployment team, and we deployed this in 10 to 15 days for all components, whether it is Workspace ONE Access or Okta integration. It's easy to use, migrate, and configure. Deployment and maintenance require four to five people, including two solution architects and two or three engineers. 

I rate Workspace ONE eight out of 10. If someone comes to me, I would advise them to go with this tool rather than Intune. There are several benefits, and it doesn't cost much compared to Intune. Intune doesn't have all the components and integration we require.

We use this solution for mobile device management. At the moment, we are focused on managing iPhones.

The most valuable feature is the security policies.

Part of the SaaS environment is the VMware identity provider, which we use to provide single sign-on for mobile phones and apps.

The SaaS environment is not very responsive at times, so the performance can be improved in that regard.

The initial setup could be easier to do.

This is a very stable product. We haven't had any problems with it, including after any updates that were made.

The scalability is very nice. As a cloud-based solution, there is no problem with this. We have approximately 2,600 users and we plan to increase our usage in the future.

The technical support from VMware is normally perfect, although sometimes, it is not fast enough. Typically, we receive answers in adequate time so overall, it is okay.

We started with VMware Workspace ONE and did not use another product beforehand.

The initial setup is not very easy.

For the deployment, two people were required. Only one person is needed to maintain it.

We needed a partner to assist us with deployment.

Our intention was to improve the security of our mobile devices. ROI is not really quantifiable.

There is a licensing fee for the users, and we pay a low amount for our support costs. We hire a consultancy for support but it is not very expensive.

We evaluated Microsoft Intune and a third product. Ultimately, we decided to implement VMware Workspace ONE.

My advice for anybody who is implementing this product is to look deeply at the technical details, right at the beginning. Doing so is necessary and makes it easier to start the project, as well as for integration.

I would rate this solution an eight out of ten.

Our primary use case is for end-user devices, such as emails and internally developed applications.

The most valuable features of VMware Workspace ONE are security and having support for all the latest features that are coming out from Apple. They're pretty fast at adopting new features. This is one of the most vital aspects of mobile device management systems.

VMware Workspace ONE platform offers support for Mac Books and we see that there is some room for improvement in that area versus all the products out there.

I have been using VMware Workspace ONE for approximately seven years.

VMware Workspace ONE is stable.

The solution is scalable.

Sometimes the first line support is a bit troublesome. It's not until you talk to a real engineer do you receive the answers to the issues you might be faced with. We had the same issue with Microsoft support.

The price of VMware Workspace ONE is reasonable.

I have evaluated Microsoft Cloud and Office 365.

Right now we don't see there's an MDM solution out there that's better than VMware Workspace ONE. It makes sense that companies are leaning more and more towards the Microsoft Cloud and Office 365, and they do offer Intune as well. That makes sense in that context, but if you look at the benefits of the MDM solutions versus each other, from what we've done in our research and analysis, VMware is still the best tool on the market.

We have a couple of issues that we have seen every now and then, but it's always the same issues and it's not something that's related to VMware. It's typically from our own underlying infrastructure components that are not really reliable.

I rate VMware Workspace ONE a nine out of ten.

It's a SIEM solution. It's a solution used to manage the identity of the users. It also makes a federation for the data applications and gives access to the users, and provisions the users in other applications, including SaaS applications (for example, Microsoft 365, SoundDesk, or Salesforce). 

We use it to provide the users a smooth authentication to the applications with, for example, mobile, or a log in with a certificate from the Windows machines.

Our users have a lot of cloud applications. To manage those, you have to manage all these passwords and users' names and provide access to a lot of services. Potentially, the users could forget their user names and passwords and everything like that. We provide smooth access with mobile SSO to these solutions with one click. The user just opens the catalog applications in the device, and those devices could be, for example, iOS or Android or Windows or macOS or Chrome OS, et cetera. They open the catalog and with just one click on they have access. They don't need separate passwords, user names, et cetera.

Its value is when you use it with a Workspace ONE UEM solution as it is part of the ecosystem for VMware Workspace ONE.

Technically speaking, it's a very good product.

The setup of the product is not complex.

The license could be better. You can't simply license access to services for devices - you have to license the product to users. The problem with that is some companies don't have licenses for the whole user catalog and just offer licenses for the devices themselves, meaning they aren't directly attached to a user. That's the main problem of Identity Manager.

In terms of stability, the performance in the SaaS environment is pretty good. The problem is, with the on-premises version, there can be hardware problems. That said, it depends on the machines that the customer use. Usually, the service is fast and you don't have any problem with the performance. It uses sometimes a lot of resources though.

It's not easy to scale it if you have a setup on-premises as it's necessary to build a cluster, and clusters are not easy to build. However, in the SaaS environment, there is no problem, it's very scalable.

Our company is a small company. We are 200 people. However, I have a lot of customers and a lot of Identity Managers deployed; there are maybe millions of people. 

Technical support is not bad, however, they are not as good as it could be. 

We are currently migrating to Okta, a different product. 

Most clients did not previously use a different solution. Identity Manager was their first. 

The initial setup of the product is very simple and quite straightforward. 

The deployment process does not require a big team. For a big company with, for example, 10,000 users or more, you can manage it with three or four people. It's enough. The amount of time it takes can range from a few days to a few weeks depending on the size of the project. It's usually less than a month. 

If it's an on-premises deployment, you do have a bit of maintenance, however, if you have a SaaS deployment, there is no maintenance required. With on-premises, you just make some changes or add new applications or new users, and that is quite simple. The problems come when you need to upgrade versions if you have the solution on-premise.

In terms of pricing, it's reasonable if you have the Workspace ONE solution. If you don't have the full solution, it's quite expensive.

There are no extra costs beyond the standard licensing fee. 

We have a partnership with this product.

We use both Software as a Service and also on-premises deployment models. That said, the on-premises version is not exactly the same as the SaaS one. 

I would recommend people to use it only if they have Workspace ONE, Workspace ONE UEM, the Unified Endpoint Management.

I would rate the solution at a nine out of ten. 

At the time, our primary use case was for the purpose of having single authentication around endpoints. Every single endpoint was managed by Workspace ONE: iOS, Android devices, and Windows standard devices. We were provisioning payloads. We had a trust relationship between Workspace ONE and the vIDM console, and we were handling certificates around those, to provide seamless certification. In the end, a user with specific applications wouldn't be required to type in any username, password, etc. 

vIDM was a SaaS-based solution, at the time, where you had the vIDM connectors in case you were required to have LDAP Synchronization. It was completely on a dedicated cloud from VMware. 

One of the main benefits was end user experience. Imagine that your business apps on your mobile device, for instance, no longer require you to type in your username, password, or second factor of authentication—as long as you're handling a managed and trustworthy device, you can seamlessly log in to applications. In the past, I personally integrated it with applications like SAT and Salesforce. As long as the application offered integration, we could easily do this. 

One of the features that I enjoyed most was the integration with Azure AD because I could use VMware Identity Manager to standardize the User Principal Name coming from Active Directory. You have Azure AD Connect to do that. In between, if you have vIDM handling it, you can easily get the synchronization of users into your VM and standardize the User Principal Name. If you require quality assurance for handling it, you can actually count on the vIDM to do so. That was one of the main things I enjoyed about the product. 

vIDM could be improved with the multi-tenant capabilities that VMware tends to offer—features like customization branding and the integration of the app catalog based on the branding. Since the integration has been at top-level OGs, you were not able to then do rebranding if you were required to use specific user groups to highlight specific applications. At the time, I was personally opening feature requests for these things. I haven't worked with the latest release, so I don't know if these features were already deployed or not. 

I used vIDM for about four years, though the last time I worked with it was about a year ago. 

I can't recall having any problems with stability or performance. 

The maintenance, regarding the core system, was provided by VMware directly. For the connectors hosted on our on-prem infrastructure, maintenance was handled by the team responsible for the product. 

It's easy to scale, since it's in the cloud. We never had to worry about scalability. 

At the time, there were about 120,000 people in the company using this solution. 

VMware has the standard support, and then they have enterprise support or special contracts for enterprise support with dedicated teams. We never had to deal with the default, but nonetheless, there will always be glitches around tech support. We were quite knowledgeable about the products, so if we actually raised a ticket, it was because something was definitely not working and there was a bug on the product itself. It was mostly the case that it would be dropped at the product management team directly. 

The deployment was complex, considering the infrastructure. Our organization has more than 400,000 users, so the complexity of the in-house infrastructure is quite high, which implies some complexity during the deployment process as well. You need to interact with several teams regarding identity management or identity access management. On a small-sized company, it may be quite straightforward. 

We first collected the requirements, which was straightforward. Then—this will depend on the size of the organization—we had five or six people around the required services. They came from Active Directory, the main identity provider, the application owners for service provider integration, and it took them a few days. 

We implemented this solution through an in-house team. 

I rate vIDM a nine out of ten. During the time I worked with it, it was a really nice product, and it was straightforward and reliable.