I use pxe-boot and a windows 2003 ris server to push out a windows pe image. But it's not working as it's supposed to do.
I boot the machine (tried several poweredge servers, 2550 and 2650 with broadcom NetExtreme nic's) with the pxe. The Ris server replies, and I log on and going through all the CIW's. When the PE image starts to load it suddenly hangs. It first says starting windows pe, and then it says please wait. There are no errormessages on the screen, like could not find nic drivers, winbom.ini could not find the correct drivers for the nic etc. The eventlog on the RIS server says something, but I can't find out what it means: "an error occurred during parsing of an INF file netclass.inf in the given section Manufacturer".
I have downloaded the latest drivers from Broadcom (the winxp/2003 drivers), but with no further luck.
The strange thing is that if I boot the machine on a CD, with the exact same PE image which RIS uses everything seems to work just fine.
If I use a different computer (like av Dell GX270) with the same PE image, everything seems to work.
Have anyone discovered the same problems? And have anyone a solution to this?
In order to get the Powerstation340 ( same nic) to RIS XP we had to modify the inf file ( with help from MS PSS) and create an OEM driver instance due to error in the broadcom b57xp32.inf. Possibly the same file could be "helping you" as well.
Unfortuneatly I can not post the INF file here as it is to big. If you Private Post me your real email address i can send you a zip of the driver file for RIS usage if you like. Or you can contact MS PSS services and they can get you one that works but thata $$$
You have to follow the MS knowledge base links, and make sure that everything is set up exactly - make sure that the paths specified in the .sif files are all valid, and in quotes, for example.
It's a real pain in the buttocks, and took me the better part of a day to get working, but I'm currently typing this on a D600 image that I just RIS-ed.
If any Dell techs are reading this, they may want to write up a how-to, to alleviate the pain and suffering of so many D600 users. I'll send a note to Broadcom and Microsoft about the fix.
DotNetShannon
4 Posts
569
0
Posted February 9th, 2004 13:00
Try check your network medium (i.e. cabling/switch). That solved my problem.