VMware vSphere Reviews

We had almost 100 servers and we wanted to consolidate them and also make them movable, especially when we have to upgrade hardware. It also allowed us to create more testing environments, because we tended to buy new iron every time. We also want users to be able to “own” servers themselves, so that we would build them for them, hand them over and say, "Have fun".

• Flexibility
• Ease of management

Maybe it's there and I don't know about it, but I would love to be able to build a standard server set and be able to give users, who want to build another server, the ability to click in and have a pool of 20 options for the five groups that are using them. I could just say, “Hey if you want a server click here," and then the server is built for them, tells them how to connect, how to login to it. Done. That would be so cool.

It's stable. It has only crashed once.

We're not a very big shop, so it's not really appropriate for me to answer this question.

I would give technical support about 7.5 out of 10.

I waited until version 5 because, prior to that, I thought it was too difficult to set up. With that version, the setup was fairly easy. And it has gotten a lot easier since.

On the server side, we have definitely seen ROI. If servers fail we just restart them, if a piece of hardware fails we just move it. We haven't saved any money but we have been able to double our load without adding any more staff. That's our ROI.

In real terms, because of the cost of the product, I don't know that we really save anything. We're a public institution and we tend to have very long time frames for holding onto hardware, not like a corporation. I would say it's a wash on a pure ROI, unless we can look into the future and say, “I'm going to be able to do increased stuff without adding any money.”

Pricing is the one "ding" I have against it. Except for VMware vSphere Essentials, it would be pretty challenging for anything but a medium or large size company to use.

If you're managing more than five servers run over and get some vSpere Essentials. I think virtualization is the only way to go, whether you do it on-premise or in the cloud, nowadays. It doesn't make any sense once you get beyond a couple.

I rate the solution an eight. Price would be the main thing, as well as the relative inaccessibility for end-users to be able to touch the product.

SAAS, SAAS, IAAS using Virtualisation of infrastructure

Work life balance as systems administrators got flexibility, robustness, scalability of current infrastructure.

The licensing part. VMware must simplify the licensing mode to help selling to business and additional products.

Almost 10years

Nope. Smooth all the way.

Never. Vmware was the easiest system i ever deployed. Did it without training.

Not yet. As long as i have the infrastructure, the system works like magic. I can add hardware and servers as i want.

I only have the online website customer service. Otherwise i have no support from anyone. Tho i love the product.

once i had to upgrade and i was adding some new hardware from DELL the company in Kenya sent very good guys to work on them directly. We have been good friends with the guys tho they are no longer in DELL.

I was deploying servers from bare metal. Once i got VMware, i have never looked back.

It was smooth. I had bought symanted brightmail and it could only deploy from VMDX. So i had to learn the hard way. I likes it. Once i learnt about VMware, i have helped no less than 20 administrators to deploy VMware in Kenya.

Dell M1000 full blade power edge, deployed by the manufacturer.

It is superb. Level of hardware investment went down. Scalability and power is superb. Next am deploying BI and warehousing on DELL poweredge using VMware and later a 4 tier (a true 4 tier) datacenter in Kenya.

This is a place VMware have to work on. Bringing in products or upgrading is difficult to sell to the finance guys.

I fell into VMware. I so far like the marriage.

Keep going guys. Best thing under the sun.

Every organization that I know of that has wanted to implement virtualization in their environments wants HA with every virtual server. That's why for us, we've found the most valuable feature is the ability to move VMs between vCenters and fault tolerance within our four vCPUs.

I would also add that the vSAN feature was not useful beforehand but now with Hyper-Converged infrastructure it will simplify vSphere management as well as storage. We may be acquiring xRAIL from EMC which will definitely eliminate needs for storage as well as Fibre Channel switches.

The biggest advantage is that it cuts costs. A few years ago, I worked in an environment of all physical servers. It was very expensive to maintain high availability with them. vSphere cuts that cost.

No more lengthy physical server server restores. When this product is coupled with Veeam Backup and replication restoring whole virtual machine or individual files or active directory objects virtually happen in minutes.

I'd like to see small VMDKs in the next version since Hyper-V provides that option. Right now, that process with vSphere is still manual and requires downtime.

I have used this product for the last five years.

With previous versions, for example in 5.1, it was inconvenient to deploy an SSO database. Now, an SSO database is local and automatically installed.

It's highly stable.

It scales without issues.

The level of technical support depends on who you're talking to. Some people are more experienced than others. Overall, though, I'd rate them well, but they don't respond very quickly during the weekends.

I used Hyper-V, which worked well on a single server running Windows 2008 R2. But as soon as a cluster is configured, there are lots of issues with SCVMM. I've heard that Microsoft made some improvements and the product is now more stable, but VMware ESXi is based on the Linux OS and is much more stable. I've had to learn command-line code in Linux, but VMware is better than Microsoft.

It's very easy to set up because it's a popular product and there are many online articles. VMware articles are a bit dry. Many consultants post their experiences, making deployment of vSphere straightforward so long as it's planned properly.

