Hi Mark,
Thanks for the follow-up. I had already tried adding VLANs to the team interface, and I was aware of the requirement to configure all VLANs (used by VMs) if any are defined at the interface level. Here is what happens when I try using PROSetCL.exe to add a 'default' (untagged) VLAN:
> PROSetCL.exe Team_CreateVlan 1 untagged default
1) TEAM : VMNetwork
Attempting to create VLAN 'default' ...
Failed to create VLAN
and if I try to add a VLAN for our IP phone VLAN:
> PROSetCL.exe Team_CreateVlan 1 5 IP_PHONES
1) TEAM : VMNetwork
Attempting to create VLAN 'IP_PHONES' ...
Failed to create VLAN
I checked Windows' event logs but didn't find anything additionally relevant. Recall from my previous post how priority / VLAN settings don't appear in Adapter_EnumerateSettings output for teamed network interfaces, and never appear for the team itself, in the output for Team_EnumerateSettings. Perhaps incorrectly, this suggested to me that (at least for my combination of hardware, drivers, etc.) prioritization and VLANs are unsupported on teams...
For now, I've reserved a non-teamed interface for our non-default (tagged) VLANs. This works, but isn't an "ideal" solution, and doesn't satisfy my curiosity. 