On my lab server (Windows Server 2012 Core) I caused an inactive port to switch to active by setting the adapter priority to PRIMARY. When you create the AFT team, the default priority is Not Set. You can see this by using the command PROSetCL.exe Team_GetAdapterInfo <AdapterIndex>. That command will show you the adapter status as Active or Standby.
If you set the Adapter Priority of the Standby adapter to PRIMARY, then that adapter's status will switch to Active and the other adapter will switch to Standby. If you then go back to the other adapter and set that adapter's priority to PRIMARY, then that adapter will go back to Active.
The command to set the adapter priority is:
PROSetCL.exe Team_SetAdapterPriority <AdapterIndex> PRIMARY.
I hope this helps.
I'm not sure why that is happening. Perhaps an older version might have been missing that command. You can get the latest version at http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21694. This is the version I was using.
Another thing that can affect issue commands is user privileges. I was logged directly into my Windows Server as administrator, so everything was executing in privileged mode. If the commands are run at less than privileged mode, sometimes the command fails. If the command fails, the message should tell you why, but occasionally the messages can throw you off.
Check this page for installation: Network Connectivity — Installing the Base Driver and Intel� PROSet via the Command Line . Installing the new version over the old version acts as an upgrade.
I tried the same option from the command prompt as administrator and I got the same results.
Unfortunately upgrading is not an easy process. The upgrade wizard doesn't preserve the VLANs and Teams, which is problematic when the host is a member of Failover Cluster.
I tried it before and I have to re-create them.
I change the adapters by disabling the one that I want in the switch.
I am not sure why your VLANs and teams were not preserved when you upgraded before. Those settings should be preserved. Nevertheless, we have a Visual Basic script that you can use to save the settings before making any upgrades (or any other changes.) You can then use the file you saved to restore the settings. See Network Connectivity - How do I save and restore adapter and team configuration settings?
You could use the script to make a back up of your settings before making any changes. That way you have a quick way to restore the settings in case the changes do not work the way you expect.