Browse thin: This Month's Archive • Main Archive Page • Related posts • Previous by Date • Next by Date
[THIN] Re: PXE Boot to ADS/WDS for Compaq G5s

From: "Malcolm Bruton" <malcolm.bruton@xxxxxxxxxxxxxxxxxx>
To: <thin@xxxxxxxxxxxxx>
Date: Mon, 4 Feb 2008 10:52:53 -0500
And just to add something to this.  I found that using HP drivers for
the NC373i now include a windows 2008 driver (as of PSP 7.8 and above if
I remember correctly.)  Interesting thing in that if you try and build
and older system (2000 or 2003) using an unattended build it fails to
copy several of the files correctly.  This is because HP have put long
file names in the driver and when it copies during the dos portion of an
unattended setup it truncates them  to 8.3 format.  Subsequently when
the build is auto detecting the NIC's it can't find all files from the
driver and fails to install them correctly.  Fix was to build using PSP
7.7 or below and update later in the full OS to latest version.

 

I reported this to HP but there response was it was a Microsoft issue!!!

 

Also we saw all the issues with Storport.sys and it is fixed using the
latest version of this form MS and then the latest PSP from HP as per
below

 

Malcolm

 

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Rick Mack
Sent: 04 February 2008 09:50
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: PXE Boot to ADS/WDS for Compaq G5s

 

Hi Andrew,

 

HP have made things more interesting by using the new multifunctional
Broadcom (iSCSI/NDIS) drivers that consist of a virtual bus driver with
either iSCSI or NDIS drivers added. However when you do a text mode
build, you will probably need the single level NIC driver which from
memory is available buried deep in the driver distribution under RIS.

 

I've included some doco I did on this stuff a while ago. It's a mixture
of info from Microsoft, broadcom and HP.

 

------------

HP DL360 G5

Introduction

This is a revamped server platform with some major differences compared
to the earlier DL360 G4. The changes relevant to an automated install
are listed below:

1. New RAID controller
The DL360 G5 uses SAS (serial attached SCSI) disks and utilizes a new
Storport RAID controller, the SmartArray P400i. This uses an updated
driver, HpCISSs2.sys (version 6.8.0.32, 21/06/2007) which is required
for disk access during the build.

2. New NIC Topology
The DL360 uses a multifunctional Broadcom NC373i PCI Express chipset
which is a divergence from the now traditional single network card
driver structure. The PCI device displays as a virtual bus device that
can be used either as an iSCSI storage interface or a network interface
using a secondary NDIS driver.

The "network card" is therefore supported by 2 drivers, the HP NC373i
virtual bus device driver (bxvbdx.sys, version 2.8.18.0 , 05/11/2006)
and the HP NC373i Multifunction Gigabit Server Adapter, (NDIS VBD
client, bxnd52x.sys, version 2.8.13.0, 07/08/2006).

While the RAID controller is simply yet another RAID controller, the NIC
presents a problem for an automated build. Any automated build process
using network components while in text mode actually requires a
different, single level NIC driver, Broadcom NetXtreme II B06ND,
(b06nd51x.sys, version 2.6.1.0, 05/04/2006).

Automated Build and the DL360 G5

The DL360 disk subsystem uses the storport driver (storport.sys). The
Microsoft update to the storport driver ( KB932755)  and an older P400i
driver (hpciss2.sys) may cause a BSOD (stop 0x000000D1) under high i/o
load. As a result, hpciss2,sys must be version 6.2.0.32 or later.

See HP Support Advisories (Document ID c01068337, c00715130)

 
Integrating the DL360 G5 NIC drivers into the build process.

A number of TechNet articles deal with the DL360 G5 NIC issues. These
are presented below:


Network Settings provided through unattend.txt fail to take effect on
Servers if NIC resides on virtual Bus 
This article covers a known issue with latest Broadcom NC Series VBD
Drivers coming with DL360 G5 and DL380 G5, which prevent the Network
Settings, provided in Unattend/sysprep answer file, to take effect.

ROOT CAUSE

The unattended installation of the server 2003 operating system with the
NC Series NIC residing on VBD (Virtual Bus Device) will fail to maintain
the Network IP settings. Unattended network settings are not applied to
these devices using the PCI information because of the way the Broadcom
hardware was designed combined with the way the drivers were written.  

Basically, the problem is that NC Series VBD driver is creating their
own bus in the system that is used to enumerate their hardware.  This
bus has no relation at all to the PCI bus, so matching PCI information
from this bus doesn't make much sense. Unfortunately, since these NICs
were NOT enumerated by pci.sys, they will NOT contain any PCI
information. After enumerating the devices in this manner, the PCI
matching doesn't make any more sense for the NC Series NIC than it does
for the USB NIC from a system perspective. This is because the system
does NOT see the NIC as part of the PCI bus.

RESOLUTION

To use netset03.exe to specify network information as per KB 920293

Extract KB920293 and locate file netset03.exe. To extract the file to a
location (e.g C:\Netset) use the following command:

WindowsServer2003-KB920293-x86-ENU.exe /X

