We use Hyper-V for our on-premise servers, and we have a couple of Hyper-V desktops that remote salespeople use to log in remotely. They have an on-premises station they can remote into and utilize everything at our other office. We replicate everything there, so if anything happens to our facility here, we can get spun up at our other location.

There are 40 people in our organization. We have sales engineers, technicians, and our standard office staff. Three servers are running off of Hyper-V, including our SQL server for our main CRM and QuickBooks databases, our central files storage server, and another files server that holds our backup domain controller. Then we have another domain controller that handles some other internal things. That is pretty much our organization in a nutshell.

We plan to expand usage of Hyper-V. For example, we have a terminal server that isn't on Hyper-V at the moment. It is session based, and we're working on transitioning over. Also, we got a brand new server two weeks ago, so we're transitioning everybody off of the terminal server to local Windows 10 and Hyper-V VMs. 

Everyone will have their own desktop environment versus having a session-based terminal. That way, if there's an emergency patch update or something like that for one person on the terminal server, we don't have to take the whole terminal server down. We can take down that person's desktop. We'll deploy as many as 12 additional Hyper-V desktops running in that. 

That will be our future deployment based on what we've seen in the Hyper-V desktop environment and its performance. It runs great. All users who have already transitioned to that environment are enjoying it compared to the old terminal server that we had.

We use the tool for virtualization. We have virtual servers so that we do not have to have individual servers for every service. We use it to create mirrors of the primary server. We can deploy a number of services on one server.

In our environment, we have a special custom configuration for the Hyper-V switches we use. We have a full-scope VM in our environment and especially for certain Cisco configurations, such as the spam folder in the Hyper-V. It is really difficult to configure from scratch. In this scenario, the agent is really helpful for us, for the restoration. The community edition provides a free, low-cost package solution.

I use the solution in my company for hosting the database in SQL Server, which acts as our company's distributor for SQL-based applications.

Hyper-V is utilized across various resources. For example, Azure utilizes Hyper-V as its hypervisor in the backend, so essentially, Azure's cloud services run on Hyper-V. Thus, Hyper-V plays a crucial role in cloud computing environments.

We use the solution to virtualize workflows on physical hosts for various use cases, such as hosting applications and databases. The hosts run Windows OS, with some running Windows Server OS at the endpoint, which allows them to host different workloads, including applications, databases, remote desktops, and other systems. Additionally, we leverage Hyper-V for infrastructure maintenance services, wireless services, and OEM-provided production images. This flexibility lets us choose between buying physical boxes from OEMs or virtualizing their images for our infrastructure.

My company needs the product for the virtual machines in our environment. The product is also useful in areas like domain controller and Active Directory.

We're using the mail correspondence and other applications which are running using Hyper-V.

Currently, we use the Windows Server 2022 Hyper-V server.

We started the virtualization and provide two virtualized environments or operating system environments in the Windows Server itself. We run in the virtualized environment under one single Windows Server license. We started our virtualization from one site on Hyper-V.

I have one host, and I need to run several servers. I created an Active Directory server on it for access and upgrades.

Mainly, I use Hyper-V to analyze whether it fits the customer's needs as a solutions architect. First, we determine whether the customer is a Microsoft user. Then, we consider pricing and compare it against the features of VMware or AHV to determine which solution would be most helpful.

We are an IT service company. We understand the technology and we provide Microsoft solutions, Linux, and Cisco solutions. We have a 360-degree relationship with Microsoft, Cisco, and two other companies. We are a premium partner with Microsoft. We use Hyper-V for virtualization and the consolidation of infrastructures. It is a cost-saving solution. We currently use 25% physical, and 75% virtual resources via Hyper-V, i.e. a ratio of 2.5 to 7.5. So we are using the virtual aspect to a greater extent.

The primary use case involves the creation and management of virtual machines. Within this framework, various types of virtual machines can be established, ranging from Windows-based systems to those dedicated to specific applications such as SQL servers.

This solution is mostly being used to deliver flexibility, high availability, and redundancy to accommodate production demand on an as-needed basis.

The main driver is consolidation, which is then complemented with the above-mentioned items. Hyper-V is a cost-effective platform that helped many companies I've been involved with to reduce data center administration and licensing costs drastically.

