The initial setup is straightforward, and it follows a logical structure both in the cloud and on-premises. I wouldn't want to change anything about it.

Initially, the product is a bit complex to deal with when it comes to the installation part, especially for people who do not have any experience in deploying products without extra or additional support. After the initial hurdles with the installation phase, the process becomes relatively easy.

The product can be deployed in two days.

The solution is deployed on an on-premises model.

The initial setup is complicated. I rate the ease of setup a six out of ten. Once the setup is done, everything else is smooth.

The product's initial setup phase was neither very straightforward nor too complex.

I deployed the solution some time ago, and since then, we have had to keep upgrading the solution in my company. The deployment process doesn't take more than a week or a week and a half for VMware Horizon View deployment in the whole infrastructure.

The deployment itself is not too complex, but the planning part needs to be done properly. In our company, we plan our user groups, use cases, and everything else, including the area related to storage sizing. Deployment-wise, I don't see much complexity.

The solution is deployed on an on-premises model.

The product's deployment phase is difficult as it contains a lot of components, which requires a technician to have a technical understanding of integrations.

The solution can be deployed in a week, but it may vary depending on the requirements of a customer.

One architect and two engineers are required to take care of the deployment part of VMware Horizon View.

For Horizon and all other VMware products, setup isn't easy, but it isn't hard. Maybe the problem is with the documentation and consultation. After consultation with my colleagues in other companies, they gave me answers to all my questions.

In previous years, the documentation was not a problem. With the latest version,  there's too much documentation compared to their last available version.

It took about two or three weeks to set up. We worked to prepare images and tools for our several user groups, which was used as a test to prepare for switching.

There were two people involved in deployment: me and a network administrator.

There haven't been any maintenance requirements.

The setup is easy for me because I have been working with the product for 20 years. I rate the ease of setup a ten out of ten. For others, the ease of setup might be a five or six out of ten because we must know what we are doing. The time taken for deployment depends on the complexity of the installation. If we just want plain desktops, I can have the infrastructure up in one week. The deployment usually takes a couple of weeks to a couple of months.

The setup depends on the requirement. Implementing VMware 3.2 was a critical setup, as we were the first to deploy it. With the current setup, the site for deployment, even if it's a dedicated VDI, an automated VDI, or some golden image-based VDI, has no redundancies. The only thing is we need to have some networking knowledge. We need to know which port must be open from where to where and see the proxy and direct model. Also, we need to have a basic understanding of firewalls and networking. It helps us do an implementation faster.

Then it comes to redundant CR architecture, which includes the UA layer, the other view, and different standpoints. If we don't understand the account, we can implement it from an infrastructure standpoint. When it comes to a VDI, we get multiple ways out. Sometimes, auto-provisioning becomes complicated. When you need more automation to meet the requirements, it becomes redundant. We need an end-to-end understanding of the security networks, AD architecture, profiling, group policy, etc. We need to know how the authentication standpoint works. The port must be kept open from one authentication server to capture all the details and complete implementation.

The initial setup was straightforward, and two people were required for deployment and maintenance.

Setting up Horizon is probably not easy for an inexperienced person. You can't just read the manual and do it. You need some experience to set it up. It's not overly complex, but it also isn't so simple that you could deploy it yourself if you've never done it before.

It took about two or three months because you can't just roll it out. You have to migrate the users in batches. If you're rolling out a thousand users, you can't just turn it on and have at it with a thousand. You deploy 30 and migrate a department and then do another. That's the case with any virtual desktop solution. Rolling it out is always going to be a more gradual process than a big bang all at once overnight.

As a technical expert, it was easy to implement. I have a technical background spanning over 17 years. 

But for someone less experienced, it could be trickier, especially setting up client-side agents and drivers and integrating with AD services. But those issues can be fixed. So, deployment is easy.

The initial setup is really straightforward. It doesn't take more than five minutes and doesn't require external help. 

The initial setup is not overly complex. It's easy. It's a part of the VMware Workspace segment which makes it quite simple. A company should have no issues with the implementation.

Normally, the process from beginning to end only takes a couple of hours. It's a pretty quick process.

For maintenance, we have a team called EUC - End User Computing - that inspects all the upgrades and handles all the maintenance.

The initial setup is complex. It is not easy to deploy. It could be much easier. The vendor must build a SaaS solution. The deployment takes too long.

The initial setup is easy. The deployment took a few weeks time. I would rate the setup an eight out of ten. 

I rate the tool's initial deployment an eight out of ten. Deployment takes two to three hours to complete. It is a simple OEM SOP. You need around two resources to complete the deployment. 

The initial setup is very simple. 

The time taken for deployments completely depends on the customer's call.