This will pop up the extraction wizard asking for a location to extract
files. Once you have the netset03.exe file, create a file named
netset.txt (You can choose any name). Now copy all the adapter specific
settings in this file and save.  

You can use any one of the below mentioned methods to specify Network
Settings:

       1. Use [SetupParams] in unattend answer file to specify settings.

Create a Folder named Netset under $oem$\$1\Netset (This can be any name
and not necessarily Netset). Copy netset03.exe and netset.txt file under

$oem$\$1\Netset Folder. Now add below entry in unattend.txt answer file.

[SetupParams]
UserExecute = "C:\Netset\Netset03.exe C:\Netset\Netset.txt"
You can add the above section just below [GuiUnattended].
OR

     2. Use cmdlines.txt to specify settings.

Create a Folder named Netset under $oem$\$1\Netset (Again, this can be
any name and not necessarily Netset). Copy netset03.exe and netset.txt
file under $oem$\$1\Netset Folder. 

Now create another file named cmdlines.txt under $oem$ folder. Populate
following entry in cmdlines.txt

[Commands]
"C:\Netset\Netset03.exe C:\Netset\Netset.txt"

If you want to install the NIC drivers along with this, you can use the
following:

[Commands]
"cmd.exe /c {location of nic driver executable} [/switch to make the
install silent]"
"C:\Netset\Netset03.exe C:\Netset03.exe\Netset.txt"

The benefit of using cmdlines.txt is that it executes commands in a
seqential order and the second command would wait for the first to
finish before it can execute. In case of SetupParams you can only run a
single command. In case you've added more than one command, the second
and subsequent will be ignored.

Note:  In case you're using Netset03.exe, make sure that you use
PCIBusNumber, PCIDeviceNumber, PCIFunctionNumber to specify settings for
each NIC. In case you're using the InfID to specify NIC settings you may
see that NIC settings are not getting implemented. If you manually run
that command after installation you will see below error:

Network Card {guid} not found in the answerfile.

HP Multifunction Gigabit Server adapters (NC37x/NC38x) use a software
architecture that includes a Virtual Bus Device (VBD) to extend its
functionalities beyond basic network connectivity

 
Windows PE and DL360 G5

HP have released a beta version of the Proliant Support Pack (PSP)
v7.65. 

For the 32-bit beta PSP 7.65:
ftp://ftp.compaq.com/pub/softlib2/softwar....65.lh.i386.exe

For the 64-bit beta PSP 7.65:
ftp://ftp.compaq.com/pub/softlib2/softwar...7.65.lh.x64.exe

You will need the following packages: 
* cp006277.exe 
* cp006284.exe 
* cp006316.exe 
* cp006913.exe 
* cp006924.exe 
* cp006926.exe 
* cp007054.exe 
* cp006258.exe
Extract the packages to c:\psp7.65, make sure that your winpe image is
mounted, and then run the following commands:

peimg /inf="C:\psp7.65\cp006284\cpqasm2.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006913\lsi_scsi.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006924\lsi_sas.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006926\hpcissx2.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp007054\cpqcisss.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp007054\hpcisss.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006277\CpqCiDrv.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006258\hpqilo2.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006316\bxvbd.inf" c:\winpe_x86\mount\Windows
peimg /inf="C:\psp7.65\cp006316\bxnd.inf" c:\winpe_x86\mount\Windows


Now, you would only really need the cp006316 package, as it contains the
necessary drivers you need to get networking to work. I would suggest
the other packages (especially cp006284, cp006258 and cp006277) if you
are going to use Altiris Deployment Solutions or HP RDP 3.50, or you
want the ability to use hponconfig to configure the iLO2 management
processor. 

 
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 - KB920293
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. 
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. 
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
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 

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
 File name File version File size Date Time Platform
Netset03.exe 1.0.0.7 46,080 05-Aug-2006 19:18 x86

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. 

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 

 
Description of the Netset.exe tool from the Windows 2000 Resource Kit -
KB268781
Important  This article contains information about modifying the
registry. Before you modify the registry, make sure to back it up and
make sure that you understand how to restore the registry if a problem
occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the
Microsoft Knowledge Base: 

256986 Description of the Microsoft Windows Registry

SUMMARY
This article describes how to use the Netset.exe tool that is included
in the Microsoft Windows 2000 Resource Kit. 
MORE INFORMATION
Overview and use of Netset.exe
Netset.exe is a stand-alone tool that you can use to add, to remove, or
to change the network configuration of a client computer that has
Windows 2000 already installed on it. For example, you can use this tool
to remove a protocol, such as Internetwork Package Exchange (IPX) or
NetBeui, from a client computer that is no longer used on your network.
You can also use this tool to change the Internet Protocol (IP)
information on a group of servers or workstations without using the user
interface. 

The Netset.exe 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. 

The following is an example of a Netset.exe answer file that you can use
to change the IP address of a client computer. 

