It is very easy to set up. You don't have to really make any effort to set it up. One or two days are enough to deploy VMware vSAN. It takes around 24 to 48 hours.

Initial setup was complex. I would rate the complexity a 5 on a scale of 1 to 5.

For an experienced IT person, it isn't that complex. But if I compare it to the  competition, Nutanix would be a 1, and VMware would be a 5. If you have never touched Nutanix, VMware is not that complex. But if I compare it to Nutanix, it's complex.

Deployment of VMware vSAN took four days.

The initial setup is very simple. It takes around a few hours to deploy, around two to three hours. It takes more hours than Nutanix takes. 

The initial setup is very easy. I rate the ease of setup a ten out of ten. The tool is deployed on the cloud. It took me a day to deploy a 3-node cluster. We need a team to implement the product.

The product's initial setup phase was very straightforward.

During the deployment process, the integration phase was an area that was internally managed by our bank, and it was challenging. From a hardware deployment perspective, the process was quick. Any product would take a week to be deployed in our company.

The solution can be deployed in a week. The configuration or integration with our components took a few more weeks. The go-to-market time is around a month to a month and a half.

The setup is quite easy. It took us around half a day to deploy the solution.

It was straightforward. There is a single checkbox if the prerequisites are met with.

The product's initial setup phase is simple.

The solution is deployed on the cloud.

The product's installation phase is easy.

I would rate my experience with the initial setup an eight out of ten, with ten being very easy.

Deployment can be done within three hours if we prepare all the information beforehand. We can set it up in two to three hours.

It has a user-friendly configuration process. The deployment typically takes approximately one to two hours. For instance, if we consider deploying a three-node vSphere operating system, it usually takes about two to three minutes to deploy. However, when factoring in the configuration of logical networking aspects, the overall deployment time extends to one to two hours. Once completed, the product is ready for usage.

The initial setup for VMware vSAN involves two key components. Firstly, we offer our flagship product which utilizes VMware's leading vSAN technology. The major components are included in the package upon purchase, making it a straightforward setup compared to building it from scratch, such as with vSphere 7. We provide pre-configured vSAN ReadyNodes for convenience, although they may lack specific branding. This option allows for a more DIY approach based on ReadyNode servers.

Deploying vSAN ReadyNodes is automated, requiring minimal manual intervention. Setting up a custom solution can be more complex. The process remains relatively straightforward with some necessary intervention. It's also possible to integrate vSAN ReadyNodes with Azure setups on a large scale.

Customers opting for the automated setup merely need to ensure they meet the prerequisites, including switches, and various other requirements such as NTP configuration. Once these prerequisites are met, deploying vSAN becomes relatively easy, as VMware handles most of the configuration automatically.

Deployment is very easy and takes less than an hour.

The initial setup of VMware vSAN is of a medium level of difficulty. Since we have a two-node cluster, they have done some very smart innovations. You first have to understand the smart solution before you can fully understand the deployment.

The time of the deployment took approximately one week, this included some experimentation and test.

The complexity of the initial setup is not really on the VMware, but only the hyper-layer because we need to check if the hyper-layer, underlying VMware are strictly compatible.

For the first implementation, it took more or less one year, but now it takes much less time to add new material and new configuration.

It is an easy-to-install and maintain product. It requires one or two executives, depending on the environment, to conduct implementation.

If you already work with vCenter and VMware, the initial setup is easy. The process is easy to understand and easy to configure. You just have to be sure that when you connect the servers with the LAN that everything is in 10 giga, then it will be easy to configure. You have to configure the root storage of the LAN and give it a switch.

You have to configure everything from the beginning to make everything work, so you must have an expert on vSAN from your side and an expert for LAN on the other side.

The product's initial setup phase was very complex.

During the deployment process, my company ensures that the product is deployed on an on-premises model, which takes about a day to complete and has 13 to 14 steps to be followed.

The solution is deployed on an on-premises model.

The solution can be deployed in a day because it was implemented with Dell VxRail. All the solutions from Dell VxRail, including the virtual machine and VMware, were implemented in one day. My company implemented the solution with the help of a third party for the implementation of all the solutions, including Dell VxRail, VMware, and VMware vSAN.

