VMware vSphere Reviews

Primary use-case would be updating our Gold/Masters for the Horizon environment. It works pretty well. We're still getting used to the HTML5 Client versus the old Flash-based Client.

We use it for all of our servers, we have virtualized everything. The mission-critical things, for a bank like us, are the mainframe - it's the IBM iSeries - and our Saleslogix application. Those would be the two biggest ones, but we use it for all of our databases as well. We're 90 percent VMware, with hundreds of servers.

It's been a pretty smooth transition. We just upgraded to 6.5. Hopefully, we'll be updated to 6.7 soon. But it's been working really well.

It's hard to say whether we've seen a boost for these apps since we were very much first onboard a long time ago with a VMware. But performance-wise, every upgrade we do, we see it gets better. Everything gets better: the networking gets better, NSX is getting better. Security-wise, that's been a really good thing for us, separating our network out a little bit more, automating our failovers.

The most valuable feature is being able to VMotion and migrate easily, moving machines around on the host. I know DRS will take care of a lot about that, but there's still some manual intervention here and there, so the flexibility of it has been really good.

It's pretty simple. It's easy to upgrade.

I would like to see DRS for the GPU machines.

It has always been stable. We haven't had any downtime in all the years we've used it.

It's highly scalable. We've grown, we've doubled our size, and it has been easily scalable for us: slide in a new host and then attach the host to the vSphere client and then push the profile out. It makes it really easy.

I've never had to use technical support, myself. We have probably used our VMware rep here and there. We usually get our answers through our rep or our TAMs. There hasn't been anything "break-fix" where we had to call technical support and get on the line right away.

Our customer rep answers all our questions and, if he doesn't know, he comes back the next week and he lets us know. It's been a really big help.

Our ROI comes from being able to replace a lot of our endpoints, mostly on the Horizon side. But using vSphere with all the endpoints, replacing all of our physical machines as well with Dell EMC's wide clients, it has almost been invaluable to us. The cost savings have been great there: buying $300 machines instead of $1,000 PCs.

It is quick to learn, it's not overly complicated. You don't have to spend a lot of time learning about it, at least from the usability perspective, once it has been set up, of course. It's really easy to use, easy to set up, easy to find what you're looking for, easy to manage.

When selecting a vendor to work with, our biggest issue would be availability. We've had some issues with some vendors in the past where they were just too small. Being in Des Moines, we don't have a lot of options, other than bringing people in from other states, or even other countries, possibly. If we do have something come up - which, luckily, we really haven't had anything too bad - just having that immediate connection and resolution is important.

This solution has to be a ten out of ten. It's been great. It's easy to use, it's laid out very well, so it's easy to onboard.

The primary use case is to virtualize our physical environment and to decentralize management of the systems themselves. It has been performing very well. We use it for everything. 

About 95 percent of our environment is virtualized at this point. Even our ERP environment, which is AIX, runs on vSphere, ESXi is the host. We have implemented SRM for failing-over and having high availability and disaster recovery in our other data centers.

We have seen a good 20-30 percent performance boost for our apps. Our underlying infrastructure is a full HPE shop. We've gone to full SSD drives at this point, so by doing that we have actually gotten a good performance boost.

The most valuable features are the scalability and the ease of use. The latter makes it most efficient to use. It is very simple, very easy. We've been doing it for a while now. Most of that comes from having the expertise in-house to run it, and that's why we're here at VMworld 2018.

I have just been looking through what vSphere 6.7 has coming, and one of the things I'm most excited about is the fact that we won't need to use multiple Clients any longer, if all the features that are supposed to be available are, in fact, available in the HTML5 Client. That's one of the biggest things because, for me, it's all about management. For the most part, all the other things that have made VMware invaluable in our lives should be working just as well, but a little bit more speed won't hurt.

The stability is okay. For the most part, when we have issues it's because the self-connections or the VPN connections between the cloud space and our internal network go down. It doesn't necessarily mean that access to those applications is cut off from the outside, because the applications are up. It's just the connectivity on the inside. Depending on the use case, if the application is hosted on the outside and it's being used by people on the inside - which in most cases is not the case - it's usually people who manage it who can't get to it. For the most part, we're okay with it.

I rate tech support highly, for the help we get.

Prior to having this, we had physical servers. We've virtualized almost everything that we can virtualize. I wish we could virtualize our IBM iSeries, the mainframe, which is impossible to do. But for everything else, I think we are pretty okay.

When selecting a vendor, I first look at

• proven industry standards
• longevity
• security
• good customer experience
• a robust infrastructure that is scalable and tested. 

