Workspace ONE UEM Reviews

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 use the solution with Horizon to set up VRA for new solutions.

When we publish the applications, getting the credentials to log in and keep the application up or running is easy.

The database gets corrupted when used in the cluster. Sometimes it works, sometimes it doesn't.

I have been using VMware Identity Manager since 2015-16.

The product is unstable.

You can use it anywhere. It's for everyone and every business.

I rate the solution’s scalability a five out of ten.

The initial setup is difficult and takes 30 minutes to complete. Depending on the customer, the deployment and configuration could take hours to weeks.

I rate the initial setup a four out of ten, where one is difficult and ten is easy.

Overall, I rate the solution a seven or eight out of ten.

I use Workspace ONE for my work with Homeland Security, but we're getting rid of it. VMware is the current mobile user platform for Homeland Security, specifically weapons of mass destruction. I've been consulting with them for the last four years, and I moved over to weapons of mass destruction four months ago. 

They're switching from VMware to Intune, and I was concerned with the due diligence. They've made a decision. and I'm helping them make that transition so that they can properly integrate the state and local devices for detecting chemical, biological, and nuclear attacks.

I just know some people at VMware at the senior level, and I talk to them when necessary. Homeland Security wasn't using the product how they should and they didn't reach out to VMware to identify the holes in the processes or inadequacies of the application that could've been addressed. 

The people in the weapons of mass destruction division didn't have the technical competencies to understand the software solutions, so they brought in a consulting company called Mobile Mentor, which is an Intune reseller. I told them that wasn't a reason to switch. 

VMware Workspace ONE is like any other product. You need to work with the vendor's software engineers to get the features you need to support your infrastructure. They can provide the technical modifications to the software you need to support your environment. 

For example, the Department of Defense has a peculiar IT infrastructure in terms of how they use SonicWall for mobile devices. If someone's using an Apple iPhone or an Android device, how do you partition it to support the mission? Public sector workers need to use a government cell because of the sensitive business they conduct on those devices. Mobile devices also include laptops and cell phones, creating more complexity. 

The bigger vendors like VMware, Insight, and MobileIron can assign engineers to customers. You can work with them to develop the right competency to use the product. 

I rate VMware Workspace ONE eight out of 10. 

Our primary use case is to control the email services for mobile devices and we are controlling that just to avoid leakage of the information for those devices.

The most valuable features are the ones that control the leaking.

The application itself individuals are getting annoyed with it. They are looking to integrate with ABB applications regardless of whether it is Android or iOS based. We are wanting to shift from this application because of the integration issues we are facing.

I have been working with VMware Workspace ONE for the past three years.

We currently have around one thousand end users.

I have spoken with technical support many times. I would rate them an eight on a scale of one to ten.

The initial setup is moderately complex. On a scale of one to five, I would rate that a five. The deployment time takes about seven months.

The pricing currently is higher than the competition.

It is based on the requirements. If he has Intune and has the Microsoft license already in place, it is based on those requirements, and based on the circumstances. But ultimately it is a good choice, I would not say it is a bad choice. I would rate VMware Workspace ONE an eight on a scale of one to ten.

We are resellers of this solution. The general use case for VMware Workspace ONE is when we need a virtual desktop.

VMware Workspace ONE gives our clients more management capacity. It makes administration control more secure, saving them time and money.

The most valuable feature of VMware Workspace ONE is that it can support most end users' enterprise applications.

VMware Workspace ONE is a stable solution.

This solution is scalable.

VMware's technical support is good. It can be difficult to reach the right person, but once you do, they are good. They are a bit slow but effective.

The initial setup is a bit complex. Deployment of VMware Workspace ONE takes about a week.

VMware Workspace requires approximately one to one and a half people to deploy and maintain the solution. These individuals are usually in a server admin or network admin role.

Our clients have commented that while it costs more for the year because of the need to add storage and servers, year two they see a decrease. They are seeing a savings of approximately 35% with the reduced need to buy new laptops and desktops. 

Our customers are concerned about the costs. The solution is higher than they want it to be. There are additional fees beyond the licensing fees. You need to have additional resources, like servers and more storage. This can become very expensive.

If you are considering VMware Workspace ONE, be sure to plan for the extra storage and server costs. 

I would rate this solution a 7 out of 10.

VMware Workspace ONE is used mainly for mobile device management.

What I found most valuable in VMware Workspace ONE is that it's user-friendly. It has a good interface for users to get access to applications and files. It's also a good source of feedback between IT and users.

A room for improvement for this product is its integration with Microsoft. It could be better, though most of it is there. There are some dependencies with Microsoft that aren't 100% yet, for example: compliance synchronization. It's something VMware is probably working on, but that's what's missing currently.