Once the platform is in place, it helps to control resources more accurately and on a consumption basis. By using the VMM (Virtual Machine Manager) you have full control of the fabric, workloads, templates and many more resources. Running Hyper-V Core also increases security and reduces update time-frames, which also helped us to increase our uptime and overall service delivery expectations. 

I'm mostly implementing Hyper-V solutions. Most of my clients are implementing Hyper-V on-premises, and on cloud my clients are using Microsoft Azure.

I am a Microsoft architect. I'm certified in Microsoft. My company is located in Cameroon and many countries in Africa and out of Africa. In my company we are working on Microsoft solutions at 80% on Windows Server, SQL, Exchange, Microsoft for Business, ISO. We are training with these solutions and implementing them.

We use this product primarily for virtualization.

In our company, we develop software internally, and many of our development systems are virtual systems hosted on Hyper-V. Additionally, we have virtual machines for office automation systems such as Exchange Server and Rack Server, which are also hosted on Hyper-V.

We are partners with Microsoft. We install 50% of VMware and 50% the solution from Hyper-V, depending on the customer's request.

Mid-level businesses who want to create their own data center, and they are using other Microsoft systems. 

We use Hyper-V to test multiple virtual machines and servers to be deployed.

I use Hyper-V for virtualization.

We have a project for disaster recovery. We are using an arc server. We have to use the basic server, each biometric server, in the virtualization environment. In the virtualization environment, we are using Hyper-V. In the software, in the arc server, they get the image from the metal and put it into the Hyper-V environment.

We are mainly using Hyper-V for VMs. The primary business is biscuit manufacturing, so we have 70 different types of sales-related software, some Windows-based SAP, and VMs running on Hyper-V. All VMs are running on Hyper-V. So indirectly, everyone is using it because it's our primary production system. We have maybe 650 employees at the moment. About 200 of these are computer users who are connected with Hyper-V in one way or another. Either they are using some of its services in a virtual machine or they're the IT guys directly involved with it. The non-IT people are using finance software or SAP-related software that they access through the web. Some servers are standalone Hyper-V, and there are two clusters of Hyper-V.

I primarily use the solution for consolidation, and I try to do replication using the last version. However, I need some time to do this configuration.

We basically use it to virtualize a service for email on-premise. We also use it to virtualize the apps, but it is mainly for virtualizing servers, such as SQL Server, Exchange Server, SharePoint, and CRM.

We use Hyper-V for virtualization. 

The solution is used as a hosting database. 

I use the Hyper-V for migration for the machines. We move our systems to Hyper-V and then from physical to virtual. I currently run on the physical server. I'm migrating this server from the physical to the Hyper-V virtual machine.

The solution serves our needs as an education entity in the UAE.

I use the solution for Jira visualization and Jira workload.

We use Hyper-V for test virtualization.

I work in an environment where we are required to use them, as well as for DevOps and a few other things like Helios and similar things. As a result, I use it for DevOps testing, infrastructure, and implementation within the product areas of my clients.

Hyper-V is used to virtualize machines. You install the latest version of Microsoft Windows Server on your hardware, and you install Hyper-V in the Microsoft Windows Server. You can now install multiple virtual servers within Hyper-V. They all can have different functionality.

The servers can be used for many things, such as file servers, ERPs, and web servers. All of this was not available before the advent of virtualization. With virtualization it's easy with one hardware machine, you can have several servers.

We usually use Microsoft Hyper-V for very small customers that don't have the budget for another library or hypervisor. We use Hyper-V when the customer has only one or two virtual machines. It's typically bundled with the Windows Server operating system, so we can provide virtual machines for free. 

In Malaysia, we started the cloud journey in 2020. Most people were looking for services, and many customers wanted to migrate to the cloud immediately. They just look forward and make some comparisons. If you say, "I want to migrate to a cloud," typically, our customers will ask for AWS as a primary choice, followed by Microsoft Azure.

Two main x3650M3 servers with 192GB and 96GB RAM. Primary case was Active Directory infrastructure (actually three DC's), file repository, main MS SQL Server and couple of applications servers.

Additionally remote access thru Desktop Services, management (nVision), central AV (ESET), software routers. In short - whole bunch of different servers and different operating systems Windows Server and desktop, different flavours of Linux, even FreeBSD).

