WDS 2012 can't deploy Windows 10

[Sheridan]

We're running WDS on 2012 to deploy Win7 which has worked fine for a while. We've created a base image of 10 and captured it to the WDS server. The only thing is no matter what we try and deploy it to (physical or virtual pc) it crashes out with an error at the 'Installing devices' stage.

 

The setuperr.log contains this:

 

[0x0b003e] WDS QueryAdapterStatus: no adapters found.

 

Followed by a lot of these:

 

[0x0b003a] WDS [gle=0x0000276d]

 

But thats it, no real as to what the problem is. I'm not sure what adapter its missing as the drivers for the network cards are injected into the image?

[Smed]

what version is your boot image?

[Steve21]

You put the NIC drivers into the boot image too?

 

Steve

[Sheridan]

Boot image is latest Windows 10 LTSB from the VLSC site. Drivers are injected into the boot image as far as we can tell - i.e the drivers we use are what was on the original image. The only thing is that the original image was created as a VM.

[Steve21]

Boot Image as in the PE environment, rather than your actual Win10 Image? (Just clarifying from your first sentence)

 

Steve

[DJ-1701]

If you haven't got the latest Windows PE image for WDS to use, it can be obtained from the Windows ADK here https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx#adkwin10

[Sheridan]

We created the Install (boot) and Capture images from the Windows 10 boot.wim. I haven't updated the ADK yet as we're not doing anything with the images apart from capturing them and deploying them (for the time being anyway)

[Steve21]

Not sure if i'm misunderstanding, but you're talking about a different image to what I mean.

 

You have your boot image (PE), your install image, (and then a capture if you're doing that).

 

Your boot image isn't the one you're deploying to your machines but the PE environment that does the deployment etc.

 

So if you're having problems with drivers and only have the NIC drivers in one of the two images (boot/install) it might be linked to that

 

Steve

[Sheridan]

Sorry yes, its my Friday keyboard!

 

We've got the drivers in the boot image and the capture and install images. I've just checked and the ADK is already the latets version (I updated that last year and must have forgotten I'd done it!)

 

It seems to be an issue with the fact the image is from a VM on virtualbox.

[Sheridan]

This is bugging me now. Tried various VMs/hardware and can capture any version of 10 absolutely fine. But as soon as we try to deploy it (back to the same hardware or VM) it stops at 42% and then crashes out.

 

We've got no chance of even a test deployment of 10 at this rate, its like an ongoing battle to fix the problems!

[JohnnyO]

Hi Sheridan, did you ever get to the bottom of this Win 10 deployment domain issue? I'm having the same thing right now...

 

cheers!