The setup is moderately complex. However, the complexity depends on the use case. For example, What features are we enabling? How complex are the policies and security controls? It's a moderate deployment because it involves the end-user side. 

We need to train users initially on what to do and not do, home storage, etc. So, it's a moderate one-time setup, but once done, day-to-day operation is very simple and less complicated.

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.

I rate the product's initial setup phase a seven to eight on a scale of one to ten, where one is a difficult setup process, and ten is an easy setup phase.

The solution is deployed on a private cloud.

The solution can be deployed in a few days since my company was dealing with a deployment process involving certain customizations.

Two people are required to do the product's deployment.

The initial setup is neither very easy nor difficult. I would say it's normal.

The setup process was not complex since my company mostly sells cloud-based instances, which means they are already pre-configured. We only need to configure the policies based on the use cases, and it works seamlessly. Therefore, the setup process is effortless. Additionally, the solution does not require any maintenance as it is a cloud instance, and all maintenance will be taken care of by VMware.

Most of our customers deploy the solution on the cloud, not on-premises. The most complicated part of the installation is installing the server.

Implementation can take six weeks to two months.

First, we get the requirement from the customers. They tell us what they want on the mobile and the features or result that they want. Then, we input and create the policy for them. After that, we test the result on the device. If it's okay, then we do the training after implementing the policy.

For deployment, usually one project manager and two engineers are needed.

The initial setup is easy. I follow the user guide for installation steps. It takes a month to complete. It is not very complicated to maintain.

The initial setup was not complicated. There may be a bit of difficulty in connecting all the components together. However, I have a year of experience, so, for me, it wasn't hard. It gets easier with time. Likely in five more years, it will be even simpler to deploy. I had some additional documentation as well that helped. 

The deployment itself took about one month. That is a typical timeframe.

Our strategy was to mainly manage all tablets and mobile devices from a single platform. Our main strategy was to connect all devices and be able to track them in case they were stolen or they were losing data. With this solution, we are able to set up and manage everything centrally.

VMware Workspace ONE is not straightforward, but we had tested for the on-premise setup. It worked very well and we also tried the SaaS solution. We have tried both solutions. It took us five months to do.

Even though we were not aware of a lot of things and there were dependencies that were the challenge. We had to address all of them. If we want to test it now, it would be two months maximum, we can test it and onboard it.

The solution is deployed on the cloud. The installation is not complicated. We are using it on the cloud. The on-premises solution is not available for the past two to three years. The vendor provides guidelines for installation. It is very easy.

The initial setup was very easy. 

We did a standard deployment process only. There are no customizations that we made. 

There is no maintenance required. 

It's not very difficult. The platform is pretty easy. I did find, however, that the two-factor authentication took some time. I'd rate the overall process a three out of five in terms of ease of setup. 

We did not face any challenges while implementing the solution. We manage very big customers to very small customers. They are doing well. The tool is easy to deploy and easy to use. It is transparent to the end user.

The setup for VMware Workspace ONE is good, e.g. there are no complexities, and they all have good discovery now. You plug them in, make sure the nodes are aligned on the network, then you can get to them. The setup process for VMware Workspace ONE and one of its competitors IBM, is very good. They've both done a very good job of it.

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.

Initially, the setup itself is quite complex. We had bought what VMware called a starter kit, which came with some professional services to get us up and running with the product. I'd rate it a four out of five in terms of ease of deployment as we did have those professional services to help us.

Unfortunately, the implementation, I would have to call a fail. We had several existing devices, and installing the product properly involved wiping the phone and installing and then restoring the user's information. And we had a very large resistance to that approach from our client community. We ended up installing more of a BYOD model, which limited the value of the platform to our organization.

The solution's initial setup is not complex. Anyone with a little basic knowledge can do the configuration.

The initial setup of VMware Workspace ONE is of a middle level of difficulty. It requires special training and skill sets.

The time implementation can take between 15 days to three months.

I rate the initial setup of VMware Workspace ONE an eight out of ten.

Our teams decide which device the solution has to be implemented. The time it took to implement all our devices took approximately five hours.

It's pretty straightforward. For the initial setup, it took around four days because we had requirements that prevented us from using it immediately as an out-of-the-box solution. That is, our setup had to adhere to certain scenarios which took some time to configure properly. To deploy the entire customized solution, I'd say it took around two to three weeks in total.

I rate the ease of setup an eight or nine out of ten. The product is installed on our hardware. It's not available for each server and hardware. The deployment took a few weeks.

The initial setup is straightforward once you get used to it.

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 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.

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 deployment of VMware Workspace ONE is easy. The time it takes for the deployment depends on the environment totally. If it is only a small environment, with no integration, with the cloud instance, and no set of a separate instance or sub-component is required, it can be set up in approximately a week.

