PXE, Collection, Advertisement woes... (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

jbenoit -> PXE, Collection, Advertisement woes... (5/9/2008 10:09:32 AM)

I'm completely new to SCCM, so please be kind. I cannot seem to get PXE boot to pick up an Advertised Task Sequence to save my life...

The Client is a Direct Member of the Collection and the Advertisement is clearly listed, and I'm sure that "Make available to PXE" is checked. I have Cleared last PXE Advertisement and completely deleted the Advertisement and created a new one. But everytime I get a PXE Boot Aborted message.

This is all smspxe.log shows when I try PXE boot:
<![LOG[[010.009.003.140:67] Recv From:[010.007.001.001:67] Len:548 a9f5b8]LOG]!><time="09:38:19.109+240" date="05-09-2008" component="smspxe" context="" type="0" thread="2880" file="smspxe.cpp:663">
<![LOG[[010.009.003.140:4011] Recv From:[010.007.022.051:68] Len:548 4312998]LOG]!><time="09:38:23.219+240" date="05-09-2008" component="smspxe" context="" type="0" thread="2888" file="smspxe.cpp:663">
<![LOG[[010.009.003.140:4011] Recv From:[010.007.022.051:68] Len:299 4313aa8]LOG]!><time="09:38:23.376+240" date="05-09-2008" component="smspxe" context="" type="0" thread="2888" file="smspxe.cpp:663">
<![LOG[[010.009.003.140:67] Recv From:[010.007.001.001:67] Len:548 aa06c8]LOG]!><time="09:38:23.376+240" date="05-09-2008" component="smspxe" context="" type="0" thread="2880" file="smspxe.cpp:663">
<![LOG[Ignoring req from [010.007.001.001:67] Dest Server:[010.010.003.012]]LOG]!><time="09:38:23.376+240" date="05-09-2008" component="smspxe" context="" type="0" thread="2880" file="pxeutil.cpp:114">
<![LOG[Executing GetBootAction(11427, CRNMSCCM01)]LOG]!><time="09:38:23.391+240" date="05-09-2008" component="smspxe" context="" type="0" thread="4308" file="database.cpp:512">
<![LOG[No Boot Action for Device found]LOG]!><time="09:38:23.391+240" date="05-09-2008" component="smspxe" context="" type="0" thread="4308" file="database.cpp:528">
<![LOG[ProcessDatabaseReply: No Advertisement found in Db for device]LOG]!><time="09:38:23.391+240" date="05-09-2008" component="smspxe" context="" type="0" thread="4308" file="pxehandler.cpp:487"

Which to my rookie eyes looks like it just doesn't see the Advertisement? What can I try to get it to find it??

I have restarted the SMS_PXE_SERVICE_POINT Component in ConfigMgr Service Manager as well as the WDS Service in Windows of the server.

Any help would be appreciated...



jsandys -> RE: PXE, Collection, Advertisement woes... (5/9/2008 1:21:23 PM)

Is the advertisement mandatory?  If not, try setting it to mandatory.



jbenoit -> RE: PXE, Collection, Advertisement woes... (5/9/2008 1:52:45 PM)

Yes, thanks for the idea. However it is Mandatory - and I even went back in and upped the Priority to High...



jsandys -> RE: PXE, Collection, Advertisement woes... (5/9/2008 2:14:08 PM)

Are you using the pxefilter from the MDT?  How did the system resource get into ConfigMgr?



jbenoit -> RE: PXE, Collection, Advertisement woes... (5/9/2008 2:16:59 PM)

I tried once again sifting through all the choices I had in regard to the Advertisement, and changed the Program Rerun behavior to "Always rerun..." where it had been set to Never by default prior to this.

It now booted to PXE...

However, this was a client PC that had been completely removed from ConfigMgr prior to this and was for all intents and purposes bare metal, and as I mentioned was a completely new Advertisement? So should this really have mattered??



jbenoit -> RE: PXE, Collection, Advertisement woes... (5/9/2008 2:21:40 PM)

Sorry Jason - I was typing my last post while you were posting your question.

I hope you won't laugh at me, but I don't know what MDT is??

Our PXE setup was installed and configured by a consultant who set it up so any unknown client to boot to PXE was created as a resource in our PXE Deployment Collection with it's MAC address as it's name. Therefore, the usual behavior is to boot to PXE once - and it will expectedly abort, but the system will now show up in that Collection. Booting to PXE a 2nd time, it would then pick up the Advertisement assigned. At least, that's how it all worked until my trouble today.



jsandys -> RE: PXE, Collection, Advertisement woes... (5/9/2008 2:30:14 PM)

It sounds like the system resourse was never actually deleted from ConfigMgr DB, maybe it was just removed from the collection or the wrong one got deleted. 

MDT is the Microsoft Deployment Toolkit, the successor to Microsoft Deployment which was the successor to Business Desktop Deployment (BDD).  It integrates with OSD in ConfigMgr and adds some new task types as well as the pxefilter which allows unknow computers to use PXE for OSD.



jbenoit -> RE: PXE, Collection, Advertisement woes... (5/9/2008 2:40:17 PM)

I guess that makes sense, but as part of my troubleshooting, I used a query to search ConfigMgr for that specific MAC and found nothing - UNTIL I tried that first PXE boot at which point it showed up in my PXE Deployment Collection.

Regardless, it's working now and I can move forward, but in the interest of understanding what the heck I'm doing moving forward I wish I was more clear on what happened.

Also, thanks for the MDT explanation. I'm completely new to all Microsoft based deployment products, having just converted over from Altiris. I see or realize that all sorts of things are "integrated" into ConfigMgr, but I'm essentially just sitting in front of the ConfigMgr Console and trying to get PCs deployed, without much understanding what's under the covers!



rjarrett -> RE: PXE, Collection, Advertisement woes... (5/19/2008 9:19:26 AM)

You are not alone...

I am going to forward some "gotchas" that you might want to be familiar with.  Sometimes the client simply fails to image properly, and the only way to check out the client side logs is to enable the F8 command line functionality.  That is a pain.  Furthermore, it is not the recommended configuration for you boot image.  So, here are some "server side" issues that can make PXE failures appear to be "client side" failures.

While not directly related to your issue, as a "newbie" to this product, they may save you a headache or two.

Network Access Account Not Set
Resolution:  Go into the Client Policy in SCCM and set a Network Access Account.  It sometimes "disappears" even after everything has been working fine.
http://www.myitforum.com/forums/m_177370/mpage_1/key_/tm.htm#177370

PXE CERT Not Set
Resolution:  Check the PXE Certificate in the SCCM console.  Verify that the Root CA is trusted.  Alternatively, reset the expiration date.
http://www.myitforum.com/forums/m_177312/mpage_1/key_/tm.htm#177312

GetHostByName Failed
Resolution:  Ensure the FQDN is properly set.
http://www.myitforum.com/forums/m_177318/mpage_1/key_/tm.htm#177318





jjgleason -> RE: PXE, Collection, Advertisement woes... (5/23/2008 8:13:40 AM)

Just an FYI for others, I ran into a few other things to be aware of as well, especially when using MDT and the pxefilter.vbs

1.  When using a mandetory advertistement, you either have to use the Right Click "Clear Last PXE Advertisement" option on the machine or collection or do as jbenoit said and change the rerun behavior.  That caused several head banging incidents when first encountered

2.  It sounds like your consultants setup the MDT integration to handle the unknown machines in a bare metal scenario.  Several ways to check but the easiest is to check for the pxefilter.vbs file on your CM server.  That said, it can be confusing how it works.  Say you just booted a machine and it created the MAC address computer name for you.  Now if you decide you want to delete the record and let it build another or for some reason and you PXE boot expecting it to create the record again it will not.  WDS (Windows Deployment Service - the PXE boot service) caches the MAC address for 60 minutes.  So when you PXE boot it assumes the machine is known and does not run the script to create the object again. 

You can get around that behavior by restarting the WDS service or just waiting the 60 min to PXE boot again




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.296875