I have implemented this product either from scratch or as part of an upgrade. One piece of advice that I would give is to make sure that the certificate is minimum 1024 bits (I forgot to check that). Other than that, an upgrade or set-up is very straightforward, especially with v6.

The ease of administration and flexibility are the most valuable features for us. Performance, stability, and functionality just keep getting better.

It enables us to move faster when we're going through the legacy systems. Before vSphere, someone had to wait between one and three months to get service which we can now implement in ten minutes.

There are a couple areas for improvement that I can see. First, I'd like to see better performance for vCenter. And, I'd also like to see NSF 4.1 fully supported. There are some NSF features lacking from version 3 to 4.1.

We've been using it for more than ten years.

We've had no issues deploying it.

The stability has been great. I have only experienced one point down and that was caused by our system.

There was also an issue with expiring licenses in 2008, but that was fixed pretty quickly and a new implementation was put in place to prevent that from happening again.

The product has been so stable that we keep using it. We also didn't want to change it too much because it would require management team training.

It has scaled for us and the workload that we have that runs on it.

We started using it because there weren't any competitors at the time. There was only VMware.

Complexity depends on how you're implementing it because vSphere has a lot of products. If you're looking looking to install vCenter, it quite easy.

If you're using a lot of the other products, you have to be careful. Today, we use almost every product from VMware and we still have to be careful with the updates.

Start small in a development environment. For $200 per year, you can get access to files VMUGs. 

You can get a 60-day free trial with a download from the VMware website, but I recommend using VMUGs and attending local VMUG meetings. They have a lot of really capable technicians who really love to share.

Of course we continue to look at the competitors to see what features are coming. In my opinion, it doesn't matter because VMware is still ahead of the competition.

Pretty much everything about VMware is a strong point. From my point of view, it's one of the most stable and scalable technologies on the market, and when it comes to virtualization it's probably the very best there is. 

As a backup and storage admin, I haven't had the chance to explore in-depth all of its features, but what I did get to work with thoroughly seemed very reliable, just to name a few: vMotion and Storage vMotion, Storage APIs (such as VAAI), Storage Thin Provisioning, good integration with LUN mapping to VMFS, etc.

Obviously, it brought with it many of the unique things that any virtualization technology provides, such as High Availability and trimming down costs and data center space requirements. It helped us develop some of our most important and complex infrastructure projects, such as: VDI, Internal Cloud (IaaS for internal Dev Teams), Data Center Clustering with good High Availability potential, etc.

Hard to say what I'd like to see in the next versions. Over the years, the VMware development team constantly delivered major improvements to this product. I've only had the chance to work version 4.5 up to 5.5. Since I haven't had the chance to test the current version which is 6, I think it wouldn't be fair to make suggestions due to the fact that some of my ideas may have already been implemented starting with version 6. 

However, when I think of what tried me most with vSphere, it's probably the fact that my colleagues and I on the Virtual Infrastructure Admin team always had to do debugging and troubleshooting on VM configuration files in a manual manner if we wanted to bring to life broken VMs. 

Sure, some official KBs are pretty useful but not all issues can be covered by them. It would really ease up and speed up the troubleshooting process for advanced and experienced administrators if vSphere had some sort of VM file debug tool that can also run automatic integrity checks and repairs based on the entire set of configuration files, live run-logs, a potential database that logs the history of changes made to the VMs, and stuff like that. 

This would be especially useful when you have environments that tend to do a lot of Snapshot manipulations such as those that use specialized virtual backup and/or replication software.

I've been using it for about a year and a half. Currently, the organization where I work has most of its virtualized infrastructure running v5.5 (we're towards the end of a broad upgrade project) throughout the last year and a half. Since I've been occupying my current position, I've also had the chance to use also versions 4.5, 5 and 5.1.

Deployment isn't the simplest nor the most complex. If you can install a standard HP & Dell server, there's no reason you couldn't take care of a VMWare ESXi Hypervisor. After that, configuration and administration via the vSphere console is pretty easy.

There have been no issues with the stability.

There have been no issues with scalability.

Personally, I haven't had the chance to work with the VMware customer service since most of the issues encountered were usually fixed by applying the solutions presented in official KBs.

Before VMware, our company used to employ Citrix for the VDI infrastructure. Besides being more easy to use for the common VDI user, VMware also allowed us to step up the game by also taking the majority of your server infrastructure to the virtual environment.

Both deployment and administration of the VMware infrastructure in our organization is performed by internal specialized teams.

vCenter Server Appliance (vCSA) is the server that controls and manages your VMware environment. I would suggest using this over the vCenter Server Windows install. It has the advantage of easier install and manageability and seems to be the method most preferred by VMware, as well.

Much of the management of the VMware environment can now be done from the web interface, but you can still use the vSphere fat client, which is still my preferred method of interacting with the VMware environment. The web interface is better than in past iterations, but still just lacks that little something that would make me voluntarily to move to it on a permanent basis.

VMware will assist your organization in managing computer and storage resources, and you will be able to shrink your physical environment significantly making it easier to manage in the long run. So don't expect immediate returns. There is a high price to be paid for licensing, hardware, configuration, and knowledge acquisition.

