WDS Realtek Drivers failed to import

[bwestlake]

Hi all,

 

Trying to import the Realtek drivers into wds, but it failes no error message just this:

 

 

So can't image the machine...

Not really sure what to do next,

 

Anyone have any ideas?

[Achandler]

Is it the NIC driver?

 

If so the "new" ones are to big for WDS apparently, so they won't import. A problem I have encountered many many times.

 

The solution is to use an older one from 2013 (still universal and still works normally). Windows likes it, uses it and then is able to update it itself.

[bwestlake]

Have tried older drivers but it still comes up with the "a matching network card driver was not found" error...

[ITJS2015]

Try and update you windows boot image to a specific version of what you need as it will have the updated drivers on it

[bwestlake]

Try and update you windows boot image to a specific version of what you need as it will have the updated drivers on it

 

How do I do that?

[ITJS2015]

Open up WDS and where it says boot images right click on the right hand side of the window and click add image

 

It ask you to locate a WIM file so what you need to do is mount an windows 10 ISO to a disk and copy and past the boot.wim which I think is in the resources folder of the windows 10 iso. Copy it to a location on your server and navigate the boot image to the location of the wim file click next and call it windows 10 setup x86 or x64 and it will appear next time you boot into wds

 

If you need to capture a windows 10 image you still need to add the this process in before you can get a capture image setup.

 

Let me know if you need any help

[bwestlake]

Open up WDS and where it says boot images right click on the right hand side of the window and click add image

 

It ask you to locate a WIM file so what you need to do is mount an windows 10 ISO to a disk and copy and past the boot.wim which I think is in the resources folder of the windows 10 iso. Copy it to a location on your server and navigate the boot image to the location of the wim file click next and call it windows 10 setup x86 or x64 and it will appear next time you boot into wds

 

If you need to capture a windows 10 image you still need to add the this process in before you can get a capture image setup.

 

Let me know if you need any help

 

Our current image is windows 7, should this make any difference?

[sted]

Our current image is windows 7, should this make any difference?

 

you will probably find if you use boot.wim from 8.1/10 it will have the network driver built in anyway

[ITJS2015]

It will defo have the latest NIC drivers for the boot image. Your deployment image will never get interrupted at all unless you have unnatend files set in there but just get your windows 10 boot image imports in there first and go from there.

 

It will defo work

[Achandler]

Your importing into WDS to deploy the drivers to the actual image as its created, your error is because the boot.wim can't find a NIC.

 

We haven't had any problems with the 2013 drivers, in fact our new 6th gen boards used the 2013 drivers fine. You need to import the old driver into WDS and then right click your boot wim and add a driver to the actual boot wim not just in WDS. It does a search on the packets you have imported into WDS and you can choose what to add. You use to have to use DISM to do it.

[ITJS2015]

Achandler is correct n his post you can either do it that way or do a new boot image.

 

Just to let you know if you create a new windows image with a higher version of the boot image it will not work

 

I have tried to deploy a windows 10 image x64 with a windows 8 x64 boot image as it came back with an error with offline services trying to install features so iv installed the windows 10 boot image and works great

[sted]

you can use windows 8 to deploy 10 just not the other way round in my experience. So for a long time i had a windows 8.1 boot file (more drivers saved effort) and was deploying windows 7 with no issues try to use a win7 boot image to deploy 8 and it will fail