VMware vSphere Reviews

Distributed Virtual Switch – you only have to configure it once, and then you can promote it to all the servers, so you have a single switch for all the systems.

Also, the HA system works very well right out of the box.

I’ve been working with VMWare for at least 10 years, so I can say that the loss that you have with virtualization has dropped – you have less loss than if you would run it on real hardware. It went from around 30% to 15%, so basically better by half. And it improves with every version.

A solution for all the different appliances that you now see running would be good. In the past you had VMWare agents, so every manufacturer installed agents on the IIS6 layers but that didn’t work well. Now every supplier has its own virtual appliance, but now some customers have five or six VAs per ESXi host which consumes a lot of processing and memory power. So maybe something like a hypervisor for virtual appliances.

I've been using it since it was released, at least two years.

Never. It just deploys. It works if you use the hardware that’s on the HCL on the VMWare web site. If you don’t do that, you could be in trouble. Some customers do that and expect it to work magically.

Yes, in combination with Broadcom network cards – there was a lot of latency in the storage area through vSphere. So in those situations we had to change the hardware – there was something buggy in the cards.

No issues encountered.

Customer Service:

Very good. VMWare visits the customers themselves, at least in the Netherlands. Once or twice per year they come on site to talk to the customers to see what they need, anything extra, any support, anything. It’s a very open contact with them.

Technical Support:

It works like every other support agency – it depends on how high you set the priority of your call or contract. If you have a basic support contract it won’t be the same as a 24/7 high priority contract, for example. So it varies depending on your support contract; it also depends on which support engineer you get. Most of the time I get a lot of questions back from the support engineer, so maybe they don’t fully understand the systems. I have a production support contract – so I expect them to take over the system and fix it! Eventually they fix the problems, but with some it takes a lot of time.

No, I've always used VMWare, as I’m not a fan of the other options available.

It depends – mostly it’s complex; first of all, I have a lot of customers that just buy some hardware and expect it to work like magic, but also not all of the configuration information is always easily available. Different components need specific configurations, and so we have to go to the vendors to get configuration information for the hardware which takes a lot of time. Customers don’t understand that and think that one size fits all.

I implement it for customers.

Get an expert with you before you buy something. Most of the customers that I work with have some licenses already; but when they explain what their core business, plans, etc., are we find that the licenses don’t match the mission. That starts with Microsoft a lot of times – the licensing isn’t correct – working with VMWare, and the vendor doesn’t see the combinations. A lot of the time, we see the software vendors maybe are VMWare partners, but they don’t care what licenses they sell. They just want to make a lot of money. So there’s a real gap in the market.

No other options were evaluated.

Look at the total product – if you’re comparing it to Citrix and Microsoft, look at all the features VMWare is hosting in your product and make a comparison. Also, understand your plans – what do you want to do, what’s your vision, and how does it match what you’re looking to buy?

The most common use case for VMware vSphere is, of course, virtualization, specifically operating system virtualization. We also have containers that are running on them.

Essentially, we have the flexibility for a hybrid cloud. We could easily move workloads from on-premises to the cloud and vice versa if we were running on-premises and cloud, which is one of the most important points in the new releases, in particular.

The quality of support could be better.

We have been using VMware vSphere for six to seven years.

We have dealt with various versions that range from 5.5 to 7.

VMware vSphere is a stable solution.

In our organization, we have at least 60,000 users.

It is being used extensively. It is one of the core products in the infrastructure.

Support has not been as good as it once was. It used to be better, but it appears that the quality of support is declining for some reason. I'm not sure why.

Previously, we were using Hyper-V, but I don't have a lot of experience using it.

The initial setup was quite straightforward. It's very simple.

The time it takes to set up will vary, but it will most likely be within a day. You could set up the environment in a day. It is determined by a variety of factors. If it is done by an experienced engineer, it will be done within a day. If not, it will take longer.

We have a team of three engineers to deploy and maintain this solution.

