I have successfully PXE booted several machines. The problem is when I PXE boot on machine and it fails for what ever reason I can no longer PXE boot it. Is there a way to get this going? I have the advertisement set to "unknown" computers and set to "always rerun program". Any help is appreciated.Thanks, Mark-

Looks like you are experiencing the default PXE Cache behavior: http://blogs.technet.com/b/configmgrteam/archive/2010/05/27/pxe-cache-expire-behavior-in-configuration-manager-2007-sp1-and-sp2.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Thanks Jason! I m also getting the following when PXE booting. it gets and IP. Downloaded WDSNBP Architecture: x64 The details below show information relating to PXE boot request for this computer. Please provide these details to your WDS admin so this request can be approved. Pending request ID: Contacting server: IP TFTP Download: smsboot\x64\abortpxe.com PXE boot aborted. Booting to next device..Thanks, Mark-

found this is the log: [010.050.000.222:4011] Recv From:[010.002.018.170:68] Len:548 6aac70 smspxe 5/19/2011 10:36:07 AM 2816 (0x0B00) [010.050.000.222:4011] Recv From:[010.002.018.170:68] Len:303 6b6db0 smspxe 5/19/2011 10:36:07 AM 5780 (0x1694) Executing GetBootAction(7326, SERVER) smspxe 5/19/2011 10:36:07 AM 5400 (0x1518) No Boot Action for Device (7326) found smspxe 5/19/2011 10:36:07 AM 5400 (0x1518) ProcessDatabaseReply: No Advertisement found in Db for device smspxe 5/19/2011 10:36:07 AM 5400 (0x1518) The task sequence is pointed to unknown computers collection. I have imported the MAC address and still get the erorr?Thanks, Mark-

Do you have Unknown Computer Support enabled on the PXE Service Point role: http://technet.microsoft.com/en-us/library/cc161877.aspx?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Yes i do. I have allow this PXE service point to respond to incoming PXE requests Enable unknown computer support I also have it password enabled. Interfaces ar set to "respond to PXE requests on all network interfaces". One thing i found but not sure if it matters or not is that my PXE advertisement is using a x86 boot but when i get the error above its showing x64. Do I need to create a different TS and advertise it with x64 boot image?Thanks, Mark-

locate your Unknown Computers collection, expand it and right click on either of the X86 or X64 sub collections, check properties, advertisements, do you see advertisements of your Task Sequence listed ? have you distributed both x86 and x64 boot images to your dps ? it's enough to have an X86 boot image attached to your task sequence, My step by step SCCM Guides I'm on Twitter > ncbrady

Niall, I do see the advertisement on both my x86 and x64 listed. I do both boot images to my dps. I am going to update my x64 to see if that helps.Thanks, Mark-

hi Mark if that doesnt help lfeel free to post the smspxe.log from a recent pxe attempt so I can review it, you can also test creating another ts by duplicating the current one and changing its boot image to the x64 one, then advertise that ts to the unknown computers collection My step by step SCCM Guides I'm on Twitter > ncbrady

