Nomgle , When you upgrade to a new Operating System such as Windows 10, your drivers will up 'updated' by the OS install to what the OS has certified as current (in other words, what it will support). Unfortunately, this means that the hardware you were using before becomes subject to the OS WHQL certifications required for that version of the OS. Thus, the loss of teaming. (This again is due to the fact that inherently, the OS does not support Teaming, and the controller silicon on the adapter you used before does not have WHQL certifications for that OS.) IN this instance, a PROSet reinstall still will not allow for teaming to setup (it requires a device to initial the team that the OS will support as WHQL certified). To support teaming using Intel hardware under Windows 10, you will need a device that has a certified driver for Windows 10 (see my post above for why).
mimi74, you are in the same boat with the Intel(r) Gigabit ET Dual Port Server Adapter, which is based on the 82576EB controller which launched in Q2'08. Like the 82571EB controller, it also does not have Windows 10 driver from Intel (only Inbox from Windows 10). The last 'Retail' driver available for that controller is Windows 8 and Server 2012. Windows 8.1 and Windows 2012 R2 and beyond are inbox only support. The Intel(r) Ethernet Server Adapter I350-T2 should work with Teaming etc., assuming you have the most current driver.
VirtualPanther and mimi74, you should also be able to download our latest driver from the Intel support site for Windows 10 for the I350-based cards. This also should allow you to create a team from the Windows device manager (there is no longer a separate PROSet application as it is integrated into Device Manager). Once you create a team you will be able to have the 1 IP address you need for your application and switch. My guess is when you upgraded the Inbox Driver that is native to the OS removed your teaming settings. Installing the Windows 10 driver from our web site should allow you to reconfigure the team you need.