Share your experience using VMware App Volumes

If you want to manage your mobile device manager, which includes mobile devices and Windows and Mac devices, you can go for Workspace ONE UEM.

If you want to manage Office 365 and any SAML authentication to secure your access with multi-factor authentication, you can go for Workspace ONE Access.

If you want a VDI solution, you can go for the Horizon VDI solution to reduce your purchase costs. If you don't want to spend money, you can buy a VDI solution, which is secure, and you can deploy any VDI machine and any virtual application through Horizon.

In UEM, the most helpful part of Windows Management is the baseline policy and central script; using this, you can replace all the AD GPO policy. You can deploy any kind of policy for Windows devices, and this is the main component of the UEM for Windows management.

The Workspace ONE UEM interface is very easy to understand; there are not many doubts regarding configuration and providing use cases, so it's good.

The major competitor is Microsoft Intune.

Pricing-wise, it is slightly less than Intune. Intune and Workspace ONE are close in pricing, but other solutions provide more competitive pricing. Another concern is that support is getting reduced by Workspace ONE; some customers are saying there are support issues on Workspace ONE right now. The two major issues are pricing and support.

I have been working with Workspace ONE UEM for approximately 11 years.

If customers are getting issues on Workspace ONE UEM, such as Windows Management or any Android, iOS management, and I'm unable to resolve the issue, I raise a ticket. Support responds immediately, but I see that some engineers are new or they don't have experience collecting logs, so they take two to three days to come back. It is not poor support, but it is not perfect support we're getting right now; it is not an immediate solution, and it may take two or three days.

Neutral

Functionality-wise, if I want to go for only Windows management, then I can prefer Intune, but other solutions provide the same functionalities. Intune is better for Windows management, but if I want to manage all platforms such as Android, Windows, iOS, and Mac, I prefer Workspace ONE.

I'm calling from India, and currently, the main concern point is pricing. There are a lot of solutions in India providing better solutions compared to AirWatch, but the main concern is pricing. Other solutions compete on pricing, and customers are buying their solutions based on that. Overall, Workspace ONE is perfect for me as it provides all the solutions that address customer use cases, but the only issue is pricing in India.

If there is less use case, it will take a day or less; with my 11 years of experience, I can do it within the first half, approximately two to three hours.

I haven't received any use cases regarding AI features or integration capabilities with Workspace ONE.

On a scale of 1-10, I rate Workspace ONE UEM a 7.

We are using VMware Workstation very heavily. VMware Workstation is our main product we are using.We primarily use VMware Workstation mainly for development. We are developing for several customers and these products cannot be developed on the same machine. So, we have virtual machines to be able to have different development environments for our different customers. That's the way we use VMware Workstation.

Simply being able to run several Windows PCs with different development environments has had the largest impact on our operational efficiency. There's no special feature from VMware Workstation that influenced our decision. For quite some time, VMware Workstation was the most stable environment we could have. In recent times we noticed some disadvantages in reliability, so we are now also using VirtualBox besides VMware Workstation.

The problem we are facing with stability is that the network adapter causes crashes of the VM when we're using it for developing purposes. It's actually the Intel network adapter in VMware that causes machine crashes frequently.I would still recommend VMware Workstation to others. It's actually only unstable in the way we are using it. We are using the network in a very specific way, and this network adapter causes crashes in the VM.

We did not face any challenges while integrating Workstation into our environment. That's very smooth.

The problem we are facing with stability is that the network adapter causes crashes of the VM when we're using it for developing purposes. It's actually the Intel network adapter in VMware that causes machine crashes frequently.I would still recommend VMware Workstation to others. It's actually only unstable in the way we are using it. We are using the network in a very specific way, and this network adapter causes crashes in the VM.

We usually try to resolve issues by ourselves. I don't think I would get any support when I bring that up because it's a very special way of working with VMware Workstation. They would probably tell me that it's not guaranteed to work this way.

Positive

We initially intended to work with Hyper-V because we are selling a virtual appliance and thought our customers would want to run that on Hyper-V. Then we realized that everybody is still using ESXi. I don't know whether that has changed in the last few months because Broadcom has bought VMware, and I think there is a lot of movement there. Some of our customers are switching to open source solutions away from Broadcom. But not Hyper-V. None of our customers are actually using Hyper-V, so we currently have a Hyper-V installation. If ever a customer would want to see our appliance on Hyper-V, we are able to look into that, but currently we are not actively working with Hyper-V.I would rate VMware Workstation a nine.