We mostly use Microsoft Hyper-V in our production environment.

The solution is server virtualization software. We're using it to create virtual servers on our hosts and assign roles to each server separately. That's basically what a virtualization server does.

I am a solution provider and Hyper-V is one of the products that I implement for my customers.

We were using Hyper-V as a part of our ERP system, proxy servers, and some very minimalistic workstations.

We use Hyper-V for data center virtualization. We initially set up 54 servers and three SANs.

Hyper-V is a virtualization layer. We use it for all of our applications.

We supply Hyper-V for hardware virtualization to customers.

We primarily use the product for multiple servers and for Dynamics AX, for example, the routing server, the load balancer, the application server, and stuff like that.

We primarily use this solution as a hypervisor.

My primary use case is for virtualization of all solutions from physical servers into other solutions for ease of management. 

I use it personally for training. I do some testing for myself. I use it for virtualization and have used it to compare testing functionality. 

We use Hyper-V for data center virtualization.

I use this solution for some of my virtual machines.

We use this solution to provide visualization for our two main server clusters; one that hosts most of our production virtual machines, and another that hosts Active Directory and the Exchange platforms.

I have been making solutions around the Hyper-V bundles for my clients. For example, hyper-converged infrastructure, such as in vSAN and Vsphere for company data centers.

Our organization is a financial institution in the banking industry. We use Hyper-V for network virtualization and storage and application virtualization. There are five or six users of the solution.

The primary use case is for customers who want to virtualize their infrastructure, but are on a budget and don't need advanced features. 

We use it for anything like production and everything we're running on right now.

We use Hyper-V for production, testing, and development.

It's a core infrastructure solution, so it's not a user-solution. It's for server virtualization. It's actually deployed virtually for other services that need to deploy virtual machines using it.

We plan to keep using this solution in the future.

We run the majority of our production servers from our Hyper-V 2012 R2 Cluster. 

The primary use case is for testing software.

We use the Hypervisor and manage the VMs. We then get a 360 degree view of the infrastructure, hardware, networking, storage, VMs, and more.

We use Hyper-V for virtualization.

We use this solution to host our corporate infrastructure servers. 

My primary use case of this solution is to increase memory for the virtual machine which can be easily done on Hyper-V.

We use Hyper-V for system virtualization.

We are currently using this solution for Exchange, as a demo controller and an antivirus, as well. We have lots of servers on our Hyper-V.

Our primary use of this solution is for production of our office business needs.

Hyper-V acts as the hypervisor for our virtualization platform. We are using it on a three-tier infrastructure and it manages our VMs that store our files and applications. 

We are using Hyper-V to host a few Linux virtual machines.

I build servers using this solution.

Our primary use case is for a UAT environment, for test purposes. We are users and I'm the COO. 

My primary use case of this solution is for virtualization.

We provide services, such as virtualization, website hosting, and some infrastructure services. We provide all the services to the public companies.

In our administration, we don't have new computers or new servers, but we want to optimize our scientific work. We're using it with two devices for scientific work and administration work.

Our primary use case of this solution is for implementing the private cloud over the system center.

We use Hyper-V for managing our virtual infrastructure.

We have installed a domain controller in Hyper-V, also managing arbitrator for SimpliVity.  We are using it for HPE SimpliVity.           

We had deployed multiple Hyper-V clusters for various projects and even have the confidence to run it for highly critical production loads.

We are mainly using Hyper-V in the financial sector.

We are just exploring the possibilities to see if it was a better alternative to VirtualBox, for running on a Windows host.

We can illustrate all of the infrastructure very easily.

I primarily use it for server virtualization and protection services.

The features I find most valuable are utilizing the hardware so there is multiple applications running on one hypervisor. This actually saves money for the user. 

This is the primary hypervisor in my organization. It runs our most critical workloads and supports all our branch offices.

The reason we use this solution is because we can do a lot more with rate configurations, and large span networks. It's a lot easier doing that versus with some of the KVM based hypervisors.

We use Hyper-V for hardware virtualization.

Providing development and test environments for risk management applications. A variety of standard images were created and could be applied as needed.

It is a consolidation of Microsoft services that we have on premise.