We help IT Professionals succeed at work.

WDS not working with boot.wim for Proliant DL380 G5 servers WinPE 2.0

hotsox
hotsox asked
on
Medium Priority
2,270 Views
Last Modified: 2012-05-06
I'm trying to PXE boot a HP Proliant DL380 G5 with HP Broadcom NICs to a newly built Windows 2008 WDS server. I've added the images (boot and OS) into the WDS server but when I PXE boot the target Proliant, I get a message telling me the WinPE images I'm using (the boot.wim from the Windows 2008 OS DVD) doesn't containg the correct NIC drivers.

I've viewed http://apcmag.com/how_to_inject_drivers_into_microsofts_free_os_windows_pe_20.htm but have read many posts where others have done this and have still had no postive results.

Could anyone advise a detailed guide as to how to remove the MS NIC drivers from the boot.wim (many others mention this but withhold the method of how they did it) and to add the Q57 Broadcom NIC drivers required for the Proliant servers?

Many thanks,
Comment
Watch Question

I've had problems with broadcom NIC's in Dell Latitudes using WDS. I solved it by downloading the latest vista drivers from broadcom (both x32 and x64) for several products (Netxtreme, Netlink etc), putting all the .inf files into one folder and using the \*.inf option which injects all of them. My 2008 Server is x64 but the clients are x32 so thats why i used both sets of drivers.  

Author

Commented:
Thanks for the information. I've already got the 64 and 32 bit drivers from the latest Proliant Support Pack for the DL380 G5.

Could you expand on how you used the  \*.inf command to inject them into the WIM file?

Thanks

Author

Commented:
I've found a blog with the below commands, is this what you used hhaywood000?

imagex /mountrw wds.WIM 1 mount
peimg /inf=drvs\*.inf mount\Windows
imagex /unmount /commit mount

WDSUTIL /Replace-Image /Image:"Custom WDS WinPE Image x86" /ImageType:Boot /Architecture:x86 /ReplacementImage /ImageFile:wds.wim
Yep, I manually replaced the boot.wim using the console rather than the command line - its the same actions though. Have you got the latest drivers from Broadcom rather than HP? thats the problem I was having as I used the original Dell ones. They were fine when using the OS but for network booting the newer ones were needed.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
I'll do as you suggest and grab the OEM ones and try again but can you tell me how you do it from the console as I've injected the drivers (from HP) into the boot wim now via the command line and would like to see both sides of how to do this?

Many thanks
Sorry I wasn't clear. I used peimg at the command line to inject the drivers (i think this is the only way possible).

I then opened the WDS console and manually replaced the boot.wim (right click replace) with the updated version.

Like I said get the latest drivers direct from broadcom http://www.broadcom.com/support/ethernet_nic/downloaddrivers.php *not* the HP/OEm ones. Make sure you get both 32 and 64 bit.

Author

Commented:
Good stuff, got the special RIS drivers as you predicted and they work fine and I'm now able to deploy the default builds taken from the 2008 x64 and 32bit DVDs.  Thank you very much for the information. Ill be selecting that as the solution but just have one more question but can one distribute already built and prepared images via WDS, I mean something like a built OS with applications installed then sysprepped and then stored on the WDS servers most likely if its possible as a WIM file so I dont have to also install a scripted build as seems the case with WIM images from the Windows 2008 Server DVD? Hope I make sense.

I believe Ive read it can but just asking as the images Ive deployed today appear to build as scripted installs not like image installs ala Ghost or Altiris.

Thx again,
Yes thats exactly what WDS is for.
Do a vanilla install using the install.wim you got from the CD/DVD.
Install drivers, apps and customise etc.
Create a Capture image (right click boot image and create capture) on the WDS server
sysprep customised machine, pxe boot, select the capture image you just created and voila!

For a more detailed explaination see http://technet.microsoft.com/en-us/library/cc766320.aspx
Also take a look at MDT2008 http://www.microsoft.com/downloads/details.aspx?familyid=3bd8561f-77ac-4400-a0c1-fe871c461a89&displaylang=en as it expands the capability of WDS by allowing you to integrate drivers, apps etc

Author

Commented:
Only wish I could offer more points. Many thanks indeed...
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.