Usually, when we make recommendations, which is one of the things we do as infrastructure specialists, we evaluate several vendors and try to see which ones match up most with these criteria. Whichever one comes out ahead, comes out ahead.

The NSX part of the setup was fairly complex: Setting up the networks and setting up the VPCs was a little bit challenging, but there was good support from both sides, from the VMware side and AWS side, to get things up and running the proper way, and that helped a lot.

We see a tremendous return on investment.

If you're not on vSphere, you should get on it as soon as possible because it will only make your life easier. All the different innovations that have been coming out over the years have shown that it's only going to get better, especially with artificial intelligence, IoT, etc. With all the different technologies that are being proposed, VMware is always going to get better. From a technology standpoint, anybody who is in the industry needs to be on this because it just makes everything easier.

We have been using the built-in security features such VM Encryptions and support for TPM and VBS, and it has been hit or miss for us. In some instances we've used it and in some instances we haven't. But for the most part, I think it's okay.

We have started using some cloud technologies with it, partnering with AWS to do that. We have a couple of internet-facing applications that we have used, that we have deployed to the cloud, and the experience has been somewhat okay.

Because of the nature of our business, there is an apprehension toward actually putting information out on the cloud, if it's not a private cloud. So the latter is what we have chosen to do. We have been able to deploy applications into our own private cloud space, with dedicated pipes to the cloud, with firewalls on both sides of it. We do AD Federation Services to authenticate between the cloud space and our internal network, and we have domain controllers in the cloud as well. We have gone through the growing pains of going to the cloud and now we're working through the quirks and nuisances that come along with that.

The primary use cases for the solution are all of our production and DTQ. 

We're not using any of the built-in security features.

We run 3,000 VMs. It works for what we need it to do. All of our retail point-of-sale stuff, the back-end for that, is on VMware. We're retail, so everything is run in virtual.

The vSphere Client always feels slow, and/or like it doesn't keep up with what I'm trying to do. So I usually use the thick client most of the time.

I'm looking forward to some of the new features on 6.7 where you can record your actions in the Client and then it will spit out all the code. So if you want a script of what you just did, it gives you all the code for that. That's probably the one thing I'm looking forward to the most in the 6.7.

I feel that it's stable. We haven't had any downtime because of the VMware.

It's scalable.

Technical support is helpful. I get through to the right people and they are able to give me the support I need.

It's the only virtual solution I've ever used.

Our main use case for this is that it's the foundation of our company. What our company, MacStadium, does is provide virtual environments for customers to do iOS development on Apple hardware. And the foundation for that, for creating the private cloud, is vSphere.

In terms of mission-critical apps, it's utilized mainly for iOS development. So customers will use the API for vCenter to automate things. They can do CICD, where they can spin up and spin down virtual machines, rapidly, and provide them to their internal groups or to their customers to do iOS development.

It has actually been performing a lot better than you'd think for an initial release. It's very smooth and I've been pretty impressed with it so far.

As a connection for our business, it goes hand-in-hand. It being the only hypervisor that runs on top of Apple hardware the way we want it, there is no "us" without that.

The most valuable feature would be the slight changes they've made to VMFork instant cloning, in which they have abstracted out the parent-child relationship in cloning, in which certain features, like HA and DRS, are now usable on that parent virtual machine. That is wildly amazing and something that wasn't available until 6.7.

We are actually making a lot of use of the VM Encryption feature. We're using that mainly because it's a customer requirement, especially after all the changes in the European Union for security. And that's a major issue. We've been adding in NSX and that, combined with the ability to have encrypted VMotion as well, has been huge.

In addition, the simplicity and efficiency in managing it has always been one big thing with the entire vSphere suite. It has been very straightforward if you're just using it from the user interface. Hitting the API has always been great, and they're continuing to grow that, which has been really good for us.

I know, coming out in 6.7 Update 1, that the HTML Client is going to reach full parity and have all the same features that they had in the now-deprecated thick client that used to be on Windows. That's one really neat feature I'm actually looking forward to.

There are always little "gotchas." In the past, little changes have broken things in vSphere. Going from 6.0, which worked perfectly fine on the Mac Pro, there were certain changes in hardware drivers, when 6.5 came out. Some were no longer present or had been deprecated. As a result, it didn't work on the Mac Pro anymore, which was business-critical. Okay, everybody could stick on one version and wait until it was fixed. We were able to take drivers out of the 5.5 version, add them to the build package for installation and it worked. It was not the most efficient, and storage I/O was kind of slow. Since 6.5 Update 1 came out, that has been solid, no real issues with that.

