VMware vSphere Reviews

I'm a Solutions Architect. I advise clients on how to leverage VMware products to provide resiliency in the face of disruptive events. VMware's platform is the most robust for running VMs upon, and it also has the most mature technology. Therefore, it is much more reliable and predictable, and those are the key characteristics needed to ensure a successful business continuity solution. Bleeding edge newcomers have yet to prove themselves production worthy compared to VMware's long history of success.

Portability of infrastructure is the greatest asset of any virtualization platform. By using VMware solutions, there is no lock-in with a particular hardware vendor for compute, network, or storage needs. Likewise, the ability to run various guest operating systems further amplifies that flexibility. The overwhelming majority of my clients are able to use VMware's solutions for 100 percent of their software application needs. Finally, the ability of a running VM to be quickly relocated to another hypervisor or launched at another site via replicated storage greatly reduces downtime.

• Storage vMotion to safely migrate VMs to other hypervisors, storage solutions and sites while the VM is still running. 
• Distributed vSwitches to better manage networking across large infrastructures. 
• vRealize for operations management and automation to remove human error from complex tasks and enable more efficient processes and business activities. 
• The VCSA appliance provides a great interface for most management tasks. 

In general, the combination of VMware products that compose or plug into vSphere enable most organizations to better prepare for disruptive events.

The ability to run ARM based VMs on an x86 platform for testing purposes. With the growing use of SBCs running on ARM architectures for IoT devices, it would be very useful if developers could build and deploy VMs running operating systems like Raspbian used on Raspberry Pi devices on their existing x86 ESXi environments. Even if this is not possible through some form of emulation, the ability to add ARM hypervisors to vSphere environments would be very useful. This will enable more rapid development cycles for customers just getting started with IoT but already existing vSphere users. 

Since 1999 when they only made Workstation.

I've used Hyper-V, AHV, VirtualBox and KVM solutions. Each of these solutions has merits, but none of them are as flexible and reliable as VMware solutions. They are all rapidly improving, but are not being adopted widely enough to rival vSphere's dominance. I rarely advise clients to switch away from a VMware based solution, because of the long history of success and reliability that comes with it.

Do not buy based on price alone. Many of my customers chose the lowest cost option only to discover that the additional funds needed to access even a few more features would have been money well spent. Likewise, if you are going to spend more money on additional features, then have a plan to actually deploy and integrate those features into your infrastructure. Many customers never take full advantage of the many features that they are paying for and that can be avoided by being proactive in developing your overall vision for the infrastructure.

I am constantly evaluating many solutions. I also regularly re-evaluate other solutions. The competition is improving, and VMware has done a great job improving as well.

The entire production and development environments are running on VMware vSphere using the 6.0 and 6.5 versions with twelve-node clustered configurations. Two data centers were deployed to separate the production side virtual machines from those of test and development.

The deployment of Enterprise VMware vSphere architecture helps us provide a robust and high availability infrastructure because of the combined features of VMware vSphere and VMware vCenter such as HA, DRS and Fault Tolerance. This base metal virtualization is highly compatible with almost all of the IT hardware.

The vMotion in particular I think is the most valuable because this feature provides migrations of virtual machines in case you want to run do maintenance. This his feature comes hand-in-hand with other features of VMware like the DRS, which automatically load-balances the whole VMware farm based on the usage and recommendation.

Improve the patch and updates online and remove mandatory reboot, or move the virtual machine onto a physical host that needs patching/maintenance.

I would like to see VMware vSphere provide a centralized patch service on the VMware level, regardless of your operating systems.

I have been using this solution for eleven years.

In my long experience, I have a single incident where our whole VMware farm went down. I can say it is very stable as long as the hardware is healthy.

The scalability is great. This solution is highly scalable and compatible with almost all IT hardware on the market.

The support is very responsive and highly knowledgeable.

Prior to this solution, we used Oracle Virtual Machine and Xen Virtualizations.

I  used the profiling feature.

I set up the system myself.

The license of VMware is a one-time payment and you can continue to enroll in support for troubleshooting and also administer the licenses.

We did not evaluate other options before choosing this solution.