I've been working with VMware Workspace ONE for six years.

VMware Workspace ONE is a stable solution.

VMware Workspace ONE is scalable. When they're in the cloud, scaling will be handled by VMware, but for on-premises environments, it's easy to scale up if you need more resources for servers.

VMware technical support is good. It depends on what trouble we get, but if there's a known fix, they're able to fix it fast. If there's a fix that needs to be created, they will focus on it and prioritize it.

The initial setup for this solution is straightforward, especially because I've done this for six years. If you know what you're doing, setting it up is easy.

This solution was implemented in-house. I could probably have done everything, but I don't have time to do everything myself, so we work as a team and share tasks between us. We don't need VMware tech support for the deployment, not unless we find some bugs.

VMware Workspace ONE has a yearly license. You pay upfront for one year. You have to buy licenses for one year at a time.

I evaluated Microsoft Enterprise Mobility.

I work as a consultant, so I'm working with VMware Workspace ONE for my customers. I work with several different versions of this solution, but mostly with the latest version, and it will also depend on the requirement. Deployment is both on-premises and on cloud.

Completing the deployment for a cloud configuration of VMware Workspace ONE depends on how much you want to do, but a good, basic configuration could take three to five days.

We work with different customers, so this solution scales from a few hundred to several thousand users. I'm working mainly with iOS, Android, and macOS. They also have colleagues that handle the Windows desktop configurations.

The number of people needed for a VMware Workspace ONE deployment varies. I can't do everything alone, but if you are running it on-premises, the company should have resources, including handling vacations and sickness. There should be available resources for its deployment.

I'm giving VMware Workspace ONE a score of eight 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. 

One of our customers used it for centralizing and managing the identity and access of a SaaS-based solution. They used Workspace ONE to provide identity-based services and authentication, such as MFA. It integrates with Microsoft Office, Google Cloud, and things of that nature.

It is deployed in the cloud with a tie-in. It synchronizes to on-prem.

It has really easy and quick onboarding. Its transition and migration capabilities have been very helpful as we transition applications to the cloud. It was a central piece for enabling that to happen very quickly.

Clear and concise documentation is most valuable. That's a feature for me. 

Its UI is extremely easy to use whether you're an advanced user or a novice user. When I first opened it up and had to learn the product, I was easily a novice. By the end of the third month, I was digging into the backend of the system and using it as a highly advanced user to accomplish what I needed to accomplish, and I was able to do it through the UI mostly.

Support is probably the main challenge that we have. Their support was not very good. We had to tell them what we told them four or five times.

This product makes use of SAML across the board, which has seven known security flaws. It would be good if the company created a way to protect against SAML flaws. One way would be to integrate a firewall server or an endpoint out in the cloud with which you could establish trust. If you knew nothing about SAML and you did some Google searches about what SAML is, what are the flaws, and what are the known vulnerabilities, eventually, you'll find that there are seven flaws. There are two methods that you can use to solve those seven problems. They essentially involve putting a firewall or putting rules, such as access controls, so that anybody in the world can't just come in, authenticate, and either be a good guy or be someone trying to knock on my door and get into my house. If I could eliminate that, it would be awesome.

I used it about 30 days ago. It was a three-month project.

We didn't run into any bugs. In terms of performance, we didn't really test it for performance. We were not at all looking at performance metrics.

It seems like it would scale, but I can't really be sure because we did not test the scalability.

Our client has probably 2,000 people with all types of job roles. They are admins, engineers, and then there are regular users with no special privileges.

Their support needs to be improved. I don't know if this is a new area that the support people are learning, but the people supporting the product, or at least the people giving us the response back from support, were not very good. We had to tell them what we told them four or five times.

I didn't use any other solution previously.

There were five people involved. We had everyone from network architects to myself, an enterprise architect, and then we had representatives from each application. Everyone had their own little part to do, but the deployment was pretty straightforward and simple. It was so simple that we didn't believe some of the documentation. All you need to do is B and then C. It took having a little bit of faith and just walking through the instructions, and then, of course, we had to blow everything away and start again to try to repeat the deployment process so that we knew that all the steps were valid and accurate in multiple use cases, and they were.

It took us two and a half to three days to stand up the product. From there, onboarding applications went from two weeks to two days.

It requires ongoing maintenance. It's like running a cruise ship. You need to constantly monitor and maintain the product. We do that on behalf of our client.

It's definitely a bit on the expensive side. It is more for smaller organizations and not large, massive enterprises.

I am not sure about any additional costs. As far as we could tell, the billing was what the billing was.

Workspace ONE is one component of the solution. It is not the solution in itself. Workspace ONE is the front door and the locking mechanisms of all the doors, but you only need that if you're going to build a house.

I would rate it an eight out of 10.