dinci5 Posted September 18, 2015 Report post Posted September 18, 2015 Try this. Create a new device collection, don't bother adding any members or rules just leave it empty. Deploy the task sequence for your legacy machines that uses your normal PXE boot image to the new collection. Now see if your PXE is working again. I will try this today. Thanks for the tip. Quote Share this post Link to post Share on other sites More sharing options...
dinci5 Posted October 2, 2015 Report post Posted October 2, 2015 I have a small update for this issue... As our problem is not yet solved, we know where to look now. The DP, PXE settings and DHCP Options are all OK. I have created a new DP with PXE and changed the DHCP options to point to this DP and placed the DP in the client VLAN rather than the server VLAN (which is behind a firewall). Tested PXE -> All works fine Then we moved the server to the server VLAN where our actual DP resides without changing any settings -> Same problem as before So it's a network problem. I don't know yet what exactly the problem is because our firewall doesn't block or drop anything to the MP and DP servers. I created explicit rules allowing all access just for testing purposes and the log files are showing that all traffic is allowed. So basically what happens during the PXE boot: wdsnbp.com file is downloaded succesfuly. We also see this traffic in our log files. then pxeboot.com also succesfuly. After this, we get the error. The bcd cannot be downloaded but this we don't see in our firewall logs. in Wireshark I can see that \boot\bcd cannot be found... whatever that means. Anybody an idea? Quote Share this post Link to post Share on other sites More sharing options...
uni Posted July 25, 2018 Report post Posted July 25, 2018 (edited) Hi...., any updates?I have a one-on-one problem .... Reinstall DP did not help Edited July 26, 2018 by uni Quote Share this post Link to post Share on other sites More sharing options...