The company I work for is a global company and has many data inflection issues. Quality control decisions are not actually made at the local level. It is made at the headquarter level in Europe. 

We have our cloud site solution, our production environment, and our data recovery environment. We use VMware solutions integrated with HP solutions for hardware replication and storage-to-replication facilities. We use vSphere with ESXi 6.0, primarily for VM migration. We have an HP storage replication system in place for our first storage requirements with the VMs. Every other one is managed by VMware vMotion. vSphere and ESXi 6.0 are used to host our application servers, operational applications, and additional HR applications.

For extensions, we have vMotion to manage the virtual machines so that we can watch the network. For all of our backup requirements currently, we use the HP Data Protector. 

We have some downtime, but we can quickly recover from a disaster depending on the magnitude or the extent of the disaster using vSphere. The software will recover from any disaster that happens. We have also reduced our cost of production as well. vSphere has also improved our operational productivity. We have isolated servers that we couldn't integrate together, but now we can with vSphere, despite the fact that they are different models. Where they're different physical models, different memory models, you can integrate all of them. It makes our resources more available and our services more reliable to our users.

The features in vSphere data recovery are excellent. Sometimes I've deleted an entire server before and was able to recover the deleted VM. I didn't have to use the backup to restore the VM. I just used some command line tools and I was able to restore the deleted VM. I find that fascinating. 

For VM migration, I can migrate my virtual machines from one place to the other. vSphere has easy integration. I have some older server models. They are HP products. I have both old and new server models. I was able to integrate all these servers despite that fact that the date of manufacture is a five-year gap between the units.

I was using the same version of vSphere and I was able to integrate all the servers together. They are working well through it.

We want to see improvement from VMware with security. We want minimal downtime. We want automation. We want to deploy more efficiently.

If there is a disaster of any kind we want to respond quickly and recover from it. With vSphere, you get to provision server resources with ease. While we like vSphere, one problem we have is saturation. For example, if I want to deploy 10 virtual machines, I will have to install the operating system one by one. I will have to install the patches one by one, also to every kind of script. I will have to learn more, but automated deployment is not easy to implement. 

It makes you spend a lot of time on deployment. You can't have time for doing other things.

On login incidents and other events, I would prefer to have some notification in the logs.

These are the main areas of improvement that we would like to see.

The stability is good. Previously, our whole infrastructure couldn't support our operations. We are always having downtime, we are always having system instabilities. 

Since we implemented a new solution with vSphere, we have a greater capacity of infrastructure relative to our virtualization that almost doubled what we used to have before the implementation. 

It makes our services more reliable. We have also had more uptime of our operational applications.

VMware vSphere is a very scalable solution. The only thing is if you are to upgrade, i.e. from ESXi 6.0 to 6.7, you might not be able to use your older servers. I believe VMware will not support these after ESXi 7.0.

For newer servers, VMware is scalable. We can always use it at least. The only issue I may have is we may not be able to use our older servers with the newer versions of VMware ESXi. 

In-house users number about 110 to 115. We have customers that login into our servers. We have web applications that customers log into from outside.

Around 2000 to 5000 customers use our vSphere installation per day.

We have billing people that are working there with our customers. We have operation people that are in the field that are using various equipment that is connected via wifi to our systems. Then we use the VMware network to carry our own operations and activities. 

We have customer service people that attend to customer inquiries, to try to resolve customer issues, but are still logged into the same application. There are various roles from read-only customers that want to pick one information or the other about their product on our sites. They don't actually update anything except they want to transact business with us. 

We use vSphere to help the users as well as to manage users that need information regarding a particular product or report. Users generate various reports from our SaaS/PaaS applications.

The staff we currently have are about five in IT. We have the manager, we have infrastructure persons that consist of system and network. We also have a database specialist that manages our applications. Our database specialists also serve as the developers for the application support. We have user support teams. The various support people that we have dedicated for the maintenance of the VMware vSphere deployment is about five in total.

We should still be able to support our users, at least, for the next five years. After five years, we may now be thinking of upgrading the infrastructure. This solution is being used every day, i.e. 24/7/365 days a year.

