The abortpxe.exe response on the screen , indicates to me you are
contacting the sccm server
What version of SCCM? there is a problem with SCCM 2007 SP2 that reset the
PXE Cache to 60 minutes

see
http://britv8.com/sccm-2007-cannot-image-devices-newly-added-using-pxe-boot/

Following on from Randy's post - Entries that have the same MAC address
will cause similar behavior as the PXE server will find the old entry
before it finds the new one. and the old entry is not in the imaging
collection you are using



On Fri, Jul 4, 2014 at 4:03 AM, Atkinson, Matt <[email protected]
> wrote:

>  Is this the MAC of the machine having the problem:
>
> 64:51:06:06:B4:91
>
>
>
> Looks like others are working and finding their optional advertisements. I
> have periodically run in to machines that I couldn’t get to PXE boot for
> some reason that I could never resolve, and for those we always kept a boot
> disc around.
>
>
>
> As suggested by Jason Wallace, you could also try manually importing the
> device MAC address, assigning it to a collection with a TS deployed to it
> and see if it can PXE boot then.
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Brian McDonald
> *Sent:* Thursday, July 03, 2014 8:50 AM
>
> *To:* [email protected]
> *Subject:* RE: [mssms] PXE not working
>
>
>
> Here is the PXE log....Thanks for taking a look!
>  ------------------------------
>
> From: [email protected]
> To: [email protected]
> Subject: RE: [mssms] PXE not working
> Date: Thu, 3 Jul 2014 15:34:02 +0000
>
> Can you post the smspxe.log?
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Brian McDonald
> *Sent:* Thursday, July 03, 2014 8:29 AM
> *To:* [email protected]
> *Subject:* Re: [mssms] PXE not working
>
>
>
> These are bare metal machine right out of the box. No SCCM client.
>
> Sent from my iPhone
>
>
> On Jul 3, 2014, at 10:14 AM, "Atkinson, Matt" <
> [email protected]> wrote:
>
>  For me this has almost always been that the computer is known to SCCM
> and has no task sequence deployed to it. Definitely search for the MAC
> address of the machine.
>
>
>
> If you don’t find it by the MAC address, check the smspxe.log file on the
> PXE enabled DP and it should tell you more about why it isn’t booting.
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Brian McDonald
> *Sent:* Thursday, July 03, 2014 7:06 AM
> *To:* [email protected]
> *Subject:* RE: [mssms] PXE not working
>
>
>
> This is a machine that has never been imaged. This is good info you sent
> though, thanks!
>  ------------------------------
>
> From: [email protected]
> To: [email protected]
> Subject: RE: [mssms] PXE not working
> Date: Thu, 3 Jul 2014 13:29:14 +0000
>
> Make sure the PXE advertisement is cleared (or the device deleted) for
> that MAC address in CM.  The device may have been imaged before, leaving
> the record behind.
>
> If you are having trouble determining whether the device was imaged
> before, run the *MAC – Computers for a specific MAC address* report from
> the *Network* category.
>
>
>
> Randy
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Brian McDonald
> *Sent:* Thursday, July 03, 2014 9:19 AM
> *To:* [email protected]
> *Subject:* [mssms] PXE not working
>
>
>
> Hey everyone,
>
> I'm experiencing a PXE issue fairly consistently. I think we are looking
> at a situation where we don't have every Cisco switch in the building
> configured to allow PXE. I am findings some port work in the primary build
> building, while others don't.
>
> I have attached a screen shot that shows the message I get when I attempt
> to PXE boot.
>
>
>
> <image001.jpg>
>
>
>
>
>
> Can anyone make sense of this? Why does it look like it cannot receive
> policy from the ConfigMgr server? Am I missing a setting on my SCCM server?
>
> Thanks!
> Brian
>
>
>
> FISHER-TITUS MEDICAL CENTER
> Providing Our Community Simply Smarter Care
> Healthcare’s Most Wired Winner, 2012
> Accredited by Healthcare Facilities Accreditation Program (HFAP)
> Primary Stroke Center / Fully Accredited Chest Pain Center/Level 3 Trauma
> Center
> Best Cancer Care, Commission on Cancer Accreditation with Commendation
> Modern Healthcare's Top 100 Best Places to Work in Healthcare in the US
>
> CONFIDENTIALITY STATEMENT: This electronic message contains information
> from Fisher-Titus Medical Center and may be protected health information or
> other confidential and privileged information under law. The information is
> intended to be for the use of the individual or entity named above. If you
> are not the intended recipient, be aware that any disclosure, copying,
> distribution or use of the contents of this message is prohibited. If you
> have received this electronic message in error, please notify the sender
> immediately by reply e-mail or telephone at 419-668-8101.
>
>
>
>
>  ------------------------------
>
>
> This message is intended for the sole use of the addressee, and may
> contain information that is privileged, confidential and exempt from
> disclosure under applicable law. If you are not the addressee you are
> hereby notified that you may not use, copy, disclose, or distribute to
> anyone the message or any information contained in the message. If you have
> received this message in error, please immediately advise the sender by
> reply email and delete this message.
>
>
>
>
>  ------------------------------
>
>
> This message is intended for the sole use of the addressee, and may
> contain information that is privileged, confidential and exempt from
> disclosure under applicable law. If you are not the addressee you are
> hereby notified that you may not use, copy, disclose, or distribute to
> anyone the message or any information contained in the message. If you have
> received this message in error, please immediately advise the sender by
> reply email and delete this message.
>
>
>
> ------------------------------
>
> This message is intended for the sole use of the addressee, and may
> contain information that is privileged, confidential and exempt from
> disclosure under applicable law. If you are not the addressee you are
> hereby notified that you may not use, copy, disclose, or distribute to
> anyone the message or any information contained in the message. If you have
> received this message in error, please immediately advise the sender by
> reply email and delete this message.
>
>



Reply via email to