The stability has been very good. I've run several builds on 6.7 from pre-release and it's been good.

As far as scalability goes for us, I've run it as far as having up to 100 hosts in the cluster and I haven't noticed any degradation. It's been running well.

I actually have gotten quite a bit of tech support for initial installations. Even though they're on the hardware compatibility list, Mac Pros and Apple hardware are very different than your traditional Dell, Cisco, or HPE Blade. Apple hardware is kind of like a black box, so it's very hard to interact with, but ESXi has been perfect.

My experience with tech support has been pretty good. The response times are really good. If the engineer that I'm working with is not directly knowledgeable on that idea, usually he'll get back to me in a short time and hand me off to a guy knows exactly how to help me out with the problem. And then, the follow-up is good as well.

We've always been using vSphere from the beginning, starting with 5.5. We actually worked with William Lam from VMware on getting ESXi working on Minis at that point in time. It's been a wonderful relationship since then.

One big thing that I know a lot of people talk about, when looking at why go with vSphere, is the ecosystem. You have other products that were built solidly to work with the vSphere product and the integration is always completely solid. The continuous development on the vSphere product and all the other products in the ecosystem, and the community, also play a part. There's pretty much nothing that I have run into where I say, "Hey, I want to do something outside of what vSphere does," and there hasn't been somebody within the community who has been able to say, "Oh yeah, I got that running, it is really easy, this is how you do it." That's not something I have seen in any of the other ecosystems.

It was pretty easy upgrading any of the older hosts from 6.5 to 6.7. Everything was pretty straightforward.

In terms of advice, especially if you are on things like Hyper-V or other products that I've touched, the simplicity and scalability of the vSphere product has been solid. For another individual who is in the IT or engineering fields, I wouldn't go with anything else.

One thing a lot of people don't realize or know about is that Xcode and OS X are closely tied to the versioning of vSphere and what features will be enabled. Coming out this September is MacOS 10.14 and that brings with it the need and requirement to run APFS, which is only supported in 6.7. So we have an abundance of customers, all of which are iOS developers, who require 6.7. So having that coming out was a major need and requirement for us.

I haven't noticed a direct performance boost, but the performance is no less than it was in 6.5, which is always generally a good thing. With the addition of features, nothing slowed down, everything is still exactly where it was.

The primary use case is to save us a lot of money. Really, the primary use case is to be flexible, to be scalable, to be agile, as the company changes. As a non-profit, we really change often. New programs come in every day. vSphere gives us the ability to be flexible The mission-critical apps we use it for include Exchange, SQL, Active Directory, document management systems. We use it for everything.

While we haven't seen a performance boost for these apps, they're flexible. That's really what it's about. I'm still learning how to make it boost performance.

We haven't used any of the built-in security features.

It saves us a lot of money.

VMotion is the biggest feature. It gives us the ability to move things on the fly. That's it.

I do not find it to be simple and efficient to manage. The tools, the interface to manage it, are a pain. In the latest version, they moved us to web-only, the Web Client and it's terrible. It's slow. It crashes. It's annoying. I used the Web Client in the older version and was happy. I would go back to the regular thick client but I don't have that option anymore, so I am always fighting it.

The solution itself is really stable.

The scalability is insane. It's great.

We were all physical and it wasn't scalable. Every time they came to me and said that they wanted to start a new project with a new piece of software, I had to buy hardware for it. One day we looked at it. Quick, funny story: big presentation to the Board. Spent an hour explaining what virtualization was. I said, "Okay. I can do this by spending less over the next five years and we've already budgeted more." And the Chief Financial Officer looked at me and said, "Why did you just waste our last hour? If it's going to cost us less, then just do it." Why didn't you start with that? Way to bury the lead!"

It was a no-brainer to move.

The most important criteria when selecting a vendor is support, absolutely. US-based support that doesn't pass the buck, that takes ownership of a situation and deals with it.

The initial setup was straightforward. I built the whole thing myself, without knowing anything about VMware to begin with, just learning it as I went.

Our ROI is huge. We put, in hardware and software, probably $80,000 dollars into the solution and have never spent another penny in the last five years, other than for support. Compare that to a budget of $30,000 a year, we'd be at $150,000 in those five years. So, the return on investment is huge.

For our initial look into vSphere versus others, we started with Cisco's version of virtualization. It was cool. It was free. But it was a pain. It didn't scale. When I started looking at the software we wanted to run on it, nobody supported it. That made the decision.