One person is required to take care of the implementation process.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight or eight and a half out of ten.

From a setup perspective with vSAN, I was involved in the original architecture and design of our specific platform. It was pretty straightforward. It's more or less point-and-click. The most challenging part is choosing the correct hardware and platform behind it. It's not so much about the fact of how to deploy vSAN. 

Once the physical hardware is there, the ESXi is installed, and configuring vSAN is pretty straightforward. It's just a few clicks. It's much easier than most other storage platforms, but the challenge is to identify the correct hardware for the use case. There are ReadyNotes and all types of other solutions, but sometimes the ReadyNote configuration doesn't match exactly what you need.

You need to be careful with some of these vendors because they might upgrade individual devices. That was one case that we had, and all of a sudden that version was no longer supported. So, we had to fight the battle of whether it is now the fault of the hardware vendor versus VMware. Those are scenarios where I can always only warn people. It's like sticking very strictly with what's in the HCL because it's nice that vSAN tells you in the UI that you are in an unsupported state, but at that point, you have the hardware already in your environment, cabled up, and in production. So, you should identify that early on. However, I think that's going to get better as well.

The initial setup took around 15 months. It was reasonably simple but there were some issues. We migrated around 150 VMs with applications on them.

It is straightforward. The duration depends on the size and the use case, but it usually takes one to four days.

For its implementation, normally, you only need one engineer or admin from the storage team, but sometimes, you need a specialist from the networking/infrastructure team, which is a very important point for vSAN implementation.

The initial setup is not quite easy but rather, a medium-level difficulty. The installation should be simple but the instructions from the vendor are not quite enough. This means that you have to conduct some trial and error.

On a scale of one to where, where five is the easier, I would rate the initial setup and deployment a three.

If you have some networking skills, it's straightforward to install, deploy, and manage vSAN. 
We have three engineers maintaining all the VSI and vSAN solutions as well as all the features and management components.

The deployment process is complex because it's a GUI infrastructure. There are two-ways configurations for the nodes or vSAN setup. You can do it on a GUI management interface or by console or CRM recommendation.

So, it could take half a day or a whole day.

It is sort of difficult to maintain without any training. If you don't have any ideas on maintaining, then it could be difficult. But if you're a master of VMware, you know how to handle it. You're already a professional and can easily handle it.

It was quite easy to install and took a couple of hours.

It's simple to build a product when you know what you're doing.

Installation and deployment can take anywhere from eight to sixteen hours, depending on the infrastructure.

We have a team of three who deal with everything.

We've had no issues with the product. We put it in in two days. The initial deployment was straightforward, easy.

The initial setup was very straightforward, a very simple implementation. It's just an easy product to use. VMware, in general, is a very easy product to use.

The initial setup is straightforward. It took us approximately one month to implement for one of our customers but there were some delays on our customer's side. We could have done it in a shorter timeframe.

It was easy to set up. 

If I would have introduce vSAN in an environment without any existing VMWare virtualization deployment and with the intention to expand to cloud based resoruces as a next step, I would not choose the product itself, I would do it with Dell and would implement the VxRail, what is actually vSAN based, it's the same product, however, in the end, you have better services. If you cover hardware and software management as well underneath one GUI, it's better for the administrators.

In the past deployment, it took us about a week to set everything up and to get everything up and running. We did need this week to bring up two 6 node clusters and today, these original six node clusters both expanded to 16 nodes on both sides.

The initial setup was straightforward and took less than two weeks.

The initial setup is very simple.

It is less than five minutes to deploy.

I can set up a platform of VMware in a week, easily. It took me about a week to deploy our platform and we basically set up all he servers, all the network and everything else. Then, it took about two or three days to work and patch everything, and cable in everything.

The older versions were a little more complicated. Nowadays, there are more documentations, videos, and tutorials. So, it is less complicated. There are still some issues, until you have to look at everything. But, I think that because there is more documentation now, and more information, you can speak with VMware and they can provide you service.

The initial setup is easy. It's not overly complex or difficult. 

