Upload capture image to WDS - credential window different

[Warchest]

Hi all,

I have setup my WDS server and it is working well after manually uploading images. Can boot to it, image PCs etc OK.

I would like to automatically upload images to the WDS server via the capture image however I am not getting the usual credential prompt window.

The attached pic shows the cmd prompt window I get when clicking "connect". When entering the username and password nothing happens, it just sits there after pressing enter or selecting Ok.

I can press enter/space on "Remember my credentials" and it adds an 'x' on top of the underscore.

 

Can anyone tell my why I'm getting this cmd prompt window instead of the usual credential pop up?

My Google search has failed me, can't find anyone with the same issue. The NonAppContainerFailedMip message doesn't show any useful results.

WDS server is running Windows Server 2012 R2, it is not the DHCP or DNS server.

[Zantec]

@marcel78 you'r solution doesn't work

 

when I click on CONNECTION from the capture sequence I get an error message : 

 

 

the version of kernel information provided is invalid

[Marcel78]

It worked for me with the customer I had to create a new WIndows 10 WDS capture image for.

WDS was already up and running. Dit nothing special en used a virtual machine to create the capture.

[Zantec]

31 minutes ago, Marcel78 said:

It worked for me with the customer I had to create a new WIndows 10 WDS capture image for.

WDS was already up and running. Dit nothing special en used a virtual machine to create the capture.

with boot.wim windows10? 

I test boot.wim 2012server & get error <<the version of kernel information provided is invalid>>

[Zantec]

 

Hello everyone here is the answer from microsoft support:

 

Hello,
 
We have worked on this problem and we have succeeded in reproducing the behavior you are experiencing. We are still working to find out why this is happening, but it will probably take time.
 
For the moment, as a workaround and not to prevent the deployment of Windows 10, I propose to use the local upload for the .wim image. Do not check the "Upload image to Windows Deployment Services server (optional)" option and save the .wim file to the machine. Then copy the .wim to the WDS server and continue with the deployment.

[Zantec]

it's OK
it works by going through a local backup of the capture before manually copying it to the WDS server.
it does not solve the problem but bypasses it

hope that Microsoft makes a quick fix

[Warchest]

Thanks for the update.

Yes I have been manually uploading to the server as well and it's working fine.

[soadgustavo]

Any news anyone about this issue? Or do we need still upload manually?

[Warchest]

I haven't tried since early December, not sure if Microsoft have updated their ISO yet.

[Tony Corsaro]

Just ran into this issue. My problem is I cant hit the OK button. It just does NOTHING when you try to hit ok. Typical MS OS BS!!!! MS workaround is a total JOKE! Oh yeah just do it manually and copy it. OH THANKS SO MUCH!!!!! How about FIXING the issue MS!!!??? Yes just use an older capture.wim and its works fine...

Edited February 1, 2018 by Tony Corsaro

[Warchest]

Yep same issue as us Tony.

I'm not going to bother trying again until 1803 comes out, hope this will fix the issue.