Sharing physical resources is the primary purpose of virtualization. in Hyper-V we assign physical resources like; CPU, RAM, and disk space for every Virtual Machine at the time of configuration. But other resources like External disks, USB flash drives, and other plug play are configured when needed. In this article, I explain how to share host resources with the virtual machine in Hyper-V.

In Hyper-V, even if you want to copy a file from the USB flash drive to your virtual machine, you have to go a long way: You must create a virtual switch, connect your host and virtual machine to the same virtual switch, and give your virtual machine access to your USB flash drive. I will go through this process step by step in this article.

Create Virtual Switch in Hyper-V

When you create a Virtual Switch in Hyper-V, you will see three types of virtual switches. Each of these switch types has its advantages, so you have to choose the right type of Switch.

External Switch

External Switch provides a connection between virtual machines, hosts, and the physical network. It means that your virtual machine can connect to the internet as well. When you connect your virtual machine to an external switch, your virtual machine will be accessible by the host, physical network and the internet.

Internal Switch

You can use an Internal switch to separate your host network from your virtual network. Your virtual machines can communicate with each other and with the host, using an internal switch. But can not communicate with the physical network.

Private Switch

Virtual machines connected to a private switch can communicate with each other, but can not communicate with the host or physical network.

Now that you have understood virtual switch types follow the steps below to create a virtual switch.

1. Open Hyper-V Manager and click on Virtual Switch Manager.

2. Click on the New virtual network switch and select External, Internal or Private, then click on Create Virtual Switch. To share local resources with a virtual machine in Hyper-V, you must create an external switch or internal Switch because just external and internal switches provide the connection with the host. A Private Switch doesn’t provide the connection between virtual machines and the host machine.

3. Name your virtual Switch; you can see it as you type the name. Choose the Internal network connection type for your virtual Switch, then press OK.

Now that you have created a virtual switch make sure that it has been created appropriately by clicking on Virtual Switch Manager in Hyper-V Manager. You can change your switch type easily from Virtual Switch Manager. Now let’s connect the virtual machine to the virtual Switch.

Check out if you want to know how to create a virtual switch by using Windows PowerShell.

Connect Virtual Machine to Virtual Switch

Both the host and the virtual machine must be connected to the same virtual Switch in order to share your host resources with the virtual machine. When you create an external or internal switch in Hyper-V, your host connects automatically to that Switch, but your virtual machine doesn’t. You have to connect your virtual machine to the virtual switch manually. I explain how to connect the virtual machine to the virtual switch step by step.

1. Open Hyper-V Manager, right-click on the name of your virtual machine and click on Settings. Or, if your virtual machine is running, maximize your virtual machine window and click on the File and click on settings.

2. Click on Add Hardware, select Network Adapter and click on Add.

3. Select the virtual Switch from the list and click OK. You can also remove any virtual switch that is not needed by selecting that virtual Switch and clicking on Remove.

4. Before you go to share local resources in Hyper-V, make sure that your host is connected to your virtual Switch. Open Control Panel, click on Network and Internet, and then click on Network and Sharing Center.

When creating a virtual switch, make sure it is the right type of Switch that you need. If you want to connect your virtual machine to the internet, create an external switch, and if you’re going to separate your virtual network from the host network, then create a Private Switch.

Configure to Share Host’s Local Resources With Virtual Machine

You can share; printers, clipboards, external hard disks, internal disk drives, USB flash drives, and other plug and play devices from the Local Resources. In Hyper-V, if you want to copy a file into your virtual machine, it doesn’t provide you with the copy and paste option from the host to the virtual machine, so you have to share it via file-sharing or share the disk or USB itself. Follow the steps below to configure resource sharing.

1. Right-click on the Virtual Machine name and click on Connect. The following screen appears, then click on Show Options.

2. Click on Local resources to see local devices, check the devices you want to share with the virtual machine, and then click on Connect. If the resource you want to share is not in the list, click on More.

