Injecting Drivers into the WinPe boot image.

[Dave73]

I need to inject a nic driver into the winpe boot image. I tried the following and it failed to resolve my issue.

My server boots into RDP. When i drop a job on the server, it re-boots as per normal. When the server trys to contact RDP again it hangs with a dhcp error. This error points to the drivers for the 361t not being in the boot image.

DL380 Gen 8

361t nic

HP Insight RDP

I launched the bootwiz.exe application.

Picked winpe

On the menu bar their is an option to add a driver to the image. i added the driver. It completed successfully. I restarted all the altiris services. Following the above, my server still errors with the dhcp issue. Is this the correct way to inject a driver ?

I am currecntly updating the RDP software to the latest version as per Shocko's advise.

[shocko]

The simplest way of doing this is to upgrade to the very latest version of Insight Deployment. THere are other ways such as using the PXE configuration tool to rebuild the PE images with additional drivers or simply mounting the .WIM image and injecting them outside of RDP.

[Dave73]

Update to Insight management 7.1 - RDP 6.9 Build517 SP5

Issue resolved :)

Thanks for your advice today Shocko, two thumbs up.

[shocko]

No probs :)

Gald to help. I find that the easiest/quickest way to maintain the drivers in the WinPE image is as follows:

1. Locate the PE images in .\pxeimages\ folder
2. Mount them in 'write' mode using imagex from the WIAK for windows Vista/2008 (not from 2008 R2 as this use WinPE 3.0!!)
3. Using the peimg tool to drivers
4. Unmount the image andcommit the changes

very quick and easy :)

[shocko · Accepted solution]

Dave,

Can you also mark this thread as 'answered' for the sake of the community searches? Thanks in advance :)