Skip navigation

JSI Tip 3440. How can I add an OEM NIC to a RIS installation?

When the PXE ( Pre-boot E xecution Environment) client connects to a RIS server and runs the client installation wizard, the NIC is using a Universal Device Interface to communicate. When the installation begins, Windows 2000 Setup switches to SMB, detects the NIC, and loads the appropriate driver. If the OEM .inf file and driver is not available, the client receives:

The network server does not support booting Windows 2000. Setup cannot continue. Press any key to exit.

Check with the manufacturer to determine if the OEM driver is digitally signed, which is likely if a .cat file is included. If the driver is not signed, add the following to the .sif file in the RemoteInstall\Setup\Language\Images\Dir_name\I386\Templates folder:

DriverSigningPolicy = Ignore
NOTE: If the OEM driver is an update of (same name) a Microsoft driver, it must be signed or Setup will use the Microsoft driver.

On the RIS server, copy the OEM .inf and .sys files to the RemoteInstall\Setup\Language\Images\Dir_name\i386 folder.

At the same level as the I386 folder, create a $oem$\$1\Drivers\NIC folder and copy the OEM driver files to the \NIC sub-folder.

NOTE: Inspect the OEM .inf file for a different folder structure. If the manufacturer places the .inf file in a folder and copies the drivers from a sub-folder, create the same folder structure below the \NIC folder.

Edit the .sif file and make the following changes:

OemPreinstall = yes
OemPnpDriversPath = \Drivers\Nic
Open a CMD prompt on the RIS server and type:
net Stop "boot information negotiation layer"
net Start "boot information negotiation layer"
NOTE: The BINL service only reads the NIC related .inf at startup, since it is a time consuming task.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.