An enterprise workload platform, vSphere is used to improve the performance for a data center. It is used to boost operational efficiency, supercharge workload performance, and accelerate innovation.
$995
per year
Pricing
Hyper-V
VMware vSphere
Editions & Modules
Developer
$24.95
per month
Bronze
$49.00
per month
Silver
$89.00
per month
Gold
$135.00
per month
Platinum
$199.00
per month
Standard
$995.00
per year
Enterprise
$3,995.00
per year
Offerings
Pricing Offerings
Hyper-V
VMware vSphere
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Hyper-V
VMware vSphere
Features
Hyper-V
VMware vSphere
Server Virtualization
Comparison of Server Virtualization features of Product A and Product B
Because Hyper-V is a Microsoft product and based on Windows OS, creating virtual Windows servers and clients are easy. When we want to test our group policies it it best to do it on hyper-v environment then implement to production clients. The same goes with operating system quality and features updates as well as operating system upgrades.
vSphere is well suited for multiple VMWare hosts and can be very useful in larger enterprises where vMotion is used to load balance and failover running virtual machines. In smaller businesses with one or two hosts then the features can be overkill. The addition of virtual TPM support is a very nice addition to provide vm security in a more Microsoft supported methodology.
Virtualization - Hyper-V does this well and I feel like it might be the best and easiest software out there to use. I am able to spin up virtual environments very quickly. Hyper-V also has a "quick" add feature where you don't even need to have the OS ISO on your computer and you can choose between Windows 10, Server or Ubuntu.
Setup and Management - Hyper-V is pretty straight forward. When I first started using this it seemed a bit confusing, but after a couple of days of playing with it you end up finding out everything is pretty straight forward and really not that complicated.
Just turn off the VM and go into the settings and you can manage the Storage, Memory, and CPU's.
Setting a VM up on a Domain is super easy and you can create a static mac address for the machine so in Windows DHCP you can use that static mac address to give that VM an IP it can use every time it boots up.
I think the best feature is the ability to create "Checkpoints" - If you are going to be doing something over and over and you need to start from the same point with each test you can setup your VM the way you need it prior to testing. Create a Checkpoint. Do your tests and then revert back to the Checkpoint so the system will be exactly how you had it setup prior to testing. Then you can go on and do your second set of tests and so on.
Another great thing is the ability to just backup the vhdx file.
As I mentioned at the beginning of this review we run most everything from Hyper-V. I make weekly backup of the vhdx files which are the Virtual Environment files.
This is an extreme example, but if the building ever caught on fire I could go out and buy like 15 PCs at Best Buy and load up Hyper-V on them and just import the vhdx files and be back up and running fairly quickly.
I would love to see Hyper-V add a better remote control feature. As it is, it uses RDP to connect to any VM in the host. This is old technology and slowly deprecating. It would be significantly more useful to have a controlled interface for remoting to the VM's that is much more like Teamviewer, LogMeIn, etc.
More detail in recent tasks. Instead of just showing a task called "Reconfigure virtual machine" also have a link to more detailed information as to what was reconfigured, changed or removed.
Cheap and easy is the name of the game. It has great support, it doesn't require additional licenses, it works the same if it is a cluster or stand-alone, and all the servers can be centrally managed from a system center virtual machine manager server, even when located at remote sites.
We are constantly looking for change that will benefit our company. We are not ones to stick with a product simply because it is what we know, but rather looking for what fits us best. We can't imagine another product on the market today doing a better job of handling our infrastructure than vSphere.
It is very easy to configure new virtual machines and manage them. But you have to use different interfaces to perform various tasks. Especially as soon as it comes to clustering you have to use at least two different interfaces (Hyper-V Manager and Failover-Cluster Manager) to perform all necessary tasks. The newly released Windows Admin Center is a way into the right direction to get all management tasks into one single interface.
Very useful for environments where space and energy consumption are issues and management is not very keen on upfront spending on hardware every time whenever requirement comes from any dept for provisioning a machine for their occasional use, easily can be done in case of VMware vSphere in few clicks. Backup, security, monitoring and management everything is covered but at additional cost.
In the past 2 years our Hyper-V servers have only had a handful of instances where the VM's on them were unreachable and the physical Hyper-V server had to be restarted. One time this was due to a RAM issue with the physical box and was resolved when we stopped using dynamic memory in Hyper-V. The other times were after updates were installed and the physical box was not restarted after the updates were installed.
Hyper-V itself works quickly and rarely gave performance issues but this can be more attributed to the physical server specifications that the actual Hyper-V software in my opinion as Hyper-V technically just utilizes config files such as xml, and a data drive file (VHD, VHDX, etc) to perform its' duties.
Most of the time, you can find support on the thousands of websites, blogs and community sites that are out there. Very much Internet supported, and if you don't stray too far away from the standard setup of Hyper-v, you shouldn't go wrong. I've had to call a couple of times, and Microsoft was very good at resolving my problem. it seem that Microsoft has heard from people and their support system, and are doing a much better job in this
I rarely ever have to contact support and when I do need to resolve an issue, there is always an abundance of kb articles and research information available that can help quickly resolve the issue. Depending on the type of support contract you have, you may get support from some offshore group in another country and this could be a little challenging because of the language barrier.
We had in person training from a third party and while it was very in depth it was at a beginner's level and by the time we received the training we had advanced past this level so it was monotonous and redundant at that point. It was good training though and would have provided a solid foundation for learning the rest of Hyper-V had I had it from the beginning.
The training was easy to read and find. There were good examples in the training and it is plentiful if you use third party resources also. It is not perfect as sometimes you may have a specific question and have to spend time learning or in the rare case you get an error you might have to research that error code which could have multiple causes.
initial configuration of hyper-v is intuitive to anyone familiar with windows and roles for basic items like single server deployments, storage and basic networking. the majority of the problems were with implementing advanced features like high availability and more complex networking. There is a lot of documentation on how to do it but it is not seamless, even to experienced virtualization professionals.
Just make sure that when you implement, that the person implementing truly knows what they are doing and has a plan of action coming in. Since our initial implementation using a consulting service, I have implemented a few vSphere just from what I learned at the initial implementation and use over time, and the person implementing really needs to know what they are doing or you will miss out on features that may help you down the line
Considering the maturity of ESXi, Hyper-V is something I would definitely consider using in future jobs or organisations. We selected Hyper-V after many years of using ESXi; several factors led us to this change, including a poor support experience with VMware, and the lower cost of Hyper-V. We looked at other options including Nutanix and Hyper Converged Infrastructure, however with such a busy team we didn't have the time to learn this completely new technology stack, whereas (whilst also new) Hyper-V had a much easier learning curve.
Nothing is perfect but Hyper-V does a great job of showing the necessary data to users to ensure that there is enough resources to perform essential functions. You can also select what fields show on the management console which is helpful for a quick glance. There are notifications that can be set up and if things go unnoticed and a Hyper-V server runs out of a resource it will safely and quickly shut down the VM's it needs to in order to ensure no Hardware failure or unnecessary data loss.
Having vSphere helped my business quickly recover from a ransomware attack which would have crippled us for weeks if we were not virtualized. I think the ROI on something like that is immeasurable.
vSphere has allowed my company to purchase bigger server hardware to host 3 or 4 virtual servers, which was at a cost much lower than buying 3 or 4 server hardware boxes, saving us thousands each time we need to upgrade hardware.