You need to do it as one complete infrastructure. It maybe takes one hour.

The implementation of VSAN along with the implementation of all hyper-convergence technology is tricky. Although we benefit greatly for it now, there were a lot of issues that, we simply had to work through. And these are not really an issue related to the product itself but more related to the nature of what the product does. Since VSAN is a software component that allows you to add storage to your hyper-converged system, which in turn is based on products like Cisco’s UCS, the revision of code in the Cisco UCS chassis, the types of drives, the levels of drivers across the entire platform are essential to keep in lock step. So, we had many cases where, as we added capacity, turned on new features, began to migrate, we ran into all sorts of, um, difficulty. But the truth is, with our people, with VMware’s, with Cisco’s, everybody supplied the skills we needed and now we're pretty much, we're there.

It was fairly straightforward. We were surprised at how fast it was implemented. The entire implementation took about two weeks. After that, it was turned over to us, and then we planned on the migration of the platforms from our old converged environment into this new environment.

In terms of the maintenance, apart from the normal operational maintenance that we're doing, we always ensure that there is a back-to-back maintenance agreement with VMware and the vendor partner who sold us the solution. So far, there has been very low admin maintenance on the platform. There have been no major issues except the last one where one node got affected by a power problem in the data center. That's just about it.

It is easy to implement, but for big organizations with multiple products, it becomes complicated. If you're going to have different clusters for your databases and workload, then setting up and deploying it could become complex. 

The initial setup is very straightforward and simple. There shouldn't be an issue if a company wants to set it up. 

If you have, for example, 100 VMs, you only need one person to manage it. It requires very little maintenance or overhead in terms of staff. 

It is straightforward. It took two to three days.

In terms of maintenance, it requires the usual day-to-day maintenance. It sometimes requires some kind of support.

I was not involved in the setup on that side, either. That's a different team that does that.

The setup had some complexity, and some of that was figuring out newer releases. Networking, originally, was kind of a pain, with having to have everything talk Multicast. They've gone to Unicast which simplifies things.

vSAN is one of the easiest implementations of any VMware product. It's almost like click it to enable it, then you're almost done. So, vSAN is very easy to set up.

The initial setup was a little complex. We did it a couple of years ago and we've heard that it is so much easier now. I know that they are working on that capability right now.

Setting up vSAN isn't too tricky. All HCI providers—Microsoft, Cisco, and VMware—have very smooth implementation except for Microsoft storage, which is complex. 

Maintenance is required. Sometimes hard disks crash, but thanks to the mobility and abstraction of the software from the hardware, we can migrate the entire infrastructure layer to some spare PC's main server and perform maintenance. This is the standard patching practice in the industry.

The initial setup is easy because our architecture is simple.

Our architecture is very simple to understand a new version. We only need to document all the configurations of the servers with all the maps that are designed. Any new person can understand fully within a day. However, we need more simplified versions of VMware vSAN in the future.

We are involved in the beta phase of the vSphere product, as well vSAN and newer product versions of VMware.

One of the best features of the configuration is vSAN at the cluster level is pretty simple. People have a lot of issues in configuration of different storages, but vSAN brings in a flexibility. Where as a vSphere admin, people can go and just configure the storage. So, VI admins don't want to have a storage knowledge when they are working with a vSAN. It is simple for us to use.

I was involved with the initial deployment of vSAN at our site. The most complex thing is you have to live and die by the vSAN HCL list. You can't put a product or a component into a vSAN node that is not on the host compatibility list, particularly the SSDs and their firmware which is specified on the HCL. You have to match that explicitly to receive good results.

I was involved with the initial setup. It was fairly easy to get up and running, at first. We had some networking hiccups here and there but, overall, it took about a day to get us ready to go.

I was involved in the initial setup. In fact, I was involved with the selection of vSAN compared to other products, as well as physical SANs, and I was involved in some of the design and configuration.

It was fairly straightforward, actually. After we got around the networking issues, we found that the vSAN setup was very good.

We published the first All-Flash vSAN in 2015. It wasn't straightforward but we got it done.

