Windows Server / Hyper-V & Failover Clustering
Inspect Switch Embedded Teaming separately from legacy LBFO
Hyper-V SET membership and load-balancing configuration use a different management path from older NIC teams.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-VMSwitchTeam -Name 'ProductionSwitch'Read the result
With Hyper-V tools, this reports the selected switch's embedded team when configured. It does not query LBFO teams or verify physical-switch health.
Resolve and verify
Compare team members and NIC capabilities with the supported design, then inspect failing ports and drivers. Repair one verified dependency in a controlled window.
Before changing production
Do not apply LBFO changes to a SET switch or change uplinks over the only management path.