Hyper-V

Hyper-V is used to host on-premise servers, is hosting Windows servers and Linux servers.It provides an easy virtualization environment without having to spend money in licensing. It's rock solid, we had not experienced availability or performance problems.

Hyper-V is our production hypervisor, replacing VMware's ESXi which we ran for nearly a decade. We moved from ESXi to Hyper-V after support issues during a major incident. We also wanted to have closer integration with Microsoft Azure, our chosen Cloud platform. This has opened up the door to Azure Site Recovery to address potential Disaster Recovery scenarios.

Hyper-V was used to extend our ability to quickly prototype and build server infrastructure. We also were using it to develop 'golden images' or other troubleshooting techniques that allowed our organization to quickly deploy and investigate strange edge cases in our infrastructure It has been slightly superseded by our movement into Azure for the majority of our server infrastructure.

Hyper-V is a great technology that allows us to create virtual machines and helps us to maintain multiple operating systems on a single physical server. This technology allows us to reduce the cost and count of physical servers in the data center.

This is an easy system with intuitive capabilities for effective virtualization and great functions for multiple big data transportation across other platforms through Cloud services. The interface of Hyper-V is a clean and very accessible tool. Hyper-V deployment and the features configuration are easy and their performance on Cloud services is excellent.

Hyper-V comes with specific Microsoft licenses to our organization so we use it as a "freebie" which makes it more desirable in some cases than any other virtualization solution simply because we don't need to pay hefty Enterprise-grade licenses. We do use Hyper-V in a rather simplistic way - host servers and guest VMs on each one. However, for this purpose alone we are pretty satisfied with what we get. In a previous company, I was a part of the efforts for automated provisioning of VMs in Hyper-V and even though it required A LOT of reading semi-internal documentation and some in-depth posts, we got it running in a pretty stable state.

We run almost all our servers virtualized and Hyper-V was the best and most cost-effective option. Especially in an almost full Windows Environment.

Hyper-V is a very cost effective and useful hypervisor. Features like replication and live migration give Hyper-V great disaster recovery or replication options for small to medium size businesses without the need to purchase much more expensive solutions like VMware. Migration from physical servers to Hyper-V VMs is very easy using many off the self products from multiple vendors.

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.

We are utilizing Hyper-v for several reasons, from servers and virtualized servers and workstations within, and on some workstations as the host with a few other workstations virtualized inside them. We have two principal Hyper-V hosts and 1 Hyper-V Replica Host that we replicate all VM's to for failover/redundancy. What this has done for us is saved drastic amounts of storage by not having to back up several versions of virtual hard disks each time we make a change, but rather depend on the replica hyper-v host to store those checkpoints as we make changes. Now our storage facilities on the two principal host servers are drastically reduced and have saved a lot of money! The speed is insane also. Reboots are a minute as opposed to 10 minutes.

Hyper-V is currently deployed as an HA cluster hosting IT management and VDI VMs. Tools such as file servers, Bomgar, Zerto, Microsoft System Center 2019, etc. It addresses the need for the IT staff to have an HA cluster outside of our other virtualization stacks that run core business systems. We are also running a second Hyper-V cluster as the replication target for Zerto for our DR.

We have configured stand-alone Hyper-V servers and failover Hyper-V clusters. All of our servers are currently running under Hyper-V. From a cost perspective, all servers running windows under the Hyper-V node are free as long as you have a Windows datacenter license. This helps us keep costs down, and allows us to spin up new servers without additional licensing costs for the OS.

We're a small IT operation in the higher education industry. We use Hyper-V as our primary production-grade virtualization tool. While it may not be as feature-packed as other options, it does what we need. At the end of the day we're just trying to virtualize infrastructure, and do not even need fancy high availability tools or near-real time replication. Just run more servers on less physical hardware.

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.

Hyper-V is our bare-metal hypervisors. Anything that we run on-premise resides on a Hyper-V virtual machine. Our Hyper-V implementation is simple, with local storage on the servers and no failover clustering.

HyperV became the Virtualization choice to replace or migrate as many systems to a Virtual Environment. This decision spanned the entire company. The largest business problem it solved was the physical space and requirements needed to continue to use physical servers. It also addressed the increasing complexity of server management. High Density computing offers many advantage and can deliver a substantial cost savings when compared.

I currently use Hyper-V with two clients to virtualize a number of different functions. Specifically, I have VMs acting as domain controllers, Linux servers, and a QuickBooks server. Using Hyper-V to virtualize these machines allows for more easy management, especially if a restart is required, as that can be done remotely without worry of the machine not turning back on. In addition, the entire VM can be backed up and restored in the case of a catastrophic failure. Finally, using Hyper-V allows me to have multiple single purposes machines running on a single higher powered physical machine.

I use Hyper-V for my personal needs. I use it for the virtual environment of solving possible issues that can happen inside this virtual network. Such as DNS, IP conflict, sharing, and permissions. I had around 7 machines and one of them was a server machine. Hyper-V helps me to easily toggle between those machines and pinpoint the issue without any trouble.

We use Hyper-V across the entire organization. Everything that requires a server is virtualized, and Hyper-V makes it easy to configure a fault-tolerant cluster for a very low price. With replication, we also don’t worry as much about downtime or data loss.

Our customers use Hyper-V for scenarios where the cost associated with VMWare solutions is simply not advantageous. It is a simple to use hypervisor packed with enterprise functionality.

We began to make an entire conversion to Hyper-V over the last 2 years for our new DC and also our remote locations. The problem it was supposed to solve was the increasing cost of VMware.

We use Hyper-V at an enterprise level to create and maintain all of our virtual machines. Currently, most of this resides on an IBM Blade Center with four blades and about 12 VMs.

Hyper-V is being used as our hypervisor platform to support our disaster recovery/secondary data center operation. VMware runs our other data center. Hyper-V was implemented in DR to save licensing costs over VMware and also as a way for the bank to assess its capabilities in a slightly less critical operation. It has been a very successful project.

Our Hyper-V infrastructure was built to reduce the cost of licensing for SQL Server that we previously had with systems running VMware. We have both a Test/Dev infrastructure and a Production infrastructure. Each contains a number of host servers with multi-path connections to storage systems (EMC VNX for less critical systems, and SolidFire for critical systems. SQL Servers were transitioned from stand-alone systems to SQL farms. We have, and will, save close to $7M over a five year lifespan just on the SQL licensing. These Hyper-V systems are used across numerous business organizations in our company, with both internal - and external-facing applications.

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.