Hyper-V, the best place to step on to virtual server management.
Hyper-V was used to extend our ability to quickly prototype and build server infrastructure. We also were using it to develop 'golden …
Hyper-V
Top Rated
Hyper-V
Top Rated
Hyper-V
Starting at $24.95 per month
View PricingOverview
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Top Rated
2022
Best of
2022
Popular Features
View all 5 features- Live virtual machine backup (60)8.686%
- Live virtual machine migration (63)8.282%
- Hypervisor-level security (63)8.181%
- Management console (68)7.878%
Reviewer Pros & Cons
View all pros & consVideo Reviews
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Hyper-V, and make your voice heard!
Pricing
View all pricingDeveloper
$24.95
Cloud
per month
Bronze
$49.00
Cloud
per month
Silver
$89.00
Cloud
per month
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Features
Return to navigation
Product Details
- About
- Integrations
- Tech Details
What is Hyper-V?
Hyper-V Integrations
Hyper-V Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Comparisons
View all alternativesCompare with
Reviews and Ratings
(259)
Attribute Ratings
Reviews
(1-5 of 5)- Popular Filters
Companies can't remove reviews or game the system. Here's why
March 25, 2022
Short review on Hyper-V
We use Hyper-V in our organization for Virtual servers with various roles and also for virtual clients for test applications.
Our scope of use case has two main cases first having virtual servers to update/upgrade servers easily/revert changes or bring servers back online from backups and also having virtual clients for testing new applications, group policy rules, and other organizational changes
Our scope of use case has two main cases first having virtual servers to update/upgrade servers easily/revert changes or bring servers back online from backups and also having virtual clients for testing new applications, group policy rules, and other organizational changes
- Editing configuration of virtual machines.
- Installing Windows operating system based VM client computer easier than rivals.
- Efficient resource use and management.
- Able to use usb drives for operating system installation without needing .iso file.
- Dedicated gpu virtualisation could be easier for VMs.
- The console interface could be improved and shows a small thumbnail of running machines.
- Based on windows OS environment.
- Easy to install and remove.
- Efficient resource management.
- Clean and easy user interface.
78%
7.8
- With Hyper-V implementing new software or rules on a test, beds take fewer resources and time which is a great bonus.
- Virtual SAN management and Virtual Switch management make it easy to manage network and storage options.
- Editing the disk option made us resize disks on the fly and saved us maintenance, production time, and costs.
VMware is the pioneer of virtualization but when you compare it with Hyper-V, VMware lacks the flexibility of hardware customization and configuration options Hyper-V has also GPU virtualization still not adequate for both platforms. VMware has better graphical interface and control options for virtual machines. Another advantage VMware has is it does not need a dedicated os GUI base installation only needs small resources and can easily install on any host.
- User interface.
- Virtual machine creation, management and resource allocation.
- Virtual Storage and Virtual Switch functions.
- GPU virtualisation.
No
March 23, 2022
Microsoft Hyper-v pluses and minuses
Hyper-V is used in our environment for test and development environments as well as VDI infrastructure and WDS image maintenance. Hyper-V is used as a lower-cost alternative to VMWare that can be installed and used on our existing Windows infrastructure. The infrastructure is used primarily by our development team.
- Lower cost
- Virtualization of Windows servers
- VDI infrastructure of Windows desktop
- Flexible
- Networking
- Managability
- Add-on tools
- lower TCO
- High availability
- relative ease of use.
70%
7.0
- Flexible, able to handle multiple workloads.
- It has compatibility with Windows.
- Cost of licensing the product in comparison to other alternatives.
- Setup is sometimes confusing and VMware knowledge does not always translate well.
Hyper-V performs very well in environment running windows operating systems and performs well under various workloads. The replication and recovery features of hyper-v work well but lack some of usability of tools such as Zerto, VMware replication and site Recovery Manager to perform tasks such as disaster recover testing. The user interface of hyper-v combined with Microsoft failover clustering can be very confusing and difficult to validate. this can cause unintended outages due to misconfigure items such as cluster-aware storage.
10
My current environment is used for testing of windows patching and other Windows specific items. Hyper-v is also used for creation and maintenance of WDS images for desktop deployment. My past employer used Hyper-v for production and near production environments with offsite replication and a 2 node cluster.
2
People who manage Hyper-v will need a wide array of knowledge in multipl IT areas such as storage, networking, virtualization, operating systems, Windows clustering, security principles and other Widows specific technology. so, the best person would be someone with a broad array of knowledge in multiple disciplines with a firm understanding of virtualization.
- pre-production testing
- need for "cheap" virtualization
- easy deployment
- management of WDS images
- offsite replication without 3rd party tools
- reduced TCO
- replacement of vmware in production to save cost
No
We evaluate several alternatives to hyper-v including MS virtual desktop, open source virtualization tools and VMWare
- Price
- Product Usability
- Prior Experience with the Product
Hyper-v was used in a test environment by my second employer and was selected primarily due to the cost of VMWare. We were able to use virtualization to spin up test environments or near production environments without the need to purchase very expensive VMWare liceses as used in production while maintaining most of the features and usability.
The main issue that I had was with learning how to enable features and to configure the environment with high availability enabled. I found that, where VMware is very intuitive via VCenter and clustering, the Hyper-v interface did not always perform in the way that it should. this ultimately resulted in an outage in that environment.
- Implemented in-house
No
Change management was minimal
Due to the learning curve of Hyper-v in a high availabilty environment, I discovered the importance of change management when performing tasks such as server migrations and failovers as opposed to how it is done in a VMWare environment. This was learned the hard way due to an outage caused by a failed server migration within the same cluster.
- configuring clusters
- outage due to misconfiguration
- convincing management
Our Support was through Microsoft Volume licensing and was running on Microsoft Windows Server Datacenter. This gave us premium support for the Windows feature set including Hyper-v.
No
NA
- Management interface
- VM Storage management
- Networking
- High Availability
- Disk resizing
- networking with multiple VLANs
May 11, 2019
Hyper-V
We chose Hyper-V to create our virtual infrastructure for our on premise servers. Our current hardware was at end of life and had the opportunity to upgrade to newer hardware and have enough space for more servers.
- Virtual Environment
- Scale-ability
- Ease of use
- None that I have noticed.
100%
10.0
- Hardware Costs
- Support Costs
- Future needs
Both products are similar but Hyper-V was included in our licensing with Microsoft.
3
Educational Technology
2
Virtual infrastructure and server operating systems, imaging and installation.
- Scalability
- Hardware Costs
- Licensing
- We use as designed
- We use as designed.
No
- Price
- Product Features
- Product Usability
- Product Reputation
- Existing Relationship with the Vendor
The price is very important, we have a volume license with Microsoft and Hyper-V is included.
None.
- Third-party professional services
SRS Technologies
No
Change management was minimal
- None
No
We had issues with the initial deployment and Microsoft support had experience with the issue before and was able to resolve quickly.
- creating a virtual machine
- adding different OS versions
- Updating virtual machine hardware requirements
- None
June 05, 2018
Enterprise Level Virtualization
We use Hyper-V (Windows Server 2016) to host our internal virtual server infrastructure. At the moment we use 4 Servers in a cluster to serve all our internal workloads. In addition, we consult our partners and customers in planning and implementation for Hyper-V as the virtualization platform. With Windows Server 2016 especially in combination with hyper-converged infrastructure with Storage Spaces Direct.
- fast and easy deployment
- clustering with live migration
- direct integration in the OS
- manageability (Windows Admin Center will solve this in future releases)
- monitoring of virtual machines performance
76%
7.6
- licensing physical server with Windows Server Datacenter also includes Windows Server licenses for virtual machines (unlimited)
We're a Microsoft Gold Partner and build solutions based on Windows Server. So it was for us internally not a real option to use another virtualization technology as Hyper-V to host our internal infrastructure. As most of our internal infrastructure servers are based on Microsoft Windows Server we stay also at virtualization level within the Microsoft Ecosystem.
- windows GUI Integration
- integration into Windows Admin Center
- full Powershell support for managing the infrastructure
- no wizard based selection of vCPU Cores
- no default monitoring overview for virtual machines (without Windows Admin Center)
No
April 13, 2016
Hyper-V Review by a Database Administrator/Developer
Hyper-V is used across R&D, IT, and support. Each department has their own Hyper-V server but can use VMs from another department's server if need be. We create Virtual Machines in Hyper-V for testing and quality control purposes and to recreate issues from clients in order to track down the proper fix for that issue. The business problem it addresses is having to recreate so many different environments for testing, quality assurance and support. We can test upgrades, patches, configuration setting, etc., with little overhead costs.
- Make creation of VMs simple with a wizard that will walk you through each step. A brand new user to Hyper-V should be able to open Hyper-V and create a VM in a matter of minutes. Creating and using the VM are different but creating the actual VM is simple.
- Taking snapshots of VMs is simple. Just choose the VM and choose to create a snapshot. The snapshots are easy to manage and are shown in a graphical 'tree' to show how they are related and what the order of their creation is.
- Changing VM setting and configurations are simple within Hyper-V settings. You can change everything from the amount of RAM to the size of the hard drive along with how many processors a VM is allocated from the Hyper-V host. You can also add network 'cards' and drives to mimic different RAID and networking setups.
- Migrating files from one Hyper-V host to another can be tricky if the VM has snapshots. In testing environments most VMs will have snapshots and it can be a headache to move a VM from one host to another.
- Export/Import process is a bit clunky. There are various options when exporting and Hyper-V doesn't do the best job describing them for new users. Once you have done this a few times it is easier but the first few times may be more difficult.
- Cloning VMs causes issues. This is more of an issue with Windows and the system ID that Windows has but cloning a VM is not as easy as just copying the files and pasting them in another folder. The VM setting will clone just fine but the VM hard drive (VHD or VHDX) could cause issues.
100%
10.0
- It allowed us to automate our VM creation process using PowerShell which cut our VM creation time down from 8+ hours to under 2 hours. This allowed us to respond to clients faster and get testing done in a much quicker manner.
- Negative impact was setting up and testing the VM creation automation process took multiple months. Part of this was because we developed a .NET interface that was used for VM data collection (name, HD size, RAM, etc) and creating and testing that application took time but getting the remote PowerShell command syntax correct and tested did take time.
I have never managed another virtual server environment so I cannot comment on how it compares.
5
Research and Development, IT, support. R&D deals with production systems, testing environments, and client environments for Issue resolution. IT utilizes Hyper-V for most of the shared drives for the company and also for specific short term needs of department members. Support uses Hyper-V to have multiple release levels of our software available at one time since our clients release level ranges over multiple releases and to properly assist and track client issues we need environments available immediately to test and reproduce their problems to troubleshoot and diagnose.
3
Database Administrators and IT Support. Database Administrators create and manage many of the VM's in the company for testing, QA, and client issue resolution. IT supports Hyper-V by supporting the physical machines in the server room and ensuring that they are performing optimally.
- QA environments at different release and version levels to test released and in-development software code.
- Shared drive locations across the company that can be backed up and snapshot at specific intervals to ensure proper record keeping.
- Client configured environments to help with Client defect tracking and resolution.
- To create a bank of test environments for testers to use and to easily create different snapshots at release levels to avoid needing 10+ physical machines to test in.
- To create on demand environments for all the various needs from clients, qa, testing, etc.
No
- Prior Experience with the Product
- Vendor Reputation
- Existing Relationship with the Vendor
- Positive Sales Experience with the Vendor
Aderant is a Gold partner with Microsoft and we use primarily all Microsoft products so this was a no brainer as it is consistent with their other software base and can be integrated using tools such as PowerShell.
We wouldn't since we are a Gold partner and we use Windows and many other Microsoft products. Having that consistency and integration possibility is of great value to us. Plus we already have the knowledge, skills and abilities to use Hyper-V and its' tools.
- Implemented in-house
No
Change management was minimal
We have been using Hyper-V for over 8 years now so there was very minimal change management. Also the team that manages Hyper-V is small and thus there isn't a large amount of people who are affected when we change versions/releases. The biggest part of Implementing a new release or version is to test a VM on it before mass migrating VM's to the new host. This is simple and Hyper-V contains export/import options to assist with moving VM's.
- There were no Hyper-V related issues. The only issue we had was reconnecting the secondary data drive to the server and configuring the RAID level on the machine.
- Online training
- In-person training
- Self-taught
Yes, it has a very intuitive graphical interface that allows a new user to immediately get down and dirty with making and managing a virtual environment. This is a good approach in my opinion as there are few things you can do in Hyper-V that would affect someone else since it is virtual and things can be rolled back or deleted without much consequence.
Don't use dynamic memory. You can end up in a black hole of sorts where the memory demands and supply get complex and you start having machines time out and shut down to save memory on the Hyper-V host. Some VM's also may not relinquish RAM the way they should depending on the OS that is on that VM so you can run into issues with RAM not being used by a VM that Hyper-V can't take back for other resources.
No - we have not done any customization to the interface
No - we have not done any custom code
We used some custom network connection setting to test certain client issues and we also utilized certain security features to replicate what client servers did or to test certain setting within on own software code. These were more VM based than the entire Hyper-V server though.
No
Our team had an issue with snapshots becoming corrupt and we were unable to delete the snapshots to make room on the server hard drive. This became an issue as we had to have larger and larger VM's to test certain client issues that had large databases on the VM's. We had to call support to find a way to get rid of these files because Hyper-V would tell us the file was in use and even after restarting Hyper-V server the file still said it was in use so we had to find certain actions in the Windows Server management tools to find the file locks and manually delete those locks and then manually delete the snapshot files. Then we had to restart the Hyper-V servers to be able to realize the space savings.
- Creating a VM using the Hyper-V wizards.
- Editing the settings and configuration of a VM
- Takings snapshots of VM's and managing the different levels is a simple 'tree' structure.
- Exporting and Importing VM's and their settings can be hard for new users.
- Cloning VM's can sometimes cause issues when starting either of the VM's (VM being cloned or that was cloned)
- Moving or migrating VM's from one VM host to another.
No
- PowerShell
- Command Prompt
- .NET
Fairly simple since Windows Server 2012 R2 has Powershell commands that are specifically for Hyper-V. .NET also has functionality to work with remote servers and send remote commands so you can put a GUI with the Hyper-V abilities.
- Team Foundation Server
- Visual Studio Test Manager
Not that I am aware of. I'm not sure how the integration would work with these as the purpose of the integration would be to automate testing of development software but deploying that software would be interesting.
I have not used any of these. The only ones I have integrated were other Microsoft products for managing Hyper-V and it's Virtual Machines.
If you have issues then use the Microsoft TechNet resource for previous users experience and knowledge. Also being familiar with PowerShell commands helps as you can manage Hyper-V solely from PowerShell if desired (this is actually required if you use the Windows Server 2012 R2 non-GUI install).
I was not present for this negotiation.
Ensure that your needs are stated in a complete manner so that you know what you are and aren't getting. Also find out about previous implementations and user experiences with similar organizations or implementations.
Yes
We upgraded from Windows Server 2008 R2 to Windows Server 2012 R2. The upgrade process was simple and straightforward and we just had to do the normal Windows upgrade and then go into the servers features and add the Hyper-V feature to access the Hyper-V management console. We then migrated our VM's to the host and began using the new Hyper-V features from Windows Server 2012 R2.
- Faster services. The new server version is faster and the wizards are just as easy to use.
- The ability to change certain settings and configurations using live VM's which kept us from having to shut down VM's causing down time to the organization.
- The ability to use PowerShell 4.0 to it's full extent in Server 2012 R2 which offers built-in Hyper-V commands which make managing VM's and Hyper-v much easier when you know the commands.
- Live migration of VM's from one host to another.
- Live cloning of VM's to be able to recreate a VM that is in production and can't be changed. This would add the ability to test changes without affecting a Production machine while ensuring that the setting and configuration variables are exactly the same.
No
No