PENDING PXE Boot aborted. Booting to next device with reset

[adispy]

Hi,
I'm trying to understand how this works, because the issue is getting annoying and I'm still learning this software, so bear with me.

I am booting from network a client then I reset it once it get's to the Task Sequence screen. Now, instead of booting I get the error message

PXE Boot aborted. Booting to next device...

If I don't reset the client, the deployment continues with no errors whatsoever, but I'm trying to simulate a network or power down issue. Imagine I have a few dozen clients to deploy, they boot and the power goes off, of an error pops-up. What then?

I read a lot of articles on the internet but they don't offer any solutions, so I'm asking someone with experience here that might put a light on this one.

Thanks,
Adrian

 

[Prajwal Desai]

I often test the OSD in my lab and sometimes when my TS fails, I reset the VM and the PXE boot works fine in my case. In your case when you reset the machine, the boot image isn't loaded. I am not sure why that's happening but can you try restarting WDS service and then reset and check ?.

 

[adispy]

Hi,
Thanks for the reply

I have figure out the booting problem, but now I have to figure out how to fix it.
It was not booting because my All Unknown Computers collection was empty. Looks like if it does not have those two default x86 and x64 computer objects in it, the deployments are not working.

I have re-installed my SCCM lab three times (DC, SQL all of it) and every time I still had the All Unknown Computers empty. There is now way to add members since the default collections are grayed out. I have re-installed my lab on server 2016 and 2019, the same problem.
SCCM 1902 ISO was taken from Microsoft's Volume License site, so it's the original one. I have used ADK 1809 and 1903.

Did this happened to you or anyone here after a fresh install? It is getting annoying and frustrating because for an enterprise product, it sure has a lot of bugs.