Licensing fees are paid on a yearly basis. The license is a one-time payment. You buy it once and own it forever, but you must pay for support, which is provided by the vendor, on a yearly basis.

We are also using NSX and vSAN. We have been using NSX for three years.

It's not strictly a cloud solution; it can be on-premises as well as in the cloud. It is, in essence, a network virtualization solution. It can be used for virtualizing the network, virtual routers, virtual switches, and virtual firewalls.

Virtualization and on-demand networking are two of the benefits. On-demand networking is the best option if I can memorize it. If you need virtual switches, we can create them as well as routers.

Virtualization would be our area of expertise.

VMware vSphere is, in my opinion, one of the best in its class on the market. However, depending on the use cases, we could certainly recommend it.

I would rate VMware vSphere a nine out of ten.

On-premises

We are using this solution to build the AD database for the server.

This solution has been very helpful to our organization. For example, if we need to run 10 servers there is a high cost attached if we buy the physical server, but if we use this solution we can buy a very large server then control everything. The most valuable feature has been the ability to utilize the vMotion when we have a problem. It has been invaluable for us when we had a problem with a broken host that we were able to redirect our traffic to a different host to keep the business operational.

I have found the solution to be flexible, and the vCenter and vMotion useful. When we have a server that is down we can use the vMotion to use another host. Additionally, the backup feature and graphics are very good. The documentations are clear and easy to understand.

There was a time we lost the password for the ESXi and we had to do a hardware reset. At this point, we had to fill up the ESXi from the bottom up. I am not sure if there was another solution to this problem but it took a long time. We were told it would only be a few hours to resolve but in fact, it took one day. Having to explain this downtime to management was not the best experience.

In an upcoming release, there could be a better ability to manage and control the synchronization of the power in the vSphere.

I have been using the solution for approximately five years.

The solution is very stable. 

The scalability is good for everything we have been using the solution for. We have three IT users using this solution, if we upgrade our hardware we might increase usage.

The technical support agents are not clear about the issues that are being discussed. They cannot address the problem or estimate the time correctly. In one particular issue, we needed to raise our ticket to the management level because they told us it would take two hours to be operational but the downtime was one day and one night. They should have first checked the vSphere technical aspects.

The installation is very easy. It was not complicated at all.

This solution has kept our business operating and has saved us money.

There is an annual cost for the use of this solution. 

The price is a little high in developing countries. If they were able to reduce the price they would receive more customers now and even more in the future.

I rate VMware vSphere an eight out of ten.

On-premises

Primary use case: data center virtualization. It's performing well. We're really happy with vSphere as a virtualization platform. 

In terms of the built-in security features, we use none of them. I really couldn't tell you much at all about that.

Mission-critical apps would be our student information system - that one is running on PeopleSoft - student portals, also PeopleSoft. Those are the mission-critical ones that we're running on VMware. There's other stuff that is critical, but I wouldn't say that it's mission-critical.

Benefits of vSphere: It saves me a ton of time, I can really quickly spin up new things to test them out or to respond to a need from the business. The way that it improves the way that the organization functions is that it makes us a lot quicker to respond to the needs of the business.

Most valuable features are 

• quick provisioning
• High Availability
• DRS for balancing workload.

I definitely find vSphere to be simple and efficient to manage. A key feature that enables this is vCenter. It is super simple to stand up, and once you're in there, especially with the new HTML5 client, everything is easy to manage.

I find the stability of vSphere to be pretty great. We've had some issues, like everybody. Most of them were around hardware, so we thought it was really important to check the compatibility lists and make sure that you're running the right driver versions. But once you've got that running, it's solid. We don't have any stability problems.

Scalability is great. It's easy to scale.

I honestly found that I spent too much time in "back-and-forth hell" with help desks that are offshore. I found that VMware Support - it used to located in North America and that's who I would get when I would pick up the phone - the last few support cases that I opened didn't go that well. I ended up finding the solution myself and just telling them, "You know what? Forget it."