VMware interacts with a lot of various hardware and has a vast array of capabilities and it seems that new capabilities are being added all the time. I would like to see more documentation and assistance provided by re-sellers to assist in the initial design of customer environments.

There are 3 levels of licensing: Standard, Enterprise, and Enterprise Plus. VMware is very pricey and really the most useful in very large virtualization environments. It takes a lot of hardware and configuration knowledge. If you don't already have this in house, obtaining it can be pricey as well. 

If you aren't already familiar with virtualization environments, I would suggest taking a course and/or doing a lot of reading before deciding on a license and configuration.

The best advice I could give is spend a lot of time designing your environment to receive VMware. Read everything you can get your hands on, and take a good online course or attend one in a city near you. Be aware that you will need to know a lot about computers, storage, networking, and security environments to determine the best design for you. 

Download the latest ESXi version and build a test lab. You get 60 days to play with the full gambit of features. Then get a lot of advice from vendor specific engineers, HP, EMC, Netapp, Cisco, etc. because the hardware you choose will run into configuration issues specific to the vendors you choose to use in your environment. Don't go into this thinking you will see immediate returns on your investment. This is a long term design decision.

• Reliability
• HA
• DR
• Ease of deployment
• We had a lot of disparate hardware and now able to consolidate into one platform
• Easy to keep hardware up to date

So much easier to back things up now. We had Oracle, SQL, everything was just a one-off, but we now have just one process for all our VMs.

We have vCloud suite, Hyperion was a pain, but now they've just announced integration into vCenter, so everytime I have a complaint, they’ve already started to address it.

• Great stability, no complaints at all
• More we move to appliances
• Easy to keep up to date

• We had a lot of standalone boxes, and management wanted to go to VMs
• We were able to consolidate all hardware without purchasing anything extra
• Able to carry us through several years when unable to purchase hardware

They've always been excellent, but we rarely contact them maybe one or two times a year. When we’ve had issues, it’s resolved in hours. We have TAM (tech account manager) so helped things along.

We had vendor come out and it set up on 3.5, and once we got our feet wet, it's easy to maintain and upgrade.

Only purchase what you’re going to use, our management makes decisions, and buy lots of products we’re not using.

We chose vSphere because of it's ease of use, especially that it's easier than Hyper-V. Deployment would have been more labor intensive, and wouldn’t have saved any more money in the long run.

Storage vMotion and vMotion are the greatest of use in my current role; however, the most prevalent features would have to be Fault Tolerance, SRM and DRS.

In my current role, VMware has been used to reduce the overall physical footprint of the environment as well as ease the management aspect of all the virtual environments we used to house. In previous roles, it not only improved the aforementioned pieces but it also improved availability time lines in a significant fashion.

The room for improvement would be just like they did with the C# (thick) client back in 2.5.1 and 3.X, they need to work on the speed of the web client as they are moving towards a distributed management environment. The C# client had its issues back in its inception so they are going through the same growing pains again with the web client. Other than that, I would like to see a stripped down version of DRS brought into the Standard licensing model as the jump from a Standard license to an Enterprise (or Enterprise Plus) license is enormous.

I’ve been using VMware in an enterprise workspace since version 2.5.1 in 2005. I have since had experience with version 3.5, 4, 5.0, 5.5 and 6.0. I'm also currently using vCenter Server 6.0.0A and B.

No issues were encountered in the latest migrations that have been performed but this is due to previous experience.

VMware has a great customer service department. If you use a trusted partner hardware (ie, HP in my experience) for your servers, they will also assist in diving into the hardware aspect of the issues you are faced with to hopefully resolve the problem. I’ve always found the VMware support has been there when I needed them. Their response times are very good and the knowledge each support engineer I’ve worked with has been more than satisfactory. I haven’t run into a “blame game” with support while using VMware.

At my current employer, they used to use Hyper-V 2008. We migrated to VMware due to a more robust feature set and the fact that, yes Hyper-V has a lot of the features that VMware does but, once deployment is complete, VMware is a clearly more stable product than Hyper-V in the long run. I’ve seen and been involved with a few Hyper-V migrations that go from VMware to Hyper-V and after six to 12 months, most of those installations wanted to migrate back to VMware.

The initial installation and setup of an ESXi server is very straightforward. When you start getting into the implementation of a vCenter Server you find all the “nooks and crannies” of the installation that are available. It is definitely more complex with a vCenter Server but that is mostly only if you are using all the features available to you. If you just use vCenter for managing multiple hosts at an Essentials license, it isn’t very complex at all.

We implemented using an in-house team (myself). The advice I have is: When you are building a virtualization environment, be it VMware, HyperV, Citrix, KVM, etc., you need to make sure you build the hosts that are going to run the environment properly. Along with that, you need to make sure the storage infrastructure and network are healthy prior to performing an upgrade. If you “cheap” out on any of those aspects, the deployment will suffer in some way.

Yes, we evaluated Hyper-V 2012. From previous experience as well as feedback from the community we decided to move forward with VMware.