NIC Teaming includes several parts:
- The core teaming engine
- The PowerShell management cmdlets ("NetLbfo")
- The NIC Teaming GUI
The core teaming engine is a server feature. It is not licensed for or included in Windows 8 or Windows RT; there is no way to enable it on these operating systems.
The PowerShell cmdlets ("NetLbfo") are built into Windows Server 2012, Windows 8, and Windows RT. However these cmdlets are only useful when targeting a Windows Server 2012 machine. When using the cmdlets from a Windows 8 or Windows RT machine,
you can only manage remote servers.
The NIC Teaming GUI can be installed on Windows 8, if you download
the RSAT package. The NIC Teaming GUI, when running on Windows 8, can again only create and manage teams on remote servers, since the core teaming engine is not present on Windows 8. (If you enable WinRM remoting on Windows 8, you
can add that client to the NIC Teaming GUI, but since you can't create teams on Windows 8, there's not much the GUI can do besides enable/disable NICs.)
Network Bridging is a related feature, and it is available in Windows 8, Windows RT, and Windows Server 2012. While Network Bridging is generally not as powerful as NIC Teaming, Network Bridging can do one neat trick that teaming cannot
do: bridge over a WiFi adapter.
Please be more respectful of other people in this forum. The question about bridging is perfectly on-topic, and the response from Jshansen was excellent.