Required OSD TS work flawless except one thing:

If PC got error on first PXE-PE loading step (missing network driver or required package) i can`t force that PC to re-run PXE deployment, except redeploying TS on OSD Collection. It always shows me abortpxe message.

Is there any way to automate or better way to handle this situation? Where can i delete information about PXE Boot of "00:21:5A:15:21:EC, 88476A71-3D11-11DD-BBDA-5A1521EC0021" PC

At smspxe.log i see, that no advertisements found for item key: 2046820353 which is "x64 Unknown Computer" account.

<![LOG[Getting boot action for unknown machine: item key: 2046820353]LOG]!><time="14:06:23.259-180" date="02-27-2015" component="SMSPXE" context="" type="1" thread="5168" file="pxehandler.cpp:231">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="14:06:23.368-180" date="02-27-2015" component="SMSPXE" context="" type="1" thread="5168" file="libsmsmessaging.cpp:6544">
<![LOG[00:21:5A:15:21:EC, 88476A71-3D11-11DD-BBDA-5A1521EC0021: no advertisements found]LOG]!><time="14:06:23.369-180" date="02-27-2015" component="SMSPXE" context="" type="1" thread="5168" file="database.cpp:483">

There is a report, MAC - Computers for a specific MAC address.  Use that report to find the computer in question and then search for it in the console to remove it.

Jeff

There is a report, MAC - Computers for a specific MAC address.  Use that report to find the computer in question and then search for it in the console to remove it.

Jeff

fter error on PXEBoot , I found the object "Unknown" and delete it from SCCM using console. At the moment search by MAC does not find anything that corresponds with troublesome PC. It refuses to re-apply PXE-Boot advertisement even after weekend.

That problem is very worries me, because a large number of scheduled baremetal deployments will be done next month and i can`t manage collection every time PC fails PXE-Boot

See if there's a OSD TS deployment for ResourceID 2046820353 available (you might have to add that column to the console firs

As i understand now, there are 4 situations with PXE boot troubleshooting take place in SCCM:

1) PC has an installed agent and has record in SCCM Database and need to be reimaged through PXE. Its name should be found by MAC adress trough report and set to "Clear required PXE Deployments" and THEN deleted from the database.

2) PC PXE OSD fail AFTER Win PE successfull boot. It should be found as computer object with "unknown" name or by MAC. Clear required PXE deployments and delete object from SCCM

3) PC PXE OSD fail during full OS first boot. It should be found as computer object with "MININT-XXXXXXX" name or by MAC. Clear required PXE deployments and delete object from SCCM

4) PXE OSD fail during Windows PE booting. The most misterious case. At this point no object accessible though SCCM console GUI. No log file troubleshooting is possible, log has just fail message without description and cause for an Unknown PC ID. The only thing exists is record in SQL database which was created by the WDS. And this record prevent PC to re-run PXE boot. Record should be deleted from SQL LastPXEAdvertisement table by MAC address.

• Marked as answer by Alexandr Kalachev 14 minutes ago
• Edited by Alexandr Kalachev 10 minutes ago

As i understand now, there are 4 situations with PXE boot troubleshooting take place in SCCM:

1) PC has an installed agent and has record in SCCM Database and need to be reimaged through PXE. Its name should be found by MAC adress trough report and set to "Clear required PXE Deployments" and THEN deleted from the database.

2) PC PXE OSD fail AFTER Win PE successfull boot. It should be found as computer object with "unknown" name or by MAC. Clear required PXE deployments and delete object from SCCM

3) PC PXE OSD fail during full OS first boot. It should be found as computer object with "MININT-XXXXXXX" name or by MAC. Clear required PXE deployments and delete object from SCCM

4) PXE OSD fail during Windows PE booting. The most misterious case. At this point no object accessible though SCCM console GUI. No log file troubleshooting is possible, log has just fail message without description and cause for an Unknown PC ID. The only thing exists is record in SQL database which was created by the WDS. And this record prevent PC to re-run PXE boot. Record should be deleted from SQL LastPXEAdvertisement table by MAC address.

• Marked as answer by Alexandr Kalachev 12 minutes ago
• Edited by Alexandr Kalachev 8 minutes ago

As i understand now, there are 4 situations with PXE boot troubleshooting take place in SCCM:

1) PC has an installed agent and has record in SCCM Database and need to be reimaged through PXE. Its name should be found by MAC adress trough report and set to "Clear required PXE Deployments" and THEN deleted from the database.

2) PC PXE OSD fail AFTER Win PE successfull boot. It should be found as computer object with "unknown" name or by MAC. Clear required PXE deployments and delete object from SCCM console

3) PC PXE OSD fail during full OS first boot. It should be found as computer object with "MININT-XXXXXXX" name or by MAC. Clear required PXE deployments and delete object from SCCM console

4) PXE OSD fail during Windows PE booting. The most misterious case. At this point no object accessible though SCCM console GUI. No log file troubleshooting is possible, log has just fail message without description and cause for an Unknown PC ID. The only thing exists is record in SQL database which was created by the WDS. And this record prevent PC to re-run PXE boot. Record should be deleted from SQL LastPXEAdvertisement table by MAC address.

• Marked as answer by Alexandr Kalachev Monday, July 20, 2015 7:34 AM
• Edited by Alexandr Kalachev 21 hours 42 minutes ago