I was not involved in the initial setup.

Straying a little bit from vSphere, but on vROps, the ROI that we're getting from that is that we're able to reclaim a lot of idle and oversized VMs, and we're actually saving money or actually giving ourselves more time with the resources we have, before we have to purchase new stuff. So that's an ROI.

Aim for simple, go for fewer hosts with bigger resources, depending of course of on what you need. Don't try to do everything at once. Start with a basic setup and work up from there.

We did not really see a performance boost with version 6.5.

Regarding the most important criteria when selecting a vendor, it needs to be an industry-leading solution, needs to be easy, simple to set up, not an entire ecosystem of things that I need to deploy to get their system working. Ideally, I want something that we can set up in a day.

I'd give vSphere about a nine out of ten. There is still stuff to work on, but it's definitely the best for me. As I said, I find that the support never blows me away, and maybe that's because I don't pay for the most premium level of support, but I find that what we got on the last few tickets that we opened was not great.

Key business drivers and benefits for us: • Co-location data centers environmental costs are greatly reduced (rack space, power, cooling). • Allows better utilization and flexibility to segment physical resources (vCPU & vMemory) • Consolidate / centralize management of all Windows and Linux infrastructure - Administer entire virtual environment via a single pane of glass (vCenter) - Provisioning of VMs is really simple and quick. Allows easy use of templates. - Utilize Distributed Resource Scheduler (DRS) & VMotion - Optimizes performance of VMs - Allows flexibility for patching cycles to minimize downtime. • VMware product has been very stable • Allows for easier compliance and consistency for meeting IT audit controls • Initial ROI analysis a few years ago did show significant savings over physical model. We are looking at updated ROI and show-back / charge-back models currently.

VMware product challenges / Areas for improvement: • Advanced Capacity Management and Performance Management & Analysis, Disaster Recovery, and private cloud capabilities are lacking out of the box for enterprise-level deployments. - Ability to “right-size” resources on all VMs is needed at enterprise installations. - Add-on / 3rd party products like vCenter Operations / VMturbo, SRM, or vCloud may be needed. - These add-on products add management complexity. They also add licensing and maintenance costs for the overall solution in a tough budget climate. • Difficulty using VMotion with Microsoft Clusters. We utilize clusters for our large SQL Farm, but we are unable to use VMotion during patching efforts. We are now looking at Hyper-V or physical servers for this functionality to minimize downtime. • Granting administrative privileges / roles can be a bit more tedious than are initially apparent.• VMware vSphere 5 is current architectural standard for 2 data centers - VMware was the major virtualization solution provider when first implemented years ago - Microsoft 2012 Hyper-V “proof of concept” is currently in progress for US - Educational discounts from Microsoft are significant - Microsoft Hyper-V 2012 version functionality appears to gain on VMware vSphere • Also have a large Solaris UNIX environment utilizing Solaris Zones. • VMware (or Hyper-V) will enable us to drive a re-platforming effort for Solaris -> Linux

Things to consider before purchasing VMware or Hyper-V: • Understand your virtualization objectives and requirements before purchase. Assess all requirements against VMware or Hyper-V licensing cost and edition functionality • Define a strategy for resource intensive applications (large CPU or memory requirements) and when to stay standalone vs. virtual • Implement processes to control “VM sprawl” as VM provisioning process is so simple. • Consider other process efficiencies that virtualization may drive (i.e. Service Catalog) • Ensure IT staff gets proper training. The learning curve can be steep initially at the enterprise level. • If possible , look at processes for show-back or charge-back model early on to assess costs and ROI.

It is a compute virtualization software. It is mainly used to virtualize physical servers and deploy virtual machines on top of virtual servers. So, instead of having one workload per server, you can have multiple workloads.

The fact that you can use all the CPU and memory power that the server can provide is most valuable. In a physical server, you might end up not using all the physical resources. There are a lot of benefits, such as flexibility and mobility, in virtualizing computes.

