Workspace ONE UEM Reviews

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 mainly use the solution for deployed iPhones and tablets. I'm a telecom and mobile device support analyst. 

Once you get to know the solution it's quite simple to use. It's really a matter of pushing profiles. Ease of use is a good aspect. 

The main negative issue is the cost of licensing. In terms of additional features, it's hard to say because I know there are other options out there, add-ons and other things that are within workspace and available,but I haven't had time to investigate. We're not going to be supported after next year.

I've been using this solution for three years. 

That area is all connected with the upgrades. We've had some issues and we've had to have a contractor come in to help us scale up. 

We're in contact with customer support all the time and they are pretty good on the phone, Because they have a 24-hour support desk, we always get somebody in India and sometimes there's a bit of a language barrier but on the whole, they're good. 

I don't deal with the licensing myself but we've got 1,500 devices so you can get an idea of what the cost is going to be. We have 500 users in the company. 

I would rate this solution an eight out of 10. 

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. 

This solution is primarily used for mobility services. The solution has been mainly used for multiple platforms, including Android, Linux-based services, Windows, and MacBooks. If you want to access your organization data from anywhere, from any device, you do it via this solution.

The solution is very stable.

The solution scales well.

We've found the solution to be easy to use. Compared to other products, this is much better for MBM products.

The solution needs to offer better training. We need to understand items such as third-party integration capabilities or new features before we start to work on a new implementation. Sometimes, this isn't clear and it can affect our work. The training that is available is quite expensive for us. They need to make it much more reasonable so that we can afford to be properly trained and informed.

Technical support needs to be more responsive to our requests. If something happens on a weekend, we won't get any help until at least the next business day.

I've been using the solution for the past two years at this point.

The product is very stable. We don't experience bugs or glitches per se. It doesn't crash or freeze. It's reliable.

The solution is quite scalable. If a company wants to expand it, they can. It's not difficult.

Currently in my organization, we are using the solution for 300 people. However, I have done installations for approximately five to six clients. In the last one and a half years I have done installations for different types of devices and have handled anywhere from 5,000 devices, and users all the way up to 10,000 users. In the latest deployment I'm working on has 30,000 users.

Technical support is pretty good. That said, if something happens on a weekend, we won't be able to get the support we need. It also sometimes takes a while to get everything resolved. We might have to email back and forth two or three times. It really should be faster.

I also have experience with Jamf Pro, however, that solution is specifically used for Apple products.

The initial setup can be straightforward, however, it depends on the installation requirements and the clients' requirements. It depends on if they want the DR setup or a DC or SA set up, and/or clustering. If the requirements increase, the time it takes will increase as well. If the prerequisite has been done clearly previous to the starting of the installation, then it will take much less time.

I implement the solution on behalf of clients.

I don't handle licensing or billing. Therefore, I'm not sure what the total cost is to our organization. I don't know if it's overly expensive or fairly reasonable. I'm purely a technical team member.

I'm using the latest version of the solution.

I'm not a client. I'm an architect of Workspace ONE. I implement the solution for clients, so I don't use it directly per se. I implement all deployment models, both cloud and on-premises.

I'd recommend the solution to other companies.

Overall, I've been pretty satisfied with the solution. I would rate it at a seven out of ten. It has all of the features I need. We just need to be better informed when there are new features or changes.

All the use cases are related to Salesforce and people who are working outside the office. Sometimes, they register their PCs inside the office in Workspace ONE to manage them and push some software or install it remotely and some kind of things.

It's easier to install new software remotely using Workspace ONE because you don't need to stay in the office or maybe connected to a certain server in order to install that software. So it's easier to manage PCs, laptops, phones, and desktops.

Workspace ONE has something like an orchestrator model that allows me to configure a set of steps to onboard new PCs, laptops, or tablets. So, it makes my work easy.

One thing VMware needs to improve is compatibility with different operating systems. Sometimes, customers have old operating systems that are outside the compatibility metrics of Workspace ONE UEM. So sometimes it's difficult to request customers to upgrade those old PCs, and that's a problem for me.

I have been using this solution for three years. We have different versions, but currently it's 20.1. It is the latest version because we use the cloud version.

I would rate the stability a nine out of ten.

I would rate the scalability a ten out of ten.

I have deployed different kinds of architectures. Some are easier, and some are complex, but I have deployed Workspace ONE many times.

I have deployed Workspace ONE, UEM, and Workspace ONE Access.

The return on investment is big because the administrators of those PCs do much less work to manage those pieces. So, it works.

I would advise just being clear about your use case and what issue you want to solve in your business. Try the drive test of Workspace ONE in VMware. It can give you some insights about this solution.

Overall, I would rate the solution a nine out of ten. 

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.

We mainly use VMware Workspace ONE for managing Macs and iOS devices. 

Although it's supposed to be compatible with Chromebooks and Windows, we find that it's quite limited. I think it doesn't work properly with Chromebooks because you need a Google license to manage them. For this reason, we didn't end up using AirWatch with Chromebooks.

The overall accuracy could also be improved. It's not accurate enough when it comes to sending items to end-users.

I have been using VMware Workspace ONE for three years.

VMware Workspace ONE has been stable so far. 

My main concern with the support is that they don't have a team. You always get a freelancer — often there are difficulties relating to language barriers. Sometimes they are experts, sometimes they are not.

I didn't do the initial setup by myself. I had to hire a consultant and some other specialists to do it for me.

VMware Workspace ONE is not cheap; it's quite expensive. However, in the end, they gave us a reasonable price.

If you have Mac or SNIS devices, it works fine and the price will be reasonable. If you have a lot of money to invest, there are better options out there.

Overall, on a scale from one to ten, I would give VMware Workspace ONE a rating of eight.

There should be more powerful features available for Mac, like what GEMS has already introduced — especially in regards to the level of system updates, and software updates. It should be easier to manage things, especially for Mac. If they improved this, I would give them a higher rating.