In terms of advice to a colleague, I'm giving it every day. I take the guy out to lunch to beat him up with vSphere. I've got a buddy who is a Hyper-V guy. He's says, "But it's free," and I keep saying, "Well, you get what you pay for." He says, "But it never gives me any problems." I say, "Then why are you calling me every week asking me why Exchange is doing stupid things? I don't have those problems and I run exactly the same version you do."

It's stable. It just works. I don't have to think about it.

Some of the new stuff that's coming out is pretty exciting, as we start thinking of moving to the cloud. But, as a non-profit, at this point, it doesn't make sense to do so, yet. But as we move to the cloud, some of the new stuff they talked about yesterday, here at VMworld 2018, is really going to help us do that.

I give vSphere an eight out of ten because of the web interface. It would be a ten otherwise.

We use it to manage our VM servers, everything we have. We're about 98 percent virtualized and we're using VMware vSphere and it works great. It performs great.

In terms of mission-critical apps, we mainly host a lot of our accountants, so we have a lot of accounting software. It's really mission-critical to where we have to have these apps running 24 hours a day, seven days a week. With vSphere, we're able to use VMotion, HA, and Fault Tolerance to keep our apps up and running for them.

We don't use VM Encryption or support for TPM or VBS. We don't yet use VMware Cloud on AWS but we're looking forward to it.

Getting rid of our physical servers and going virtual is saving us some money in overall rack space.

Server consolidation.

It's extremely simple. Installing the ESXi is a piece of cake and then putting servers on there is really simple, as is having HA and building a cluster for our VM servers. It's very easy.

The UI is great with the new HTML.

In terms of stability, so far it's been really simple. We've been running it for a few years now and it has been flawless. We haven't looked back.

It's really simple to scale. Just add another server, add it to the cluster and, bingo bango, you're done.

Our experience with technical support has not been the greatest. We currently have a ticket open and it's been open for a few months now, for our VDI solution. I can't complain. In other situations, it has been fine.

A big thing for us, and the reason we went with VDI, was for security. We didn't want folks having laptops or taking them out of our environment, out of our building, and not having them secured, where somebody could just pick one up and take it. This way, we keep it all in-house and it's more secure. It's in our hands and not theirs.

We went with VMware because we were all more familiar with VMware and our vendors, our reps. We all have a great relationship with them, so we decided to go that route.

The setup was pretty straightforward.

I honestly don't know what our ROI is, but it's a lot.

We looked at Citrix and we looked at Azure.

Give it a shot, check it out how easy it is. It just works.

I rate it a ten out of ten. I'm a big advocate of VMware.

We use it to virtualize our server infrastructure.

Virtualization has made it easier for us to manage our environment. We can manage it from location, the vSphere web client.

We find the solution simple and efficient to manage. 

It provides us cost savings. We are able to virtualize instead of buying many physical servers. Therefore, we can buy one server and add VMs on top of it.

The SQL Servers are our mission critical apps.

• Keep innovating.
• Make it more efficient and stable.

It's very stable. We've had no issues with it.

It's very scalable. You can add different components to it. Moving into the future, as we do different things, we'll be able to stay with VMware.

The technical support is very helpful. VMware's technical support seems to be very knowledgeable.

We did not have a previous solution that we were using.

I was not involved in the initial setup.

It's huge. It has been a big return on investment for us. It saves us money because we don't have to buy as many physical servers. VMware seems to be the future of computing.

It is cost effective. 

We did not look at anything else. We just looked at VMware.

We are just learning about VM Encryption, TPS, and VBS right now. We just moved to VMware ESX 6.7. While I don't have a lot of experience in it yet, but we're looking to implement them.

Since we have had VMware, we've had no problems with it. It's easy to manage. It works very well. Other competitors may not offer as much. You can do a lot with VMware. You get different plugins, so it's a great product. Just go with it.

Most important criteria when selecting a vendor:

• Cost
• Stability.

It's how we manage our server infrastructure virtually.

It meets all of our needs.

I'm looking forward to the HTML client being finished. That's the thing that's annoying me, but I know it's coming this fall.

If they were going to make the transition from the standalone installable client to the HTML, I wish they would have done more development on it before they released. It's not feature-complete, so we have to go back to the old client to do certain things, and I don't really want to.

It's a very stable product.

We haven't had any scalability issues yet. I don't foresee us having that issue. We're small enough that, if there is a case where it wouldn't scale, it's not going to be discovered by us.

Technical support is always helpful.

I would absolutely recommend it. vSphere has been at the last two jobs that I've had and it's solid.

It's a definite nine out of 10. I'm not sure that there's anything out there that would be better. Microsoft has a hypervisor but I think VMware is more feature-complete.