Protocol driver doesn't bind to teamed network adapters in Windows Server 2012
Content provided by Microsoft
Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 StandardWindows Server 2012 StandardMore
Consider the following scenario:
You use the NIC Teaming feature to set up a network adapter team in Windows Server 2012.
You install an Intel FCoE/DCB protocol driver on one of the adapters in the team.
The NdisImPlatformBindingOptions registry entry is configured to enable protocol binding.
In this scenario, the network adapters in the team are not bound to the protocol driver as expected.
Note This issue does not occur if you install the Intel FCoE/DCB protocol driver before you set up the NIC Teaming.
Cumulative Update information
To resolve this issue, install the Windows 8 and Windows Server 2012 cumulative update 2822241. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2822241 Windows 8 and Windows Server 2012 cumulative update: April 2013
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about NIC Teaming, go to the following Microsoft TechNet website:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
ERROR: at System.Diagnostics.Process.Kill()
at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)New URL: about:blank