We believe that there's been increased usage, but we just implemented it last year. From our plan, we know that at least for the next five years we may not upgrade.

We also have a maintenance contract with HP. Any event that we could not handle locally, we escalate to HP to be aware of and also to the application vendors. 

For technical support, we have people that maintain the solution. We have a network of experts and specialists. We have a cloud computing specialist as well. We have a database specialist that does VMware integration and so does our software application developer. 

Even with all these people, we still also have a customer service contract with VMware and another with HP, the hardware vendor. We don't actually have any contract with Cisco, but we use Cisco devices. The main vendors that we have a contract with are the application vendors Dell and HP. We have a maintenance contract with VMware in case there are any issues beyond local resources. VMware will escalate them quickly when they respond to our queries.

We didn't use anyone before we procured VMware. Before we procured the product, we didn't use any other advisor. We were using HP hardware and servers. 

For the implementation period prior to 2015, we first implemented on-premise attached solutions. Prior to that time, all our applications were stand-alone IDS servers.

Our initial setup was outsourced, possibly it wasn't that complicated. Because it was outsourced, the consultant made it easy for us. 

After the initial setup, the subsequent ones were relatively easy for us. We trained in the VMware settings for the hardware. Depending on the part of the initial setup, we had older models of servers than we had new models. For the initial setup for the older models, we employed a consultant that did it for us. We implemented the newer models ourselves last year. 

We consulted with HP to do the initial setup for us which was relatively cheap. We did the integration of the old and the new servers. Running the new server models with our VMware vSpehere license, we used our own local resources to do that work.

Implementation actually took longer than planned because of some issues that we did not envisage at the start. When we called HP for price assessment, they came and discovered that our power solutions were not good for their product. We had to spend extra buying new UPS units and installing them. That made the implementation take an extra month. 

For everything together, both the implementations, it was four or five months or so for us to install the new server models and the integration as well. We used the VMware ESXi as the VMware vSphere hypervisor, prepared the servers, and installed the hardware from an HP reseller. 'The installation, especially the setting up of partial integration, was actually done by HP Nigeria. Everything went great because we didn't have any issues. 

Some of the administrative tasks we were supposed to carry out by ourselves. HP gave us direction on how to go about it and it went pretty well.

This is really a niche area, but we have an enterprise license for our business. We have many users on our cloud applications, so we went with a costly enterprise license.

VMware does provide organizations with discounts. The customer service license fee we got discounts on from the supplier in order for us to get the best out of the license fees. That's our experience. We possibly paid less than our partner company. The partner is only local and not global like our firm.

Even if I decide to use a product, I cannot deploy it because my superiors have to determine the policy. Those superiors are not here locally. They are in Europe. 

We don't use Veeam here, though I've used it at some point. Right now we don't use it in our production environment. We currently use HP Data Protector. 

We evaluated other options like Salesforce and Microsoft Active Directory, which we only tested for production. The policies were on central management, so we only tested these solutions with our time. The applications we used were effective only when activated.

The advice I would give is that there should be proper planning for implementing VMware solutions. With us, the content management suppliers and the various vendors provided this. 

If VMware vSphere is the particular product you are choosing, consider where the sellers were located and if they have a knowledge of the product.

• Do the suppliers have the right models for your business?
• Do the suppliers have different VMware licenses available?
• Will you be able to enjoy the VMware license discount with the manufacturer?
• Does the integrator company have good partners in the supply chain?

If you just launch a VMware deployment without planning, it is not advised. Engage with all management and staff, then do proper planning before going into vSphere implementation.

No product is perfect but VMware vSphere is absolutely excellent. It has issues, i.e. the result of insufficient speeds, but no product is 100% perfect. That is why I would give it a nine out of ten rating.

We have three different types of environments: internal cloud, managed hosting, and VDA. We use VMware vSphere as the main product to accomplish this.

VMware is now the main backbone in our company.

We are not using VMware cloud on AWS. We are in PoC mode. We may use it in another six months to a year.

