Jump to content

Recommended Posts

Posted (edited)

I'm having trouble imaging a batch of Very PC Thinbooks. In WDS I created a capture boot image, loaded the network drivers in to it using DISM and successfully captured an image from the reference laptop and uploaded it to the deployment server. I created another boot image for installing the image and did the same thing by inserting the drivers with DISM. However, when I load into this image I get "a matching network card driver was not found in this image".

 

The device ID of the NIC is PCI\VEN_10EC&DEV_8168&SUBSYS_54551558&REV_12, I have downloaded more drivers for this ID and tried them in the boot image but I still get the same error. As far as I can tell Realtek don't do specific WinPE drivers. I have tried the Windows 7 and Windows 8 drivers included in the driver package from Very PC. I don't understand why the capture boot image worked fine once I inserted the drivers but this boot image won't work.

 

Has anyone got any ideas?

 

EDIT: I put the drivers on a USB stick and loaded them with the DRVLOAD command from within WinPE. I then checked ipconfig and it got an IP address so the drivers obviously work.

Edited by JordanT91
Posted
I've managed to solve the problem. When I was using DISM to insert the drivers to the boot image I was specifying index:1, I have now used index:2 and it worked. I don't know what the difference is though.
  • Thanks 1
Posted
I've managed to solve the problem. When I was using DISM to insert the drivers to the boot image I was specifying index:1, I have now used index:2 and it worked. I don't know what the difference is though.

 

Hi Jordan,

 

Glad to hear you are sorted, I'm no deployment expert but if memory serves me correct (from my limited experience with imagex back in the day), using index specifies which image in the .WIM you are making the change to (I believe), so if things haven't changed that much and your .WIM has multiple images inside, you can inject different content into each.

 

it's been a few years since doing any CLI tasks with deployment, if you have any further issues, please feel free to get in touch with our support team who can escalate to the production team any issues you have with deploying on our kit.

 

Thanks,

 

Ed

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...