Workspace ONE UEM Reviews

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. 

We use VMware Workspace ONE for desktop virtualization.

When compared to competitors, VMware Workspace ONE is quite good.

As we are driving this business for the credit bureau, all of the benefits and features are available, as well as a few regulatory terms from the RBA. We have to abide by the rules and the regulatory terms. The MDM solution satisfies all of the requirements.

The performance is good, and it is easy to configure.

The user interface is very friendly.

Our central authentication mechanism is not integrated with this solution, which we deployed three years ago. So far, our goal is to integrate it with our two directory servers, but we've run into a few challenges. We are not able to connect with support to help us resolve this integration issue.

I would like to see improvements made to both the support, and the pricing.

We have been using VMware Workspace ONE for three years.

VMware Workspace ONE is a stable solution.

This system may be scaled up with further licensing, which is beneficial to the company.

It has scalable capabilities.

In our organization, I believe we have 100 users.

Technical support is an area that needs improvement.

I'm having difficulties with VMware support, with AirWatch, Workspace ONE. We would like to integrate it with our central authentication system, but there are some issues. We have been trying to connect with the technical support team to help us resolve this issue.

We are using AirWatch, which is an MDM solution, and we are also using SaltStack, for automation. 

VMware recently acquired SaltStack. According to my knowledge, the merger with SaltStack occurred this year.

After you've deployed the solution for your company, there are only a few things left to accomplish, such as adding or configuring new users. If someone leaves the organization, you have to remove them, which does not require further administrative effort.

I believe it takes around 10 to 15 minutes to configure a new user.

A technical team of only two to three people is sufficient, especially considering they have 24/7 assistance.

The installation can easily be done yourself, it's easy. 

Anyone can follow the instructions or watch the video and do it themselves.

It's a costly solution.

While it is not inexpensive in terms of price, it is definitely worth it. In terms of pricing and the functionality we get with the MDM, I believe it is more than adequate.

We have a three-year subscription.

With the many solutions available such as IBM MaaS360 and Microsoft Intune, you have to consider the business requirements, the software you will be using, and the strength of the security it provides.

This solution is very secure, and I would definitely recommend it to others.

I would rate VMware Workspace ONE a nine out of ten because the support is lacking.

We use VMware Workspace ONE for our Android devices. I also use it for handheld scanners.

From a remote management perspective, I like the management and the inventory.

In terms of Workspace ONE, we are migrating it from on-premises to the cloud.

I would like to see more service notifications.

We have been using VMware Workspace ONE for five years.

VMware Workspace ONE is stable. We do have a few outages, but they are few and far between. We were able to recover quickly.

Scalability is a problem because we have a service provider who is supposed to maintain the backend with patching. As a result, when we want to use a remote capability the environment must be updated.

The technical support is good.

We use Jamf, for our MacBook Space and our Apple Mac Space.

I prefer working with Jamf. When we did a side-by-side pilot, and I found it to be easier.

When I focus on one product, I gain a better understanding. It is the Apple brand, in my opinion. I now have a better grasp of the policies and groups.

It's pretty simple in my opinion, but I'm not the technical owner. I was just collaborating with a colleague to assist him with it, but it was fairly simple.

I don't have a view on pricing.

I would rate VMware Workspace ONE a six out of ten.

Our use case of this solution is for the Zero Trust feature; when anyone from the company logs in, the authentication goes through VMware Access and checks that only devices owned by our company can access all their source and on-premise applications. I'm CEO of the company. 

We use the solution in conjunction with Okta and that is perfect because it enables us to set it up and get the best out of the Zero Trust implementation. Both the identity MSA as well as the device are checked at the same time.

Using the solution on Android requires a special setup, the mobile SSO doesn't work as well. It would be easier if it was integrated and we could do it similarly to the iOS SSO setup. 

Our users access the solution every day and we haven't had a single stability issue in the past 12 months. It just works. We have one person working part-time on maintenance which is usually when we have changes to our applications, otherwise, it just runs in the background. Because it's a SaaS service all the upgrades are done automatically in the cloud. 

We've done 10,000 implementations globally and we have 250 users in the company. The advantage of it being a SaaS application means that even small companies, say 10 or 20 people, can use it. There's no financial hindrance to doing that.

They have a very knowledgeable guy, who's worked on the development side and provides us with good service. With some of the bigger US software companies, getting through the first level of support can be tedious.

The initial setup is pretty simple. We deployed internally, we have really good senior consultants who carry out the installations for us and for our customers. Deployment takes a maximum of two days. 

The solution is licensed per user. It's part of their advanced package, and it comes together with the MDM part. Depending on your needs, the license can be $40, $60, or $100 per year. It's an SaaS subscription.

VMware bought AirWatch mobile management and married Identity Manager with MDM. When VMware and Okta started working together for Adobe, they needed to make it work successfully. When we got the results, it was a no-brainer for us.