vSphere helps our organization. Initially, we don't have an internal Cloud. We have an internal cloud, which is four years old now. We have 8000 to 9000 VMs standing in our internal cloud. We also implemented VDA using a VMware vSphere. So, it has been an absolutely pleasure having vSphere.

We provide a service to our internal customers for our development center. We have internal cloud developers. If they require 1000 VMs or 500 VMs, and in the background, we're using a vSphere VMware product. 

The most valuable feature is performance, especially the 6.7 version. 

We were looking for content library options for templates and were happy that VMware introduced it in 6.7 version. 

I like the speed and the quickness of the boot in the newest version of vSphere.

The mission-critical applications in our company, like SAP, Siebel, and a lot of financially related applications are running. Our developer uses most of animation, etc., and we are using the vSphere for that.

We have seen a performance boost compared to the previous versions, like a 5.1, five years ago. It has gradually increased. Previously, we hadn't migrated any database, like SQL or Oracle, into VMware. However, we are planning to now. We are moving forward because a lot of new features are now available on 6.7. 

We are doing a PoC, which we are happy about now. We may move over the database into our VMware environment.

It is simple to manage. However, some of our operation teams, they are used to the desktop line, but VMware removed it in the previous version. Initially, we had an issue on the flash, but now we are happy. With VMware moving to HTML, it's really fast. We did a bit of version testing, and it's really fast and easy to use now.

I have seen some sessions for version 6.7 covering its improvements, which I was looking for, mainly the content library. Our requirement is to move our templates from one location to another location. Previously, this was not available. We are happy this was introduced. 

Another thing is the flash. However, in 6.7, they completely removed it and they are bringing in the HTML. Let's see, as I haven't tried the 6.7 update yet. I hope it will satisfy everything from our point of view.

The stability is good. We have different clusters based on the load of the application and requirements. We can slice the cluster.  

Since we have an internal cloud, suddenly people may require 1000 or 2000 VMS in something. We have options to analyze and make sure we have enough scalability. 

We have some issues but so far it has been good.

We use tech support, which is okay. We used to have a hard time, but at this time, we are happy.

Previously, for monitoring, we use other products. Slowly, we are moving to vRealize now. It depends on our requirements and budget. 

When 5.5 went to 6, we found it a bit difficult because they changed the model. 

Now, we are okay. We have gotten used to it, because it is a new platform. Initially, it was difficult, but now we are okay.

Five years ago, we planned to move from a physical to virtualization environment. We evaluated a lot of other hypervisors, did some PoCs, etc. We decided on VMware. For the past six to seven years, it's been a big journey. 

I would rate vSphere as a nine out of 10.

I will recommend the solution, but there are some steps to take first. There are some VMware videos to view and some KB articles to read, which are available, regarding compatibility. I would recommend them to go through everything. Go through the KB articles, then I will recommend them to implement that one.

An important criteria for choosing a vendor is evaluating how a company behaves. We will review their past history, the current market, and the value of that product. Then, we will see whether that product can used for our requirement. Based on that, we choose our vendors.

We haven't started using the VM encryption. We are in the very initial stage, doing a PoC for it and also the UEFI Secure Boot. These are options that we are trying. Let's see how they will work, and we're looking forward to their results.

I use it as systems administrative management tool. I use VMware vSphere, vCenter, and vSphere ESXi.

We do not use VMWare cloud on AWS.

vSphere has improved our organization by far, and it's hard to even quantify. The ability to to virtualize systems and run those virtual workloads with a fewer number of servers is tremendous. We are still in the process of converting physical to virtual, but we are getting there.

The mission critical apps that we use for our system are for monitoring different meters throughout households in the greater area in which we operate.

The most valuable feature is the single pane of glass management. There are a number of things which vSphere offers in terms of consolidating infrastructure onto single pieces of hardware. This is instead of having multiple systems running on the OSs that we need. I like the capability of logging into one system, then being able to shift over to another system within that single pane of glass.

vSphere is simple to manage. Some of the best parts of managing it is vCenter. I use that to provide entry points for different administrators to login from different environments to manage either physical or virtual servers and resources on the network in our storage site.

vSphere is going in a good direction already with its improvement. The one area where I would love to see an improvement is the HTML5 client. It's great, but it could get better. I know it can.

