I recently setup my new host and one of my old ones on Hyper-V 2019. The old host got a new (2) 10GB NIC and the new host has (4) 10GB ports. In my efforts to get the hosts working and all my VM's converted over, I neglected to setup teaming on the host. Now that most of my VM's are converted, I attempted to make a team on the old host with (2) ports, but I did not use the method that most of the posts on ML use. I created a new vswitch with both ports as members using WAC, but I am not sure if this is the same as what I see in other posts. In WAC, I am able to set it to dynamic for the load balancing algorithm (the only other choice is Hyper-V port), but there is no place to say if it is switch independent or dependent. Also, if I look under NIC teaming in server management, it shows up as a vEthernet at 20gbps, but does not have any other information about algorithm or mode. I am wondering if I should break this back apart and do it from server management (which does have all the options). Also, I have read @JaredBusch's comments on generally using switch independent mode because of it's ease, but since my switch (edgeswitch XG) does support LACP, it seems like it would be beneficial to set it up to help balance incoming traffic as well.