It's important to look at the bigger picture to get the full benefit of the product. It can be tailor-made to suit your needs. Some countries might not be able to access it or they might find that there's an extra MFA. MDM or Identity Manager separately are not enough. You need both, as well as Okta to get the full story, so to speak. They work closely with VMware so that the pieces all work together with their product. It's perfect for our customers and our company. The important thing is that it's developing all the time and they are constantly working on it, so if it's good now, it will be good in two years as well.

I rate the solution nine out of 10. 

We use VMware Workspace ONE for our mobile devices. We are not building Workspace ONE; we are maintaining mobile device compliance and corporate device tracking compliance.

We create policies, push apps, and enable users to download apps according to the ASA request and the company requests.

The most valuable feature of this solution is the tracking of the devices. It is not only available for iPad and iMac Pro, we can track Android devices and cross-functional devices in Workspace ONE.

It's a simplified platform for managing all of our devices.

There is no Apple zero-day support for updates.

The Apple developer option is not enabled in OEM, which makes it very difficult to manage the Mac devices proactively. 

They rely on a third-party tool for the packaging, which is why they are lagging.

I would like to see Apple and Mac devices have zero-day support. It needs to be activated.

The Macbook downloadable license needs to be integrated.

We have faced some issues with the stability of this solution.

It is not as stable on mobile devices as Jamf Pro and Mac devices.

They do not have 24/7 support or in-person support available in OEM. Any issues we have will take one or two days to get a response. As we are in India, the response comes a bit late and will drag to the next day or two. Will be waiting for at least two days for a solution in the OEM.

I have only used it with Mac devices. Comparatively for Mac devices, I can rate it a six out of ten.

We deploy AirWatch on the mobile devices of our employees. 

It has improved the way our organization functions. It provides security. If you're giving phones to your employees, you want the platform to be secure. If an employee loses his or her phone or someone steals it, the data on the phone itself is secured because you can just centrally disable everything. So, you only lose the device but not the data. If you lose your phone and there is no AirWatch in it, you need to find other creative ways to disable or get your phone back.

It allows companies to apply rules related to company policy. You can use your phone like a normal device with the exception that it is being monitored by the company, which I don't mind because I use the phone exclusively for work.

You can put all your applications on a mobile device, be it a phone or tablet. It is secure and easy to use. Because it is centrally managed, you don't have to do any configuration on the phone. I just got the phone and connected to the central applications. I just downloaded one thing and everything got rolled out. Email, calendar, and other things were deployed centrally. If you don't have AirWatch, you have to configure your phone manually. For example, you need to deploy and configure your email manually and then synchronize everything. It is much simpler when a mobile device is centrally managed.

Its performance is quite good on Apple phones or even mid-range phones. If you install an AirWatch on a phone that is not too powerful, you will have performance issues. That's because the phone is not too powerful, and there is not enough memory, etc. They could do a lighter version for a less powerful phone. It would also be useful for very small companies that don't want to spend money on expensive phones. Having said that, I don't think that is their target market. If their target market is enterprise, all enterprises perhaps have an agreement with Google or Apple, and they would get a phone that has already been tested, and they know that AirWatch will work on that phone.

I have been using this solution for three months.

It is stable. There are no issues or bugs at this moment. In the earlier versions, there were some bugs, but they have fixed those. My experience is only with iOS, and it seems stable. I have got an Apple device. iOS is a quite stable platform, and they have tuned it to work really well with iOS and even Android. 

My company is quite big, and it seems good for big companies. It is for the enterprise environment. You won't use AirWatch for one or two individuals. You use it when you have a quite sizable mass of employees. In our company, it is being used by sales professionals, VPs, and C-levels.

I have not used their technical support. After you do the installation, usually you shouldn't have any problem unless there is a hardware issue with the phone itself. If there is any problem with AirWatch, they should be able to fix it from there because everything is centrally managed.

When I joined the company, they gave me the phone and asked me to install AirWatch, so that was it.

It is quite straightforward for technical and non-technical people. You just press next and read what you're doing, and that's it. It is nothing too complex.

It is quite expensive, but I think large companies have agreements with these organizations that provide remote monitoring for phones, and they get massive discounts. The public price does not reflect what they pay. You won't get the same pricing if you're buying for 10 employees versus 1,000 employees. On the public price, you get perhaps a 10% discount, but if you're buying 1,000, the discount could be really massive, especially if you signed a contract for a number of years.

I would rate AirWatch a nine out of ten. It is quite good, and I have a good experience with it. The phone has never failed, so it is working well.

We've had a full range of use cases. It's great for community colleges or remote workers. Onsite it can be on desktops or mobile. It has the ability to wipe mobile devices. You can lock them down or control them.

Obviously, with COVID, the remote workforce has been a huge driver.

