Upload capture image to WDS - credential window different

[Warchest 0]

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 0]

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 0]

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

[StefanMelocha 0]

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

[Zantec 0]

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 1]

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 0]

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 1]

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 0]

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 1]

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

[Zantec 0]

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 ?

[Zantec 0]

@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 1]

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 0]

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 0]

 

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 0]

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 0]

Thanks for the update.

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

[soadgustavo 0]

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

[Warchest 0]

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

[Tony Corsaro 0]

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 0]

Yep same issue as us Tony.

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

[iuqam 0]

i have resolve the probleme  (setup wds with server 2016)  ->when he ask the username  you must tape if you are in local  the name of the machine were is the wds server with \ and then the username

  ex:  srv_wds\administrator

[Rodd 0]

I'm using 1903 insider and receiving the command window pictured above while using usb recovery..?  Then again I've factory reset this device nearly a dozen times and it is always something new that prevents my utilizing any meaningful function. Code 500 seems to be one most common. To be completely honest, I'm beginning to believe (based on folders of Dev reports) that I'm dealing with hackers within Microsoft proper. Support has provided 0 assistance on any of a number of issues. Moreover attempts to set up 2 step verification go through and are validated, however upon powering on for the next use th password does not work nor is two step verification set up. Tabbing through code in an admin prompt window reveals hundreds of .dll commands I've never heard of. Enterprise level forensics receive access denied in command lines, while find, finger and mrinfo do not exist, are not files... Unfortunately I don't lose, know how to quit, understand what can't is nor value anything above the shared vision I will see brought to fruition.

 

 

[Sizif 0]

Windows 10 pro, version 1909, same problem, no solution. 

[Wanderson Lopes 0]

O que funcionou pra mim foi utilizar o arquivo boot.wim do Windows Server 2012 para realizar a captura, ficou perfeito! 😃