It has been fairly stable in 6.7. I have not had any major issues. 

I've come up on older versions from 3.5 until 6.7. This version has been the best experience so far.

I can build out hundreds of hosts, but my environment's not that big. It is not as big as most of the larger companies out there, so I've not hit a bottleneck yet in terms of scalability.

Every now and then, I have to use vSphere technical support. My experience with them has been a positive one overall. Usually, if I don't get an answer from one tech support engineer, I can get another answer from another engineer who will help me out with my particular issue.

I wouldn't say that I invested in a new solution to get to where I'm right now. I just really have been upgrading upon what's already there. I'm pretty much in bed with VM. I'm staying with VM, and that's where I want to be. I don't want to go anywhere else. VMware is top of the line.

I've done setups of different versions of vSphere. The latest one was more complex than 6.5, which had an external platform services controller. Now with 6.7, you have an embedded platform services controller, much like 6.5, but you also get the enhanced link mode capability. That was a big shift for me. 

ROI is tough to quantify once you are already in bed with VMware. However, I did a comparison between physical server to virtual. There was a point in time where we would size out a virtual server to be a massive size, then we'd buy a physical server of the equivalence. We saved somewhere around 20 percent going virtual, as opposed to the physical equivalent.

I have seen a performance boost in a sense that we have provided better utilization of system resources within vSphere. However, I don't have an actual percentage to provide.

Before I started with VMware, I did not have any other vendors on my shortlist.

I would rate it at a nine, because I don't believe any type of technology is a ten. There is always room for improvement. However, this is a solid nine.

Spend time researching, investing, and testing for months. Spend a few months testing the product before implementing it to production.

I don't have too much experience with the encryption or secure features of the new vSphere version.

The primary use case is spinning up lab VMs. We can spin up several hundred VMs for students to work with, which could be Windows-based or Linux-based. It's about creating these VMs, then destroying them as soon as they are done. So, there is a lot of creation and destruction. We also spin up VM environments as well. On the vSphere 6.7 product, the optimization is great. The older versions, 6.0 and 6.5 were sluggish. When your spinning and destroying things, it's a big deal to have higher performance.

We don't do a lot with the encryption, but we do have the ability to encrypt something if we send it offsite. We have multiple locations, so we can encrypt our VMs, if necessary. However, we don't have a big need for it, but it's nice that it's there.

Our mission critical is our classroom. If we have college students who can't work, they paid to be there, and are paying us for the environment. Therefore, if we're down for a day, that's a real problem. Given that people have a choice of where they can go for education, we have to be always available. Otherwise, they will go next door. For us, it's about a student's success and you can only do that if you're up and running.

1. A big feature for us was Quick Boot. You don't have to wait for the host to do a recheck on memory. You do an upgrade, and it's not a 10-minute reboot cycle. You can bring your host online and offline. 
2. Database optimization. They did a lot in enhancing the performance. They took down the memory utilization and increased what it brought in. You see more responsiveness, especially now with having the HTML5 client. It feels like a much snappier product.

The biggest feature that everybody wanted was the HTML5 client. This has made everything native where you're able to surf through it. Going into our web page, you're no longer refreshing it. It feels more like an enterprise product now. With Adobe Flash, it didn't feel that way.

The biggest thing to improve is to have more self-service in the portals. I would like to receive more help through the web interface. 

I would like to see continual improvements of the client. It doesn't need to go much larger for support on the number of VMs or its size, because there are pretty high limits already. However, it needs a bit more in the management and the reporting aspect. We have to get a third-party for that. It would be great if it was a bit more integrated.

Stability has been good since the 6.0 days. The biggest issue with stability is the SSO. That is still an issue as far as integrating it with Active Directory, and any large scale of it. That is still a work in progress. However, the core stability aspect of it has been there and hasn't changed. This has just gotten better.

I have no issues with scalability. As large as we have wanted to go with as many VMs, we have never had an issue pushing its limits. 

The majority of the issues are truly integrating it into the Active Directory structures. This doesn't seem to be there yet.