The initial setup was pretty straightforward. I had a couple of Knowledge Bases I followed, but it was straightforward, once I read all of them.

Initial setup was not difficult to do at all.

The setup is easy.

The implementation is simple, it was very straightforward. It took us approximately three weeks because it was installed in four locations.

The initial setup was straightforward, not complex at all.

The initial setup was straightforward, as was learning the vSAN environment. The complexity comes in setting up and managing the storage policies. These can be simple or complex depending on the environment. When using VMware Horizon View, there are several storage policies that are auto-created and -managed. Creating and managing your own policies and rule sets depend on your needs and workloads.

Setup was straightforward. With ESXi as the base, it was quite easy to then enable vSAN. We used the just a bunch of disks (JBOD) configuration and vSAN consumes those disks easily through the vCenter web GUI.

We spent quite a bit of time studying the design guides from VMware about the proper implementation and the hardware compatibility list. Ran all of the self-checks that were listed on the website and we used hardware that was certified ATL. And with these requirements- having passed the requirements it was very simple to enable Virtual SAN. So, after the initial, deployment design we're able to implement it in a matter of hours. It was, very, very simple. Much easier than deploying a hardware based storage system.

The initial setup is somewhat complex. It involves checking hardware compatibility before buying it and installing the VMware components. One person can deploy an entire environment in a day.

The last setup was an upgrade. It's not so complex as we had to upgrade an existing system. It's not overly complex. I'd rate the process at a four out of five. 

The issues we had were mainly due to other things like the backup and data transfer. It wasn't actually to do so much with VMware itself and the other things. It was the transfer of data from one storage device to another and VMware wouldn't let us do it.

The deployment took about two weeks. 

All the vendors are working on making the setup more straightforward. Things are becoming a little more scripted. More automation and installations where you don't have to check every box are always good.

The initial implementation is straightforward. The time of installation can vary, it depends. If you're looking at virtualizing a host only, it can be done in five minutes.

The initial setup was complex.

The initial setup is not difficult or complex. It's very simple, very straightforward. A company should find it very easy to set up.

The initial setup is not complex. It's very simple and very straightforward. 

While we handle the maintenance ourselves in-house, we have the option of calling our integration partner if we run into any issues.

For us, it was fairly straightforward. You need to have knowledge of vCenter. The deployment took about two to three days in total.

The initial setup was very straightforward.

The initial setup was pretty straightforward.

It is not really difficult, but you need a skilled resource to manage that. The deployment duration varies. It usually takes a week or so.

The installation process isn't easy. It's not straightforward. It's a bit difficult, actually. They could work to make it easier.

We have about 17 people on staff that can handle maintenance tasks.

I am the manager of the guys who will be implementing the product. We recently received our client from Dell and we have installed it. My two main CI guys are here with me at VMWorld 2018 this week, so we're on a temporary hiatus, but we did get one full rack installed so far, and we're getting ready to deploy the vSAN to it.

The solution is only as good as the technicians you have and the investment put into proof of concept testing. My two technicians are some of the smartest people. You always hire someone smarter than you and I definitely did with these two guys. They've already got it worked out. We had the tasks laid out, what we were going to do day-one, day-two, rolling it into a test environment, and then production. We already had that done before we had the equipment on site.

The initial setup was straightforward as was learning the vSAN environment.

The complexity comes in setting up and managing the storage policies. These can be simple or complex depending on the environment.

When using VMware Horizon View, there are several storage policies that are auto-created and managed. Creating and managing your own policies and rule sets depend on your needs and workloads.

The installation was easy.

Very straightforward, you need to obviously follow the configuration guide, read advance, just so that you understand the components around VSAN. Then it was just a matter of enabling VSAN, provisioning all the data storage that it needs. You obviously need to have a Solid State Drive to go with it, so many people don't realize that, but you should have one. That is to allow the performance that is required from commodity hardware to be scaled up.

It was pretty straightforward, but we had some issues with drivers, although nothing in the setup. After some time, we were losing some disks that was because of driver issues.

The initial setup was straightforward but we have experienced some setbacks with deployments. 

