Firstly, not my first SCCM rodeo, so we can skip the newbie formalities. Found this post, which gave me some hope, but didn't work for the reasons listed below: http://www.eggheadcafe.com/software/aspnet/33017797/pxe-service-point--unknown-computer.aspx So when restarting WDS, the SMSPXE.LOG shows GetUnknownMachineResource function fires and activates two IDs. Those two Resource IDs in my instance are 5 and 6. When I look at the Resource ID property in the "All Unknown Systems" collection, the two records for the site have IDs of 8 and 9. Hence this is why it isn't working - Which is exactly the situation mentioned in the linked posting. The known workaround for this is to change the query for the "All Unknown Systems" collection to say "Decommissioned = 1" so it will show the obsolete unknown resources. HOWEVER, in this case, the IDs that are being referenced by WDS (5 and 6), do not exist ANYWHERE in the SCCM database. Yes, that's right, they don't exist (if they do, they aren't where they are supposed to be and I can't find them). None of my unknown computer resources are considered obsolete either. This environment is BRAND NEW. So can anyone explain how WDS on my PXE service point is getting a Resource ID and initializing it, when it doesn't exist? For the site in question, there are only two VALID IDs in the SCCM database (8 and 9), and it doesn't load them. Looking for someone to describe how the process works so I can better understand what is broken and how I can fix it. I would like to know where WDS is looking for it's GetUnknownMachineResource information, because it makes no sense that it is magically using imaginary resources. TIA, Matt