Jump to content


anyweb

how to get rid of abortpxe.com

Recommended Posts

Something I just noticed is that those affected computers have the same GUID. Could that be part of the problem? From my previous post, does "GuidCount=510" mean that there are 510 objects with the same GUID?

 

I went to the console and deleted the existing object for that MAC address and now all of the computers that had the F12 line missing are showing it and are booting to PXE. I do not get it.

Share this post


Link to post
Share on other sites


I found these two blogs that talk about the same issues i am experiencing. I think they are on the right path but would like to know if any of you have tried the solution they suggest.

 

http://dragos.madarasan.com/tag/guidcount

http://myitforum.com/cs2/blogs/idany/archive/2008/10/22/how-to-enable-osd-with-duplicate-uuid-in-configuration-manager.aspx

 

Thanks.

Share this post


Link to post
Share on other sites

Hi Guys ,

 

I have some what similar problem, My Testvm boots with DHCP and goes till Pending Request ID : ?? Contacting Server : SCCM (IP Address) ......

it does not go ahead. I have assigned a Task Sequence on this collections and i also did what Mr Anyweb Said to Do "Direct" but No luck.

 

smspxe.log file says "Device has been accepted"

 

Thanks

Share this post


Link to post
Share on other sites

Hi Niall

 

I have tried your process. This time it didn't work. I have also deleted the computer in question from "all systems" collection and did a Computer Association import. Still no luck. I also went through the process of "clear Pxe advertisement " etc. I also checked in the "conflicting records " area... No luck.

 

Also FYI, when I carried out your method, I couldn't see two entries for this PC in the collection I was interested in. I had a query based selection for this PC and a direct rule as well. I could see only one entry in the collection. I went through the routine of Update collection and Refresh....

 

For now it's a restart of the server and then WDS .. I think.

 

Thanks in advance for any help.

Share this post


Link to post
Share on other sites

Hi Peter,

 

Thanks for the response. I have set the wds cache timeout to 10 minutes using the registry key we have all been told about. However I found that advertising this TS to unknown computers did the trick. Also I found that the laptop name label had been changed so I was trying to deploy to the wrong machine almost. Once I knew this and then used the unknown computers collection all seemed to fall in to place.

 

It's a jungle, this SCCM is, and with the help of all the good Bloggers and web sites like these i will get there...

 

Many thanks to all who put valuable information out to help each other.

Share this post


Link to post
Share on other sites

Thanks everyone for all the advice, all very useful, but I still couldn't PXE boot my new machine.

 

I checked the SMS PXE Service Point under Site Status and saw the below:

The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned.

 

SMSPXE.log showed: No Boot Action for Device (2119) found

 

I searched for the error and found the below link:

http://blogs.technet.com/b/smsandmom/archive/2008/10/02/configmgr-2007-osd-pxe-booting-fails-with-error-no-boot-action-for-device-x-found.aspx

 

Some clever ... cleared out the boot images

Share this post


Link to post
Share on other sites

Hi, just want to say thanks for the steps listed here....

 

So...I'm trying to figure out *why* this happens. On a test machine that I'd be reimaging, I could select "Clear Last PXE Advertisement" and that would work a few times, then stop, just as detailed here. I did the steps listed above (direct membership rules, finding a duplicate entry listed once I did that, deleting that, etc.)

 

The strange part was once I did that, the test collection I had that one PC in was gone, as was the task sequence advertisement. I had to recreate both. No big deal, but is that normal?

 

And, is this a bug with SCCM 2007, or is more to do with WDS caching as some have mentioned? Is the process any smoother in SCCM 2012?

Share this post


Link to post
Share on other sites

Dear AnyWeb,

 

This post is awesome! It helped me a lot.

 

I just have a bit confusing about PXE booting. All my machines now could boot and run SCCM as normal, but the booting screen is still like below:

 

Downloaded WDSNBP

 

Architecture: x64

 

The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved.

 

Pending Request ID: 45

 

Contacting Server: 192.168.3.1.

TFTP Download: smsboot\x64\abortpxe.com

 

PXE Boot aborted. Booting to next device...

 

I tried to run on x84 Windows 7 platform. Is it anything missing that I need to take care about PXE boot? Thanks you so much!

 

Cheers,

Share this post


Link to post
Share on other sites

  • I signed up for an account just to thank you! I had spent hours trying to clear one of my test imaging machines. This worked perfectly. I have used several of your postings to fix issues. Thanks again!

  • Like 1

Share this post


Link to post
Share on other sites

I encountered this error after not reading the instructions carefully.

 

When creating the task sequence I had gone with the default, instead of selecting "Make available to the following : Configuration Manager clients, media and PXE"

Initially I wasn't even getting to this point as the WDS service had to be restarted after installing automatically and SCCM doesn't make this apparent.

Hopefully I can edit this from work to make it clearer.

Share this post


Link to post
Share on other sites

I am running into same issue with SCCM 2012 . Here is my issue :

 

have created OS image , Boot images and deployed it to all distribution points .

Enabled PXE support and all Unknown computer support on secondary server DP.

Changes Scope options in DHCP to reflect the secondary server values .

Created task sequence to deploy my image to all unknown computers and created optional advertisement . Now the issue is when I PXE boot my computer I can see the communication to my secondary server , As soon as I hit F12 button I got the below message . smsboot\x64\abortpxe.com PXE Boot aborted. Booting to next device... PXE-M0F: Exiting Intel PXE ROM. Operating System not found

I have restarted Windows deployment service in secondary server and reboot the server as well .

The strange thing is if I change the option 66 value in DHCP to primary server it is working pretty well . If I change it back to secondary server the same issue .

SMSPxe.log was not much helpful as I cant see any error message. All I can see is "No Advertisements found " .

I am running SCCM 2012 on server 2012 operating system . Does anyone have any idea on where I should look to resolve this problem or to dig deeper?

Thanks in Advance .

 

Cheers,

Kishore

Share this post


Link to post
Share on other sites

I had a similar issue and stumbled upon this forum. All solutions provided did not help in my case. I have been able to resolve this by adding the BIOS GUID to the computer information when importing. This machine was once added with BIOS GUID info. It seems that when deleting the device from SCCM and then re-adding it with only a MAC address gives exactly this issue:

 

<![LOG[00:21:70:E5:AD:11, 4C4C4544-0038-4410-8033-B1C04F37344A: device is in the database.]LOG]!><time="15:33:56.160-60" date="01-13-2015" component="SMSPXE" context="" type="1" thread="1464" file="database.cpp:483">

<![LOG[00:21:70:E5:AD:11, 4C4C4544-0038-4410-8033-B1C04F37344A: no advertisements found]LOG]!><time="15:33:56.488-60" date="01-13-2015" component="SMSPXE" context="" type="1" thread="1464" file="database.cpp:483">

 

When re-added I see:

 

<![LOG[00:21:70:E5:AD:11, 4C4C4544-0038-4410-8033-B1C04F37344A: device is in the database.]LOG]!><time="15:37:59.485-60" date="01-13-2015" component="SMSPXE" context="" type="1" thread="1464" file="database.cpp:483">

<![LOG[00:21:70:E5:AD:11, 4C4C4544-0038-4410-8033-B1C04F37344A: using advertisement P0020008]LOG]!><time="15:37:59.798-60" date="01-13-2015" component="SMSPXE" context="" type="1" thread="1464" file="database.cpp:483">

 

So clearly this solved my issue.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...