I rate VMware Horizon View's deployment a five out of ten. You must install different components to get it working, which is cumbersome. We completed the deployment in three to four days. Once the hardware is in place, you proceed to provision your password and select the components you want to use.

The initial setup was difficult. I rate it a seven out of ten.

It's very complex. There are multiple steps, connectors, and servers. All of them have multiple components that all talk, so that's never going to be easy. But I think it's complex because of what it's doing. And if you use it all the time, that complexity just becomes familiar.

The initial setup is complex. Depending on the project, it can take one year, one and a half year to deploy. We have to take a lot of things in the configuration.

The initial setup is easy. The solution's deployment takes one day and requires a maximum of five engineers. VMware is easy to maintain. 

The setup is straightforward in comparison to Citrix. 

The design was complex to understand. When we set it up on our environment, I went through the classes but doing it hands on was a little different. However, after that initial hurdle, it was very clear.

Building the infrastructure is relatively straightforward; however, the challenge is in retrieving the master image or golden image for your desktop, which can be a time-consuming process depending on your specific needs. 

For an experienced individual, the implementation of the health solution should not take more than three days.

The initial setup was simple and straightforward although it will be more difficult for anyone who doesn't have experience. We have around 200 users and deployment took about three days. We have one admin for patching and updating.

It's not shake the box easy but if you do your homework, do some rudimentary testing and do a lot of research it's possible, viable - you can even do it yourself.

Setting up Horizon View is somewhat complex, but we got some professional services from VMware. It would probably be complicated if you tried to set it up on your own. 

In this instance we were implementing in two data centers and introducing not only a VDI, but also replicating all the data from one place to the other. Deployment involved building Microsoft clustered file servers and setting up replication between those two file servers and then mirroring the configurations. It probably took us about six months but we were doing other things at the same time. If we'd focused only on that, I think it would probably have taken about a week or two. It depends how much effort is put in. 

The installation process is really fast.

The initial setup is complicated. It takes one week to complete and requires two executives to work on deployment and maintenance.

The initial setup of VMware Horizon View is easy.

The initial setup is a little bit complex at the start and that's related to the migration of the current users to the client. The setup was a little easier in the latest version. The migration to our 315 clients took a couple of weeks. We have one person dedicated to monitoring the system. 

VMware Horizon View's initial setup is complex and takes several days.

The initial setup is not always straightforward. It can be a bit complex, a bit difficult. We struggle with some aspects of the configuration which slows things down during the implementation. We have two companies and we've found that the configuration has been a real challenge for them.

In general, the deployment took us about two days to complete.

We have three people that handle the deployment and maintenance process.

The initial setup was not difficult but there is room for improvement.

It was complex, and many facets on the networking side sit on top of vSphere, with multiple composer engines, and connection servers.

The deployment model is on the hybrid cloud.

Most organizations have gone to virtualization and VMware clustering. Most of the work is already done.

It requires some experience to deploy it, but overall, It's not that difficult.

It was fairly straightforward. It took getting used to the new technology but it wasn’t too difficult.

Deployment is not very easy, because there are many implications with the underlying infrastructure (which must be used only as a VDI infrastructure) and Active Directory GPO, which cannot be directly handled by View Administrator.

The initial setup was complex, and you need system experience to walk through it.

Somebody else does the setup. I just do the endpoint.

The initial setup is straightforward, although customization is a little kludgey.

The installation is complex and could be easier. The full installation with testing took a couple of weeks to complete.

It’s a little complex, we missed the initial deployment. They were trying to get the most out of the resources on the servers and it undercut what some users needed.

Colleagues of mine are implementing the software. I am the team leader for the modern workplace. It is simple to install, according to my colleagues.

We have a two-person team to maintain this solution. Both are architects, but we only need one architect and an engineer.

It’s a little advanced because more gotchas (certificates, different servers in different order).

If you don't know enough about VMware, then the initial setup can be complex. It's not for a standard user. You need to have some experience with VPN otherwise it creates issues. Standard deployment takes a minimum of one or two days. 

The initial setup was straightforward, but minimal. It takes time to configure all details. The default configuration should be better.

Very simple.

It was a little complex when configuring Active Directory and other server roles.

The solution isn't complex. It's pretty straightforward, largely due to the fact that there's only one application to deploy. We deployed one connection server and one replica. For the external users, I deployed a Unified Access Gateway (UAG). They have volumes and that's it.

With no dependency on the firewall, I think I can deploy the solution in one week. That would be the average amount of time it would take.

At this point, the solution has been running for about 10 months and hasn't required any maintenance whatsoever.

The initial setup on the desktops was easy but it was more difficult on the server. You need to check the server for OS, CPU, memory, etc., is not easy.

The setup is a little complex.