Rule "Network binding order" generated a warning.

The below describes the issue and how to resolve it.

Network Binding Order - Failover cluster Setup operations include a rule that checks network binding order. Although binding orders might seem correct, you might have disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC configurations can affect the binding order and cause the binding order rule to issue a warning:
Rule "Network binding order" generated a warning.
The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced configuration to change the binding order.

Possible causes for the above warning are due to following reasons:
1. The domain network is not the first bound network.
2. This issue may also occur when you have a disabled network adapter or a ghosted network adapter on the computer.

Note: A network adapter that is enumerated in the Windows registry but that is hidden in Device Manager is called a ghosted network adapter. This issue may occur when you change a network connection's TCP/IP configuration from DHCP to a static IP. This issue may also occur when you have added and removed network adapters multiple times. For Disabled network adapter or ghosted network adapter we need to follow the below KB article: http://support.microsoft.com//kb/955963

Change the Binding Order using Registry - To avoid the "Network binding order" warning message we need to change the Bind Order and reorganize it in a way that domain bound network is top in the list.
Within this registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage, double-click on Bind.
The associated domain name is determined by doing a registry query on, HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ DNSRegisteredAdapters\{ADAPTER_GUID}\PrimaryDomainName
In the Bind Value data box, select the "\Device\{ ADAPTER_GUID }" item that matches the DNSRegisteredAdapters, press CTRL+X, click the top of the list of devices, and then press CTRL+V.
Changes need to be made on both nodes.

This Hot Tip was provided by David, one of our Wellington based SQL Server consultants. David acknowledges that variances may occur, so recommends this activity is carried out very carefully by an experienced consultant and the registry backed up before modifying.