Study guide
7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET)
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET)
Key Takeaways Explain This Topic AI
Hyper-V Virtual Switches operate at Layer 2 in three distinct isolation modes: External (bridges to physical NICs with optional management OS sharing), Internal (host-to-VM only, supports NAT), and Private (VM-to-VM isolated only).
Advanced vSwitch capabilities provide enterprise traffic control: 802.1Q VLAN tagging, Port Access Control Lists (ACLs), DHCP Guard (prevents rogue DHCP servers), Router Guard (blocks rogue IPv6 RAs), and QoS Bandwidth Management.
Switch Embedded Teaming (SET) supersedes legacy LBFO NIC Teaming by integrating teaming directly into the Hyper-V vSwitch, supporting up to 8 matching physical NICs, RDMA (RoCEv2/iWARP), and SR-IOV.
SET operates exclusively in Switch Independent mode and utilizes either Dynamic load balancing (default, flowlet-based bidirectional balancing) or Hyper-V Port load balancing.
NIC teaming inside a guest VM requires two vNICs on two different external virtual switches, Set-VMNetworkAdapter -AllowTeaming On in the parent partition, and a Switch Independent + Address Hash LBFO team of exactly two members inside the guest.
Last updated: August 2026
Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET)
Network virtualization in Windows Server 2022 and 2025 provides high-throughput, software-defined connectivity between physical networks, virtual machines, and host management interfaces. Designing secure and resilient network infrastructure requires mastery of Hyper-V Virtual Switch isolation types, advanced port security features, and modern teaming architectures like Switch Embedded Teaming (SET).
1. Hyper-V Virtual Switch Types & Architecture
A Hyper-V Virtual Switch (vSwitch) is a software-based Layer 2 Ethernet network switch operating inside the root partition. It manages packet inspection, MAC address routing, VLAN tagging, and bandwidth policies for connected virtual network adapters ( vNICs ). +-----------------------------------------------------------------------------------------+
- | HYPER-V VIRTUAL SWITCH ISOLATION TYPES |
- | |
- | [EXTERNAL vSWITCH] [INTERNAL vSWITCH] [PRIVATE vSWITCH] |
- | +--------------------------+ +--------------------------+ +----------------------+ |
- | | Physical NIC (Uplink) | | NO Physical NIC Uplink | | NO Physical NIC | |
- | | ^ | | | | NO Host Management | |
- | | | | | Host Management vNIC | | OS vNIC | |
- | | +--------v-------------+ | | +--------^-------------+ | | +------------------+ | |
- | | | Virtual Switch Engine| | | | | Virtual Switch | | | | | Virtual Switch | | | |
- | | +----+-----+-----+-----+ | | +-+------+-----+-------+ | | +-+------+-----+---+ | |
- | | | | | | | | | | | | | | | | |
- | | vNIC vNIC HostOS | | vNIC vNIC HostOS | | vNIC vNIC vNIC | |
- | | [VM-1] [VM-2] [vNIC] | | [VM-1] [VM-2] [vNIC] | | [VM-1] [VM-2] [VM-3] | |
- | +--------------------------+ +--------------------------+ +----------------------+ |
- +-----------------------------------------------------------------------------------------+
- Virtual Switch Characteristics Matrix
Virtual Switch Type Binds to Physical NIC? Management OS Communication? VM-to-VM Communication? Internet / Physical Network Access?
External Switch Yes (One or more physical NICs) Yes (Optional via -AllowManagementOS $true ) Yes (Across same or different hosts) Yes (Direct physical Layer 2 access)
Internal Switch No (Software-only) Yes (Host receives a dedicated virtual network adapter) Yes (Only VMs on the same physical host) No (Unless NAT / WinNAT is configured on host)
Private Switch No (Software-only) No (Host OS cannot send or receive frames) Yes (Only VMs on the same physical host) No (Fully air-gapped isolation)
Creating Virtual Switches with PowerShell # 1. Create an External Virtual Switch sharing the physical adapter with the host OS
- New-VMSwitch -Name "vSwitch-External" `
- NetAdapterName "Ethernet1" `
- AllowManagementOS $true
- # 2. Create a Private Virtual Switch for isolated test environments
- New-VMSwitch -Name "vSwitch-Private" -SwitchType Private
- # 3. Create an Internal Virtual Switch and configure NAT for outbound Internet access
- New-VMSwitch -Name "vSwitch-Internal-NAT" -SwitchType Internal
- # Configure host gateway IP on the newly created internal virtual adapter
- New-NetIPAddress -IPAddress 192.168.100.1 -PrefixLength 24 -InterfaceAlias "vEthernet (vSwitch-Internal-NAT)"
- # Create a Network Address Translation (NAT) rule for guest outbound traffic
- New-NetNat -Name "HyperV-NAT-Network" -InternalIPInterfaceAddressPrefix "192.168.100.0/24"
- 2. Advanced Virtual Switch Security, Filtering & QoS
Hyper-V vSwitches include built-in packet inspection, security filtering, and quality of service (QoS) controls configured directly on virtual network adapters.
1. VLAN Tagging (IEEE 802.1Q)
Virtual network adapters can be configured in Access Mode (belonging to a single VLAN) or Trunk Mode (passing multiple tagged VLANs to nested firewalls or virtual appliances). # Assign a VM to VLAN 100 in Access Mode
Set-VMNetworkAdapterVlan -VMName "VM-APP-01" -Access -VlanId 100
- # Configure Trunk Mode for a virtual firewall appliance passing VLANs 10, 20, and 30
- Set-VMNetworkAdapterVlan -VMName "VM-FW-01" -Trunk -AllowedVlanIdList "10-30" -NativeVlanId 1
- 2. Advanced Security Protections (DHCP Guard & Router Guard)
DHCP Guard: Intercepts and drops unauthorized DHCP Server OFFER and ACK messages originating from rogue virtual machines, preventing man-in-the-middle DHCP hijacking.
Router Guard: Discards IPv6 Router Advertisement (RA) and ICMP redirect messages originating from unauthorized guest VMs. # Enable DHCP Guard and Router Guard on a VM's virtual adapter
- Set-VMNetworkAdapter -VMName "VM-APP-01" -DhcpGuard On -RouterGuard On
- 3. Port Access Control Lists (Port ACLs)
Applies stateful Layer 3/4 firewall rules directly at the virtual switch port level before traffic reaches the guest OS: # Block all incoming traffic to VM-APP-01 from a specific malicious subnet
- Add-VMNetworkAdapterAcl -VMName "VM-APP-01" `
- RemoteIPAddress "198.51.100.0/24" `
- Direction Inbound `
- Action Deny
- 4. Bandwidth Management & Quality of Service (QoS)
Controls minimum guaranteed bandwidth (weight or bps) and maximum ceiling bandwidth (rate limiting) to prevent noisy neighbor contention: # Configure absolute bandwidth limits (Minimum 50 Mbps, Maximum 200 Mbps)
- Set-VMNetworkAdapter -VMName "VM-APP-01" `
- MinimumBandwidthAbsolute 50000000 `
- MaximumBandwidthAbsolute 200000000
- 3. NIC Teaming Evolution: Legacy LBFO vs Switch Embedded Teaming (SET)
Windows Server historically used Load Balancing and Failover (LBFO) NIC Teaming ( lbfoadmin.exe / New-NetLbfoTeam ). However, LBFO has significant architectural limitations that make it obsolete for modern software-defined datacenters. Switch Embedded Teaming (SET) is the modern standard integrated directly into the Hyper-V Virtual Switch. +-----------------------------------------------------------------------------------------+
- | LBFO NIC TEAMING VS SWITCH EMBEDDED TEAMING (SET) |
- | |
- | [LEGACY LBFO NIC TEAMING] [SWITCH EMBEDDED TEAMING (SET)] |
- | +------------------------------------+ +------------------------------------+ |
- | | Hyper-V Virtual Switch | | Hyper-V Virtual Switch | |
- | +-----------------+------------------+ | (Teaming logic built INTO switch) | |
- | | | - Supports RDMA (RoCE / iWARP) | |
- | +-----------------v------------------+ | - Supports SR-IOV | |
- | | OS LBFO Team Driver (NIC / NetLbfo)| | - Up to 8 Matching NICs | |
- | +--------+------------------+--------+ +--------+------------------+--------+ |
- | | | | | |
- | +--------v-------+ +--------v-------+ +--------v-------+ +--------v-------+ |
- | | Physical NIC 1 | | Physical NIC 2 | | Physical NIC 1 | | Physical NIC 2 | |
- | | (NO RDMA supp) | | (NO RDMA supp) | | (RDMA Enabled) | | (RDMA Enabled) | |
- | +----------------+ +----------------+ +----------------+ +----------------+ |
- +-----------------------------------------------------------------------------------------+
- Comprehensive Comparison Matrix
- Technical Feature Legacy LBFO NIC Teaming ( NetLbfo ) Switch Embedded Teaming (SET)
- Architecture Level Operating system driver layer below vSwitch Integrated directly inside the Hyper-V vSwitch
- Management Interface New-NetLbfoTeam / Server Manager GUI New-VMSwitch -EnableEmbeddedTeaming $true
- Maximum Physical Adapters Up to 32 physical NICs Up to 8 physical NICs
Adapter Compatibility Can mix different physical speeds and vendors Requires identical speed, duplex, and model
- RDMA (RoCEv2 / iWARP) NOT SUPPORTED (LBFO breaks RDMA stack) NATIVELY SUPPORTED for host and guest vNICs
- SR-IOV Acceleration Not Supported Supported directly with hardware teaming
- Teaming Modes Switch Independent, Static Teaming, LACP (802.3ad) Switch Independent ONLY (No LACP required)
- Storage Spaces Direct (S2D) Strictly Blocked / Unsupported Mandatory Standard for converged S2D networks
Caution
LBFO Deprecation Warning: Starting with Windows Server 2022 and Windows Server 2025, LBFO NIC Teaming is deprecated for Hyper-V workloads. Attempting to deploy Storage Spaces Direct (S2D) or RDMA over an LBFO team is blocked by cluster validation rules.
4. SET Load Balancing Algorithms
Switch Embedded Teaming operates exclusively in Switch Independent mode , meaning physical upstream switches do not require LACP or multi-chassis link aggregation (MLAG/vPC) configuration. SET supports two distinct load balancing algorithms:
Hyper-V Port Mode ( -LoadBalancingAlgorithm HyperVPort ):
Distributes outbound traffic based on the source virtual network adapter port ID or MAC address.
Each virtual network adapter is statically affinitized to one of the physical NICs in the team. All inbound and outbound traffic for that specific vNIC passes through its assigned physical adapter.
Advantage: Low CPU overhead, highly deterministic.
Limitation: A single vNIC with high throughput cannot exceed the bandwidth capacity of its single assigned physical adapter.
Dynamic Mode ( -LoadBalancingAlgorithm Dynamic ) (Default & Recommended) :
Evaluates outbound TCP flowlets and hashes (Source/Destination IP and TCP ports).
Dynamically rebalances TCP streams across all active physical adapters in the team in real time.
Inbound traffic is distributed using the Hyper-V Port algorithm, while outbound traffic utilizes multi-link dynamic hash balancing.
Advantage: Maximizes aggregate bandwidth utilization across all physical uplinks.
5. NIC Teaming Inside the Guest Virtual Machine
SET and LBFO protect the host's uplinks. They do nothing for a virtual machine whose traffic bypasses the virtual switch entirely — which is exactly what happens when a vNIC is bound to an SR-IOV virtual function (VF) . An SR-IOV VF is mapped straight from the physical adapter into the guest, so if that one physical NIC fails, the VM loses connectivity even though the host still has a healthy second adapter. The blueprint objective is "Configure NIC Teaming on the Hyper-V host and virtual machine ," and guest teaming is the answer to that second half. +-----------------------------------------------------------------------------------------+
- | GUEST (IN-VM) NIC TEAMING TOPOLOGY |
- | |
- | +---------------------------------------------------------------------------------+ |
- | | GUEST VM -- LBFO team (Switch Independent + Address Hash, exactly 2 members) | |
- | | +---------------------------+ +---------------------------+ | |
- | | | Guest vNIC 1 | | Guest vNIC 2 | | |
- | | | AllowTeaming = On | | AllowTeaming = On | | |
- | +------------+-------------+-------------+-+-------------+-------------+-----------+ |
- | | | |
- | +----------v----------+ +----------v----------+ |
- | | External vSwitch A | | External vSwitch B | <-- MUST be |
- | +----------+----------+ +----------+----------+ different |
- | | | switches |
- | +----------v----------+ +----------v----------+ |
- | | Physical NIC 1 | | Physical NIC 2 | |
- | +---------------------+ +---------------------+ |
- +-----------------------------------------------------------------------------------------+
- The Four Hard Requirements
Requirement Detail What breaks if you skip it
Two vNICs on two different external vSwitches Each team member must reach a different physical adapter Both members share one uplink — the team survives nothing
AllowTeaming enabled on each vNIC Set in the parent partition, not the guest The host silently filters the team's control frames and the team never converges
Switch Independent teaming mode The only mode supported inside a VM Static/LACP teaming in a guest is unsupported
Address Hash load distribution The only supported distribution mode in a VM Dynamic/Hyper-V Port in a guest is unsupported
Microsoft supports exactly two team members inside a virtual machine. Larger guest teams can be created, but they are not a supported configuration.
Step 1: Allow Teaming on the Virtual Network Adapters (Host Side)
This is the step candidates forget, and it is the single most likely thing an exam item will test. Without it the guest can build the team object, but the virtual switch drops the teaming traffic and failover never works. In Hyper-V Manager it is the NIC Teaming checkbox under the adapter's Advanced Features page. # Enable teaming on every virtual network adapter of the VM
Get-VMNetworkAdapter -VMName "VM-SRIOV-01" | Set-VMNetworkAdapter -AllowTeaming On
- # Verify the setting took effect
- Get-VMNetworkAdapter -VMName "VM-SRIOV-01" | Format-Table Name, SwitchName, AllowTeaming
- Step 2: Create the Team Inside the Guest
There is no SET inside a guest — SET only exists as part of a Hyper-V virtual switch, and a VM has no virtual switch. Guest teaming therefore still uses LBFO , and this is the one remaining scenario where New-NetLbfoTeam is the correct answer on a modern Windows Server. The host-side LBFO deprecation covered above applies to Hyper-V hosts , not to teams built inside guests. # Run INSIDE the guest operating system
- New-NetLbfoTeam -Name "GuestTeam" `
- TeamMembers "Ethernet","Ethernet 2" `
- TeamingMode SwitchIndependent `
- LoadBalancingAlgorithm TransportPorts `
- Confirm:$false
- Get-NetLbfoTeam -Name "GuestTeam"
- Get-NetLbfoTeamMember -Team "GuestTeam"
Tip
Decision rule for the exam. If the scenario mentions SR-IOV, a VM that must survive a physical NIC failure, or a guest that needs its own fault tolerance, the answer is guest NIC teaming with -AllowTeaming On . If the scenario is about host uplinks, RDMA, converged networking, or Storage Spaces Direct, the answer is SET on the host . Configuring one never substitutes for the other.
6. PowerShell SET Switch Deployment & Converged Networking
In modern datacenter designs, enterprise hosts implement Converged Networking , where management traffic, Storage Spaces Direct (S2D) SMB Direct traffic, cluster heartbeats, and VM payload traffic share a single redundant SET switch pair. +-----------------------------------------------------------------------------------------+
- | CONVERGED NETWORKING ON SET VSWITCH |
- | |
- | [HYPER-V HOST MANAGEMENT OS] [TENANT GUEST VMs] |
- | +---------------------------------------+ +------------------------------------+ |
- | | vEthernet (Management) - VLAN 10 | | VM-1 (Tenant Traffic) - VLAN 100 | |
- | | vEthernet (Cluster-Heart)- VLAN 20 | | VM-2 (Tenant Traffic) - VLAN 200 | |
- | | vEthernet (SMB-Direct-1) - RDMA / RoCE| | | |
- | | vEthernet (SMB-Direct-2) - RDMA / RoCE| | | |
- | +-------------------+-------------------+ +-----------------+------------------+ |
- | | | |
- | +-------------------v--------------------------------------------v------------------+ |
- | | SWITCH EMBEDDED TEAMING (SET) vSWITCH | |
- | | (Dynamic Load Balancing / Switch Independent Mode) | |
- | +---------------------------+----------------------------+--------------------------+ |
- | | | |
- | +------------v-----------+ +------------v-----------+ |
- | | Physical 25GbE NIC 1 | | Physical 25GbE NIC 2 | |
- | | (Mellanox / Intel RDMA)| | (Mellanox / Intel RDMA)| |
- | +------------------------+ +------------------------+ |
- +-----------------------------------------------------------------------------------------+
Step-by-Step Converged SET Switch Deployment Workflow # Step 1: Create the SET Virtual Switch with Dynamic Load Balancing
- New-VMSwitch -Name "SET-ConvergedSwitch" `
- NetAdapterName "NIC1","NIC2" `
- EnableEmbeddedTeaming $true `
- LoadBalancingAlgorithm Dynamic
- # Step 2: Add dedicated host management vNICs for SMB Direct Storage
- Add-VMNetworkAdapter -ManagementOS `
- Name "SMB-Direct-1" `
- SwitchName "SET-ConvergedSwitch"
- Add-VMNetworkAdapter -ManagementOS `
- Name "SMB-Direct-2" `
- SwitchName "SET-ConvergedSwitch"
- # Step 3: Configure VLAN IDs for host management adapters
- Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "SMB-Direct-1" -Access -VlanId 10
- Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "SMB-Direct-2" -Access -VlanId 20
- # Step 4: Enable Remote Direct Memory Access (RDMA) on host storage adapters
- Enable-NetAdapterRdma -Name "vEthernet (SMB-Direct-1)", "vEthernet (SMB-Direct-2)"
- # Step 5: Verify SET Team Health and Physical Member Status
- Get-VMSwitchTeam -Name "SET-ConvergedSwitch"
- Get-NetAdapterRdma
- Managing SET Team Members Online
Physical adapters can be added or removed from an active SET team without deleting or re-creating the virtual switch: # Add a third physical adapter to the existing SET team