So you are basically making the physical ports on the host machines to be VLAN-aware or similar as a trunk port, right? That way all traffic (tagged or untagged) can traverse through one physical interface, right?
In most "regular" cases, the port on switch should be set as "access port", then VLAN is transparent to the OS, so this video does not apply. However, if in the OS, you need to run a server to provide services to multiple VLANs, the switch port should be set as "trunk port", then you need to setup VLAN interfaces for the OS.
Windows Server 2022/2025 prefers something called SET (Switch Embedded Teaming) and not the Teaming as presented in the built-in Server Manager UI. SET does not have a UI, except via WAC (sorry, Windows Admin Center). Finally my question: can you also create VLANS using SET and WAC? If so can you please make a video, reason being on Windows Server Hyper-V they 'really' push SET over Teaming. Thx for your videos, super useful.
Yep, the NIC teaming way in the video does not work for hyper-v in windows 2022. But as I know the way shown in windows 11 also works for windows 2022. Please correct me if I am wrong. When it comes to WAC, sorry I am not familiar with Windows admin so may not be the best person to have a video about it.
Thanks again for another informative and detailed networking video. Always plenty to learn from your channel. 🎉
Perfect! Thanks
So you are basically making the physical ports on the host machines to be VLAN-aware or similar as a trunk port, right? That way all traffic (tagged or untagged) can traverse through one physical interface, right?
Yes
Is it better to have the VLAN set on the device or using the switch?
In most "regular" cases, the port on switch should be set as "access port", then VLAN is transparent to the OS, so this video does not apply.
However, if in the OS, you need to run a server to provide services to multiple VLANs, the switch port should be set as "trunk port", then you need to setup VLAN interfaces for the OS.
@ thanks! Love the videos by the way, they’re really bridging the gap between basic and advanced networking knowledge.
Windows Server 2022/2025 prefers something called SET (Switch Embedded Teaming) and not the Teaming as presented in the built-in Server Manager UI. SET does not have a UI, except via WAC (sorry, Windows Admin Center). Finally my question: can you also create VLANS using SET and WAC? If so can you please make a video, reason being on Windows Server Hyper-V they 'really' push SET over Teaming. Thx for your videos, super useful.
Yep, the NIC teaming way in the video does not work for hyper-v in windows 2022. But as I know the way shown in windows 11 also works for windows 2022. Please correct me if I am wrong.
When it comes to WAC, sorry I am not familiar with Windows admin so may not be the best person to have a video about it.