In the use case scenarios, for example, where there is an on-premise instance where there are unified access gateway components required, then it takes a little longer because the firewall ports and setting up the infrastructure will take some time.

The product's initial setup phase was quite complex.

The solution is deployed on the cloud.

The time required to deploy the solution depends on the type of configuration and the kind of devices managed in an environment. In general, it may take a couple of days to deploy the solution.

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 installation and configuring of the solution are easy for a beginner. We help clients with some parts of the environment if needed but mostly the solution is straightforward to understand.

In a standard version, one week is enough to start using the solution, configuring the GUI, and getting through any obstacles that might be encountered. At this point, there can be discussions about the cost. The disadvantage of the older type of license is I need more time to understand the whole installation environment and processes. For example, whether I need to do some integrations or not.

The premise is that you just have to install the software. We had already programmed the server. It was a bit complex on the setting up of the policy, at first. Once the policy was done, then we had to update. Every so often, we still need to update. It's not too complex.

It is very easy to deploy. For the installation and configuration, we had straightforward documentation. With the help of consultants and architects, we developed the right design. They helped us to move forward.

If you ask me, in terms of installation, configuration, management, and monitoring, this solution is far better than others.

I didn't set it up. It was set up by a different team for the customer. I was only responsible for managing the backup and recovering the files. Its implementation took about six months period. 

In terms of maintenance, it was just myself. There wasn't much maintenance to do apart from getting the latest version and ensuring it was applied to all machines. 

The initial setup is an easy process. It's more complex than if it were a cloud solution but comparing the platform with some other on-premise solutions it's quite easy. 

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.

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.  

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

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.

The initial setup is not very easy.

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

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 was the one who set it up. It was not complex, it was an appliance-based setup and it was pretty easy. AirWatch was there, but I was the one who was there from day one.

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

We had no problems setting up the solution.

Setup is complex in a large or on-premise environment. Recommend SaaS model for most scenarios, but still complex once you start plugging in the additional features.

The initial setup was okay. It's straightforward.

As it has been two years, I cannot recall the implementation strategy. I do recall that it was straightforward and took us a couple of days.

The initial setup was straightforward with the consultant's help, but without, I couldn't do it by myself. The documentation is not enough to do the implementation of the product. You still need a consultant to guide you. 

The deployment changes every year and the policies change every year. The time it takes to deploy depends on how many devices you have. If you're like ourselves and have a ton of devices, it takes a month to finish the deployment.

For our implementation strategy, we moved on the groups of the policies that were assigned for each. Our strategy was to bend different policies on each so we can get the most of the features we needed to apply to each group.

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. 

The initial setup is not complex. It's very straightforward. A company shouldn't have any issues with the initial setup process.

The deployment took a few days to roll out. We did the implementation about two years ago now, and therefore it's hard to recall exactly what our deployment strategy was at that time.

Not particularly, they are all evenly matched here.

Setup is easy.

The initial setup was straightforward. For us, it was more about how we were deploying it and what resources were needed. Our deployment took place over a period of three months.

I would suggest accessing support from VMware when you begin the implementation.

The setup of AirWatch itself was performed by AirWatch, however the setup of groups, policies, apps, etc. was straightforward.

For the cloud solution, it was really straightforward. There are some, they weren't issues, I wouldn't call them issues, there was just some technical obstacles to overcome that were more organizational than anything else related to the AirWatch connector to sync active directory, et cetera with the enterprise.

The on-premises version of the solution installation is complex.

The initial setup is straightforward although the configuration guide is a little outdated.

It was simple.

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.

The initial setup is pretty straightforward, especially the cloud setup is very simplified.

Deployment duration depends on the customer success criteria or the scope of work. We have handled 3,000 and 5,000 users deployments. It took one and a half months to role out 1,500 users. Our largest scope was around 5,000 users, which took almost two months to complete.

It depends on the number of users because you need Windows 10 management, mobile management, and everything you want to see. If it is a greenfield deployment, then it's very straightforward. If it is not a straightforward greenfield deployment, integration also takes some time. Everything is a working field where we need to manage the timeline, production, clean window, and communication with customers and users, which takes some time. 

The initial setup is pretty complicated. It can be a steep learning curve.

It can take between three to six months to deploy and get everything fully working.

The initial setup for us was simplified because we started with implementing a PoC. There are too many interfaces involved, which makes it complex at the start of the deployment.

The setup was very difficult. It was not as easy as I had expected.

The setup was straightforward. There were no challenges during the initial setup.

I wasn't involved in the setup.

It depends. On-prem is a lot more involved than SaaS. There are a lot of moving parts for the on-prem version of the solution that can be consolidates if it is the desire of the client/customer.