WINPE issues with PXE
I know I am missing something I get it to Load NBP file then it fails with Boot configuration data for your PC is missing or Contains errors. I have merged the tfpboot per the instructions. But could not get the image to load. I don't think I got the right file for the BCD. I am trying to find the correct file that is made with the wie_builder. I have the ISOs that work and everything else but I am just missing the BCD
This was a bug and is fixed in the latest download.
that working fine now - thanks.
I used the old bcd-files from clonedeploy and thought that that leads to the problem I'm facing. Now with the new built files still the same error: "Could Not Contact Theopenem Com Server". I guess Com Server isn't working correct. I can't access the clientimaging/test folder (404). IP-Address and Drivers should be alright.
Is there any way to check the com server? We've installed und configured by tutorial. rest is working fine.
Did you run this test?
it's correctly showing "60".
but I found the mistake in that moment. in the ToemsPE-Build.cmd ComServerURL was set to http://servername instead of http://servername:8888
Thanks again for fast help.
I'm confused. It worked for a while and could make an Image.
Now this error appears again and again "Could Not Contact Theopenem Com Server".
- DHCP/IP working
- http://servername/clientimaging/test showing "true"
- We use different HP notebooks. all of them got realtek ethernet network card. I put the *.inf files from the driver in the Optional\Drivers\WinPE 10 x64 folder and built the PE again. merged the tftpfolder with that one on the server.
am I missing something? what's going wrong here?
Is this limited to a specific model, or is it not working on computers that did work already?
no. there are diffrent models with the same issue.
I'm now pretty sure it has something to do with the network configuration. pxe server is in another subnet/vlan than clients. I did a test with a client in the same server vlan and it worked all the time.
I tried setting an ip-helper but that didn't solve it. I'm digging deeper since the issue has to be in the network imo.
if you have any experience or tips that would be much appreciated.