Is there a way using VBscript, WMI etc to bind your NICs the way you prefer ? I have looked at netsh syntax to no avail. I have also looked at this KB http://support.microsoft.com/Default.aspx?id=299540It explains about the 'Automatic metric' but does not tell how you can modify the settings for multiple computers thru Group policy.Does 'Automatic metic' option (being checked in your TCP/IP Advanced Settings) takes over the binding order and makes it irrelevant ?Your insight is appreciated.Regards

Looking at this myself right now. This link may help (not sure if it still applies to Vista/Srv 08): http://support.microsoft.com/kb/894564 And: http://www.microsoft.com/technet/scriptcenter/scripts/cfgmgr/default.mspx?mfr=true My guess is that a computer startup script in a GPO running the above may work for you, but when messing around with metrics you should set metrics for the different adapters at different values so the script would need to be beefed up somewhat to work out which adapter is primary and go from there. In most casesthe auto metric does the job pretty well, but binding order is still important. (The one case I'm looking at right now is with a laptop connected wired and wirelessly at the same time and with Remote Assistance (XP SP3). With the binding order of wireless higher than wiredthe laptop thinks, rightly so, that it's primary IP address is the one sourced from the wireless connection. For some reason Remote Assistance uses this when trying to set up a session rather than using DNS. But anyway...long story short...I'm looking for something to set binding order at boot/startup.) Unfortunately the article mentions "You cannot change the connection order during an unattended setup. There also is no programmatic way to change the binding order of network adapters for a computer that is running. This inability to make a change is a problem if you want to programmatically move one local area connection ahead of another local area connection. However, no documented programmatic method exists for changing the order of the adapters." but then goes on to mention it can try to be forced during sysprep. Still looking...

Thanks BWalter. The articles you have provided are relevant to the cause yet I find myself in the same situation as yours :Why is the binding order important anyway ? i.e if the automatic metric does its job of giving higher throughput interface more importance which in your laptop scenario (same as my dilemma) would be the LAN NIC (100mb) rather than the wireless NIC of (22mbps or 54mbps). Why should Remote assistance programs alike try and choose the lower weight NIC i.e wireless over the LAN NIC.Secondly, is there then a programmatic way to the change the binding order during sysprep, if so, how ?Please keep me posted of your findings. I am glad to find some one in the same boat.Regards,

Can anybody shed some more light on my questions above ?Thanks,

The KB article (894564) is explicitly talking about Windows XP when saying we cannot change the NIC binding order.What about Windows Server 2003 and Windows server 2008? Can we still not change the NIC binding order by script?Can anyone provide a statement about this?TIA,D-J.