The improvement is more from a licensing perspective rather than from a feature functionality perspective. There could be more flexibility and fewer model options to make it easier to sell. Today, there are so many different options available, and sometimes, it is not really clear which one is the right version or the right model to propose. 

We have been providing this solution to our customers for 15 years.

It is definitely stable.

It is scalable. In our country, I believe 50% of the customers are running vSphere virtualization.

I don't have experience with their technical support. 

I never did an installation, but as per my understanding, it is straightforward.

The number of people required for installation and maintenance really depends on the scale of the project. Usually, one engineer can deploy vSphere very easily.

It depends on the contract they have with VMware.

I can recommend this solution. I would rate it at least an eight out of 10.

On-premises

We implement all the standard VMware data solutions. Typically, that's vSphere and sometimes DataCore, the other product we like. We use vSphere for the virtualization of data servers, and other common uses.

Our customers opt for virtualization because it's cheaper and better than non-virtualized solutions. VMware is probably the best on the market now. 

We're implementers and we started using vSphere when it was first released. We've been with VMware since the beginning. There was no ES6 at that time, only GS6 on Microsoft, so we started with Windows-based VMware. It's an old solution. We've been using it for a long time. 

We haven't encountered any limitations with vSphere's scalability. At the same time, we usually do not install huge server farms here in the Slovak Republic, so we only use VMware for small installations with a few host servers. I don't think we'll reach the limits of VMware's scalability since we only work with small organizations. 

We tried Hyper-V a few years back, but there was a problem with the 2012 version of Hyper-V, so we prefer VMware because we know it works. However, I'm not sure about the newer versions of Hyper-V. I can only speak to our experiences with the older one. We weren't satisfied with the features, and the Microsoft code had bugs that they didn't repair those errors. 

Overall, Hyper-V was a highly unstable solution at the time, so we decided to stick with VMware because it was much more reliable. Maybe Microsoft has improved Hyper-V since then. I can't say.

I rate VMware vSphere nine out of 10. It does what we need it to do, and works fine. There aren't any additional features that we need at this time.

On-premises

Our primary use case is for integrating data feeds from multiple applications. 

The ability to redistribute loads, to re-spin failed processes, monitor resource utilization, and such are all valuable features in VMware. In industrial IoT, most elements end up being terrestrial. With VMware, especially when you're working with niche products, you can manage the integrated solution and multiple systems from a single pane of glass.

We're moving towards containerization and it was unclear what I'd have to do to support containerized environments alongside multiple systems of Linux and Windows. My aim was to get to a single hypervisor environment in which I could support a container environment as one of the array of other applications. Whether due to a lack of training or information, I was unable to get to that. Some people look at VMware as being an alternative to containerization, enabling them to dispense with solutions like Kubernetes and Docker in order to do away with VMware. That's not the reality and I'd like to have a transparent platform that can support all of them.

Aside from cost, I'd like to see some simplification in the solution. The main issue is manageability or scalability of skilled resources, the degree to which the product delivers a stable environment that can be managed by a less technical person. 

I've been using this solution for two and a half years. 

The solution is stable. 

The solution is very easy to scale, especially when you are trying to scale resource availability and the management of the solution. You need to have a degree of transparency across all those environments.

I haven't personally had any contact with technical support. 

I've deployed Docker as a standalone using Linux, multiple servers, etc. I'm currently learning Kubernetes so that I can create a new island in the chain and do a container, but I still have the other systems that continue to run in environments best suited to VMware.

The initial setup is straightforward for a computer savvy guy. I haven't experienced any bugs or glitches. Our customers are generally small to medium size organizations. 

For now, I would go with VMware for the Windows and Linux environment and do Kubernetes as a new island in the chain for containers. For most organizations, the ideal is the number of other users of a solution, because they're the ones that find the problems before you. Going off into some experimental environment may sound great and you might have a good initial experience, but if you're going to be the only person walking the minefield, it may not be a good ending.

I rate VMware nine out of 10. 

On-premises