SCCM SP2 OSD Clear Pxe empty
- Ever since I have upgrade our SCCM to SP2 (either RC or RTM) the Cleat Pxe does not showing anything to be cleared. Once the TS has deployed through pxe, the next time the process is aborted, so ii have to clear the PXE, but the wird thing is that nothing is there, so i continue by clicking OK, and the process of PXE Boot starts again. I have noticed the same ont the LAB and in Production.
Any body ha any clue?
:-)
Answers
I had the same issue awhile back, called Microsoft tech support, they had me build a new box, install PXE there. that fixed it for awhile, now the issue is back. So I built another new machine, added the pxe role and it's fixed again. NOT a good solution; just a workaround that got me going again.
Here's a thought to confirm that it's the same issue that I had:
1. Create a new SQL query in SQL management studio, point it at your SCCM's database.
2.SELECT * FROM system_aux_info where netbios_name0 like 'lt-d800'
substitute lt-d800 with the machine name you're using to PXE boot. If the issue is like mine, you'll see a value for "LastPXEAdvertisementTime" with a valid timestamp of when it PXE booted. The issue is that there is NOT data for "LastPXEAdvertisementID". So if you're issue is like mine, the sql database only has half of a real PXE boot record. A proper PXE service point will have data for both of those feilds after a PXE boot is initiated.
-Ben
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 4:08 AM
All Replies
- are the task sequences optional or mandatory ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 I think you are referencing the Advertisement!! It is Mandatory
:-)- Do you have the advertisement on "always rerun"?
Yes and Not... I have publish an advertisement with alwaya rerun and another with the defalut configuration "Never rerun"
:-)I had the same issue awhile back, called Microsoft tech support, they had me build a new box, install PXE there. that fixed it for awhile, now the issue is back. So I built another new machine, added the pxe role and it's fixed again. NOT a good solution; just a workaround that got me going again.
Here's a thought to confirm that it's the same issue that I had:
1. Create a new SQL query in SQL management studio, point it at your SCCM's database.
2.SELECT * FROM system_aux_info where netbios_name0 like 'lt-d800'
substitute lt-d800 with the machine name you're using to PXE boot. If the issue is like mine, you'll see a value for "LastPXEAdvertisementTime" with a valid timestamp of when it PXE booted. The issue is that there is NOT data for "LastPXEAdvertisementID". So if you're issue is like mine, the sql database only has half of a real PXE boot record. A proper PXE service point will have data for both of those feilds after a PXE boot is initiated.
-Ben
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 4:08 AM
- Peacepenguin,
the defect is the same, but I cannot assure you that the cause is the same.
If you read my post on my blog you'll see how I have resoloved it: http://blogs.technet.com/gastori/archive/2009/11/08/sccm-osd-clear-pxe-advertisement-issue.aspx
:-)
sorry the blog is in Italian so use a Bing translator to read it in English
