Create a VLAN with Hyper-V

For Windows 11 Servers such as the RX III/ EX 2C/ VX 3

With Intel PROSet and Advanced Network Services (ANS) no longer supported on Windows 11, managing VLANs and network redundancy requires new workflows. This guide shows how to configure basic VLANs on Disguise media servers using Hyper-V and PowerShell.

Install Hyper-V

1. Open Windows Features:
   • Press Win + S, type Windows Features, and select Turn Windows features on or off.
2. Enable Hyper-V:
   • Check:
     • Hyper-V Management Tools → Hyper-V Module for Windows PowerShell
     • Hyper-V Platform → Hyper-V Hypervisor
3. Click OK and restart if prompted.

---

Identify Network Adaptors

To configure VLANs, you first need to identify the available network adapters.

1. Open PowerShell as Administrator.
2. Run the following command:

   GET-NETIPCONFIGURATION

   This will list all network adapters and# their details.

Example Output:

InterfaceAlias  : Ethernet 1
InterfaceIndex  : 4
IPAddress       : 192.168.1.100
...

Create a Virtual Switch

Create a virtual switch in Hyper-V to route traffic through a specific network adapter.

1. Run the following command in PowerShell:

   New-VMSwitch "disguise" -AllowManagementOS $true

   • Replace "disguise" with your desired switch name.
   • The -AllowManagementOS $true flag allows Windows to communicate through this switch.

2. When prompted, enter the name of the network adapter you identified in Step 1 (e.g., Ethernet 1).

Note

Do not attempt to assign multiple adapters to the switch. This can cause the setup to fail after a reboot.

Add a VLAN to the Virtual Switch

Now, create a VLAN on the newly created virtual switch.

1. Use this command:

   Add-VMNetworkAdapter -ManagementOS -Name VLAN1-D3NET -SwitchName "disguise"

   • Replace VLAN1-D3NET with the desired VLAN name.
   • Replace "disguise" with the name of the virtual switch you created.

Hyper V Limitations and Considerations

• No NIC Teaming: Windows 11 does not support NIC teaming, so redundancy for network port failure is not included.
• Single Adapter: Configure VLANs on only one adapter per virtual switch for stability.
• Redundancy Options: Consider using hardware redundancy with stacked switches.

By following this guide, you can successfully configure VLANs on a Disguise server using Windows 11.

Troubleshooting: How to Prevent Hyper-V from Reserving Specific Ports

When Hyper-V is enabled on a Windows machine, it automatically reserves multiple port ranges within the dynamic port range upon startup. This can cause conflicts if Windows happens to reserve a port required by another application—such as port 56565, the default PSN port needed for a d3 project.

Prerequisites

• You must be logged in as an Administrator.
• Important: Disabling and re-enabling Hyper-V usually requires a system restart. Please save any open work before proceeding.

How to exclude ports

1. Open PowerShell as an Administrator. Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin).
2. Check currently reserved ports. Run the following command to see which UDP ports are already reserved: netsh interface ipv4 show excludedportrange protocol=udp
3. Temporarily disable Hyper-V. Run the command below to disable the hypervisor. (Note: You may be prompted to restart your computer here. If so, restart, then reopen PowerShell as Administrator to continue). Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
4. Exclude your required port. Run the following command to exclude your port. netsh int ipv4 add excludedportrange protocol=udp startport=<port> numberofports=<number> store=persistent
5. Re-enable Hyper-V. Once the port is successfully excluded, turn the hypervisor back on: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
6. Restart your machine. If you aren’t automatically prompted to do so, restart your computer one final time to ensure Hyper-V is fully active and the new port rules have taken effect.

Note

In this example, we are setting startport=56565 and numberofports=1 to exclude exactly one port. Change these values if you need a different port or a wider range).

Tip

Once your computer has restarted, open PowerShell as an Administrator again and run the check command: netsh interface ipv4 show excludedportrange protocol=udp

Look for your port (e.g., 56565) in the list. It should appear with an asterisk (*) next to it, which indicates that it is a manually added, persistent exclusion.