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.

[StefanMelocha]

I am having the same problem. Yours is the only post I have found that details the same error.

I am running Server 2016 and attempting an Image Capture of a Windows 10 Pro desktop (version 1709).

Have you had any luck finding a solution to the problem?

 

[Warchest]

No solution yet unfortunately, hopefully someone will see this and know what it is.

[StefanMelocha]

I will let you know if I come up with anything.

[Zantec]

we encounter the same problem
with server 2012 r2 & w10 1709 (and 1703 ...)

We contacted Microsoft support ...
I'm at the 3rd rack scaled at the support without solution for the moment

 

(sorry for my english, i'm french)

Edited December 12, 2017 by Zantec

[Marcel78]

Same problem when I use the 10.0.16299 OS version (shipped with WIndows 10 Update 1709 DVD). No problems when I use the older 6.3.9600 OS version boot.wim.
Think Microsoft has changed something in the boot file causing this problem

[Warchest]

Thanks all for the replies,

Should have added the Windows version I was trying to upload.

Looks like we are all in the same boat - I am also trying to use a sysprepped 1709 (Win 10 Creators Fall).

I wonder if this will ever be fixed.

[Marcel78]

Just use the old boot file. Works like a charm. If MS is going to fix it, it will be in the next major update in March.

[Zantec]

4 minutes ago, Marcel78 said:

Just use the old boot file. Works like a charm. If MS is going to fix it, it will be in the next major update in March.

it's possible to take me more info please

[Marcel78]

If you use the boot.wim file from an older Windows 10 or Windows Server 2012 R2 DVD, you should have no problems.

[Zantec]

3 hours ago, Marcel78 said:

If you use the boot.wim file from an older Windows 10 or Windows Server 2012 R2 DVD, you should have no problems.

 I take boot.wim server2012r2, 

launch sysprep & boot pxe : contact with server wds isn't possible

 

I added the network driver on my wds

I restart the capture process on the pc

I do not get the "start" page of the capture menu

hp probook 650G2 laptop pc network drivers
I tested drivers windows10 & windows8 ...

 

an idea ?