Does anyone else have issues with the Add-VNIC cmdlet not enabling failover when you set the option to yes? In the below snippet, I pipe in an object from a previously created Service Profile Template and attempt to add a VNIC. The VNIC adds just find but it doesn't matter if I set the -FailOver option to  yes or no, the VNIC is still created without the failover enabled. Is this an error with the cmdlet?
 

$vnic = $SPTemplate | Add-Vnic -VnicName Templates -FI A -FailOver yes -macpool ($OrganizationName + "_MacPool") -NetcntrlPolicyName ($OrganizationName + "_NwCtrlPol") -VLANName '21717_BB_2' -Force

 
Also, why is this cmdlet and the Set version missing the option to configure MTU and Desired Order? Right now I am just sending the XML after the creation of the VNIC to go back and edit those settings if necessary but it seems like the simplest of options to add when compared to VLAN and macpools that require more error checking to make sure those items exist before adding them.
 
Kevin