3. The following screen appears, select your resource from that list and click OK. I want to share Local drive C and a USB Pendrive which is plugged into my computer.

4. After your virtual machine is connected, log in with a username and password. Check the File Explorer, drive and devices you shared before will appear under Redirected drives and folders.

Sharing local resources look complicated, but it gets easier when you understand the process well. If you create the correct type of switch, connect your host and virtual machine to the virtual switch properly, so you will not find issues to share local resources with the virtual machine in Hyper-V.

Check out this article to know more about the installation of Hyper-V on Windows 11 and Windows Server 2022.

Check out this article if you want to know How To Connect Hyper-V Machines To Internet?

The post How to Share Host resources with Virtual Machine in Hyper-V appeared first on TECHNIG.

To restore to the previous configuration, you have to create virtual machine checkpoints in Hyper-V. You often make some changes to your virtual machine, but that change doesn’t go well, and you want to restore it to the previous configuration.

Checkpoint Types

We have two types of checkpoints in Hyper-V: standard checkpoints and production checkpoints. The production checkpoint is more stable than the standard checkpoint.

Standard Checkpoints: capture the virtual machine and everything running in virtual machine memory. Formerly it was known as snapshots before windows 10.

Production Checkpoint: saves the virtual machine state but does not save the information about the running application.

Configure Checkpoints in Hyper-V

Follow the steps below to create virtual machine checkpoints in Hyper-V

1. Right-click on the virtual machine name and click on Checkpoint, or select your virtual machine and click on Checkpoint at the right column in Hyper-V Manager. When you click on Checkpoint by default, it creates a standard checkpoint, but you can configure it to create a production checkpoint.

To configure checkpoint settings, open Hyper-V Manager, click on Action, then settings. The screen below appears. Click on Checkpoints in the left menu, check Enable checkpoints and click on Production checkpoints.

Once your checkpoint is created, select your checkpoint and click on Apply.

This screen appears. I suggest clicking on Create Checkpoint and Apply because it creates a checkpoint on the current state of your virtual machines and then applies the previous checkpoint.

A checkpoint is a valuable tool in Hyper-V. It helps try the different applications, settings, and configurations without damaging your machine.

To know more about checkpoints, click here.

You may also like How to connect the virtual machine to the internet?

The post How to Create Virtual Machine Checkpoints in Hyper-V appeared first on TECHNIG.

The error of “User account does not have permission to open attachment” in Hyper-V Server can occur when you try to use an ISO located on a network drive as a boot drive for a VM. A workaround is to copy the ISOs on the host machine directly but that’s inconvenient and tedious. Follow these steps to fix the permissions and allow Hyper-V to use images through SMB.

User Account Does Not Have Permission

We can fix the user account that does not have permission to open an attachment in Hyper-v with two stages. The first one granting the Hyper-V server access to the network shared folder and the second stage enabling CIFS delegation on the Hyper-V machine.

To fix this issue you must have an AD domain account to grant the Hyper-V host access to the network share.

1. Grant the Hyper-V Machine Access to the Network Shared File.

1. Right-click the network shared folder and open the properties then click Edit under the Security tab.
2. Click Add in the new window then click on Object Types and tick the checkbox next to Computers and then press OK to apply the changes.

3. Now, type the name of the Hyper-V machine which you want to authorize on the shared folder and then press Check Names to validate. After validating the name just click the OK button to add it.

Note: If you do not tick the checkbox of Computers on Object Types the system will not find your Hyper-V machine. Make sure you’ve ticked the Computer checkbox and also your machine should be joined to the domain.

4. Click OK to close all the opened file sharing permissions windows to complete the first stage successfully.

2. Enable CIFS Delegation on the Hyper-V Machine

The CIFS delegation gives service administrators the ability to specify and enforce application trust boundaries by limiting the scope where application services can act on a user’s behalf. Service administrators can configure which front-end service accounts can delegate to their back-end services.

On your AD domain controller complete the following steps.

1. Open the Server Manager then click Active Directory Users and Computers from Tools menu. Or type the dsa.msc on Windows Run to open Active Directory Users and Computers only using shortcut.
2. Expand domain, and then expand the Computers folder.
3. In the right pane, right-click the Hyper-V Machine name, and then click Properties.
4. On the Delegation tab, select Trust this computer for delegation to specified services only and Use any authentication protocol.
5. Click Add to open the Add Services dialog window.

6. Select the Users or Computers on Add Services window, and type the computer name where the network shared folder is located then validate it by clicking on Check Name and click OK.

7. Select the CIFS service for the file-sharing server and click OK to enable CIFS delegation on the Hyper-V Server.

8. Finally, click OK to close all opened windows. Now you can install operating systems on your Hyper-V server virtual machines via network shared files.

Perfect, we’ve done!

The post Fix User Account Does Not Have Permission to Open Attachment in Hyper-V appeared first on TECHNIG.

You can enable Hyper-V to create virtual machines on Windows 10 without downloading any extra Hyper-v software. Hyper-V can be enabled in many ways including using the Windows 10 control panel, PowerShell (my favourite) or using the Deployment Imaging Servicing and Management tool (DISM). But here you can free download Hyper-v Server 2016 iso file for installing Hyper-v server directly on a physical server and creating a network and server virtualization environment.

Related Article: Enable and Configure Hyper-v in Windows 10

Differences between Hyper-V on Windows and Hyper-V on Windows Server

There are some features that work differently in Hyper-V on Windows than they do in Hyper-V running on Windows Server.

Hyper-V features only available on Windows Server:

• Virtualizing GPUs using RemoteFX
• Live migration of virtual machines from one host to another
• Hyper-V Replica
• Virtual Fiber Channel
• SR-IOV networking
• Shared.VHDX

Hyper-V features only available on Windows 10:

• Quick Create and the VM Gallery
• Default network (NAT switch)

The memory management model is different for Hyper-V on Windows. On a server, Hyper-V memory is managed with the assumption that only the virtual machines are running on the server. In Hyper-V on Windows, memory is managed with the expectation that most client machines are running software on host in addition to running virtual machines.

Limitations

Programs that depend on specific hardware will not work well in a virtual machine. For example, games or applications that require processing with GPUs might not work well. Also, applications relying on sub-10ms timers such as live music mixing applications or high precision times could have issues running in a virtual machine.

In addition, if you have Hyper-V enabled, those latency-sensitive, high-precision applications may also have issues running in the host. This is because with virtualization enabled, the host OS also runs on top of the Hyper-V virtualization layer, just as guest operating systems do. However, unlike guests, the host OS is special in that it has direct access to all the hardware, which means that applications with special hardware requirements can still run without issues in the host OS.

Free Download Hyper-v Server 2016 ISO File

Microsoft Hyper-V Server is a free product that delivers enterprise-class virtualization for your datacenter and hybrid cloud. Microsoft Hyper-V Server 2016 provides new and enhanced features that can help you deliver the scale and performance needs of your mission-critical workloads.

Microsoft Hyper-V, codenamed Viridian and formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems running Windows. Starting with Windows 8, Hyper-V superseded Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks.

Hyper-V was first released alongside Windows Server 2008, and has been available without additional charge for all the Windows Server and Windows 8 and later. A standalone Windows Hyper-V Server is free, but with a command line interface only.

The Windows hypervisor technology in Microsoft Hyper-V Server 2016 is the same as what’s in the Microsoft Hyper-V role on Windows Server 2016. It is a stand-alone product that contains only the Windows hypervisor, a Windows Server driver model, and virtualization components. It provides a simple and reliable virtualization solution to help you improve your server utilization and reduce costs.

Editions: Microsoft Hyper-V Server 2016 | 64-bit ISO

For more to learn virtualization technology, read the virtualization section articels and check the online Windows Serve virtual lab.

The post Free Download Hyper-V Server 2016 ISO File for Server Virtualization appeared first on TECHNIG.