The initial setup is quite simple according to our customer feedback. The time it takes for the deployment depends on many factors, such as use case and environment size.

The installation is easy. My team worked on the installation and, for our company, we only need one engineer for deployment and maintenance. 

There is not a lot of maintenance required.

The initial setup is very straightforward. It's so simple you don't need any technical assistance or anything like that.

The deployment is pretty fast and only takes one to three hours or so. It's not a long process at all. 

It depends on the project, but vSAN, in particular, is an easy setup.

I was not involved in the initial setup but I have taken it over since then and I have implemented some of the newer features that vSAN has come out with; capabilities that we weren't using when I came in.

We leveraged a partner who helped to make it an easy implementation.

Initial setup was pretty straightforward.

The initial setup is straightforward because a wizard helps you to enable vSAN.

The initial setup was pretty straightforward.

When we were setting it up the very first time, we had to start over a few times, but again it was just a learning curve. I think during the first setup, especially if it’s in a testing environment, it’s the best time to hammer it and experiment a little.

Initial setup and implementation was pretty easy. It's all about the design and all about the thinking process at the beginning of a product; so implementation was pretty easy.

The initial set up of VMware vSAN is easy. The implementation requires just one click and VMware will take care of the rest.

Our engineers have a lot of experience with vSAN, so we think it's easy to implement. One person is usually enough to set up the solution and apply updates. 

Our initial vSAN setup is a backup from Rubrik being thrown up to AWS for Glacier. But in the near term, maybe we could migrate that kind of solution in a more seamless and resilient way. That's what we're considering right now.

I was not a part of the implementation process and therefore cannot speak to how easy or difficult it may be. 

The solution has very few maintenance requirements. Occasionally, they may recommend a fix or patch by updating it, and we do so. However, other than that, it's pretty simple to maintain.

The initial setup is not overly complex or difficult. It's very straightforward and very simple to set up.

It took us about two days to deploy the product.

We had about five people who handled the deployment.

The vSAN is very easy to deploy.

To deploy a full cluster in a data center, can take four hours.

We are all engineers. We don't need a team to maintain this solution, as everyone services themselves.

The initial setup is straightforward. 

The initial setup is fairly straightforward. You just need to do a level of due diligence before you do the installation. You can run into issues depending upon the compatibility with drivers.

There's no complexity in the original setup of the solution. The implementation is very straightforward.

Deployment was pretty quick. Just testing it out and finally rolling it out we managed to do in a couple of days. I would say within a week we were able to be up and running. 

The initial setup for vSAN was extremely simple. There are some concepts that you need to understand before you go in, install, and click the buttons, but once you have your drives configured and inside of the individual nodes, the configuration takes just a few minutes. Everything gets done and orchestrated for you directly from the vSphere or vCenter consoles.

It was really straightforward. 

The setup was straightforward. It literally took a few mouse clicks to setup vSAN.

We have three hosts in a cluster, and it was surprisingly easy.

Setup is very straightforward.

The initial setup is very straightforward. The length of time required for deployment depends on the number of nodes that it will be installed in. The typical setup takes from one week to two weeks.

It is very easy to configure and setup. vSAN is already part of vSphere ESXi. You simple need to apply a license and do minor configuration to get it to work.

During my current project, initial setup was very complex, though this was by our own choosing and was needlessly complex. In the past, setups were often very straightforward, though you need to verify your design properly, as mentioned.

It was simple and straightforward.

The initial setup was easy and straightforward. We had no issues. It took us about a month for installation and configuration.

Its initial setup is not difficult.

The initial setup was pretty straightforward.

I can't comment on the initial setup.

The setup was very easy if you have the correct hardware and firmware.

Initial setup is straightforward but somehow we need to understand the high level topology and way of working with it.

The initial setup was quite straightforward. All in all, it took three days to complete the entire process; that included installation of the hardware itself, installation of ESXi onto the hardware, creating the data center and the cluster, configuring the networks and multicasting on the surrounding network infrastructure, defining all the disk groups and networks at the cluster, and finally turning the vSAN on. vSAN was the simplest part of the whole process.

