Apologies if this is the wrong place to be asking this, I have looked all over and am yet to find a solution.

I have inherrited a WDS / Vista setup that is configured is an x86 deployment image, an x86 cature image and an x64 deployment image. We have recently started getting stock of new x86 Toshiba M10 laptops with NIC drivers that are unsupported on the current x86 image.

My plan is to update the image so that we can start deploying Vista to the new laptops, should be simple.

I have so far:
  1. Exported the current x86 image by right-clicking and selecting "Export image"
  2. Used ImageX to mount the image: “imagex /mountrw E:\RemoteInstall\Boot\x86\images\boot.wim 1 E:\RemoteInstall\Boot\x86\images\mount”
  3. Used peimg to inject the correct NIC Driver (tested on an M10): "peimg /inf=E:\Drivers\M10_LAN\Disk1\e1y6032.INF E:\RemoteInstall\WdsClientUnattend\mount\Windows" - then checked in "Windows\System32\DriverStore\FileRepository\e1y6032.inf_e1d5ac7a" to see that the drivers have been placed successfully.
  4. Unmounted the image: "imagex /unmount E:\RemoteInstall\WdsClientUnattend\mount /commit"
  5. Created a new boot image from this exported image, by right-clicking in "Boot images" in WDS and selecting "Add boot image"

I then start up my M10, PXE boot and select the newly added image. However after the PXE fles load I get error "WdsClient: An error occured while starting networking: a matching network card driver was not found in this image."

I have tried importing all NIC drivers from the setup file I have (just to be sure) and even adding the drivers to the main Vistax86 image. However i'm not getting any joy.

If someone can help, or can point me in the right direction, it would be much appreciated.


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Also, I managed to find this: http://support.microsoft.com/kb/923831 which I thought might help but did not.

There is a RIS_INF folder in the driver setup files which includes this information in the readme:

Microsoft Windows XP and Microsoft* Windows Server* 2003 (32-bit)

1. Create an [IMAGE_ROOT]\$oem$\$1\Drivers\NIC directory if one does not already exist.
2. Copy all files from the PRO1000\Win32 directory to the [IMAGE_ROOT]\$oem$\$1\Drivers\NIC directory.
3. Make the following changes to the .SIF file that is used for this image installation (located in the [IMAGE_ROOT]\I386\Templates directory):
OemPreinstall = yes
OemPnpDriversPath = \Drivers\Nic

4. Copy all .SYS files from PRO1000\Win32 directory to the [IMAGE_ROOT]\i386 directory. Do NOT copy the INF files to this directory.

5. Delete E1000325.PNF, E1E5132.PNF, E1Q5132.PNF, and E1Y5132.PNF (if present) from the [IMAGE_ROOT]\i386 directory.
6. Extract the .INF files from PRO1000\Win32\RIS_INF\E1000325.ZIP, E1E5132.zip, E1Q5132.ZIP, and E1Y5132.ZIP to the [IMAGE_ROOT]\i386 directory.
7. Restart the Remote Installation Service.
8. Follow the rest of the Microsoft instructions for adding a new network driver to the RIS installation.

However from what I can see this is purely for a RIS install. Could there be a similar change to the INF that I should make when using WDS?
Answered 03/20/2009 by: tomanderson
Yellow Belt

Please log in to comment
For anyone interested, I have resolved this issue.

When you boot into the boot.wim without NIC drivers you can press SHIFT + F10 to get to a command prompt. I then navigated to Windows\System32\DriverStore\FileRepository\ and saw that there was no folder "e1y6032.inf_e1d5ac7a"

As per the mount command above “imagex /mountrw E:\RemoteInstall\Boot\x86\images\boot.wim 1 E:\RemoteInstall\Boot\x86\images\mount” I have been mounting the first image in the file. All of my testing was taking place on a second image so I should have typed “imagex /mountrw E:\RemoteInstall\Boot\x86\images\boot.wim 2 E:\RemoteInstall\Boot\x86\images\mount” to mount the second image.

I have now added the drivers to the correct image and tested successfully.
Answered 03/23/2009 by: tomanderson
Yellow Belt

Please log in to comment