Thanks.

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.

I have created a OSD Seq Task to deploy windows 10 1607 english with the de-CH (swiss german locales) according to the guide I found here and deployed this

task by choosing only media and pxe a collection as install - available (because of the collection

When I boot from pxe I dont see this task as an option to install.

If I deploy this task to unknown computers, then the task is appearing to boot pxe

is it probably a setting that I have to do to let it appear in the boot menu.

however, if I import a computer by defining its mac address under devices and adding this computer to the collection OSD German, then the

task appears in the boot menu as well.

any idea why the task is not apearing when deploying it to the specific collectoin but is appearing only when deployed to unknown computers?

Thank you

Chrys

I have a question about WDS logs in Event Viewer;
is there a way to find out which user deleted image from WDS or made any changes to existing image?

I'm looking at "Deployment-services-diagnostics" and have enabled all logs under it, but nothing useful is coming up. 

Capture image was successfully imaged using DISM (.wim file) and deployed it successfully however the restore partition is missing on the deployed PC.

Can I ask for your recommendations please.

For reference please see details:

Windows server 2012 dell

OS (captured image) Windows 10 x64

PC dell micro 7050

I struggled with machines in our company all of a sudden giving "Selected boot image did not authenticate." when doing a F12 PXE boot when secureboot is enabled in the bios. I have done searches on the internet and all of them either suggest to disable secureboot or doing some funny reset on the machine.

The reset didnt work for me and we need to use secureboot for security reasons, so I cannot simply cut off my finger if it has pain.

Stuff I tried that didnt work:
Rebuild the boot images.
Upgrading SCCM from 1610 to 1706
Upgrading ADK from 1610 to 1703 ADK
Upgrading our DHCP server.

What finally fixed it?

Upgrading the affected machines BIOS! That's it! No other upgrade of change nessasary.

Enjoy!

I got PXE boot working but it's taking over 3-5 minutes to load the boot wim file that's 150MB.

My PXE server is on the same gigabit switch as the desktops and is running Windows 2008. At the time it takes to deploy the boot wim file I could have already been half way into deploying the 3.5GB O/S image if I booted up using a CD. It seems to vary on different computers and funny that hte older GX620 are faster in loading the boot WIM faster than the 760 and 745.

Since I never had experience with it before it, what is the normal time it takes to PXE boot a wim file?

Also if I load more than one boot wim like one for production and one as a test for new drivers, does it prompt an option to load or I should only have one on there?

Thanks,

Harvey

I want to make sure I'm jumping down the right rabbit hole.

I've got 8 machines that we use to render and updating the software/changing settings on each machine is a pain.  They all literally have to be the same except for their name.  What I've started doing is installing WDS on our Windows 2012 R2 Server, and then on a VM machine I've set up Windows the way we need the render nodes set up.  The rest of the steps I still have to do.

So now how, without being able to see what's going on, do we get the machines to boot from the network to install these images once I've set it all up?  Is this the right way of doing what I want to do?

Thanks!  Please hold my hand, I make pretty pictures for a living; not IT.

EDIT:  Forgot to mention that I can remote in.  But that's all.  Unless I move them around and connect a monitor to each of them, but I'd rather not have to pull them all off the shelf.

I'm having a problem with WDS, which is why I'm posting here. I mentioned I'd start a new thread about this in another thread as well.

Working with a new system, I want to capture an image to my WDS server. This requires putting the drivers for the NIC into the boot image to allow it to actually work, but for some reason, I can't. If I try and use the wizard, I get 'The request is not supported' and the logs complain about 'It is an unsupported scenario to service an up level image using low level dism.' This led me to believe that there was a version issue somewhere. All updates have been done on the box, and the latest ADK has been installed. Thing is, if I try and use WDS's driver tool, it defaults to the older version of DISM. Is there a way to change the version it uses or to update the version it's pointing to to the latest version?

If I use the DISM located in Program Files (x86)\10\Assessment and Deployment Kit\Deployment Tools\dism, I get Version 10.0.10586.0, but if I use the version located at C:\windows\system32 (the one I suspect WDS uses), I get version 6.3.9600.17031. Simply put, I need to make the old one go away, point WDS to the new one instead, or upgrade the old to the new.

Any suggestions?

Thanks.

Edit 29 July 2016:

Okay, so.

I've been poking around the internet and a few suggestions have been thrown out to change the Path in System Properties. Windows/system32 is still first in line, so for grins and giggles, I put the ADK DISM location in front of that. WDS still runs the older version, from what I can tell. I also renamed and deleted all versions of DISM with the same problem, but that led me to realize that WDS is using WDSUTIL, not DISM. The old version of WDSUTIL installed has almost the same version number as the version of DISM. Now I'm trying to see if there's a way to update WDSUTIL to something newer than 6.

I've tried using the WDS snap-in and the dism command line. It keeps telling me I need a newer version of dism - but I'm using MDT 2013 Update 2.

Any help appreciated

We got systems with a single hard drive (500gb or 1tb) with 2 partitions each (C & D)

Via WDS what we need is:

1. C drive should get fully wiped/formatted during wds
2. The OS should install by default to C drive only without any prompts
3. D drive shouldnt get disturbed, lost or formatted during wds process.

So what exact settings do I need to do in the answer file?