Saving Media Variables to "H:\RemoteInstall\SMSTemp\2011.05.19.14.32.11.0001.{34A25AF9-CE1E-4518-B6EF-EEBBE80DBE2D}.boot.var" smspxe 5/19/2011 2:32:11 PM 7780 (0x1E64) [010.050.000.222:4011] Recv From:[010.002.018.190:68] Len:303 10f6370 smspxe 5/19/2011 2:32:25 PM 6608 (0x19D0) MAC=00:07:E9:5D:BE:0E SMBIOS GUID=7D02A8E0-1DE4-11B2-8000-FDEB3EAE2B5C > Device has been accepted. smspxe 5/19/2011 2:32:25 PM 7780 (0x1E64) [010.050.000.222:4011] Recv From:[010.050.000.222:9000] Len:274 fec530 smspxe 5/19/2011 2:35:07 PM 7696 (0x1E10) Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF) smspxe 5/19/2011 2:35:07 PM 7780 (0x1E64) CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 5/19/2011 2:35:07 PM 7780 (0x1E64) MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database. smspxe 5/19/2011 2:35:07 PM 7780 (0x1E64) [010.050.000.222:4011] Recv From:[010.050.000.222:9000] Len:274 ff69b0 smspxe 5/19/2011 2:40:07 PM 7700 (0x1E14) Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF) smspxe 5/19/2011 2:40:07 PM 7780 (0x1E64) CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 5/19/2011 2:40:07 PM 7780 (0x1E64) MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database. smspxe 5/19/2011 2:40:07 PM 7780 (0x1E64) [010.050.000.222:67] Recv From:[010.002.018.251:67] Len:548 10f2bb0 smspxe 5/19/2011 2:42:23 PM 7700 (0x1E14) [010.050.000.222:67] Recv From:[010.002.018.250:67] Len:548 e231b0 smspxe 5/19/2011 2:42:23 PM 7696 (0x1E10) Executing LookupDevice(22752782-AD94-DF11-B9A1-0011D8A46686, 70:71:BC:6C:71:A0) smspxe 5/19/2011 2:42:23 PM 7660 (0x1DEC) Executing LookupDevice(22752782-AD94-DF11-B9A1-0011D8A46686, 70:71:BC:6C:71:A0) smspxe 5/19/2011 2:42:23 PM 7780 (0x1E64) CDatabaseProxy :: LookupDevice succeeded: 7326 1 7326 1 smspxe 5/19/2011 2:42:23 PM 7660 (0x1DEC) MAC=70:71:BC:6C:71:A0 SMBIOS GUID=22752782-AD94-DF11-B9A1-0011D8A46686 > Device found in the database. MacCount=1 GuidCount=1 smspxe 5/19/2011 2:42:23 PM 7660 (0x1DEC) CDatabaseProxy :: LookupDevice succeeded: 7326 1 7326 1 smspxe 5/19/2011 2:42:23 PM 7780 (0x1E64) MAC=70:71:BC:6C:71:A0 SMBIOS GUID=22752782-AD94-DF11-B9A1-0011D8A46686 > Device found in the database. MacCount=1 GuidCount=1 smspxe 5/19/2011 2:42:23 PM 7780 (0x1E64) [010.050.000.222:67] Recv From:[010.002.018.250:67] Len:548 e1bbb0 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) Ignoring req from [010.002.018.250:67] Dest Server:[010.050.000.160] smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) [010.050.000.222:67] Recv From:[010.002.018.251:67] Len:548 e2c2f0 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) Ignoring req from [010.002.018.251:67] Dest Server:[010.050.000.160] smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) [010.050.000.222:4011] Recv From:[010.002.018.170:68] Len:548 11e0db0 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) [010.050.000.222:4011] Recv From:[010.002.018.170:68] Len:303 10ed330 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) Executing GetBootAction(7326, -SCCM) smspxe 5/19/2011 2:42:25 PM 7780 (0x1E64) No Boot Action for Device (7326) found smspxe 5/19/2011 2:42:25 PM 7780 (0x1E64) ProcessDatabaseReply: No Advertisement found in Db for device smspxe 5/19/2011 2:42:25 PM 7780 (0x1E64) [010.050.000.222:4011] Recv From:[010.050.000.222:9000] Len:274 10f08b0 smspxe 5/19/2011 2:45:07 PM 7808 (0x1E80) Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF) smspxe 5/19/2011 2:45:07 PM 7780 (0x1E64) CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 5/19/2011 2:45:07 PM 7780 (0x1E64) MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database. smspxe 5/19/2011 2:45:07 PM 7780 (0x1E64)Thanks, Mark-

here the MAC is known, but no boot action found (so no advertisement found for that computer) MAC=70:71:BC:6C:71:A0 SMBIOS GUID=22752782-AD94-DF11-B9A1-0011D8A46686 > Device found in the database. MacCount=1 GuidCount=1 smspxe 5/19/2011 2:42:23 PM 7780 (0x1E64) [010.050.000.222:67] Recv From:[010.002.018.250:67] Len:548 e1bbb0 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) Ignoring req from [010.002.018.250:67] Dest Server:[010.050.000.160] smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) [010.050.000.222:67] Recv From:[010.002.018.251:67] Len:548 e2c2f0 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) Ignoring req from [010.002.018.251:67] Dest Server:[010.050.000.160] smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) [010.050.000.222:4011] Recv From:[010.002.018.170:68] Len:548 11e0db0 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) [010.050.000.222:4011] Recv From:[010.002.018.170:68] Len:303 10ed330 smspxe 5/19/2011 2:42:25 PM 7696 (0x1E10) Executing GetBootAction(7326, -SCCM) smspxe 5/19/2011 2:42:25 PM 7780 (0x1E64) No Boot Action for Device (7326) found smspxe 5/19/2011 2:42:25 PM 7780 (0x1E64) ProcessDatabaseReply: No Advertisement found in Db for device smspxe 5/19/2011 2:42:25 PM 7780 (0x1E64) looks to me like you have a known system but it isn't in a Deploy 7 (or XP or whatever) collection, so can't see any Deploy task sequence advertisement find out what that device is, and add that computer to a collection with a task sequence advertised to it. then pxe boot it again My step by step SCCM Guides I'm on Twitter > ncbrady

How would i find that machine and either delete it out of the database or move it to the "unknown" computer collection so it can get the advertisement. To my knowledge this machine has never had the agent on it.Thanks, Mark-

create a query on a test collection and filter by MAC address, (network adaptor.) use the mac address I posted and then refresh that collection (update collection membership) you should see a computer appear there, and it's the one you are seeing in that log once you have the computername, add that computername (via direct membership or other means) to your Deploy whatever OS collection, OR delete that computername from the All Systems collection, then reboot the system and it should be unknown, and thus see the unknown computers collection advertisement My step by step SCCM Guides I'm on Twitter > ncbrady

That was it! Thanks for your help! Funny thing is that i do not find that one in the "all systems" container but when i did a query for it by MAC I did in a test collection.Thanks, Mark-

so all is working now ? great :) note that when you import a computer into SCCM that it's not an unknown computer anymore, so you must either import it into a collection with an advertisement (a Deploy collection) or not import it at all and leave it as unknown as long as you have unknown computers support enabled (via R2 or R3) and have an task seuqnece advertised to the Unknown Computers collection cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

Yes all is now working. I figured out that this machine was a rebuild that one of the technicians "faild to mention" so it was previously in the DB with a different name. Thanks for your help again!Thanks, Mark-