Our scope of …
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
- 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%
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!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
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.
- 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.
- User interface.
- Virtual machine creation, management and resource allocation.
- Virtual Storage and Virtual Switch functions.
- GPU virtualisation.
- Ease of Use.
- Low Entry Cost.
- Quick Deployment.
- Improved backup system.
- Better central management.
- Ease of use.
- Speed of deployment.
- Low cost of licensing.
- Low/no cost makes ROI very attractive.
- The fact it already exists on most server installs means little to no downtime for deployment.
- Minimizes costs as upgrading RAM is much cheaper then additional servers.
- New System Deployment.
- Base Install.
- 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
- Virtualization of internal infrastructure
- Virtualizing Windows OS
- SQL Server hosting
- Hosting Linux web server farms
- licensing physical server with Windows Server Datacenter also includes Windows Server licenses for virtual machines (unlimited)
- 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)
- 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.
- 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.
- 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.
- Prior Experience with the Product
- Vendor Reputation
- Existing Relationship with the Vendor
- Positive Sales Experience with the Vendor
- Implemented in-house
- 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
- 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.
- Command Prompt
- Team Foundation Server
- Visual Studio Test Manager
- 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.