Dell PowerEdge 2970 - Manual (Page 9)

Dell Enterprise Server Windows Installation Best Practices with Broadcom NetXtreme Devices
Joining a domain can be accomplished using netset.exe in either manner listed above by
specifying the domain to join in the normal answer file manner.
Example:
[Identification]
JoinDomain = MyDomain
A VBScript can be used to determine if NetXtreme II adapters are present before running
netset.exe if netset is run from with in a script in either SetupParams or cmdlines.txt,
thus allowing one answer file template for systems with NetXtreme II adapters and
systems without them. See Appendix E for an example script.
6. NetXtreme II WinPE Considerations
Due to the unique architecture and new technology of the Broadcom NetXtreme II drivers,
there are some new process considerations when using the NX2 devices and drivers in
conjunction with WinPE.
When building a WinPE image, the following must be considered:
• The “/PnP” switch must be specified in order for the NetXtreme II driver to load.
•
The DRVINST utility must be used to inject the NetXtreme II drivers. Copying the files
to the various directories will not work.
• Only the “–winpe” switch for factory.exe works with the VBD and NDIS Client
NetXtreme II drivers. A simplistic NDIS driver for RIS use is provided on the Dell
support web site that works with the “–minint” switch. See Section 7 for more
information on the RIS specific driver.
7. PXE, RIS, and ADS
7.1. ADS
A simplistic NDIS driver must be used for initial network connectivity during the copy
portion of the install. This driver resides in the RIS directory within the standard
NetXtreme II driver package. This driver should be added to the Presystem directory as
any other driver would be added. This driver is not sufficient, nor will it install in a fully
installed operating system. This driver is only for use during operating system deployment
and installation; the normal VBD and NDIS client combination of drivers must be used for
all other instances.
It is advised that static network settings should be set according to the method described
in the ADS documentation under the heading “Image Deployment and IP Address
Configuration”. This method uses the “SetStaticIP” VBScript in conjunction with the set-
static-ip.xml sequence file.
If the ADS deployment solution incorporates custom variables in the sysprep.inf file for
the various network settings using PCIBusNumber, PCIDeviceNumber, and
PCIFunctionNumber as adapter identifiers, the solution must be changed to use the
methods described in the sections above.
Page 9