There was a small learning curve, but it's pretty straightforward once you understand the basics of how everything works.

Once we got all of the driver configurations done, etc., it was easy enough.

The initial setup was straightforward.

The initial setup is straightforward, but only after deploying the vCenter service. Once the vCenter is up and running, it is pretty easy to enable vSAN. Despite the automatic selection of disks, we chose the manual selection and it was extremely easy to set up vSAN.

When you don’t have a chance to build upon an existing vCenter service, you have to think about the deployment of vCenter without having vSAN. There are several options, like deploying vCenter temporarily on a client PC and then migrating it later onto the vSAN cluster. But it’s always a bit tricky and you probably need some extra time to get the installation done. In most of my vSAN installations, the vCenter was already up and running, so the initial setup of the vSAN cluster literally takes minutes.

I would say initial setup is complex. But we decided to go with best practices and we had consultants from VMware designing and planning the configuration for us, so it wasn't an issue.

It is easy for a VMware administrator to install.

The installation was as complex as any iSCSI scenario can be. However, it was radically simple in terms of the networking part.

In our case, we passed from our standard virtual switches to distributed ones in order to meet the vSAN’s requirements. We had to take into consideration the disks/RAID controller configuration. We chose an acceptable balance between performance and cost, creating a RAID 0 with each disk of each server on the cluster and made them available for vSAN.

I found challenges in setting up a VSAN Cluster that were not related to VMware VSAN itself. They were related to server hardware and network configurations.

The initial setup was a little bit complicated because we have to do everything from scratch. It’s a new world, and much easier in the newer releases.

It's not very different than vSphere 3. If you're comfortable with VMware it’s straightforward. From what Ive seen, it’s a simple install once you have all the hardware. I have heard you have to tweak it performance wise.

The initial setup is straightforward and it's very easy to implement in any X86 server so anyone can use it in their existing environment. 

This product is easy to set up. It is easy to deploy.

Setup is not that difficult. We have had a few issues with the implementation. Initial setup is not as straightforward as Nutanix.

The initial setup isn't too complex. It's pretty straightforward. The entire implementation process, in fact, is very simple.

If I have an infrastructure already in place then deploy it, the configuration of vSAN will take less than an hour. If the implementation is happening from the scratch, with new equipment, then it will take four hours approximately.

The initial setup is straightforward. 

For me personally, the initial setup was not straightforward; I struggled quite a bit.

In preparation, I had to study a lot about the documentation, etc. It took at least one week to complete that.

The initial setup is very straightforward.

From the moment you're used to the VMware vSphere Web Client interface, there are no problems.

The activation is really simple, since it is done with a simple click if one can stay at the level of the parameters of the cluster VMware vSphere.

Then, depending on the number of hosts in the cluster, it will be possible to define a certain number of Fault Domains, that is to say, a quantity of permissible hosts losses, for example.

Moreover, depending on the amount of RAM available in each host and the amount of SSD, we can define one or more Disk Group, as well as host more or fewer objects. But this is more a question of design, which must intervene upstream of course.

The biggest difficulty lies in the design of the solution in order to be closer to the Service-Level Agreement of the company. There are a lot of possibilities according to the number of fault domain one wishes to have, if one makes vSAN on a site or multi-site, the degree of protection of virtual machines, etc,

I wasn't familiar at all with VSAN at the time, so there was a little learning curve there but outside of that it would be comparable to setting up a legacy SAN environment.

Setup was not complex at all, was very straightforward, and was easily implemented by everyone on the team.

The initial setup is very simple and straightforward. If the setup also involves hardware deployment, the process can take a day or so, but if it's just the vSAN deployment, it can be done in several minutes. I generally carry out the implementation. 

The setup is not complicated. The deployment of VMware vSAN with VxRail can be completed in three to four hours, for one cluster out of the physical setup. The physical setup could take approximately one day. After that, deployment is very easy to complete.

The installation was straightforward. We did not find it difficult.

Initial setup was straightforward. You'll only have what you want.

Initial setup was very simple for me. It is easy to set up if you get used to using vCenter.

This solution was easily installed by our team.

