Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot configure a network adapter that resides on a virtual bus to use a static IP address in an automated deployment of Windows Server 2003


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use an answer file to perform an automated deployment of Microsoft Windows Server 2003. For example, you use an Unattend.txt file or a Sysprep.inf file for the answer file.
  • The answer file uses the PCIBus, PCIDevice, and PCIFunction headers to identify the network adapter. The answer file uses the TcpipParams header to set any network settings, such as the IP address, the Subnet mask, the default gateway, and so on.
  • The network adapter resides on a virtual bus.
In this scenario, network settings, such as the static IP address, in the answer file are ignored. Instead, the network adapter acquires an IP address from the Dynamic Host Configuration Protocol (DHCP) server after Windows starts.

↑ Back to the top


Cause

Assume that you are using an answer file for an automated deployment and that the network card resides on a virtual bus. In this case, you cannot currently set network settings by using an answer file that uses the PCIBus, PCIDevice, and PCIFunction headers to identify the network adapter. Instead, you can use the MAC address of the adapter as the identifier.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100� How to obtain the latest service pack for Windows Server 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. To resolve this problem, use the Netset03.exe tool from this hotfix to configure the network settings. The tool uses an answer file to perform the configuration of the network components. The procedure follows the same format as an unattended Setup answer file by using the Network section to configure the client. For more information about how to use the Netset03.exe tool, click the following article number to view the article in the Microsoft Knowledge Base:
268781� Description of the Netset.exe tool from the Windows 2000 Resource Kit
Knowledge Base article 268781 discusses the Netset.exe tool from the Windows 2000 Resource Kit. However, the procedure is the same for using the Netset03.exe tool in Windows Server 2003.

Note The Netset03.exe tool will not process the [netoptionalcomponents] section of the unattend file. However, the Sysocmgr.exe tool can be used for the installation of the optional components. The Sysocmgr.exe tool is not needed to configure network components. The Sysocmgr.exe tool is included in Windows Server 2003, and is installed in the %SystemRoot%\System32 folder. Sysocmgr.exe accepts an answer file that has the [components], and [netoptionalcomponents] sections, and then it applies the required entries.

If you use the Sysocmgr.exe tool, you must first run the Netset03.exe tool. This is because certain optional components cannot be installed before the network adapter has been configured. Run the Sysocmgr.exe tool only if you have to use the [netoptionalcomponent] section in your unattend file. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
136153� Using an answer file for an unattended installation
222444� How to add or remove Windows components with Sysocmgr.exe
323438� How to use Setup Manager to create an answer file in the Windows Server family

Prerequisites

No prerequisites are required.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Netset03.exe1.0.0.746,08005-Aug-200619:18x86
Windows Server 2003, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Netset03.exe1.0.0.769,12006-Aug-200612:12x64SP1SP1QFE
Wnetset03.exe1.0.0.746,08006-Aug-200612:12x86SP1WOW
Windows Server 2003, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Netset03.exe1.0.0.7129,02406-Aug-200612:12IA-64SP1SP1QFE
Wnetset03.exe1.0.0.746,08006-Aug-200612:12x86SP1WOW

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top


More information

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915� New file naming schema for Microsoft Windows software update packages
For more information, 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


Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:

↑ Back to the top


Keywords: kbautohotfix, kbwinserv2003presp2fix, kbhotfixserver, kbqfe, kbbug, kbexpertiseinter, KB920293

↑ Back to the top

Article Info
Article ID : 920293
Revision : 12
Created on : 10/11/2007
Published on : 10/11/2007
Exists online : False
Views : 122