programmatically changing windows network adapter binding order
06-10-2005, 09:21 PM
#1
Three Wheelin'
Thread Starter
Join Date: May 2001
Age: 53
Posts: 1,377
Likes: 0
Received 0 Likes
on
0 Posts
programmatically changing windows network adapter binding order
I am trying to find a way to programmatically change network adapter binding order in Windows 2003 Server. Is it possible?
06-10-2005, 09:31 PM
#3
Three Wheelin'
Thread Starter
Join Date: May 2001
Age: 53
Posts: 1,377
Likes: 0
Received 0 Likes
on
0 Posts
I need to deploy a lot of Proliant DL380 clusters in a short amount of time using Sysprep.
One thing that Sysprep doesn't help with is the binding order. Each DL380 node has multiple NICs. Two NICs will be teamed and a public IP will be assigned to them. The third NIC will be for cluster heartbeat. I want to make sure that the virtual team NIC is at the top of the binding order. Sysprep doesn't understand stuff like this - when I build the OS from an image and Sysprep completes its mini-setup, the NICs are rediscovered fresh.
One thing that Sysprep doesn't help with is the binding order. Each DL380 node has multiple NICs. Two NICs will be teamed and a public IP will be assigned to them. The third NIC will be for cluster heartbeat. I want to make sure that the virtual team NIC is at the top of the binding order. Sysprep doesn't understand stuff like this - when I build the OS from an image and Sysprep completes its mini-setup, the NICs are rediscovered fresh.
06-11-2005, 12:03 PM
#5
Three Wheelin'
Thread Starter
Join Date: May 2001
Age: 53
Posts: 1,377
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Malayalee King
Could you run a script that changed the binding order after sysprep install?
well, that's what I am trying to find - a script to change the bindings
06-11-2005, 12:43 PM
#6
Race Director
I had tried this.
The damn thing is in the registry and the bindings are generated with a 60 character SID and it is unique on every sysprep so you cannot do it. I worked on it for 2 months as I have the same situation. Deploying syspreped images to 100 machines and was trying to name the interfaces Public and Private, but it ended up being faster just booting the machine and doing it for every interface.
The damn thing is in the registry and the bindings are generated with a 60 character SID and it is unique on every sysprep so you cannot do it. I worked on it for 2 months as I have the same situation. Deploying syspreped images to 100 machines and was trying to name the interfaces Public and Private, but it ended up being faster just booting the machine and doing it for every interface.
06-11-2005, 01:06 PM
#7
Race Director
After looking at it again, you might be able to do it with a vb script and editing the registry.
You will first have to find the key that is the "Local Ethernet Adapter"
Something like this
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Ne twork\{4D36E972-E325-11CE-BFC1-08002BE10318}\{E8482428-2D9B-4A58-B9B5-402B8321249D}\Connection\Name
Then you will need to change the parameters for the {4D36...} in the tcp section
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{E8482428-2D9B-4A58-B9B5-402B8321249D}
It is a pain in the ass but now I see it can be done.
You will first have to find the key that is the "Local Ethernet Adapter"
Something like this
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Ne twork\{4D36E972-E325-11CE-BFC1-08002BE10318}\{E8482428-2D9B-4A58-B9B5-402B8321249D}\Connection\Name
Then you will need to change the parameters for the {4D36...} in the tcp section
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{E8482428-2D9B-4A58-B9B5-402B8321249D}
It is a pain in the ass but now I see it can be done.
Trending Topics
06-11-2005, 11:23 PM
#9
Three Wheelin'
Thread Starter
Join Date: May 2001
Age: 53
Posts: 1,377
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Beelzebub
After looking at it again, you might be able to do it with a vb script and editing the registry.
You will first have to find the key that is the "Local Ethernet Adapter"
Something like this
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Ne twork\{4D36E972-E325-11CE-BFC1-08002BE10318}\{E8482428-2D9B-4A58-B9B5-402B8321249D}\Connection\Name
Then you will need to change the parameters for the {4D36...} in the tcp section
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{E8482428-2D9B-4A58-B9B5-402B8321249D}
It is a pain in the ass but now I see it can be done.
You will first have to find the key that is the "Local Ethernet Adapter"
Something like this
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Ne twork\{4D36E972-E325-11CE-BFC1-08002BE10318}\{E8482428-2D9B-4A58-B9B5-402B8321249D}\Connection\Name
Then you will need to change the parameters for the {4D36...} in the tcp section
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{E8482428-2D9B-4A58-B9B5-402B8321249D}
It is a pain in the ass but now I see it can be done.
Thanks. Yeah, I took a look there too... I am afraid that there are more places other than Services/Tcpip that would need to be changed too...
06-11-2005, 11:24 PM
#10
Three Wheelin'
Thread Starter
Join Date: May 2001
Age: 53
Posts: 1,377
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Malayalee King
I'm not sure if you're a programmer or not, but I am.
I keep forgetting why I look for the answer in a script anymore (sometimes)..
MSDN
Run exe after install, perhaps?
Good luck!
I keep forgetting why I look for the answer in a script anymore (sometimes)..
MSDN
Run exe after install, perhaps?
Good luck!
This looks promising... now I have to rewind my brain 15 years back when I was doing C programming
Thread
Thread Starter
Forum
Replies
Last Post
cycdaniel
1G TSX Performance Parts & Modifications
8
12-17-2019 10:58 AM
spoiler900
5G TLX Photograph Gallery
11
09-11-2015 09:39 PM