We have a team of four people to deploy and maintain this solution, including one administrator and one manager.

The initial setup was manageable. It was not a problem.

The initial setup was straightforward.

The initial setup is pretty easy. I would like to have some additional automation wrapped around it. In the earlier versions, PowerCLI was very limited, but as the versions have progressed the modules have progressed as well. It's getting better. I consider it to still be a fairly new product and, over time, it's continually getting better and better.

The initial setup for vSAN is simple. A couple clicks, we were up and running. 

It does takes more time to rack it than to actually configure it.

With a good hardware design, the setup is straightforward.

The actual implementation of vSAN is very easy to do. Once the equipment is racked, stacked, powered on and installed with ESXi, the vSAN cluster can be up and running very quickly. To avoid any hiccups, it should be properly sized and designed.

Even an IT administrator with some basic VMware experience would be able to set up vSAN in just a couple of minutes. This is one of the easiest setups I have had in a while.

If you do not know about this technology, you cannot put it into production easily, but I know about vSAN, so it was very easy to deploy a vSAN environment.

The product's initial setup is not overly complex or difficult. I found it to be straightforward and relatively easy. A company shouldn't have any issues with the setup process. 

vSAN isn't easy to install, because it's separate from VMware. You have to install vSAN and monitoring separately. Configuration is not straightforward. You have to define the policy first and then allocate through the virtual machine.

• Setup just a few clicks after hardware all connected, “pretty stupid easy”.
• Customers can test and validate without going out and buying vSAN ready nodes.

We had one issue with an MTU, but it didn't take me even a day to set up.

The initial setup was straightforward. We did not have any problems with it at all.

The deployment did not take more than two or three days. It was very fast.

We have two people to deploy this solution.

The initial setup is easy but the deployment can take some time, approximately six hours.

I was involved in the initial vSAN setup. The experience was really wonderful, it was really easy, it was very intuitive. There were some learning curves for us because we had never done it before but, overall, the wizard and the experience with the online tutorials that we were able to find solved every concern or question that we had, very quickly.

Initial setup was straightforward; I had the KB from VMware to help me deploy the solution.

It is neither easy nor complicated. It is in-between. The deployment took one to two days. You need one to two engineers for its deployment and maintenance.

Initial setup was straightforward.

Setup is simple because the product is automatically installed once the license is activated.

The installation is straightforward. I have developed an automatic script that can install the solution which has been very good for customers.

As a system architect, I have not deployed it myself.

The initial setup was easy, if you’ve got such experience. It is a little tricky the first time.

Its straightforward.

It's not difficult, but there are still limitations even in in-depth white papers because it's so new.

The complexity of the initial setup varies with the customer. 

Initially, you need to have enough expertise. You need to read some popular bloggers and select hardware from “recommended nodes”. And then you can start a PoC.

Very easy, just a few clicks. You don’t need special knowledge of storage .because it can be fully automated or you can set it manually if you want

It's straightforward. Because we are deploying it from the VxRail global setup, there is no dedicated vSAN setup that we are providing. It's all integrated into the VxRail setup. However, installing vSAN itself can be quite complex if you're doing it from scratch.

Initially, it was quite difficult to understand the solution because we tend to do a PoC. Later on we got used to it. Now it's quite easy for us, but at first it was not easy. We now have about 48 locations where we have deployed vSAN.

As I have worked with the HC Platform, the setup was very simple and easy.

The initial setup is really straightforward, you only have to enable it on the VMware cluster. But, before the initial setup you will have to check the HCL of vSAN for the compatibility of the different components. With VMware vSAN-ready nodes, this process is made simple, but it still is something you have to take into consideration.

The setup is really easy and straightforward. vSAN is built in vSphere, and you have a dashboard to manage the system.

It was straightforward.

The initial setup is straightforward. People with existing knowledge in VMware technology will find it easy to set up because it's not a different platform than what they are used to.

The initial setup is very simple and doesn't take long, perhaps two to five days. 

The initial setup is pretty straightforward.

The Initially setup is easy. We have only three or four hosts. However, I might need to use some more services. A larger environment requires more hosts.