Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
How to Add Third-Party OEM Network Adapters to RIS Installations
Article ID: 246184 - View products that this article applies to.
This article was previously published under Q246184
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
Adding a network adapter that requires an OEM driver to a CD-ROM-based Remote Installation Service (RIS) image involves some of the same steps as adding one to a typical unattended installation. However, because the installation method begins by using Pre-boot Execution Environment (PXE) and then switches over to Server Message Block (SMB), the network adapter driver and .inf file must be available during Text-mode Setup. If they are not available, you receive the following error message:
When a PXE client connects to a RIS server and is running Client Installation Wizard (CIW), the network adapter is using Universal Network Device Interface to talk to the RIS server. When the installation portion begins, Windows Setup switches to SMB, the network adapter is detected, and the appropriate driver is loaded. Therefore, the driver must be available.
The network server does not support booting Windows 2000. Setup cannot continue. Press any key to exit.
NOTE: This article applies only to CD-based images (those created through the use of Risetup.exe). For additional information on how to add third-party party network adapters to Riprep images, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/254078/EN-US/ )How to Add OEM Plug and Play Drivers to Windows Installations
Check with the hardware manufacturer to see if the supplied network adapter driver is digitally signed. (If the drivers from the manufacturer contain a .cat file, it is likely that they have been properly signed.) Drivers signed by Microsoft have been verified and tested to work with Windows. If your driver has not been signed but you still want to use it, make sure to add the following unattended Setup parameter to the .sif file to be used for this image installation:
[Unattended]NOTE: The default name of the .sif file is RemoteInstall\Setup\Language\Images\Dir_name\I386\Templates\Ristndrd.sif
DriverSigningPolicy = Ignore
NOTE: If the OEM driver is an update of an included Windows 2000 driver (for example, has the same name), the file must be signed or Setup uses the included driver instead.