[Networking] 
[NetAdapters] 
Adapter01=Params.Adapter01 
[Params.Adapter01] 
InfID=* 
[NetProtocols] 
MS_TCPIP=Params.MS_TCPIP 
[Params.MS_TCPIP] 
AdapterSections=params.TCPIP.Adapter01 
DNS=yes 
DNSSuffixSearchOrder= mycorp.com, <name>.com 
EnableLMHosts=No 
[params.TCPIP.Adapter01] 
SpecificTo=adapter01 
DNSDomain=mycorp.com 
DNSServerSearchOrder=10.10.1.5 
DHCP=no IPAddress=10.10.1.100 
SubnetMask=255.0.0.0 
DefaultGateway=10.10.1.1 
[NetServices] 
MS_Server=params.MS_Server 
[Params.MS_Server] 
optimization=balance 
[NetClients] 
MS_MSClient=Params.MS_MSClient 
[Params.MS_MSClient] 

After you create and save the answer file, run the following command to
apply the settings: 

Netset.exe path_of_answer_file

To remove a component, build an answer file that lists every component
except for the one that you want to remove. This same rule applies when
you add a component. When you build the answer file, you must also
include the network components that are already installed in addition to
the component that you want to add. 
Limitations and restrictions

Warning  If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft cannot guarantee that you can solve problems that result from
using Registry Editor incorrectly. Use Registry Editor at your own risk.

The following restrictions apply when you use Netset.exe:
 
 The following registry subkey must exist for Netset.exe to run
successfully: 

HKEY_LOCAL_MACHINE\System\Setup\AnswerFileMap

If you used an unattended Setup to install Windows 2000, this registry
key is present. If you did not use an unattended Setup to install
Windows 2000, manually create this key. To do this, follow these steps: 

1. Click Start, click Run, type regedt32 in the Open box, and then click
OK.
2. Locate the following registry subkey: HKEY_LOCAL_MACHINE\System\Setup
3. Click Add Key on the Edit menu.
4. Type AnswerFileMap in the Key Name box, leave the Class box blank,
and then click OK.
5. Click Exit on the Registry menu to quit Registry Editor.

If the key does not exist, when you try to start Netset.exe, you receive
the following error message: 

The settings for the network adapter GUID cannot be set 

Note:  GUID is the Globally Unique Identifier (GUID) of the network card
that is installed on the computer. This GUID contains a number that
varies among different computer systems. 

This issue occurs because the Netset.exe utility creates registry
subkeys under the HKEY_LOCAL_MACHINE\System\Setup\AnswerFileMap subkey.
If the AnswerFileMap subkey is not present, the Netset.exe utility stops
responding, and you receive the error message that is discussed earlier.
The AnswerFileMap subkey is only present if an unattended answer file
was used to install Windows 2000. 

If you have already configured computer-specific information in the
network components, for example, a static IP, the Netset.exe tool
removes these configuration settings and replaces them with information
that is listed in the answer file. 
You must have local administrative rights to run Netset.exe or you must
use the Runas utility.

For information about using the Runas utility, see the Windows 2000
Resource Kit.

Note: The Netset.exe tool removes and replaces network configuration
settings instead of merging them with existing installations. 

If you want to change the IP address of a Windows 2003 client or a
Windows 2003 server, you must create a Netset.exe answer file that is
similar to the following example: 

[Networking] 
[NetAdapters] 
Adapter01=Params.Adapter01 
[Params.Adapter01] 
InfID=* [NetProtocols] MS_TCPIP=Params.MS_TCPIP 
[Params.MS_TCPIP] 
AdapterSections=params.TCPIP.Adapter01 
[params.TCPIP.Adapter01] 
SpecificTo=adapter01 
DHCP=no 
IPAddress=10.10.0.100 
SubnetMask=255.0.0.0 
DefaultGateway=10.10.0.2 

However, when you run the Netset.exe tool by using this answer file, a
network configuration is created that only has TCP/IP installed. Any
other services or protocols such as the Server or Workstation service
are removed. When you create answer files to be used with the Netset.exe
tool, you must decide how you want the networking to be configured on
the client after the tool has been run. 
Answer file keys and sections that are used by the Netset.exe tool
The Netset.exe tool uses an answer file format and parameters that are a
subset of the Windows 2003 Setup parameters. These parameters can be
found in the Unattend.doc on the Windows 2003 CD. The following sections
currently are supported by the Netset.exe tool: 

[Identification] 
[Networking] 
[Netadapters] 
; along with all related sub-sections 
[NetProtocols] 
; along with all related sub-sections 
[NetServices] 
; along with all related sub-sections 
[NetClients] 
; along with all related sub-sections 

----------------------

regards,

Rick
-- 
Ulrich Mack
www.commander.com  

 


 

On 2/4/08, Andrew Wood <andrew.wood@xxxxxxxxxxxxxxxx> wrote: 

Hi, 

Has anyone been able to successfully  boot a Compaq G5 to an ADS/WDS
build? 

Every driver I try comes up with a RAMDISK error - I've seen an article
that suggests using specific Broadcom II drivers but I've had no joy
with that either

Tia.

Andrew

Gilwood CS Ltd

Registered Office :  197 Leechmere Road, Sunderland, UK, SR2 9DL. No.
6099397 England
References:

[THIN] Re: PXE Boot to ADS/WDS for Compaq G5s
From: Rick Mack
[THIN] Re: PXE Boot to ADS/WDS for Compaq G5s

Other related posts:
