Install HyperV and Configure vSwitch on Windows Server with PowerShell
Microsoft’s hardware virtualisation product is Hyper-V. It enables the creation of a software version of a computer known as a virtual machine. Each virtual machine functions as a complete computer. In this article, we shall discuss how to Install HyperV and Configure vSwitch on Windows Server 2022 with PowerShell. Please see “vSwitches: How to delete Virtual Switches from Hyper-V“, Enable HyperV on Windows: How to install Windows 11 on HyperV, and How to run Windows 11 on HyperV.
With the whole VMware/Broadcom licensing concerns and the discontinuation of VMware vSphere Hypervisor (free edition) on the VMware website from Feb 12, 2024. You may want to see the employ HyperV in your lab or production environment.
Virtual machines provide greater flexibility, time and cost savings, and a more efficient utilisation of hardware when computing resources are required, compared to merely operating one system on physical hardware. These VMs runs in its own isolated space, which means you can run more than one virtual machine on the same hardware at the same time.
Note: Here is a guide if you would like to install HyperV on Windows Server 2019, 2022, or 2025 via the Roles and Features. The below steps are applicable to the following Windows Server 2019, 2022, or 2025 Editions.
Install HyperV via PowerShell
Fire up PowerShell as an Administrator (Elevated rights).
Use the command below to install Hyper-V with automatic restart
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart
I have removed the “-Restart” just to be able to show you the screenshot of the process. You will be requested to restart your server now if you also did not include the switch.
You can also accomplish this via the DISM command as shown below.
dism /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V /AllConfigure Hyper-V Virtual Switch
Creating the external, internal and private virtual switches is essential to establishing comprehensive networking configurations within Hyper-V. These virtual switches operate in distinct modes, each serving specific purposes.
Here is a guide on “Hyper-V Server Core Mode: How to install free Hyper-V Server on a VMware Workstation“. and how to create an Amazon Relational Database Service Instance.
Create External vSwitch
External Virtual Switch: Hyper-V virtual switch in external mode allows communications between virtual adapters connected to virtual machines and the management operating system.
It uses single or teamed physical adapters to connect to a physical switch, thereby allowing communications with other systems. To initiate this process, open Hyper-V Manager.
Navigate to the Virtual Switch Manager
Choose the type of virtual switch, then select Create Virtual Switch
Enter a name for the virtual switch. Since this is an External vSwitch, select the network adapter (NIC) that you want to use, then select OK.
You will receive a warning indicating that proceeding with the change may interrupt your network connectivity. If you are comfortable with this potential disruption, please select “Yes” to continue.
To do this via PowerShell, run the following command below to determine your existing network adapters by running the Get-NetAdapter cmdlet. Identify the network adapter name that you want to use for the virtual switch.
Get-NetAdapterTo create an external virtual switch, run the following commands, replacing the placeholder with your own values.
New-VMSwitch -Name <switch-name> -NetAdapterName <netadapter-name>Create Internal vSwitch
A Hyper-V virtual switch in internal mode allows communications only between virtual adapters connected to virtual machines and the management operating system.
From the HyperV Virtual Switch Manager, select Internally and click “Create Virtual Switch”.
Enter the Virtual Switch name and ensure the internal network is selected and click Ok to complete the process.
To create an internal vSwitch with PowerShell, run the following command. Replace <switch-name> with the name of your switch and <switchtype> with the Internal
New-VMSwitch -Name <switch-name> -SwitchType <switchtype>New-VMSwitch -Name "Internal vSwitch" -SwitchType InternalCreate Private vSwitch
A Hyper-V virtual switch in private mode allows communications only between virtual adapters connected to virtual machines.
From the Virtual Switch Manager, select Private and click on “Create Virtual Switch”.
Enter the Private Virtual Switch Name and ensure the private network is selected and click ok.
To create an Private vSwitch with PowerShell, run the following command. Replace <switch-name> with the name of your switch and <switchtype> with the Private.
New-VMSwitch -Name <switch-name> -SwitchType <switchtype>New-VMSwitch -Name "Private vSwitch" -SwitchType PrivateFAQs on HyperV and vSwitch Creation
Is it possible to create a vSwitch without disrupting existing VMs?
You can create a vSwitch without disrupting existing VMs. However, if you are modifying the network configuration of existing VMs, such as connecting them to a new vSwitch, there may be a temporary disruption during the reconfiguration.
How can I troubleshoot vSwitch connectivity issues?
Common troubleshooting steps include checking the vSwitch configuration, ensuring the correct network adapter is selected, verifying VLAN settings, and inspecting the network configurations within the VMs themselves. Additionally, check for any issues with the physical network.
Can I add multiple vSwitches to a Hyper-V host?
You can add multiple vSwitches to a Hyper-V host. This allows you to segment and control network traffic between different VMs and external networks.
I hope you found this article useful on how to install HyperV and Configure vSwitch on Windows Server 2022 with PowerShell. Please feel free to leave a comment below.