I had one client that had a bunch of gyms where you got to work out and they deployed Workspace One across all of them and used that just to serve all the desktops. That way everything was uniform, and everything was the same patching level. It just simplified management. That's one example of a specific use-case.

You can always do more to gain network efficiency for delivery. At the end of the day, you're sending mouse clicks, keyboards, and screens out, and just improving delivery mechanisms. If you've got a full spectrum of consumers out there, they are there on everything. You've got everything from cellular service to multi-gigabit in homes these days. Just optimizing the network, that is a thing companies are going to chase - and that will be the case across all solutions.

The customer needed to cut their budget. They already owned Workspace One which was an additional cost. VMware just released an MDM-only version of Workspace One, which was much less and that met their budget needs. They were able to stay on the same platform and cut their budget as they needed.

All of the features have been quite helpful. They are all equally powerful and equally valuable for businesses - however, for different reasons. It just depends on the business which features end up being the most valuable to them.

Mainly, the solution offers a simplified administration, which is likely the biggest value for a business. The solution makes it possible for businesses to free their people up to think about the next steps for the business.

 Particularly during COVID, everybody had to evolve all of their businesses to survive. Everyone has been looking for better ROI.

The initial setup is pretty straightforward.

The solution has very good documentation.

We've found the solution to be very stable.

I'd like to see expanded device support, particularly for IoT things like SCADA devices. That would be a huge benefit, especially as we automate more in production in the commercial sectors like manufacturing.

I've been using the solution for about three and a half years at this point. It's been a while now.

Overall I'm impressed with the solution. Some of the historical predecessors have not been as solid and stable as compared to Intune. VMware is adapting and scaling the Workstation One product line, and they likely just created the new MDM-only version to have something outside of Horizon for people who want only MDM. 

That said, this is very stable. It doesn't have bugs or glitches and doesn't crash or freeze. It's very good.

We've found that the solution works just as well for small companies as it does for large ones. It works across the spectrum of business sizes very well.

I have had interactions with technical support. Each customer is different, however. Sometimes we get into some squirrely situations where we're trying to meet a weird customer need and have to pull them in. 

I have found them to be very, very knowledgeable and very good at thinking out of the box. I've never had a bad experience with one of their engineers - even if they are trying to help me do something weird. When a customer wants to do something really weird, they find a way to make it work. I haven't had a situation where they couldn't make it work.

We are extremely satisfied with their level of support.

The initial setup is not complex, especially if you're familiar with the VMware product line. It's very straightforward due to the fact that it's intuitive with our way of thinking.

Most IT people will tell you if they came up with Microsoft or Cisco, whichever ecosystem, once they understood the mental model behind product design, then it didn't matter. They could find their way around anything new. The same is true with VMware. If a company is used to VMware tools and other areas, it'll transition straight across for that.

In our case, we did an emergency deployment. What I would call a saturation deployment. We threw technical bodies at it to get it done faster. We turned it in in about 48 hours. The equipment came onsite. 

Assuming the equipment's there, you can move fast. What might be an issue right now is lag time. The big lag time is just trying to get the equipment. Once it's was there, we were able to turn it around within 48 hours. It was for a 3,500 students community college that went overnight during COVID from classroom instruction to online. 

Their first online classes were zoom. They deployed a whole bunch of low-cost laptops out there and they allowed people to bring their own devices if they had one, as long as the college could manage it. It was just kind of a rush, however, we got it out and deployed and we found that help desk calls were very low. It's just a combination of a great product and good documentation.

In terms of maintenance, if it's MDM-only then you just need one person, maybe half time, for up to a thousand users. I've got one person at about 2,500 users right now. It's just a matter of how much change goes on in the environment, or if are you deploying new applications or iOS versions. If you are constantly turning over devices, you may need a bit more maintenance. Typically this type of work is assigned to an end-point administrator.

The solution runs at roughly around $36/user for a year. Companies just pay the basic fee. That's MSRP. They do sales off of that so that vendors can get discounts under certain circumstances. The price will vary, however, that's the MSRP on it.

I've seen them go crazy at the company's year-end. Timing really can be everything.

I'm a solutions architect for a VMware partner. I supervise the implementation team. There are engineers that are out there that implement it and do the post-implementation support as well.

Largely, we are working with on-premises deployment models, however, we're working towards a hybrid deployment. It's hard for some organizations to break the old ways of thinking. They mistrust the cloud and while on-site is tried and true, and something you can put your hand on, it's just an education process and it takes time for companies to come around to the cloud is just as good.

I would advise companies to not implement as you learn. Rather take time to understand the product and plan everything ahead. It will be easier.

On a scale from one to ten. I'd put it at an eight. There's always room to improve and always room to grow. In comparison, for example, I'd rate Intune about a six, however, it's definitely coming.