VMware tech support has always been good to us. Our biggest challenge is getting them the logs, but once they have them, the logs are so detailed that any possible issue usually is resolved within a few hours. So, it has always been a positive experience.

Given that we spin up and down hundreds of VMs, we physically couldn't do that with physical hardware. It would just be financially impossible. Having a virtualized infrastructure and being able to bring up Windows, Linux, and VMware within a virtualized environment brings more technology into the classroom. Without it, we couldn't do what we do.

There wasn't a short list. It was the only solution. It's the only thing that made financial sense as far as being able to do what we needed it to do. Nobody out there had it.

I would rate it as a nine out of ten.

Go big with your hardware. You have to be willing to invest in the hardware platform. Storage is key. Make sure you have enough performance with it. When you're looking at the actual overall product, make sure you understand what third party offerings you need to put in. It could be something from VMware or one of the partners, but it's going to be more that just the VMware Suite. There will be one or two things you need to add to it. Specifically, monitoring or reporting will be the big draws.

I don't have a percentage for the performance boost of the apps. However, there is noticeably different speed of how the database is working and how you move through the client. Everything is a bit more responsive. Part of that was getting rid of the flash client as well. We're seeing an overall general performance increase in everything we do, whether it's the monitoring aspect or deploying.

It's running mission-critical and business-critical workloads for our customers, and the experience has been positive.

The mission-critical apps include core banking systems, core healthcare systems, artificial intelligence. And highly transactional workloads are also great fits for vSphere 6.7.

We've seen an increase of about five to ten percent for the mission-critical apps. Their code is a lot more optimized now that they're using it in the public cloud with VMware Cloud on AWS.

In our organization, the lifecycle management has improved. What that means is our customers are spending a lot less time on "keeping the lights on." Day 2 Operations are being simplified a lot.

• The move towards feature-parity with HTML5 for the user interface.
• Also, increasing the release of features, which is partly through the use of that technology stack with VMware Cloud on AWS, so it's a much more robust product right now.
• It is a lot more simple and efficient to manage. It has improved a lot from the early days of vSphere 5.x. Lifecycle management and reducing the number of clicks that an administrator has to do to actually do a task have been greatly optimized, particularly with the HTML5 interface.
• In terms of more easily managing networks and improving visibility, the two go hand in hand. Compared to the vCloud Air days, it's come a long way. It's a solution that actually works now, and you can use your vSphere staff - who have been trained on and understand vSphere - to actually consume that hybrid cloud with very little or no training.

vSphere is the Rolls Royce of hypervisors. Moving forward, they just need to continue integrating and simplifying that user interface experience. With VMware Cloud Foundation, that's the Day 2 lifecycle management. You've got the VMC offering that's obviously all public cloud. They need to keep on integrating the APIs and simplifying the user experience. And they're definitely moving towards the one-click experience that you have with other technology vendors.

The stability has been good. Now that the VMC on AWS codestream is 6.7, and they're following a DevOps methodology, the stability of vSphere obviously has increased greatly.

It scales very well. Now, with vSphere 6.7, it's 128 hosts. Talk about scale with vSphere is now a non-issue. Typically what we do with our customers is deploy vSan clusters, typically 20 to 30 hosts, because that's a natural failure domain. Going beyond that, it really makes no sense, because you want to have separate failure domains.

In the early 6.x days, their support went down. Now with 6.7, being with VMware Cloud on AWS, their support level has increased, because they've had to. It's definitely a better experience now.

Regarding knowing that it is time to switch to this solution, our customers tend to be existing vSphere customers. End-of-life, end-of-support tend to be the trigger for, "Okay, we need to upgrade our infrastructure stack."

The other big trigger is end-of-life of the hardware stack that they're going with. That's typically a conversation about moving from legacy, three-tier infrastructure to a hyperconverged infrastructure stack. And then there's a hypervisor conversation about the best-of-breed to use to meet their business requirements.

Nutanix AHV, Hyper-V is commonly on the list, and Red Hat KVM is the other one.

