Windows 10: Boot configuration Data error during PXE boot after add VMware drivers

I have WDS and MDT installed on a Windows Server in my network. The WDS server is on the same subnet as the client machine. I am getting the following error on my VMware VMs when trying to boot LiteTouch over PXE:I can't figure out how to get rid of the error. I've tried:Recreating the LiteTouch boot image in MDT and re-importing it into WDS.Rebooting the WDS/MDT server multiple times.Switching the client VM's adapter type between E1000E and VMXNET3.Deleting and remounting the hard drive on the VM.Any other ideas on what I should do to troubleshoot?

:)

 

PXE Boot configuration in WDS

I would like to set up some computers as "Thin Clients" in that when they boot up they PXE boot to a VM that is set up in Kiosk mode. Is it possible to change the WDS settings to point the PXE booting computers to a VM instead of WDS/MDT?

 

Can't PXE boot

I am trying to find out why some PC's boot and others don't. The ones that don't give me a 53 error, no boot filename received. I can take another PC and plug it into the port that the PC was in that will not boot and that PC will PXE boot. These PC's are different models and the one that doesn't work may be older, but has the PXE option in the BIOS. Could it be that you have to have different boot images on the server? If you do, are these boot images based on the NIC type? If I need to create other boot images how do I create them?

 

PXE BOOT and Defrag

Fog is an awesome utility we used it to image over 200 machine over at place I used to be employed at. You might be able to setup a PXE of hirens boot