This issue can occur if WDS (Windows Deployment Services) is installed incorrectly. Also, this issue can occur if WDS is corrupted. See ME938612
for information on how to solve this problem.
If this error occurs with Intel’s e100bnt5.sys, you need to download Intel’s official fix. See “INF for 10/100 Adapters in Windows XP” to download the fix.
Expanding on Niels Piersma's comment. After upgrading my Windows 2003 RIS server to SP1, my old RIS images for Windows2003 servers did not seem to work. My XP workstations images continued to function. Each time I would attempt to RIS a server image, the server would tell me the appropriate network drivers were not installed. What I believe eventually solved the problem, was that I took all the network associated driver files with extensions of “.sys”, “.cat” and “.dll” and ran the makecab command on them from the command prompt. Example, "makecab e1000325.sys e1000325.sy_".
I then copied all of those files into the i386 directory of the root image. Even though I continued to receive the 1101 warning in the event log, the installation would at least continue. It is also a little easier potentially than going through the “.inf” files to fix the manufacturer sections.
For Broadcom NICs there is an article available under item 79 of the "Broadcom Ethernet NIC FAQ". Under Windows Server 2003 SP1, all three steps must be followed to succeed a complete RIS installation.
I have found a good article about this problem on the Dell forums. Look at "Dell Forums Message ID 3927" for details.
See "Cannot Load PRO/100 or PRO/1000 Network Adapters Using RIS Installation" for information on this event.
This was in relation to installing a Broadcom NetXTreme NIC. The directions given to make ''$oem$\$1\Drivers\NIC'' style directory structures under the i386 folder on the RIS server do not work for some reason. Best guess is that the BINLSVC is not correctly parsing these files because it encounters an error on the “netclass.inf” file from Microsoft (which is logged only once after the BINLSVC service starts).
Simply copying the INF, CAT and SYS files for the Broadcom NIC into the actual i386 distribution directory instead of in the “$oem$” directory structure, then deleting all “.pnf” files from that image and restarting the “GROVELER” and “BINLSVC” services fixed the problem.
I have not gotten this to work with a RIPrep image yet, but at least with a standard CD image and unattended installation text file.
This occurred after installing the P100BETA inf files provided by Intel.However RIS keeps on working fine. When adding E100B support to your RIS image, be sure to delete or rename e100bnt5.sy_ in the I386 directory. Somehow even IF you copied in the new file, Windows 2000 fallsback to e100bnt5.sy_. Remove or renaming it completely forces the installation procedure to use the new e100bnt5.sys.
This error is generated whenever you start an Installation from a RIS server for software that is unofficially supported by Microsoft. In it's original incarnation the RIS system was intended for only pushing Windows 2000 Pro. It can now (Since SP3) push out images of Windows XP as well as 2K server but it does generate this event whenever you trigger an install. The event is harmless and does not affect the RIS push.
When running RIS on Windows 2003 there's a hotfix for this: ME823658
. In my case it didn't help though.
From a newsgroup post:" This error gets generated the first time you attempt to boot from a Ris image. If you have more than one image on your RIS server, you get one for each image that you've tried to boot. As netclass.inf has a .inf extension, I think its looking for a [Manufacturer] section which you'd normally find in a .inf."