Partner with the right partner because not all partners are the same. And have a strategy in mind. Have a design in place, the logical design. What functions are you trying to achieve? What business problems are you trying to solve? And then go ahead and do your due diligence with testing, etc. Once you involve the partner and you're implementing, make sure you have proper testing, have a soft launch, and then a go-live, so that you've got a risk-free solution.

That's where a lot of customers go wrong. They don't do their due diligence, and they don't properly launch, and they have the wrong partner that they partnered with, who is not quite up to the task of doing this type of thing.

For our customers that are very security conscious, in the financial space and the healthcare space, they typically will have clusters where TPM and virtual machine encryption are enabled to provide a more secure experience for those services.

We sell a lot of VMware Cloud on AWS. It integrates natively through hybrid cloud extensibility into VMC on AWS. That's actually been a big selling point with 6.7.

I rate the solution at nine out of ten. What would bring it up to a ten is feature-parity with the HTML5 interface.

My primary use case for vSphere 6.7 is that it's used strategically as a management plain for all 2,100 ESXi hosts across our environment.

In terms of mission-critical apps, I couldn't tell you, because I operate the public cloud and we don't really care what our customers use it for.

We do not use VMware Cloud on AWS yet but it is something we are exploring.

In regards to a performance boost, I don't know at the application level, but I can tell you, purely at the vCenter level, that we have seen improvements in our ability to migrate from Windows to the appliance, now that there is full feature-parity across the stack. We're seeing reduced resource usage from the appliance, it's way more efficient in 6.7. Operations are able to complete faster, so we're happy.

It has streamlined things for us. We've been able to standardize on the newer 6.7. It's definitely given us a path forward, where we might be able to look at expanding into the public cloud, augmenting our on-prem solution now that we have some sort of feature parity.

Most valuable features of vSphere 6.7, for us, at the management level would be:

• VCHA is a nice redundancy feature that they added in 6.7.
• I like the quality of life improvements with the VMFS-6 for using auto UNMAP on the data stores.
• We really appreciate the improvements to the Clarity UI where we can manage Update Manager (VUM) and our vSAN stack within the modern interface.

The solution is also very simple and efficient to manage. Features that have made it simple and easy to manage include the newer VAMI for the V-center appliance, it's very easy to see what version we are at, and very easy to upgrade to the next version. The fact that we can now use VCHA at the appliance level just decreases our chance of having an outage, because so many of our customers rely on the API interface for V-center. 

There are a few things I wanted to see in the next version of vSphere 6.7 which, it turns out, were announced today (at VMworld 2018) so I haven't had time to explore them. But one of the things that was most important to me was the ability to automate or improve deployment of VCHA in an advanced configuration, where it's not hosting itself. I'm looking forward to playing with the new release and seeing where it's at.

The solution has been very stable for us. Since we rolled the 6.7 we have seen consistent uptime.

Being that it's reduced our resource footprint, I think its very scalable.

We have had to open up support cases for vSphere 6.7. We have gotten generally good feedback, but it's still fairly new for them, like it is for us. A lot of things work differently in production then they do in the lab or in your QA environments, and they're willing to help however they can to stabilize the product.

As we're a partner, we do get generally good help pretty early on.

I was not using any other solution before vSphere.

I was involved from all the early stages of planning to move to vSphere 6.7.

We were already considering moving to 6.5 and, for us, there were so many added benefits of going to 6.7, and being that it's not a real major bump - it's more like 6.5 "Update 3" with a lot of quality of life improvements - it made it very easy for us to make that decision.

When I'm working with a vendor, some of the most important criteria are 

• their release cadence
• how much support they're giving to the product
• what kind of R&D they're investing in
• generally, anecdotally, the response we're getting when we're asking for support.

Moving to 6.7, like I said, has standardized a lot of our environment for us so we have definitely seen a reduction in the amount of time we are spending trying to troubleshoot things. It's very consistent. Everything has performed exactly how we expected it to.

We don't use any of the built-in security features but I do appreciate that vSphere 6.7 is inherently more secure in that it's limited, by default, to using TLS 1.2.

I would rate the solution to be a nine (out of ten) but I think they're steadily creeping towards a ten with some of the post-GA releases I've seen.