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. SMSPXE.LOG ---------------------------------------------- GetUnknownMachineResource (XYZ,x86): smspxe 3/15/2011 1:39:54 PM 6336 (0x18C0) GetUnknownMachineResource: 0c009c22-712b-4bc1-b067-87c238549704, 6 smspxe 3/15/2011 1:39:54 PM 6336 (0x18C0) GetUnknownMachineResource (XYZ,x64): smspxe 3/15/2011 1:39:54 PM 6336 (0x18C0) GetUnknownMachineResource: c0ad7d74-ab1c-4587-8b90-bd50bf6178d5, 5 smspxe 3/15/2011 1:39:54 PM 6336 (0x18C0) ALL UNKNOWN COMPUTERS COLLECTION ------------- Name Resource Type Domain Site Code Client Resource ID Decommissioned x86 Unknown Computer Unknown System x86 Unknown Computer … No 3 No x64 Unknown Computer Unknown System x64 Unknown Computer … No 4 No x86 Unknown Computer Unknown System x86 Unknown Computer XYZ No 8 No x64 Unknown Computer Unknown System x64 Unknown Computer XYZ No 9 No x86 Unknown Computer Unknown System x86 Unknown Computer … No 1275 No x64 Unknown Computer Unknown System x64 Unknown Computer … No 1276 No x64 Unknown Computer Unknown System x64 Unknown Computer … No 1286 No x86 Unknown Computer Unknown System x86 Unknown Computer … No 1287 No x64 Unknown Computer Unknown System x64 Unknown Computer … No 1657 No x86 Unknown Computer Unknown System x86 Unknown Computer … No 1658 No SQL QUERY OF DBO.UNKNOWNSYSTEM_DISC ----------------- ItemKey DiscArchKey SMS_Unique_Identifier0 Name0 Description0 CPUType0 Creation_Date0 SiteCode0 3 2 c4ebb965-2893-4654-8dba-557d2cd4200a x86 Unknown Computer x86 Unknown Computer x86 55:26.0 … 4 2 dbd25110-d2b6-4502-9097-a3d47ae94875 x64 Unknown Computer x64 Unknown Computer x64 55:27.0 … 8 2 0c009c22-712b-4bc1-b067-87c238549704 x86 Unknown Computer x86 Unknown Computer x86 51:17.0 XYZ 9 2 c0ad7d74-ab1c-4587-8b90-bd50bf6178d5 x64 Unknown Computer x64 Unknown Computer x64 51:18.0 XYZ 1275 2 0c102984-0e71-4c5f-addd-9cec67a71873 x86 Unknown Computer x86 Unknown Computer x86 16:25.0 … 1276 2 42c74a10-ee39-4f82-be8c-8d54aa681080 x64 Unknown Computer x64 Unknown Computer x64 16:25.0 … 1286 2 2995dbbf-2d44-4c43-941a-f6ee2ad536bc x64 Unknown Computer x64 Unknown Computer x64 19:58.0 … 1287 2 b1d310b7-54b6-4e11-82c9-bc7ff1f260fd x86 Unknown Computer x86 Unknown Computer x86 19:58.0 … 1657 2 00073841-521a-45be-afcc-3bb9d02064dd x64 Unknown Computer x64 Unknown Computer x64 30:45.0 … 1658 2 1f964033-0cc2-4822-927b-32c2f087f6ea x86 Unknown Computer x86 Unknown Computer x86 30:45.0 … So where are Resource IDs 5 & 6? TIA - Matt

ADDITONAL INFORMATION FOUND: So if I connect directly to the Child Site, the unknown computer records display the correct 5 and 6 values, however ALL of my child sites share the 5 and 6 values. The information above was taken from the central site. According to the central site, the values are all different, but this is not the case when looking directly at the child site database. Can anyone else with multiple primary child sites with PXE points confirm this? My lab is offline right now.