Export (0) Print
Expand All

[adapter_specific_protocol_section] (Sysprep)

Updated: March 28, 2003

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

[adapter_specific_protocol_section]

Each [adapter_specific_protocol_section] section can contain an entry for specifying a network component. This section must be used in conjunction with the [Networking] section.

SpecificTo

Specifies the name of a network component on the computer to which the protocol settings apply.

Syntax

                SpecificTo = 
                network_component_name
              

 

Value Description

network_component_name

Network adapter name.

Example
[Networking]

[NetAdapters]
Adapter01 = params.Adapter01
Adapter02 = params.Adapter02

[params.Adapter01]
INFID = "pci\ven_0e11&dev_ae32"

[params.Adapter02]
INFID = "pci\ven_8086&dev_1229&subsys_00018086"

[NetClients]
MS_MSClient = params.MS_MSClient

[params.MS_MSClient]

[NetProtocols]
MS_TCPIP = params.MS_TCPIP

[params.MS_TCPIP]
AdapterSections = params.MS_TCPIP.Adapter01,params.MS_TCPIP.Adapter02

[params.MS_TCPIP.Adapter01]
DHCP = Yes
SpecificTo = Adapter01

[params.MS_TCPIP.Adapter02]
DefaultGateway = 192.168.1.1
DHCP = No
IPAddress = 192.168.1.2
SpecificTo = Adapter02
SubnetMask = 255.255.255.0
WINS = No

[NetServices]
MS_Server = params.MS_Server

[params.MS_Server]
BroadcastsToLanman2Clients = No
Optimization = Balance 
Comments

If the SpecificTo entry is not present in an adapter-specific section, then the entries in that section are global to the network protocol that is configured during the Windows setup process.

If you specify an entry that is in both the [Protocol] section and an adapter-specific protocol section, Setup ignores the entries specified in the adapter-specific section.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft